Re: [shara] aplusp BOF

<teemu.savolainen@nokia.com> Fri, 09 October 2009 06:39 UTC

Return-Path: <teemu.savolainen@nokia.com>
X-Original-To: shara@core3.amsl.com
Delivered-To: shara@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 920D73A68E3 for <shara@core3.amsl.com>; Thu, 8 Oct 2009 23:39:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.359
X-Spam-Level:
X-Spam-Status: No, score=-6.359 tagged_above=-999 required=5 tests=[AWL=0.240, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a3Z116bf8mbh for <shara@core3.amsl.com>; Thu, 8 Oct 2009 23:39:40 -0700 (PDT)
Received: from mgw-mx09.nokia.com (smtp.nokia.com [192.100.105.134]) by core3.amsl.com (Postfix) with ESMTP id A1A463A683C for <shara@ietf.org>; Thu, 8 Oct 2009 23:39:40 -0700 (PDT)
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-mx09.nokia.com (Switch-3.3.3/Switch-3.3.3) with ESMTP id n996f0Ie004531; Fri, 9 Oct 2009 01:41:16 -0500
Received: from vaebh104.NOE.Nokia.com ([10.160.244.30]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 9 Oct 2009 09:40:59 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.6]) by vaebh104.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Fri, 9 Oct 2009 09:40:54 +0300
Received: from NOK-EUMSG-01.mgdnok.nokia.com ([65.54.30.86]) by nok-am1mhub-02.mgdnok.nokia.com ([65.54.30.6]) with mapi; Fri, 9 Oct 2009 08:40:53 +0200
From: <teemu.savolainen@nokia.com>
To: <rdroms@cisco.com>, <remi.despres@free.fr>
Date: Fri, 9 Oct 2009 08:40:53 +0200
Thread-Topic: [shara] aplusp BOF
Thread-Index: AcpInm8n3wphSUiKR9msx7nwFOCt8wADEbCb
Message-ID: <18034D4D7FE9AE48BF19AB1B0EF2729F3EF09BCC72@NOK-EUMSG-01.mgdnok.nokia.com>
References: <7B6AA02E-2736-43BB-BED8-205EF98B773E@cisco.com> <m2ws3dwg1q.wl%randy@psg.com> <6DB98895-B9E3-467B-A022-5989005BD169@free.fr>, <D17AD36F-6FCD-4A2F-87C0-FF41CD64866E@cisco.com>
In-Reply-To: <D17AD36F-6FCD-4A2F-87C0-FF41CD64866E@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 09 Oct 2009 06:40:54.0408 (UTC) FILETIME=[73466080:01CA48AB]
X-Nokia-AV: Clean
Cc: shara@ietf.org
Subject: Re: [shara] aplusp BOF
X-BeenThere: shara@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Sharing of an IPv4 Address discussion list <shara.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shara>, <mailto:shara-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shara>
List-Post: <mailto:shara@ietf.org>
List-Help: <mailto:shara-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shara>, <mailto:shara-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Oct 2009 06:39:41 -0000

Ralph,

The DS-Lite essentially is encapsulation+CGN. The most commonly discussed encapsulation method is IPv4-over-IPv6. However, L2TP, PPP, GTP, etc "point-to-point" connections are also possible in addition to plain IPv6. This is mentioned in DS-Lite dradt as well. I believe these other encapsulation means are in the scope of the BOF? 

Best regards,

Teemu
________________________________________
From: shara-bounces@ietf.org [shara-bounces@ietf.org] On Behalf Of ext Ralph Droms [rdroms@cisco.com]
Sent: Friday, October 09, 2009 8:07 AM
To: Rémi Després
Cc: shara@ietf.org
Subject: Re: [shara] aplusp BOF

But generalizations of A+P were argued against in the shara BOF.  A+P
represents a truly significant change to the IPv4 addressing
architecture that makes fundamental changes to the behavior of IP and
applications built on IP when implemented in a host.  By constraining
the problem space to the scenario with well-defined endpoints and a
well-defined forwarding mechanism, the BOF will have an opportunity to
focus on a case where it can be found to be useful.

- Ralph

On Oct 8, 2009, at 6:35 AM 10/8/09, Rémi Després wrote:

> Ralph,
>
> I fully support Randy's view.
>
> Having as A+P *on dual-stack lite* as "main objective" of an aplusp
> WG would be much too restrictive.
>
> Having it as a "minimum objective" would be OK though, because of
> recent progress made on this particular A+P application.
>
> The WG SHOULD be the place to determine which other architectures
> and signaling alternatives address new operational requirements, and
> therefore justify quick progress.
>
> In particular, while dual-stack lite is for IPv6-only ISPs, some
> ISPs will rather deploy IPv6 AND private IPv4 addressing on their
> infrastructures. They should also be able to take advantage of A+P.
> (These advantages are good to have: simple server reachability when
> communicating with IPv4-only remote hosts; restored end-to-end
> transparency for hosts that support A+P.)
>
> Similarly ISPs that only have private IPv4 routing so far, across
> which they can quickly deploy native IPv6 with 6rd, should also be
> able to take advantage of A+P. For this, IPv4 in IPv4 tunneling
> mentioned by Randy does make sense.
>
> Regards,
> RD
>
>
> There are other approaches
> Le 3 oct. 09 à 01:07, Randy Bush a écrit :
>
>>> The IESG has approved the aplusp BOF for IETF 76.  The BOF will be
>>> used to discuss A+P addressing and forwarding as it applies to
>>> dual-stack lite [draft-ietf-softwire-dual-stack-lite-01].
>>
>> excuse?  folk such as the wireless gang have a very different need
>> for
>> it, and an architecturally different spin.  some are using ipv4 over
>> ipv4 tunneling.  some are using very different signaling mechanisms.
>> etc.
>>
>> currently, ds-lite has been restricted to one view of provisioning.
>> this is a pretty restricted view.
>>
>> randy
>> _______________________________________________
>> shara mailing list
>> shara@ietf.org
>> https://www.ietf.org/mailman/listinfo/shara
>

_______________________________________________
shara mailing list
shara@ietf.org
https://www.ietf.org/mailman/listinfo/shara