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

Ross Chandler <ross@eircom.net> Tue, 22 April 2014 20:08 UTC

Return-Path: <ross@eircom.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 292C41A019F for <v6ops@ietfa.amsl.com>; Tue, 22 Apr 2014 13:08:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.824
X-Spam-Level:
X-Spam-Status: No, score=-0.824 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.272] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UdlRwui3GPtI for <v6ops@ietfa.amsl.com>; Tue, 22 Apr 2014 13:08:30 -0700 (PDT)
Received: from mail19.svc.cra.dublin.eircom.net (mail19.svc.cra.dublin.eircom.net [159.134.118.218]) by ietfa.amsl.com (Postfix) with SMTP id D255E1A016E for <v6ops@ietf.org>; Tue, 22 Apr 2014 13:08:27 -0700 (PDT)
Received: (qmail 46500 messnum 998013 invoked from network[213.94.190.12/avas01.vendorsvc.cra.dublin.eircom.net]); 22 Apr 2014 20:08:21 -0000
Received: from avas01.vendorsvc.cra.dublin.eircom.net (213.94.190.12) by mail19.svc.cra.dublin.eircom.net (qp 46500) with SMTP; 22 Apr 2014 20:08:21 -0000
Received: from mac1.home.ross.net ([159.134.196.35]) by avas01.vendorsvc.cra.dublin.eircom.net with Cloudmark Gateway id t88D1n0040mJ9Tz0188Kz4; Tue, 22 Apr 2014 21:08:21 +0100
From: Ross Chandler <ross@eircom.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-Id: <B81CE1EC-D5E7-4ED2-A884-DC379DFF8AFE@eircom.net>
Date: Tue, 22 Apr 2014 21:08:18 +0100
To: v6ops@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/ERXSHKj1KlFL0WQkAF_aKdVuFV8
Subject: [v6ops] draft-byrne-v6ops-clatip-01
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 22 Apr 2014 20:08:34 -0000

Would also like to see this advance.

Ross


-----Original Message-----
From: v6ops [mailto:v6ops-bounces at ietf.org] On Behalf Of Fred Baker (fred)
Sent: 21 April 2014 17:16
To: V6 Ops List
Subject: [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 <cuiyong at tsinghua.edu.cn> 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 Eventually. 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) <fred at cisco.com> 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 . <cb.list6 at gmail.com> wrote:
>> 
>>> *fixing the softwire chair email address since it bounced.
>>> 
>>> On Fri, Apr 4, 2014 at 5:44 PM, Fred Baker (fred) <fred at cisco.com> wrote:
>>>> 
>>>> On Apr 4, 2014, at 6:34 AM, Cb B <cb.list6 at gmail.com> 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 192.0.0.0/29.  
>>>> 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