RE: [Sip] comments on draft-gurbani-sip-ipv6-abnf-fix-00

"Brett Tate" <brett@broadsoft.com> Wed, 05 December 2007 17:49 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 1IzyNQ-0005J3-C8; Wed, 05 Dec 2007 12:49:40 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IzyNP-0005Iu-Ic for sip-confirm+ok@megatron.ietf.org; Wed, 05 Dec 2007 12:49:39 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IzyNP-0005Im-96 for sip@ietf.org; Wed, 05 Dec 2007 12:49:39 -0500
Received: from out002.iad.hostedmail.net ([209.225.56.24]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IzyNO-0001XJ-PY for sip@ietf.org; Wed, 05 Dec 2007 12:49:39 -0500
Received: from ATL1VEXC020.usdom003.tco.tc ([10.158.7.31]) by out002.iad.hostedmail.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 5 Dec 2007 12:49:43 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] comments on draft-gurbani-sip-ipv6-abnf-fix-00
Date: Wed, 05 Dec 2007 12:49:41 -0500
Message-ID: <BBE61D1553D8A34F812FF87377B2935F01EE19DD@ATL1VEXC020.usdom003.tco.tc>
In-Reply-To: <200712050424.lB54OmtH016484@dragon.ariadne.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] comments on draft-gurbani-sip-ipv6-abnf-fix-00
Thread-Index: Acg29s54K2uSMgVsQq+p+ys7MgzBFwAbRvRQ
From: Brett Tate <brett@broadsoft.com>
To: Dale.Worley@comcast.net, sip@ietf.org
X-OriginalArrivalTime: 05 Dec 2007 17:49:43.0631 (UTC) FILETIME=[37BC5DF0:01C83767]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc:
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

> > However concerning things like To/From sip-uri's host, 
> > I assume that there will currently be poor 
> > interoperability if devices adjust things per 
> > section 2.2's flexibility (beyond hex case) 
> > within a transaction or dialog.
> 
> To and From headers shouldn't be a problem because 
> applications really shouldn't be comparing them; they 
> should be treated as comments.
> IIRC, there is some circumstance during registration 
> where URI equivalence is important, though.

RFC 3261 still requires the To/From uri's to not change.  However I
agree that it won't be a problem if vendors have adjusted/deployed their
implementations based upon rfc3261's comment that such a requirement is
expected to be deprecated in the future or have accommodated the IPv6
address representation flexibility.


_______________________________________________
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