Re: [Softwires] Unified proposal for stateless IPv4 Residual Deployments (4rd-U) - Contributors?

Alain Durand <> Tue, 29 November 2011 17:35 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1DD2121F86A5 for <>; Tue, 29 Nov 2011 09:35:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -106.299
X-Spam-Status: No, score=-106.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id TB4-wyQEwm6N for <>; Tue, 29 Nov 2011 09:35:07 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 1D25621F8548 for <>; Tue, 29 Nov 2011 09:35:00 -0800 (PST)
Received: from ([]) (using TLSv1) by ([]) with SMTP ID; Tue, 29 Nov 2011 09:35:00 PST
Received: from ([fe80::c821:7c81:f21f:8bc7]) by ([fe80::88f9:77fd:dfc:4d51%11]) with mapi; Tue, 29 Nov 2011 09:33:39 -0800
From: Alain Durand <>
To: Rémi Després <>
Date: Tue, 29 Nov 2011 09:33:38 -0800
Thread-Topic: [Softwires] Unified proposal for stateless IPv4 Residual Deployments (4rd-U) - Contributors?
Thread-Index: AcyuvQfmF2YpBsRBSF65BS51aPUWjg==
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Softwires WG <>
Subject: Re: [Softwires] Unified proposal for stateless IPv4 Residual Deployments (4rd-U) - Contributors?
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: softwires wg discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 29 Nov 2011 17:35:08 -0000


Thank you for starting this discussion on the mailing list.
Let me clarify my chair perspective on 4rd-u

You brought this to the Taipei meeting as an attempt to 'unify' encapsulation and translation.
I have always been of the opinion that fewer options are better, so I support attempts at converging the solution space.

The caveat is, if the proponents of the other solutions are not inclined to adopt the new 'unified' scheme,
we end up with just one more incompatible solution.

Now, I have observed during the Taipei meeting a certain level of interest to understand better the 4rd-u proposal,
as some of technical characteristics were not clear to the majority of the working group.

WIth that and the previous point in mind, I'd like to encourage you to keep working on 4rd-u and come back next meeting
in Paris. I hope by them those technical characteristics will be clearly understood by the working group and we could
form a wg consensus  as to whether this work is useful or distracting.


On Nov 29, 2011, at 10:31 AM, Rémi Després wrote:

> Hi all,
> Some IETF-82 participants have expressed wishes to pursue the work on 4rd-U. Alain mentioned to me he would be interested, as Softwire chair, he would be interested in having at IETF 83 not only the MAP proposal (with its Encapsulation and Translation variants), but also a 4rd-U proposal. He also said I would be welcome to lead the effort. 
> To start the work, I therefore plan to edit in December a new version of the 4rd-U draft. It will be in particular updated  to delete the Max-PSID/Max-EA-bits mechanism.
> For the discussion starting from it, the plan is to have a 4rd-U mailing list on the IETF site.
> On this list, all those wishing to contribute to the 4rd-U proposal will be invited to participate (including, of course, those who are already interested in MAP, both approaches remaining open at this stage).
> Please le me know if you plan to contribute.
> For those who attended the Softwire session in Taipei, please note that the serious objection against 4rd-U expressed by several participants during the meeting has been, soon after, acknowledged to be invalid (
> Also, other (less important) objections have been answered in, without reaction so far. 
> Best regards,
> RD
> _______________________________________________
> Softwires mailing list