
From ot@cisco.com  Mon Dec  5 04:19:34 2011
Return-Path: <ot@cisco.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7761F21F8B70 for <softwires@ietfa.amsl.com>; Mon,  5 Dec 2011 04:19:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Cy6xC2QsYvur for <softwires@ietfa.amsl.com>; Mon,  5 Dec 2011 04:19:33 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 6931D21F8B33 for <softwires@ietf.org>; Mon,  5 Dec 2011 04:19:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ot@cisco.com; l=1127; q=dns/txt; s=iport; t=1323087573; x=1324297173; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=d6O7+LdDlXt0h5sIBQizCUv5/GT2cfurp82+VnvbNwQ=; b=I1GXOH57UT6Mn2KvVHDPOCymTW/J3b0Q/5MutZ7ucHtjzljIZdxv9CRR +xhrLv6G8AxnlC+NdqbZ3gLqHRap42HSG2aXOCZ67i94ctNQnsM/8l49x l21LdugvONHjsGvhYvre2ieIbJtK7BhblqrPNfuRxwmnnTm9gTd8XViH9 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoQAAKK23E6Q/khM/2dsb2JhbABEmhKQKYEFgXIBAQEDARIBJz8FBwQLEQQBASgHRgkIBhMih2WXLAGeHIo+YwSUXIVHjFI
X-IronPort-AV: E=Sophos;i="4.71,298,1320624000";  d="scan'208";a="4214483"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-3.cisco.com with ESMTP; 05 Dec 2011 12:19:32 +0000
Received: from [173.38.129.208] ([173.38.129.208]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pB5CJV8j004381; Mon, 5 Dec 2011 12:19:31 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <ot@cisco.com>
In-Reply-To: <E1CE3E6E6D4E1C438B0ADC9FFFA345EA1CA97542@SZXEML510-MBX.china.huawei.com>
Date: Mon, 5 Dec 2011 13:19:31 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4AD5506B-A579-4D86-8740-61AD0EDC0F4A@cisco.com>
References: <35CC3E09-4E5E-4383-ADE3-29EACBE5BD81@cisco.com> <4ED9A57E.7070003@cernet.edu.cn> <E1CE3E6E6D4E1C438B0ADC9FFFA345EA1CA97542@SZXEML510-MBX.china.huawei.com>
To: Leaf yeh <leaf.y.yeh@huawei.com>
X-Mailer: Apple Mail (2.1084)
Cc: softwires <softwires@ietf.org>, "map-dt@external.cisco.com team" <map-dt@external.cisco.com>, "fine_sz@huawei.com" <fine_sz@huawei.com>
Subject: Re: [Softwires] Revision 02
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Dec 2011 12:19:34 -0000

Leaf,

thanks for your comments, I will incorporate those together with the =
comments received by Xing Li.

> The new draft (-02) is more readable to me than before, but it still =
sounds not complete yet.=20

what do you think isn't complete? I didn't see that reflected in your =
comments.

> The attached is my copy revisions after the quick reading, just for =
your reference to the progress of the text.
> If there is anything shows my understanding is wrong or not perfect, =
pls. feel free to indicate.

Best regards,
Ole


>=20
>=20
> Best Regards,
> Leaf
>=20
>=20
> -----Original Message-----
> From: Xing Li [mailto:xing@cernet.edu.cn]=20
> Sent: Saturday, December 03, 2011 12:29 PM
> To: Ole Troan
> Cc: map-dt@external.cisco.com team; softwires
> Subject: Re: Revision 02
>=20
> Hi, Ole,
>=20
> Thank you very much for your work. Attached please find our additional =
comments and suggestions for =
draft-mdt-softwire-mapping-address-and-port-02
>=20
> Regards,
>=20
> xing, congxiao
>=20
>=20
>=20
> <draft-mdt-softwire-mapping-address-and-port-02-Leaf-C-1112.pdf>


From wwwrun@rfc-editor.org  Sun Dec 11 07:14:22 2011
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC98321F853A for <softwires@ietfa.amsl.com>; Sun, 11 Dec 2011 07:14:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.445
X-Spam-Level: 
X-Spam-Status: No, score=-102.445 tagged_above=-999 required=5 tests=[AWL=0.155, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 iZvVXkVsoTbf for <softwires@ietfa.amsl.com>; Sun, 11 Dec 2011 07:14:22 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 243C621F852E for <softwires@ietf.org>; Sun, 11 Dec 2011 07:14:22 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 5234D72E004; Sun, 11 Dec 2011 07:13:33 -0800 (PST)
To: mark@townsley.net, ot@cisco.com, rdroms.ietf@gmail.com, jari.arkko@piuha.net, adurand@juniper.net, cuiyong@tsinghua.edu.cn
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20111211151333.5234D72E004@rfc-editor.org>
Date: Sun, 11 Dec 2011 07:13:33 -0800 (PST)
Cc: softwires@ietf.org, alessandro.cortiana@gmail.com, rfc-editor@rfc-editor.org
Subject: [Softwires] [Technical Errata Reported] RFC5969 (3049)
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Dec 2011 15:14:22 -0000

The following errata report has been submitted for RFC5969,
"IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=5969&eid=3049

--------------------------------------
Type: Technical
Reported by: Alessandro Cortiana <alessandro.cortiana@gmail.com>

Section: 12

Original Text
-------------
By restricting the 6rd domain to within a provider
network, a CE only needs to accept packets from a single or small set
of known 6rd BR IPv4 addresses.

Corrected Text
--------------
By restricting the 6rd domain to within a provider
network, a CE only needs to accept packets from a single or small set
of known 6rd BR IPv4 addresses and from other CEs within the 6rd domain.

Notes
-----
A CE also needs to accept packets from other CEs within the 6rd domain.
This happens when, within a 6rd domain, two customer sites want to communicate.
Reference: RFC5569 section 3

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC5969 (draft-ietf-softwire-ipv6-6rd-10)
--------------------------------------
Title               : IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification
Publication Date    : August 2010
Author(s)           : W. Townsley, O. Troan
Category            : PROPOSED STANDARD
Source              : Softwires
Area                : Internet
Stream              : IETF
Verifying Party     : IESG

From shemant@cisco.com  Sun Dec 11 09:13:48 2011
Return-Path: <shemant@cisco.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 656AF21F845B for <softwires@ietfa.amsl.com>; Sun, 11 Dec 2011 09:13:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.518
X-Spam-Level: 
X-Spam-Status: No, score=-6.518 tagged_above=-999 required=5 tests=[AWL=0.081,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 i6iadHfQHo+V for <softwires@ietfa.amsl.com>; Sun, 11 Dec 2011 09:13:47 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 9E16721F8457 for <softwires@ietf.org>; Sun, 11 Dec 2011 09:13:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=3008; q=dns/txt; s=iport; t=1323623627; x=1324833227; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=6b1STtg7EABIzniVj/HJlUjKmcEEceTExGFVkwd/lBY=; b=FM346EIJ2bSri0l1tnuw3QQOCTqW2TwtlDYogCFx2WacN2Is9JtaYOeG m3Y+uqIwSQKSeLT3IdeFZySks7rn62qeGW9b3v8Op/pE8UEEvzQk+faAR xO9p15CK5fFnCQ4OL0cKuj4rV4A6vgaEm5sotFTPbRWM3xkKfhBbGquiq k=;
X-IronPort-AV: E=Sophos;i="4.71,335,1320624000"; d="scan'208";a="42976465"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-1.cisco.com with ESMTP; 11 Dec 2011 17:13:47 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-6.cisco.com (8.14.3/8.14.3) with ESMTP id pBBHDlpB008088;  Sun, 11 Dec 2011 17:13:47 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sun, 11 Dec 2011 11:13:47 -0600
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
Date: Sun, 11 Dec 2011 11:13:45 -0600
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C3038294B5@XMB-RCD-109.cisco.com>
In-Reply-To: <20111211151333.5234D72E004@rfc-editor.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Softwires] [Technical Errata Reported] RFC5969 (3049)
Thread-Index: Acy4F5Lp+hAJiv9VTYykrK4sfNY87wADrQRQ
References: <20111211151333.5234D72E004@rfc-editor.org>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "RFC Errata System" <rfc-editor@rfc-editor.org>, <mark@townsley.net>, <ot@cisco.com>, <rdroms.ietf@gmail.com>, <jari.arkko@piuha.net>, <adurand@juniper.net>, <cuiyong@tsinghua.edu.cn>
X-OriginalArrivalTime: 11 Dec 2011 17:13:47.0032 (UTC) FILETIME=[3E4CB980:01CCB828]
Cc: softwires@ietf.org, alessandro.cortiana@gmail.com
Subject: Re: [Softwires] [Technical Errata Reported] RFC5969 (3049)
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Dec 2011 17:13:48 -0000

While we are on the subject of Errata in RFC 5969, aren't the following
two pieces of text from RFC 5969 inconsistent?

[In 6rd, all CEs and BRs can be considered as connected to the same
virtual link and therefore neighbors to each other.]

[with all 6rd CEs and BRs defined as off-link neighbors from one other.]

There is no such thing as an off-link neighbor - a neighbor, by
definition is on the same link.  Maybe I have a nitpick, but certainly
some better text could be uses because off-link vs. on-link has specific
rules for when to issues an NS or not. =20

Hemant

-----Original Message-----
From: softwires-bounces@ietf.org [mailto:softwires-bounces@ietf.org] On
Behalf Of RFC Errata System
Sent: Sunday, December 11, 2011 10:14 AM
To: mark@townsley.net; ot@cisco.com; rdroms.ietf@gmail.com;
jari.arkko@piuha.net; adurand@juniper.net; cuiyong@tsinghua.edu.cn
Cc: softwires@ietf.org; alessandro.cortiana@gmail.com;
rfc-editor@rfc-editor.org
Subject: [Softwires] [Technical Errata Reported] RFC5969 (3049)


The following errata report has been submitted for RFC5969,
"IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol
Specification".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=3D5969&eid=3D3049

--------------------------------------
Type: Technical
Reported by: Alessandro Cortiana <alessandro.cortiana@gmail.com>

Section: 12

Original Text
-------------
By restricting the 6rd domain to within a provider
network, a CE only needs to accept packets from a single or small set
of known 6rd BR IPv4 addresses.

Corrected Text
--------------
By restricting the 6rd domain to within a provider
network, a CE only needs to accept packets from a single or small set
of known 6rd BR IPv4 addresses and from other CEs within the 6rd domain.

Notes
-----
A CE also needs to accept packets from other CEs within the 6rd domain.
This happens when, within a 6rd domain, two customer sites want to
communicate.
Reference: RFC5569 section 3

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary.=20

--------------------------------------
RFC5969 (draft-ietf-softwire-ipv6-6rd-10)
--------------------------------------
Title               : IPv6 Rapid Deployment on IPv4 Infrastructures
(6rd) -- Protocol Specification
Publication Date    : August 2010
Author(s)           : W. Townsley, O. Troan
Category            : PROPOSED STANDARD
Source              : Softwires
Area                : Internet
Stream              : IETF
Verifying Party     : IESG
_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www.ietf.org/mailman/listinfo/softwires

From internet-drafts@ietf.org  Fri Dec 16 18:19:33 2011
Return-Path: <internet-drafts@ietf.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17CEE21F84B6; Fri, 16 Dec 2011 18:19:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.559
X-Spam-Level: 
X-Spam-Status: No, score=-102.559 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ufJ4rnPSOFOd; Fri, 16 Dec 2011 18:19:32 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8607421F84B2; Fri, 16 Dec 2011 18:19:32 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111217021932.18439.46486.idtracker@ietfa.amsl.com>
Date: Fri, 16 Dec 2011 18:19:32 -0800
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-gateway-init-ds-lite-06.txt
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Dec 2011 02:19:33 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies. This draft is a work item of the Softwires Working Group of the IETF.

	Title           : Gateway Initiated Dual-Stack Lite Deployment
	Author(s)       : Frank Brockners
                          Sri Gundavelli
                          Sebastian Speicher
                          David Ward
	Filename        : draft-ietf-softwire-gateway-init-ds-lite-06.txt
	Pages           : 15
	Date            : 2011-12-16

   Gateway-Initiated Dual-Stack lite (GI-DS-lite) is a variant of Dual-
   Stack lite (DS-lite) applicable to certain tunnel-based access
   architectures.  GI-DS-lite extends existing access tunnels beyond the
   access gateway to an IPv4-IPv4 NAT using softwires with an embedded
   context identifier that uniquely identifies the end-system the
   tunneled packets belong to.  The access gateway determines which
   portion of the traffic requires NAT using local policies and sends/
   receives this portion to/from this softwire.


A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-softwire-gateway-init-ds-lit=
e-06.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

This Internet-Draft can be retrieved at:
ftp://ftp.ietf.org/internet-drafts/draft-ietf-softwire-gateway-init-ds-lite=
-06.txt


From iesg-secretary@ietf.org  Mon Dec 19 06:42:13 2011
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB9CC21F891D; Mon, 19 Dec 2011 06:42:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.044
X-Spam-Level: 
X-Spam-Status: No, score=-102.044 tagged_above=-999 required=5 tests=[AWL=0.555, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 r1qScjVOyDYc; Mon, 19 Dec 2011 06:42:12 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68A9821F8494; Mon, 19 Dec 2011 06:42:12 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111219144212.8365.73553.idtracker@ietfa.amsl.com>
Date: Mon, 19 Dec 2011 06:42:12 -0800
Cc: softwires@ietf.org
Subject: [Softwires] Last Call: <draft-ietf-softwire-gateway-init-ds-lite-05.txt> (Gateway	Initiated Dual-Stack Lite Deployment) to Proposed Standard
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Dec 2011 14:42:13 -0000

The IESG has received a request from the Softwires WG (softwire) to
consider the following document:
- 'Gateway Initiated Dual-Stack Lite Deployment'
  <draft-ietf-softwire-gateway-init-ds-lite-05.txt> as a Proposed
Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2012-01-04. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   Gateway-Initiated Dual-Stack lite (GI-DS-lite) is a variant of Dual-
   Stack lite (DS-lite) applicable to certain tunnel-based access
   architectures.  GI-DS-lite extends existing access tunnels beyond the
   access gateway to an IPv4-IPv4 NAT using softwires with an embedded
   context identifier that uniquely identifies the end-system the
   tunneled packets belong to.  The access gateway determines which
   portion of the traffic requires NAT using local policies and sends/
   receives this portion to/from this softwire.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-softwire-gateway-init-ds-lite/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-softwire-gateway-init-ds-lite/


The following IPR Declarations may be related to this I-D:

   http://datatracker.ietf.org/ipr/1411/
   http://datatracker.ietf.org/ipr/1630/




From iesg-secretary@ietf.org  Mon Dec 19 06:43:54 2011
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E82B21F8B57; Mon, 19 Dec 2011 06:43:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.377
X-Spam-Level: 
X-Spam-Status: No, score=-102.377 tagged_above=-999 required=5 tests=[AWL=0.222, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 EjxXHyrmxBL2; Mon, 19 Dec 2011 06:43:53 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A26D721F8513; Mon, 19 Dec 2011 06:43:53 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111219144353.9907.74689.idtracker@ietfa.amsl.com>
Date: Mon, 19 Dec 2011 06:43:53 -0800
Cc: softwires@ietf.org
Subject: [Softwires] REVISED Last Call: <draft-ietf-softwire-gateway-init-ds-lite-06.txt>	(Gateway Initiated Dual-Stack Lite Deployment) to Proposed Standard
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Dec 2011 14:43:54 -0000

The IESG has received a request from the Softwires WG (softwire) to
consider the following document:
- 'Gateway Initiated Dual-Stack Lite Deployment'
  <draft-ietf-softwire-gateway-init-ds-lite-06.txt> as a Proposed
Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2012-01-04. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   Gateway-Initiated Dual-Stack lite (GI-DS-lite) is a variant of Dual-
   Stack lite (DS-lite) applicable to certain tunnel-based access
   architectures.  GI-DS-lite extends existing access tunnels beyond the
   access gateway to an IPv4-IPv4 NAT using softwires with an embedded
   context identifier that uniquely identifies the end-system the
   tunneled packets belong to.  The access gateway determines which
   portion of the traffic requires NAT using local policies and sends/
   receives this portion to/from this softwire.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-softwire-gateway-init-ds-lite/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-softwire-gateway-init-ds-lite/


The following IPR Declarations may be related to this I-D:

   http://datatracker.ietf.org/ipr/1411/
   http://datatracker.ietf.org/ipr/1630/




From iesg-secretary@ietf.org  Mon Dec 19 11:47:20 2011
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C38DE21F8482; Mon, 19 Dec 2011 11:47:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.541
X-Spam-Level: 
X-Spam-Status: No, score=-102.541 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 6wJz10EU-XFi; Mon, 19 Dec 2011 11:47:20 -0800 (PST)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FDE711E809D; Mon, 19 Dec 2011 11:47:20 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p1
Message-ID: <20111219194720.4769.8657.idtracker@ietfa.amsl.com>
Date: Mon, 19 Dec 2011 11:47:20 -0800
Cc: softwire mailing list <softwires@ietf.org>, softwire chair <softwire-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Softwires] Protocol Action: 'RADIUS Extensions for Dual-Stack Lite' to Proposed	Standard (draft-ietf-softwire-dslite-radius-ext-07.txt)
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Dec 2011 19:47:20 -0000

The IESG has approved the following document:
- 'RADIUS Extensions for Dual-Stack Lite'
  (draft-ietf-softwire-dslite-radius-ext-07.txt) as a Proposed Standard

This document is the product of the Softwires Working Group.

The IESG contact persons are Ralph Droms and Jari Arkko.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-softwire-dslite-radius-ext/




Technical Summary

   This document specifies a RADIUS attribute, DS-Lite-Tunnel-Name,
   that carries an FQDN identifying a DS-Lite AFTR.  The
   DS-Lite-Tunnel-Name attribute is to be used between DHCPv6 server
   and AAA server.  The document also describe the use of the
   DS-Lite-Tunnel-Name attribute in combination with DHCPv6 and with
   PPP sessions.

Working Group Summary

   This document was carefully reviewed by the working group and
   discussed in depth. There were some disagreement over small
   details, which were addressed in the most recent revision of the
   document.  Working group consensus is to accept the resolution of
   those details and overall WG consensus is strong in support of
   publication this document. 

Document Quality

   We haven't seen any implementations yet, but there is a vendor
   working on this.

Personnel

   Yong Cui <cuiyong@tsinghua.edu.cn> is the document shepherd. Ralph
   Droms <rdroms.ietf@gmail.com> is the responsible Area Director.


From stefan.winter@restena.lu  Wed Dec 21 01:25:13 2011
Return-Path: <stefan.winter@restena.lu>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8E2321F84D4 for <softwires@ietfa.amsl.com>; Wed, 21 Dec 2011 01:25:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_37=0.6]
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 6qB5wtwf3Hw3 for <softwires@ietfa.amsl.com>; Wed, 21 Dec 2011 01:25:13 -0800 (PST)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id 1D21B21F84B8 for <softwires@ietf.org>; Wed, 21 Dec 2011 01:25:13 -0800 (PST)
Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id 290E610A16; Wed, 21 Dec 2011 10:25:11 +0100 (CET)
Received: from [IPv6:2001:a18:1:8:710e:3e63:6b3b:8003] (unknown [IPv6:2001:a18:1:8:710e:3e63:6b3b:8003]) by smtprelay.restena.lu (Postfix) with ESMTPS id 106E810A15; Wed, 21 Dec 2011 10:25:11 +0100 (CET)
Message-ID: <4EF1A65F.9080609@restena.lu>
Date: Wed, 21 Dec 2011 10:26:55 +0100
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Peter Deacon <peterd@iea-software.com>
References: <4EC1BD65.4040205@restena.lu> <4EEB1014.1030307@restena.lu> <5D36713D8A4E7348A7E10DF7437A4B9218583E44@SZXEML506-MBX.china.huawei.com> <4EF047A3.5090906@restena.lu> <4EF08F63.1010600@deployingradius.com> <alpine.WNT.2.00.1112200950300.2472@SMURF> <5D36713D8A4E7348A7E10DF7437A4B9218584374@SZXEML506-MBX.china.huawei.com> <alpine.WNT.2.00.1112201948210.2472@SMURF>
In-Reply-To: <alpine.WNT.2.00.1112201948210.2472@SMURF>
X-Enigmail-Version: 1.3.4
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE35A15DC25BA5C64CA32EC5B"
X-Virus-Scanned: ClamAV
Cc: softwires@ietf.org, Alan DeKok <aland@deployingradius.com>, GuoDayong <guodayong@huawei.com>
Subject: Re: [Softwires] 6rd RADIUS attribute - grouped attributes
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Dec 2011 09:25:14 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigE35A15DC25BA5C64CA32EC5B
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

added softwires cc. This really belongs on the mailing list.

> My understanding there already was agreement on format.  Recommend
> maintaining current -04 format instead of these changes.

I suggested this on the softwires mailing list because it has a number
of advantages. Right now there are at least two drafts which need to
encode structured information.

There is one agreed model how to encode this, it's the extended type TLV.=


If both drafts have their own complex encoding, it's double work:
everyone needs to write their own parser for their own attribute. As
time goes by, there will be more drafts needing to encode some complex
information. Consolidation of such complex types into a common format is
a good thing IMHO.

OTOH, using the new TLVs, only one parser needs to be written, *and*
that code is reusable for future attributes with complex encoding needs
with no extra effort.

>> IPv6-6rd-Configuration Attribute
>>  0                   1                   2                   3
>>  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> |      Type     |    Length     | Extended-Type |M|    Flag     |
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> |                            Suboptions                         |
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> Type 245, extended-type TBD.
>=20
> Using Extended-Type means you would have to wait for the extensions
> draft to be an RFC in order to be assigned an Extended-Type.

That's right. It is the only drawback. If you choose to go the
custom-encoding way, you avoid a bit of waiting time at the expense of
extra, non-reusable code in every 6rd implementation.

> Compromised solution I originally suggested (Currently
> draft-ietf-softwire-6rd-radius-attrib-04) sought to avoid dependencies
> on other drafts while at the same time providing maximum compatibility
> with existing and future systems.

It requires an implementer to write one parser specifically for the
6rd-attribute, with no code re-use for other attributes that will be
defined in the future. The code needs to be maintained separately from
the a generic extended-attributes parser. That sounds rather
short-sighted to me and goes contrary to the claim of "compatibility
with future systems".

I'm not sure what "compatibility with existing systems" should mean.
Existing systems can't make anything out of the IPv6-6rd-Configuration
attribute, because they can't parse the content. All they can do is
ignore the attribute. They can do that with an extended-type attribute
just as well.

Greetings,

Stefan Winter

>=20
>> IPv4MaskLen suboption
>>  0                   1                   2                   3
>>  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> |   sub-Type    |    Length     |   IPv4MaskLen |
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> Subtype 1
>=20
>> 6rdPrefix suboption
>>  0                   1                   2                   3
>>  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> |   sub-Type    |    Length     |  6rdPrefixLen |               |
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+               +
>> |                                                               |
>> +                      6rdPrefix                                +
>> |                                                               |
>> +                                                               +
>> |                                                               |
>> +                                               +-+-+-+-+-+-+-+-+
>> |                                               |
>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>> Subtype 2
>=20
> Prefix attribute was implemented a decade ago in RFC 3162 2.3. 1-octet
> reserved field before prefix length is required.
>=20
> regards,
> Peter


--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


--------------enigE35A15DC25BA5C64CA32EC5B
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7xpmMACgkQ+jm90f8eFWZAiQCfUYIjAZLJ6MjB7LJ7Yft29Kdz
XkYAn3hiZ/KZczxx9pS54wlO+XvdDUwT
=ZDmf
-----END PGP SIGNATURE-----

--------------enigE35A15DC25BA5C64CA32EC5B--

From stefan.winter@restena.lu  Wed Dec 21 06:10:50 2011
Return-Path: <stefan.winter@restena.lu>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0389F21F84AA for <softwires@ietfa.amsl.com>; Wed, 21 Dec 2011 06:10:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.149
X-Spam-Level: 
X-Spam-Status: No, score=-2.149 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, J_CHICKENPOX_37=0.6]
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 wg6INoKpLdbJ for <softwires@ietfa.amsl.com>; Wed, 21 Dec 2011 06:10:49 -0800 (PST)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id 3E0DA21F84A8 for <softwires@ietf.org>; Wed, 21 Dec 2011 06:10:49 -0800 (PST)
Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id E9FDB10A08; Wed, 21 Dec 2011 15:10:43 +0100 (CET)
Received: from [IPv6:2001:a18:1:8:2097:ab95:6a35:4b95] (unknown [IPv6:2001:a18:1:8:2097:ab95:6a35:4b95]) by smtprelay.restena.lu (Postfix) with ESMTPS id D6DA310A01; Wed, 21 Dec 2011 15:10:43 +0100 (CET)
Message-ID: <4EF1E94D.2080006@restena.lu>
Date: Wed, 21 Dec 2011 15:12:29 +0100
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Peter Deacon <peterd@iea-software.com>
References: <4EC1BD65.4040205@restena.lu> <4EEB1014.1030307@restena.lu> <5D36713D8A4E7348A7E10DF7437A4B9218583E44@SZXEML506-MBX.china.huawei.com> <4EF047A3.5090906@restena.lu> <4EF08F63.1010600@deployingradius.com> <alpine.WNT.2.00.1112200950300.2472@SMURF> <5D36713D8A4E7348A7E10DF7437A4B9218584374@SZXEML506-MBX.china.huawei.com> <alpine.WNT.2.00.1112201948210.2472@SMURF> <4EF1A65F.9080609@restena.lu> <alpine.WNT.2.00.1112210204010.2472@SMURF>
In-Reply-To: <alpine.WNT.2.00.1112210204010.2472@SMURF>
X-Enigmail-Version: 1.3.4
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigD68C21658F4B6FEDB87032D3"
X-Virus-Scanned: ClamAV
Cc: softwires@ietf.org, Alan DeKok <aland@deployingradius.com>, GuoDayong <guodayong@huawei.com>
Subject: Re: [Softwires] 6rd RADIUS attribute - grouped attributes
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Dec 2011 14:10:50 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigD68C21658F4B6FEDB87032D3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

> I don't think this is correct.  The extensions document describes a
> *data type* 'TLV'.  My suggestion simply leverages this type in the sam=
e
> way IPv4 Address and IPv6 prefix type from existing RFCs are already
> being leveraged.
>=20
> If you implement extensions RFC in the future your implementation
> supports the TLV data type giving you the ability to encode and decode
> this attribute with configuration dictionaries.  The wire format of
> IPv6-6rd-Configuration was intentionally made to be the same as a TLV.

Ah! I'm just looking at the -04 with this extra context. It's certainly
close. I think there's only one thing which is not inline: 6rdprefixLen
and 6rdPrefix immediately follow each other. In a version
compatible/analogous to the radius-extensions draft, the former would be
of type integer, the latter of type IPv6Address, and each would have its
own (Subtype,SubLen) tuple.

If that were to change, the two approaches are indeed very nicely
aligned. ASCII-art below:

  0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Type     |    Length     |    SubType    |    SubLen     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | IPv4MaskLen   |    SubType    |    SubLen     |  Reserved     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  6rdPrefixLen |    SubType    |    SubLen     |               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+               +
   |                                                               |
   +                                                               +
   |                     6rdPrefix                                 |
   +                                                               +
   |                                                               |
   +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               |   SubType     |    SubLen     |   SubType     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |    SubLen     | 6rdBRIPv4Address                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               |
   +-+-+-+-+-+-+-+-+

Any particular reason why the 6rdPrefixLen and 6rdPrefix are glued into
one blob in -04?

> The compromise allowed someone to *choose* to implement the TLV type
> generically OR a much less flexible parser capable of handling just thi=
s
> attribute without having to also support extensions.
>=20
> Some vendors already support the TLV concept as it is necessary for
> wimax. It is possible to configure the -04 draft today with just
> configuration in some systems already supporting TLV.

That's quite good to hear. As said above, the only thing I'm wondering
is why there's a glued datatype for prefixlen+preifx in one go.

> My understanding they were not willing to wait for extensions to move
> ahead with the 6rd draft.  In that light my view was something that
> looked like a "TLV" was better than the alternative fixed format.
>=20
> If this constraint is invalid and they are willing to wait allowing 6rd=

> draft to be dependent on extensions I agree it would certainly be the
> best approach for all concerned.

If you take the ASCII art above and add 16 bits of "reserved" after the
overall length, the rest of the attribute would even be bitwise aligned
with a later extended attribute (the space that an extended-attr would
fill with Extended-Type and Flags. Not sure if that's important or even
helpful for implementers though.

Greetings,

Stefan

--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


--------------enigD68C21658F4B6FEDB87032D3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7x6VEACgkQ+jm90f8eFWZvAwCfZpb5PV2vXCuk0zJrE31F6bX5
MN4An01S+fbZHWzguDtYDlSjw/Js5+1f
=shTM
-----END PGP SIGNATURE-----

--------------enigD68C21658F4B6FEDB87032D3--

From jiangsheng@huawei.com  Wed Dec 21 06:46:23 2011
Return-Path: <jiangsheng@huawei.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 494B911E8080 for <softwires@ietfa.amsl.com>; Wed, 21 Dec 2011 06:46:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.174
X-Spam-Level: 
X-Spam-Status: No, score=-6.174 tagged_above=-999 required=5 tests=[AWL=-0.175, BAYES_00=-2.599, J_CHICKENPOX_37=0.6, RCVD_IN_DNSWL_MED=-4]
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 Fg9YO0OROhoL for <softwires@ietfa.amsl.com>; Wed, 21 Dec 2011 06:46:22 -0800 (PST)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 1C2FD11E8073 for <softwires@ietf.org>; Wed, 21 Dec 2011 06:46:22 -0800 (PST)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LWK00LOO6CWX6@szxga04-in.huawei.com> for softwires@ietf.org; Wed, 21 Dec 2011 22:46:09 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LWK00CLC6CTMY@szxga04-in.huawei.com> for softwires@ietf.org; Wed, 21 Dec 2011 22:46:08 +0800 (CST)
Received: from szxeml205-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFV86536; Wed, 21 Dec 2011 22:46:07 +0800
Received: from SZXEML405-HUB.china.huawei.com (10.82.67.60) by szxeml205-edg.china.huawei.com (172.24.2.57) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 21 Dec 2011 22:46:02 +0800
Received: from SZXEML506-MBX.china.huawei.com ([169.254.4.239]) by szxeml405-hub.china.huawei.com ([10.82.67.60]) with mapi id 14.01.0323.003; Wed, 21 Dec 2011 22:46:00 +0800
Date: Wed, 21 Dec 2011 14:45:59 +0000
From: Sheng Jiang <jiangsheng@huawei.com>
In-reply-to: <4EF1E94D.2080006@restena.lu>
X-Originating-IP: [172.24.1.45]
To: Stefan Winter <stefan.winter@restena.lu>, Peter Deacon <peterd@iea-software.com>
Message-id: <5D36713D8A4E7348A7E10DF7437A4B92185856E5@SZXEML506-MBX.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-language: en-GB
Content-transfer-encoding: quoted-printable
Accept-Language: en-GB, zh-CN, en-US
Thread-topic: [Softwires] 6rd RADIUS attribute - grouped attributes
Thread-index: AQHMu9aQPTzd97i0lEik0CA/6hS55pXkZG3g//+BCYCAAFWJgIAAR0wAgAECspD//64HgIAAVI6AgAAXD4CAADi6gIAAj02H
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
References: <4EC1BD65.4040205@restena.lu> <4EEB1014.1030307@restena.lu> <5D36713D8A4E7348A7E10DF7437A4B9218583E44@SZXEML506-MBX.china.huawei.com> <4EF047A3.5090906@restena.lu> <4EF08F63.1010600@deployingradius.com> <alpine.WNT.2.00.1112200950300.2472@SMURF> <5D36713D8A4E7348A7E10DF7437A4B9218584374@SZXEML506-MBX.china.huawei.com> <alpine.WNT.2.00.1112201948210.2472@SMURF> <4EF1A65F.9080609@restena.lu> <alpine.WNT.2.00.1112210204010.2472@SMURF> <4EF1E94D.2080006@restena.lu>
Cc: "softwires@ietf.org" <softwires@ietf.org>, GuoDayong <guodayong@huawei.com>, Alan DeKok <aland@deployingradius.com>
Subject: Re: [Softwires] 6rd RADIUS attribute - grouped attributes
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Dec 2011 14:46:23 -0000

No, we don't want to wait for extensions draft. 6rd technical is actually i=
n a little bit emerge. We'd like to get this document published as soon as =
possible.

6rdPrefixLen and 6rdPrefix are bound together because the 6rdPrefixLen is e=
xplain hom many bits with in 6rdPrefix are real valid. They are actually on=
 parameter.

So, looks for me, the format in 04 version is already the best choice.

Cheers,

Sheng
________________________________________
From: Stefan Winter [stefan.winter@restena.lu]
Sent: 21 December 2011 22:12
To: Peter Deacon
Cc: Sheng Jiang; Alan DeKok; GuoDayong; Maglione Roberta; softwires@ietf.or=
g
Subject: Re: [Softwires] 6rd RADIUS attribute - grouped attributes

Hi,

> I don't think this is correct.  The extensions document describes a
> *data type* 'TLV'.  My suggestion simply leverages this type in the same
> way IPv4 Address and IPv6 prefix type from existing RFCs are already
> being leveraged.
>
> If you implement extensions RFC in the future your implementation
> supports the TLV data type giving you the ability to encode and decode
> this attribute with configuration dictionaries.  The wire format of
> IPv6-6rd-Configuration was intentionally made to be the same as a TLV.

Ah! I'm just looking at the -04 with this extra context. It's certainly
close. I think there's only one thing which is not inline: 6rdprefixLen
and 6rdPrefix immediately follow each other. In a version
compatible/analogous to the radius-extensions draft, the former would be
of type integer, the latter of type IPv6Address, and each would have its
own (Subtype,SubLen) tuple.

If that were to change, the two approaches are indeed very nicely
aligned. ASCII-art below:

  0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |      Type     |    Length     |    SubType    |    SubLen     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   | IPv4MaskLen   |    SubType    |    SubLen     |  Reserved     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |  6rdPrefixLen |    SubType    |    SubLen     |               |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+               +
   |                                                               |
   +                                                               +
   |                     6rdPrefix                                 |
   +                                                               +
   |                                                               |
   +               +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               |   SubType     |    SubLen     |   SubType     |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |    SubLen     | 6rdBRIPv4Address                              |
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |               |
   +-+-+-+-+-+-+-+-+

Any particular reason why the 6rdPrefixLen and 6rdPrefix are glued into
one blob in -04?

> The compromise allowed someone to *choose* to implement the TLV type
> generically OR a much less flexible parser capable of handling just this
> attribute without having to also support extensions.
>
> Some vendors already support the TLV concept as it is necessary for
> wimax. It is possible to configure the -04 draft today with just
> configuration in some systems already supporting TLV.

That's quite good to hear. As said above, the only thing I'm wondering
is why there's a glued datatype for prefixlen+preifx in one go.

> My understanding they were not willing to wait for extensions to move
> ahead with the 6rd draft.  In that light my view was something that
> looked like a "TLV" was better than the alternative fixed format.
>
> If this constraint is invalid and they are willing to wait allowing 6rd
> draft to be dependent on extensions I agree it would certainly be the
> best approach for all concerned.

If you take the ASCII art above and add 16 bits of "reserved" after the
overall length, the rest of the attribute would even be bitwise aligned
with a later extended attribute (the space that an extended-attr would
fill with Extended-Type and Flags. Not sure if that's important or even
helpful for implementers though.

Greetings,

Stefan

--
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education Nationale =
et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473=

From stefan.winter@restena.lu  Wed Dec 21 23:37:22 2011
Return-Path: <stefan.winter@restena.lu>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78BB011E80CB for <softwires@ietfa.amsl.com>; Wed, 21 Dec 2011 23:37:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.399
X-Spam-Level: 
X-Spam-Status: No, score=-2.399 tagged_above=-999 required=5 tests=[AWL=0.200,  BAYES_00=-2.599]
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 CSN37dBISyhV for <softwires@ietfa.amsl.com>; Wed, 21 Dec 2011 23:37:22 -0800 (PST)
Received: from smtprelay.restena.lu (smtprelay.restena.lu [IPv6:2001:a18:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id E6E1A11E80CA for <softwires@ietf.org>; Wed, 21 Dec 2011 23:37:21 -0800 (PST)
Received: from smtprelay.restena.lu (localhost [127.0.0.1]) by smtprelay.restena.lu (Postfix) with ESMTP id 9215D10A08; Thu, 22 Dec 2011 08:37:20 +0100 (CET)
Received: from [IPv6:2001:a18:1:8:3427:d2f8:b1a4:57de] (unknown [IPv6:2001:a18:1:8:3427:d2f8:b1a4:57de]) by smtprelay.restena.lu (Postfix) with ESMTPS id 7F13C10A01; Thu, 22 Dec 2011 08:37:20 +0100 (CET)
Message-ID: <4EF2DE99.7050207@restena.lu>
Date: Thu, 22 Dec 2011 08:39:05 +0100
From: Stefan Winter <stefan.winter@restena.lu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Peter Deacon <peterd@iea-software.com>
References: <4EC1BD65.4040205@restena.lu> <4EEB1014.1030307@restena.lu> <5D36713D8A4E7348A7E10DF7437A4B9218583E44@SZXEML506-MBX.china.huawei.com> <4EF047A3.5090906@restena.lu> <4EF08F63.1010600@deployingradius.com> <alpine.WNT.2.00.1112200950300.2472@SMURF> <5D36713D8A4E7348A7E10DF7437A4B9218584374@SZXEML506-MBX.china.huawei.com> <alpine.WNT.2.00.1112201948210.2472@SMURF> <4EF1A65F.9080609@restena.lu> <alpine.WNT.2.00.1112210204010.2472@SMURF> <4EF1E94D.2080006@restena.lu> <alpine.WNT.2.00.1112210807180.2472@SMURF>
In-Reply-To: <alpine.WNT.2.00.1112210807180.2472@SMURF>
X-Enigmail-Version: 1.3.4
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig8738D1EEF24D7ECB9E560788"
X-Virus-Scanned: ClamAV
Cc: softwires@ietf.org, Alan DeKok <aland@deployingradius.com>, GuoDayong <guodayong@huawei.com>
Subject: Re: [Softwires] 6rd RADIUS attribute - grouped attributes
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Dec 2011 07:37:22 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig8738D1EEF24D7ECB9E560788
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

>> Any particular reason why the 6rdPrefixLen and 6rdPrefix are glued int=
o
>> one blob in -04?
>=20
> If you ignore the 6rd references it is describing prefix data type
> defined a decade back in RFC3162 2.3 (Framed-IPv6-Prefix).  Logically i=
t
> counts as one field.

Framed-IPv6-Prefix and your data type are different. Frames-IPv6-Prefix
is of variable length, and requires to insert only those parts of the
IPv6 address which are relevant for the prefix length. You can pad with
more zeroes if you feel like it, but don't have to. (That in itself is a
rather inconvenient construct, and I like yours more than that one
actually.) Sure, if you opt to always pad with zeroes to the full 128
bit, even if not necessary, you get the same fixed length as your
datatype requires.

Still, you have introduced a new data type
"almost-but-not-quite-Framed-IPv6-Address".

If you consider it a good idea, then fine - I'm sure you have much more
experience in terms of actual implementations than I do. From a design
point of view, I'd consider a pair of (int,IPv6-Address) cleaner than an
implicit struct. The "belong together" can be expressed in the RFC as
"both of the sub-TLVs have to appear exactly once".

Greetings,

Stefan Winter

--=20
Stefan WINTER
Ingenieur de Recherche
Fondation RESTENA - R=E9seau T=E9l=E9informatique de l'Education National=
e et
de la Recherche
6, rue Richard Coudenhove-Kalergi
L-1359 Luxembourg

Tel: +352 424409 1
Fax: +352 422473


--------------enig8738D1EEF24D7ECB9E560788
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7y3p0ACgkQ+jm90f8eFWYpGQCfbzOF5x7eHX3vT+07b6VIMx4d
sG4Ani3qsD3V8grcgaBKX9lgMsmA6L8i
=Fj/8
-----END PGP SIGNATURE-----

--------------enig8738D1EEF24D7ECB9E560788--

From despres.remi@laposte.net  Thu Dec 29 10:07:57 2011
Return-Path: <despres.remi@laposte.net>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81E7521F8AFC for <softwires@ietfa.amsl.com>; Thu, 29 Dec 2011 10:07:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 tWvra4mV1a7P for <softwires@ietfa.amsl.com>; Thu, 29 Dec 2011 10:07:56 -0800 (PST)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.82]) by ietfa.amsl.com (Postfix) with ESMTP id 86F5D21F8AF9 for <softwires@ietf.org>; Thu, 29 Dec 2011 10:07:55 -0800 (PST)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2409.sfr.fr (SMTP Server) with ESMTP id CB27B70004ED for <softwires@ietf.org>; Thu, 29 Dec 2011 19:07:54 +0100 (CET)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2409.sfr.fr (SMTP Server) with ESMTP id 9EA1670004EC for <softwires@ietf.org>; Thu, 29 Dec 2011 19:07:50 +0100 (CET)
X-SFR-UUID: 20111229180754649.9EA1670004EC@msfrf2409.sfr.fr
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <despres.remi@laposte.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Thu, 29 Dec 2011 19:07:50 +0100
Message-Id: <87FFBCD9-AD17-45AB-A00C-6FCA16CBF70C@laposte.net>
To: Softwires WG <softwires@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
X-sfr-mailing: LEGIT
Subject: [Softwires] 4rd-U - The Unified stateless solution for IPv4 Residual Deployment via IPv6
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Dec 2011 18:07:57 -0000

Hello, all,

 The new version of the 4rd-U draft has just been posted.=20
It is available at www.ietf.org/id/draft-despres-softwire-4rd-u-02.txt.

 As previously announced, it should be a starting point for =
contributions from those who believe that, for stateless deployments =
residual IPv4 via IPv6, one standard would be better than two.


 It is written a self-contained specification, in principle sufficient =
for compatible implementations, but has been too rapidly written to be =
without a number of inadequacies.
 If you are interested in becoming contributor, please let me know.

 Clarification questions are most welcome from anyone, even if not =
interested in becoming contributor.

 Best wishes for a happy new year.

RD




Abstract

   This document specifies an automatic tunneling mechanism tailored for
   residual deployment of public IPv4 via IPv6 networks (the reverse of
   6rd whose purpose is rapid deployment of IPv6 via IPv4).  In order to
   deal with the IPv4-address shortage, customers can be assigned shared
   IPv4 addresses with statically assigned restricted port sets.
   Operation is stateless, with no per-customer state in network nodes.

   4rd-U unifies in a synthesis features of double-translation-based
   solutions (in particular compatibility with some IPv6-only middle-box
   tools inside IPv6 networks), and those of IP-in-IP encapsulation
   solutions (in particular complete end-to-end transparency to IPv4
   packets).  It is proposed as a unified standard replacing the two
   standards that are otherwise envisaged.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Requirements Language  . . . . . . . . . . . . . . . . . . . .  3
   3.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4.  The 4rd-U Model  . . . . . . . . . . . . . . . . . . . . . . .  5
   5.  Protocol Specification . . . . . . . . . . . . . . . . . . . .  6
     5.1.  Reversible Header Mapping from IPv4 to IPv6  . . . . . . .  6
     5.2.  Mappings Rules . . . . . . . . . . . . . . . . . . . . . . 10
     5.3.  Mappings from IPv6 prefix to Residual-IPv4 prefix  . . . . 10
     5.4.  Mapping from Residual-IPv4 address to IPv6 address . . . . 12
       5.4.1.  =46rom Residual-IPv4 address to IPv6 prefix  . . . . . . =
12
       5.4.2.  =46rom IPv6 prefix to IPv6 address . . . . . . . . . . . =
14
     5.5.  Fragmentation Considerations . . . . . . . . . . . . . . . 16
       5.5.1.  Ports of Fragments sent to Shared-Address CEs  . . . . 17
       5.5.2.  Datagram-Identification Updates in BRs . . . . . . . . 17
     5.6.  Translating Tunnel-Generated ICMPv6 into ICMPv4  . . . . . 17
     5.7.  Provisioning 4rd-U parameters to CEs . . . . . . . . . . . 18
     5.8.  BR and CE Behaviors  . . . . . . . . . . . . . . . . . . . 19
   6.  Use-Case Examples  . . . . . . . . . . . . . . . . . . . . . . 25
     6.1.  Moving from IPv4-only to IPv6 and Residual IPv4  . . . . . 25
     6.2.  Residual-IPv4 Service via a Third-Party IPv6 Network . . . 27
     6.3.  Adding Residual IPv4 to an IPv6-only network . . . . . . . 28
     6.4.  IPv6 and Residual-IPv4 added to a net-10 network . . . . . 29
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 29
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 30
   9.  Contributors and Acknowledgements  . . . . . . . . . . . . . . 31
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 31
     10.2. Informative References . . . . . . . . . . . . . . . . . . 31
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 34=
