[Sip] Service route discovery draft revised

"Dean Willis" <dwillis@dynamicsoft.com> Wed, 14 May 2003 01:09 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 VAA05901 for <sip-archive@odin.ietf.org>; Tue, 13 May 2003 21:09:25 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4E0Zg113806 for sip-archive@odin.ietf.org; Tue, 13 May 2003 20:35:42 -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 h4E0ZLB13766; Tue, 13 May 2003 20:35:21 -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 h4E0YuB13725 for <sip@optimus.ietf.org>; Tue, 13 May 2003 20:34:56 -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 VAA05847 for <sip@ietf.org>; Tue, 13 May 2003 21:08:09 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19FkmT-0001HP-00 for sip@ietf.org; Tue, 13 May 2003 21:10:05 -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 19FkmS-0001HF-00 for sip@ietf.org; Tue, 13 May 2003 21:10:04 -0400
Received: from txdwillis ([63.206.46.200]) (authenticated bits=0) by bdsl.greycouncil.com (8.12.8/8.12.8) with ESMTP id h4E1AY6n006987 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 13 May 2003 20:10:37 -0500
From: Dean Willis <dwillis@dynamicsoft.com>
To: sip@ietf.org
Cc: mankin@psg.com
Date: Tue, 13 May 2003 20:10:08 -0500
Message-ID: <000c01c319b5$958b5fa0$06f30a0a@txdwillis>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
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: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h4E0YuB13726
Subject: [Sip] Service route discovery draft revised
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: 8bit

Bernie and I revised the Service Route Discovery draft to align with the
current policy on example domain-name usage as requested by the AD. I also
added a small clarifier to the applicability statement as recently requested
on-list. This clarifier is "The service route constructed by the registrar
is the same for all contacts associated with a single address-of-record.
This mechanism does not provide for contact-specific service routes."

The draft has been submitted to internet-drafts, and in the interim is
available from:

http://www.softarmor.com/sipwg/drafts/draft-ietf-sip-scvrtdisco-04.html
http://www.softarmor.com/sipwg/drafts/draft-ietf-sip-scvrtdisco-04.txt
http://www.softarmor.com/sipwg/drafts/draft-ietf-sip-scvrtdisco-04.xml


Note that this draft is in state "IESG Evalution -- AD Followup" according
to the Draft Tracker.

Barring having done something stupid in the processing of the changes (and
given the Blessing of the AD), I believe we're ready to proceed with this
draft. If I understand the process correctly, AD/IESG review the changes as
requested, and if acceptable the doc goes to the RFC editor.

--
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