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

"Brett Tate" <brett@broadsoft.com> Thu, 06 December 2007 18: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 1J0LQE-0006IT-NF; Thu, 06 Dec 2007 13:26:06 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1J0LQD-0006IN-Og for sip-confirm+ok@megatron.ietf.org; Thu, 06 Dec 2007 13:26:05 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J0LQD-0006IF-E6 for sip@ietf.org; Thu, 06 Dec 2007 13:26:05 -0500
Received: from out003.iad.hostedmail.net ([209.225.56.66]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J0LQD-0003eY-4f for sip@ietf.org; Thu, 06 Dec 2007 13:26:05 -0500
Received: from ATL1VEXC020.usdom003.tco.tc ([10.158.7.31]) by out003.iad.hostedmail.net with Microsoft SMTPSVC(6.0.3790.3959); Thu, 6 Dec 2007 13:26:10 -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: Thu, 06 Dec 2007 13:26:03 -0500
Message-ID: <BBE61D1553D8A34F812FF87377B2935F01F571BC@ATL1VEXC020.usdom003.tco.tc>
In-Reply-To: <DED0424C02C83A4AB0419517605CD11E02F5D215@EXCHANGE-BE2.speakeasy.hq>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] comments on draft-gurbani-sip-ipv6-abnf-fix-00
Thread-Index: Acg29s54K2uSMgVsQq+p+ys7MgzBFwAbRvRQABXJFjAAGp63IA==
From: Brett Tate <brett@broadsoft.com>
To: Jane Jiang <janej@hq.speakeasy.net>, sip@ietf.org
X-OriginalArrivalTime: 06 Dec 2007 18:26:10.0218 (UTC) FILETIME=[7974D0A0:01C83835]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
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

> I guess the purpose of this discussion is about this 
> particular draft, which intends to correct some mistakes 
> existing in some RFCs.

Yes; the draft is expanding beyond the current ABNF fix to also correct
or more clearly document other IPv6 areas of rfc3261.


> I am wondering if you will want to discuss about the impacts 
> of mapping between IPv6 address and IPv4 address?

I'm not sure which aspect of mapping you are mentioning.
Draft-ietf-sipping-v6-transition and
draft-ietf-sipping-ipv6-torture-tests discuss some of the potential
issues.


> I feel like if we simply try to match the two from each 
> other, we will not be able to maintain the original design 
> beauties behind each address structure.  Correct me if I am wrong.

I'm not sure that I understand the matching comment.  The current
understanding is that an IPv6 address does not equal an IPv4 address
from a SIP equality perspective.  However there are obviously
situations/services on a device where they might be treated the same:
identity, access control, etcetera.

There are situations where an IPv6 address contains an IPv4 address.
However I currently doubt that we need to discuss the matter beyond
highlighting such an address concerning equality and maybe additionally
503, looping, downgrading to IPv4, etcetera.


_______________________________________________
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