[Sip] Question on Service Route Discovery draft and multiple contacts per AoR

"Dean Willis" <dwillis@dynamicsoft.com> Mon, 14 April 2003 18:52 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16094 for <sip-archive@odin.ietf.org>; Mon, 14 Apr 2003 14:52:00 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h3EIxjH13912 for sip-archive@odin.ietf.org; Mon, 14 Apr 2003 14:59:45 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3EIx9813890; Mon, 14 Apr 2003 14:59:09 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3EIqY813695 for <sip@optimus.ietf.org>; Mon, 14 Apr 2003 14:52:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15878 for <sip@ietf.org>; Mon, 14 Apr 2003 14:44:19 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.12) id 1958yh-0004E1-00 for sip@ietf.org; Mon, 14 Apr 2003 14:46:51 -0400
Received: from bdsl.66.12.12.130.gte.net ([66.12.12.130] helo=bdsl.greycouncil.com) by ietf-mx with esmtp (Exim 4.12) id 1958yg-0004Dr-00 for sip@ietf.org; Mon, 14 Apr 2003 14:46:50 -0400
Received: from txdwillis ([216.229.166.130]) (authenticated bits=0) by bdsl.greycouncil.com (8.12.8/8.12.8) with ESMTP id h3EIjQIH002709 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for <sip@ietf.org>; Mon, 14 Apr 2003 13:46:24 -0500
From: Dean Willis <dwillis@dynamicsoft.com>
To: sip@ietf.org
Date: Mon, 14 Apr 2003 13:44:31 -0500
Message-ID: <003301c302b6$08e9f680$40f30a0a@txdwillis>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Content-Transfer-Encoding: 7bit
Subject: [Sip] Question on Service Route Discovery draft and multiple contacts per AoR
Sender: sip-admin@ietf.org
Errors-To: sip-admin@ietf.org
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Id: Session Initiation Protocol <sip.ietf.org>
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>
Content-Transfer-Encoding: 7bit


The current text in draft-ietf-sip-scvrtdisco-03.txt says, in "6.3
Procedures at the Registrar":

   A REGISTER operation performing a Fetching Bindings (i.e.  no Contact
   header field is present in the request) SHOULD return the same value
   of Service-Route as returned in the corresponding previous REGISTER
   response for the address-of-record in question.  In some cases, the
   Service-Route may be dynamically calculated by the registrar rather
   than stored, and the decision as to whether this route should be
   recalculated in the event of a Fetching Bindings operation is left to
   the implementation.


Ben Jenkins pointed out to me that this may be unclear in cases where there
are multiple contacts registered for a specific AoR.

We do not state explicitly that the Service Route is common to all contacts
for the AoR. Is it really? Do we need to add anything here for clarity?

--
Dean

_______________________________________________
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