Re: [v6ops] draft-byrne-v6ops-clatip-01

<> Wed, 23 April 2014 08:11 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 4BBDB1A013A for <>; Wed, 23 Apr 2014 01:11:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.549
X-Spam-Status: No, score=-1.549 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id KMIwrhHmEyns for <>; Wed, 23 Apr 2014 01:11:00 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 654F81A00CF for <>; Wed, 23 Apr 2014 01:11:00 -0700 (PDT)
Received: from (unknown [xx.xx.xx.198]) by (ESMTP service) with ESMTP id BE08AC07F0; Wed, 23 Apr 2014 10:10:53 +0200 (CEST)
Received: from (unknown []) by (ESMTP service) with ESMTP id 72A5E180063; Wed, 23 Apr 2014 10:10:50 +0200 (CEST)
Received: from ([]) by ([]) with mapi; Wed, 23 Apr 2014 10:10:50 +0200
To: "Fred Baker (fred)" <>, V6 Ops List <>
Date: Wed, 23 Apr 2014 10:10:49 +0200
Thread-Topic: draft-byrne-v6ops-clatip-01
Thread-Index: AQHPXX0GoCnfuCMMckahK1B0I3gQqZse2v2g
Message-ID: <>
References: <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: fr-FR
Content-Language: fr-FR
acceptlanguage: fr-FR
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-PMX-Version:, Antispam-Engine:, Antispam-Data: 2014.4.23.61819
Subject: Re: [v6ops] draft-byrne-v6ops-clatip-01
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 23 Apr 2014 08:11:09 -0000

This proposition is useful for IPv6-only design and I support its adoption. 

-----Message d'origine-----
De : v6ops [] De la part de Fred Baker (fred)
Envoyé : lundi 21 avril 2014 18:16
À : V6 Ops List
Objet : [v6ops] draft-byrne-v6ops-clatip-01

Following up from the recent meeting.

We discussed clatip. The outcome was that we wanted to know what softwire wanted done with it, and I took the action to ask. 

The response from the softwire chairs was that they wanted to consider the draft there, and advance it from there. However, it appears to be bottlenecked. So, the softwire chairs have stepped back.

I want the opinion of v6ops. Do we need this, or not? If we need this, we should adopt it, and then (I think) go to an immediate WGLC and potentially advance it. If it’s not needed, we should say it is not needed.

Please reply in this thread.

On Apr 21, 2014, at 5:55 AM, Yong Cui <> wrote:

> Hi Fred,
> Thanks for your email and reminding.
> You are right that we are glad to take this work in Softwire as we discussed in March. However, for some reasons we need to focus on MAP package right now. There is the consensus that Softwire will NOT take any new work before we submit the MAP package to IESG. There are even some other wg items blocked in Softwire at this moment. We are trying to solve the MAP issues asap and accelerate the process. But I'm afraid we still need some time.
> So if you'd like to take this work in v6ops, please do so. Otherwise, we still need to wait for some time before taking it in Softwire.
> Thanks for understanding and let us know your decision.
> Yong
> On 2014-4-19, at 上午12:23, Fred Baker (fred) <> wrote:
>> Softwire chairs:
>> In March, you indicated that you wanted to progress this in softwire. The authors haven’t heard from you and are looking for guidance. Pick one: do you want it, or do you want it done for you?
>> Fred
>> On Apr 18, 2014, at 4:55 AM, TheIpv6guy . <> wrote:
>>> *fixing the softwire chair email address since it bounced.
>>> On Fri, Apr 4, 2014 at 5:44 PM, Fred Baker (fred) <> wrote:
>>>> On Apr 4, 2014, at 6:34 AM, Cb B <> wrote:
>>>> Hello folks,
>>>> No follow-up in a week. I assume the below explanation and 
>>>> exisiting text are ok.
>>>> To restate, this I-D simply generalizes the scope of  
>>>> There is no guidance on how specific addresses may be used. It is 
>>>> assumed the deploying party will not cause a conflict on the host 
>>>> by assiging the same address to the host multipls times.... as that 
>>>> is a general ip configuration rule.
>>>> I will ask v6ops to accept this i-d and direct them to this thread 
>>>> to see the softwire view.
>>>> My understanding is that softwires wants to progress this one. I 
>>>> guess I’d like to hear from the softwires chairs before bringing it back.
>>> Fred,
>>> It has been 14 days since your  email.  I am not sure if you sent 
>>> the email to the wrong address of fixed it.  Either way, i would 
>>> like to make progress on this I-D in v6ops since this I-D is about a 
>>> generalized approach that exceeds the bounds of softwires.  This has 
>>> also been presented twice in person to v6ops.
>>> Cameron
>>>> CB
>>>> On Mar 29, 2014 4:59 AM, "Cb B" <> wrote:
>>>>> On Thu, Mar 27, 2014 at 3:38 PM, Dave Thaler 
>>>>> <>
>>>>> wrote:
>>>>>>> -----Original Message-----
>>>>>>> From: Softwires [] On Behalf Of 
>>>>>>> Cb B
>>>>>>> Sent: Thursday, March 27, 2014 10:58 AM
>>>>>>> To:
>>>>>>> Subject: [Softwires] draft-byrne-v6ops-clatip-01
>>>>>>> Hi Softwires,
>>>>>>> Ales presented draft-byrne-v6ops-clatip-01 in softwires at the 
>>>>>>> last IETF meeting.
>>>>>>> I am attempting to have this I-D adopted by v6ops, but v6ops 
>>>>>>> requested feedback from softwires first.
>>>>>>> Pertaining to the minutes, i would like to address some topics 
>>>>>>> to make sure it is ok  for v6ops to move forward with adoption
>>>>>>> ire.html
>>>>>>> The addresses, both in DS-lite and 464xlat, never appears on the 
>>>>>>> wire so there is no chance of overlap or collision.
>>>>>> Disagree, that conclusion doesn't follow (and in my experience 
>>>>>> it's wrong).
>>>>>> Overlap/collision happens when there are two interfaces on the same host
>>>>>> (even if they're not in use simultaneously).   The collisions can affect
>>>>>> the routing table (if the host implements in such a way), ACLs 
>>>>>> like in host firewall policies and such, and various application-layer uses.
>>>>> Ah, i see your point.  If the host is itself both a B4 and a CLAT 
>>>>> at the same time, then this collision may occur within the host, 
>>>>> not on the wire.
>>>>>> It's fine to specify use as the default range (e.g. for 464xlat 
>>>>>> or
>>>>>> DS-lite) but
>>>>>> important to never constrain it to only that range, assuming the 
>>>>>> range is made non-DS-lite specific.
>>>>>> -Dave
>>>>> Is there such a constraint that would cause a problem?
>>>>> Looking at RFC6333 and draft-byrne-v6ops-clatip, i see that 
>>>>> RFC6333 says the B4 SHOULD use  To a rational person, a 
>>>>> good reason to not use is that it is in use for a CLAT 
>>>>> interface on the same host, which fits with the SHOULD wording.
>>>>> Is there some text that you could suggest that may clarify this 
>>>>> situation in draft-byrne-v6ops-clatip or is it ok for v6ops to 
>>>>> adopt as-is?  As it stands, the I-D simply says that 
>>>>> will be generalized without making any further statements how 
>>>>> addresses may be used within that range.
>>>>> CB
>>>> ------------------------------------------------------
>>>> 8 issues in virtual infrastructure
>> ------------------------------------------------------
>> 8 issues in virtual infrastructure

8 issues in virtual infrastructure


Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.