In addition to what has been indicated, the design team discussed this in mid-2007. Now, the UA either sends the SIP SUBSCRIBE request via configured outbound proxies (if available) or via 3263. In the case of the latter, the FQDN in the SIP URI (sip:_sipuaconfig.<domain name>) is used to determine the next-hop proxy. We debated whether to use 'sipuaconfig' or '_sipuaconfig'. There was a concern that there would be considerable pushback if we ask that no-one use the name sipuaconfig for a host name in any domain - or if they do use it, they can expect to get random requests hitting their box. Hence the suggestion was to use _sipuaconfig. We contacted the DNS experts and did not get any objections. However, we failed to see that this would break the URI (as Geir indicated, correctly). I will let the design team pitch in with any additional details. - S -----Original Message----- From: sipping-bounces@xxxxxxxx [mailto:sipping-bounces@xxxxxxxx] On Behalf Of Robert Sparks Sent: Wednesday, December 10, 2008 10:01 AM To: Geir Arne Sandbakken Cc: sipping@xxxxxxxx Subject: Re: SIP Configuration Framework uses underscore in SIP URI Geir is correct that _ can't appear bare in the hostname part of a SIP URI. It can appear %-escaped. Is that what the profile should be using? RjS On Dec 2, 2008, at 9:32 AM, Geir Arne Sandbakken wrote: > The Local-Network profile in the framework requires "_sipuaconfig" > concatenated with the local network domain to be used as the host part > of the Request URI. > > Our SIP stack does not view this as valid SIP URI, and rejects the > message. AFAICC RFC 3261 seems to agree with our parser. > > IMHO, using underscores in DNS host for finding services related names > in DNS queries is one thing. Changing the grammar of a SIP URI > potentially breaking parsers is quite another matter. > > Geir Arne > _______________________________________________ > Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping > This list is for NEW development of the application of SIP > Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip > Use sip@xxxxxxxx for new developments of core SIP _______________________________________________ Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip Use sip@xxxxxxxx for new developments of core SIP _______________________________________________ Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip Use sip@xxxxxxxx for new developments of core SIP
