[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Sip] note: change in URI comparison rules coming
Good.
Well while we're at it can I suggest we remove all default values from
SIP URIs. My reasoning would be, port and transport seemed the least
arbitrary. The user parameter has consistently been abused; the method
parameter defaulting to INVITE doesn't seem so convincing in these
SIMPLEr times; ttl does this really justify a default parameter, if you
insist on using multicast you should do it properly with some thought.
This also results in a far simpler comparison rule, that's easy to grasp
and apply.
James
> -----Original Message-----
> From: Robert Sparks [mailto:rsparks@dynamicsoft.com]
> Sent: 14 February 2002 22:35
> To: James Undery
> Cc: Jonathan Rosenberg; sip@ietf.org
> Subject: Re: [Sip] note: change in URI comparison rules coming
>
>
> The current proposal is no.
>
> Those two URLs will resolve to the same host/port/transport, but
> making the URLs equivalent will require separate equality rules
> for when the hostpart is an IPv4 address vs a DNS name.
>
> RjS
>
>
> James Undery wrote:
>
> > Is sip:10.0.0.1 == sip:10.0.0.1;transport=udp still going to hold?
> >
> > James
> >
> >
> >>-----Original Message-----
> >>From: Robert Sparks [mailto:rsparks@dynamicsoft.com]
> >>Sent: 14 February 2002 15:32
> >>To: Jonathan Rosenberg
> >>Cc: sip@ietf.org
> >>Subject: Re: [Sip] note: change in URI comparison rules coming
> >>
> >>
> >>The same argument applies to the transport parameter
> >>sip:user@domain;transport=udp will always resolve to udp,
> >>but
> >>sip:user@domain may resolve to tcp through DNS.
> >>
> >>The next version of bis will reflect
> >>
> >>sip:user@domain:5060 != sip:user@domain !=
> >>sip:user@domain;transport=udp
> >>
> >>
> >>RjS
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip