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

"Brett Tate" <brett@broadsoft.com> Fri, 07 December 2007 21:07 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 1J0kQ2-0005tj-Jt; Fri, 07 Dec 2007 16:07:34 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1J0kQ0-0005pY-Sh for sip-confirm+ok@megatron.ietf.org; Fri, 07 Dec 2007 16:07:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J0kQ0-0005n6-I2 for sip@ietf.org; Fri, 07 Dec 2007 16:07:32 -0500
Received: from out001.iad.hostedmail.net ([209.225.56.23]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1J0kQ0-0002PD-Be for sip@ietf.org; Fri, 07 Dec 2007 16:07:32 -0500
Received: from ATL1VEXC020.usdom003.tco.tc ([10.158.7.31]) by out001.iad.hostedmail.net with Microsoft SMTPSVC(6.0.3790.3959); Fri, 7 Dec 2007 16:07:36 -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: Fri, 07 Dec 2007 16:07:31 -0500
Message-ID: <BBE61D1553D8A34F812FF87377B2935F01F5787C@ATL1VEXC020.usdom003.tco.tc>
In-Reply-To: <DED0424C02C83A4AB0419517605CD11E02F5D235@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+ys7MgzBFwAbRvRQABXJFjAAGp63IAAU71TAACSvjAA=
From: Brett Tate <brett@broadsoft.com>
To: Jane Jiang <janej@hq.speakeasy.net>, sip@ietf.org
X-OriginalArrivalTime: 07 Dec 2007 21:07:36.0691 (UTC) FILETIME=[31750C30:01C83915]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
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

> Though IPv6 was initially designed to address the IP address 
> space issue, I feel like the mobility feature afforded by 
> IPv6 address design is a true value added.  
> 
> When we are mapping from IPv6 to IPv4, we will certainly 
> loose some information.  However, when we are mapping from 
> IPv4 to IPv6, how can we expand the digits in a way that we 
> can actually  make the mapped IPv6 address to support 
> mobility?

The IPv6 mobility topic would likely be beyond intended purpose of the
draft.

Your question would potentially be relevant to
draft-ietf-sipping-v6-transition.  

If IPv6 mobility has impacts upon SIP which have not been analyzed
within SIPPING or another working group, the community would likely
welcome the analysis even if it doesn't produce new SIP related
requirements.

Thanks,
Brett


_______________________________________________
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