Re: [Sip] submission of a new I-D: "Dialog Event foRIdentityVErification"

["Dan Wing" <dwing at cisco.com>]

> -----Original Message-----
> From: sip-bounces at ietf.org [mailto:sip-bounces at ietf.org] On 
> Behalf Of Iñaki Baz Castillo
> Sent: Tuesday, October 28, 2008 4:44 AM
> Cc: sip at ietf.org
> Subject: Re: [Sip] submission of a new I-D: "Dialog Event 
> foRIdentityVErification"
> 
> 2008/10/28 Dan Wing <dwing at cisco.com>:
> > Here is another return routability check,
> > http://tools.ietf.org/html/draft-wing-sip-e164-rrc-01#section-3.1
> > (My I-D expired due to lack of interest.)
> 
> It uses RFC 4474, certificates... is it really feasible in 
> this real world?

No, it doesn't use RFC4474.  The steps merely show where an RFC4474 
signature could be performed.  If no RFC4474 signatures are
being created, or validated, those steps are the 'null operation'
(not performed).  Without those steps, it is remarkably similar
to DERIVE.

> IMHO "Dialog Event foR Identity VErification" is the more feasible
> solution at the moment.

The differences are minor.

-d


> 
> 
> -- 
> Iñaki Baz Castillo
> <ibc at aliax.net>
> _______________________________________________
> Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors at cs.columbia.edu for questions on current sip
> Use sipping at ietf.org for new developments on the application of sip

_______________________________________________
Sip mailing list  https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip