Re: [v6ops] Agenda discussion

Rémi Després <despres.remi@laposte.net> Wed, 14 March 2012 13:33 UTC

Return-Path: <despres.remi@laposte.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0650021F86F8 for <v6ops@ietfa.amsl.com>; Wed, 14 Mar 2012 06:33:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.931
X-Spam-Level:
X-Spam-Status: No, score=-1.931 tagged_above=-999 required=5 tests=[AWL=-0.232, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iaFuHCk+5LXf for <v6ops@ietfa.amsl.com>; Wed, 14 Mar 2012 06:33:34 -0700 (PDT)
Received: from smtpout.laposte.net (smtpout5.laposte.net [193.253.67.230]) by ietfa.amsl.com (Postfix) with ESMTP id 61DD221F86F3 for <v6ops@ietf.org>; Wed, 14 Mar 2012 06:33:34 -0700 (PDT)
Received: from [192.168.0.21] ([88.166.221.144]) by mwinf8509-out with ME id lRZZ1i00837Y3f403RZZq8; Wed, 14 Mar 2012 14:33:33 +0100
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="iso-8859-1"
From: Rémi Després <despres.remi@laposte.net>
In-Reply-To: <4F609B96.90409@gmail.com>
Date: Wed, 14 Mar 2012 14:33:32 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E3D79449-B183-44D3-AB3A-16897B206CCB@laposte.net>
References: <25E067CE-65BF-462E-9A45-2D09451256F9@cisco.com> <23B5B3FA-A0A1-4671-97A9-D8964706344B@laposte.net> <8AD0DC9E-29C6-4E9D-AB30-4DE1DD37A62B@cisco.com> <C6EB6D4C-45C2-47A3-85C9-EDC5C9733406@laposte.net> <4F609B96.90409@gmail.com>
To: Tom Taylor <tom.taylor.stds@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] Agenda discussion
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Mar 2012 13:33:37 -0000

Le 2012-03-14 à 14:22, Tom Taylor a écrit :

> Perhaps it would be useful to know that Rémi's 4rd-U is actually a competitor to MAP.

Yes, indeed.
4rd is proposed as a unified standard, expected to replace the two standards of the MAP proposal, but the two designs have otherwise a lot in common.

That said, the point to be presented in v6ops is the relationship between 4rd and 464XLAT, while such a relationship hasn't been considered so far for MAP.

Regards,
RD



> 
> On 14/03/2012 7:23 AM, Rémi Després wrote:
>> Fred,
>> 
>> 2012-03-14 11:38, Fred Baker:
>> 
>>> 
>>> On Mar 13, 2012, at 8:40 AM, Rémi Després wrote:
>>> 
>>>> Hi Fred,
>>>> 
>>>> There has been discussion on the list about the relationship between 464XLAT and 4rd (24 v6ops e-mails with these 2 acronyms)
>>>> The latest version of draft-despres-softwire-4rd-U (posted on March 12) introduces a NAT64 variant called NAT64+.
>>>> Its purpose is 464XLAT-like scenarios with improved IPv4 transparency.
>>>> 
>>>> I would appreciate a slot (10 minutes or more) to present what is at stake, operationally speaking.
>>>> There is no v6ops-specific draft: time has been too short to make one despite relevance to v6ops of the subject matter to v6ops.
>>>> (There is of course no plan to present protocol contents in v6ops, Softwire being the place for this.)
>> 
>> This is only based on a small part of the latest 4rd-u draft.
>> There is definitely no need to present all other documents you listed below.
>> I do believe that, in 10 min, I can usefully inform the v6ops WG about the relationship between 464XLAT and 4rd.
>> 
>> Regards,
>> RD
>> 
>> 
>> 
>> 
>>>> 
>>>> Thanks,
>>>> RD
>>> 
>>> 4rd and dIVI are two legs of MAP, as I understand it. I was expecting that discussion during the 464xlat discussion, from the floor, but I'm willing to give someone ten minutes to present the MAP effort
>>> 
>>> 	http://datatracker.ietf.org/doc/draft-despres-softwire-4rd-u
>>> 	http://datatracker.ietf.org/doc/draft-fu-softwire-4rd-mib
>>> 	http://datatracker.ietf.org/doc/draft-mdt-softwire-map-deployment
>>> 	http://datatracker.ietf.org/doc/draft-mdt-softwire-map-dhcp-option
>>> 	http://datatracker.ietf.org/doc/draft-mdt-softwire-map-encapsulation
>>> 	http://datatracker.ietf.org/doc/draft-mdt-softwire-map-translation
>>> 	http://datatracker.ietf.org/doc/draft-mdt-softwire-mapping-address-and-port
>>> 	http://datatracker.ietf.org/doc/draft-murakami-softwire-4rd
>>> 	http://datatracker.ietf.org/doc/draft-sarikaya-softwire-4rdmulticast
>>> 
>>> and discuss its implications vis-a-vis 464clat. In ten minutes, this is obviously at a very high level. Do you think you can talk with your fellow contributors to the MAP effort and find one person who can fairly the describe all of that?
>>> 
>>>> Le 2012-03-06 à 05:46, Fred Baker a écrit :
>>>> 
>>>>> Stated in no particular order, we have the following documents that meet these criteria:
>>>>> - not in the IESG process somewhere
>>>>> - posted or updated since IETF 82
>>>>> - have had list discussion since IETF 82 or responds to discussion at IETF 82
>>>>> 
>>>>> At this point, I take them as our agenda at IETF 83. If I am missing a document (if you have posted it since Sunday, I may well be missing it), please remind me.
>>>>> 
>>>>> 
>>>>> http://tools.ietf.org/html/draft-carpenter-v6ops-icp-guidance
>>>>> "IPv6 Guidance for Internet Content and Application Service Providers",
>>>>> Brian Carpenter, Sheng Jiang, 22-Feb-12
>>>>> 
>>>>> No presentation expected, but the authors would like working group adoption. We need to decide whether we want to do that.
>>>>> 
>>>>> http://tools.ietf.org/html/draft-carpenter-v6ops-label-balance
>>>>> "Using the IPv6 Flow Label for Server Load Balancing", Brian Carpenter,
>>>>> Sheng Jiang, Willy Tarreau, 17-Jan-12
>>>>> 
>>>>> http://tools.ietf.org/html/draft-ietf-v6ops-464xlat
>>>>> "464XLAT: Combination of Stateful and Stateless Translation", Masataka
>>>>> Mawatari, Masanobu Kawashima, Cameron Byrne, 14-Feb-12
>>>>> 
>>>>> http://tools.ietf.org/html/draft-ietf-v6ops-6204bis
>>>>> "Basic Requirements for IPv6 Customer Edge Routers", Barbara Stark,
>>>>> Chris Donley, Hemant Singh, Ole Troan, Wes Beebee, 22-Dec-11
>>>>> 
>>>>> http://tools.ietf.org/html/draft-ietf-v6ops-ivi-icmp-address
>>>>> "Stateless Source Address Mapping for ICMPv6 Packets", Xing Li, Congxiao
>>>>> Bao, Dan Wing, Ramji Vaithianathan, Geoff Huston, 24-Feb-12
>>>>> 
>>>>> http://tools.ietf.org/html/draft-ietf-v6ops-ra-guard-implementation
>>>>> "Implementation Advice for IPv6 Router Advertisement Guard (RA-Guard)",
>>>>> Fernando Gont, 3-Mar-12
>>>>> 
>>>>> http://tools.ietf.org/html/draft-ietf-v6ops-wireline-incremental-ipv6
>>>>> "Wireline Incremental IPv6", Victor Kuarsingh, Lee Howard, 1-Feb-12
>>>>> 
>>>>> In the coming week, I am told to expect one additional -00 draft, and I could imagine other drafts being updated. I will be looking for those drafts to meet the criteria above as well, but please drop the chairs a note.
>>>>> _______________________________________________
>>>>> v6ops mailing list
>>>>> v6ops@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>>> 
>>> 
>> 
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>>