Re: [Sip] draft-lee-sip-dns-sd-uri-00 - SIP URI Service Discovery using DNS-SD

Dale.Worley@comcast.net Fri, 09 March 2007 09:26 UTC

Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HPbMa-0001WL-0l; Fri, 09 Mar 2007 04:26:12 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HPWKS-0004Pw-7S for sip@ietf.org; Thu, 08 Mar 2007 23:03:40 -0500
Received: from rwcrmhc13.comcast.net ([204.127.192.83]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HPWKP-00077E-Ut for sip@ietf.org; Thu, 08 Mar 2007 23:03:40 -0500
Received: from dragon.ariadne.com (dworley.hsd1.ma.comcast.net[24.34.79.42]) by comcast.net (rwcrmhc13) with ESMTP id <20070309040324m13007ge9ee>; Fri, 9 Mar 2007 04:03:34 +0000
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1]) by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id l2943NtB015980 for <sip@ietf.org>; Thu, 8 Mar 2007 23:03:23 -0500
Received: (from worley@localhost) by dragon.ariadne.com (8.12.8/8.12.8/Submit) id l2943NUR015976; Thu, 8 Mar 2007 23:03:23 -0500
Date: Thu, 08 Mar 2007 23:03:23 -0500
Message-Id: <200703090403.l2943NUR015976@dragon.ariadne.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <20C3595B-9392-477C-BF6F-F246F67CBD1D@cs.columbia.edu> (jae@cs.columbia.edu)
Subject: Re: [Sip] draft-lee-sip-dns-sd-uri-00 - SIP URI Service Discovery using DNS-SD
References: <200703061607.l26G7UID032011@dragon.ariadne.com> <20C3595B-9392-477C-BF6F-F246F67CBD1D@cs.columbia.edu>
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Errors-To: sip-bounces@ietf.org

   From: Jae Woo Lee <jae@cs.columbia.edu>

   > 5.2.  Request Destination
   >
   > It seems to me that this could be both simplified and corrected by
   > just saying that if a "contact" attribute is available, it should be
   > used as the request-URI of any out-of-dialog SIP request.  Since this
   > definition automatically refers to RFC 3263, it allows a lot of
   > generality while behaving correctly in various special cases.
   >

   We specify in Section 5.1 that the Request-URI must be set from the  
   SIP URI from the service instance name (which SHOULD be AOR.)  We  
   look at the contact attribute to determine where to send the  
   request.  We felt that this is natural since the Request-URI then  
   reflects the logical recipient who advertised the service.

I'd suggest that you change this so that the SIP URI from the service
instance name is the To value, and the URI part of the contact becomes
the request-URI.  This gives DNS SD the same redirection power as a
proxy/registrar.  It also allows you to not have to specify how the
contact value is to be interpreted, because you inherit all the rules
of RFC 3263 automatically.

Dale

_______________________________________________
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