Re: [CCAMP] Generalized Labels for the Flexi-Grid in LSC Label Switching Routers

Curtis Villamizar <curtis@ipv6.occnc.com> Fri, 31 January 2014 17:01 UTC

Return-Path: <curtis@ipv6.occnc.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65A111A0442 for <ccamp@ietfa.amsl.com>; Fri, 31 Jan 2014 09:01:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.837
X-Spam-Level:
X-Spam-Status: No, score=-1.837 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_52=0.6, RP_MATCHES_RCVD=-0.535, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 eLaPLp6kpchu for <ccamp@ietfa.amsl.com>; Fri, 31 Jan 2014 09:01:41 -0800 (PST)
Received: from maildrop2.v6ds.occnc.com (maildrop2.v6ds.occnc.com [IPv6:2001:470:88e6:3::232]) by ietfa.amsl.com (Postfix) with ESMTP id 6158F1A0576 for <ccamp@ietf.org>; Fri, 31 Jan 2014 09:01:41 -0800 (PST)
Received: from harbor3.ipv6.occnc.com (harbor3.v6ds.occnc.com [IPv6:2001:470:88e6:3::239]) (authenticated bits=128) by maildrop2.v6ds.occnc.com (8.14.7/8.14.7) with ESMTP id s0VH1ajh081684; Fri, 31 Jan 2014 12:01:36 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201401311701.s0VH1ajh081684@maildrop2.v6ds.occnc.com>
To: Lou Berger <lberger@labn.net>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Thu, 30 Jan 2014 20:28:52 -0500." <52EAFC54.1000507@labn.net>
Date: Fri, 31 Jan 2014 12:01:36 -0500
Cc: 'CCAMP' <ccamp@ietf.org>, Iftekhar Hussain <IHussain@infinera.com>
Subject: Re: [CCAMP] Generalized Labels for the Flexi-Grid in LSC Label Switching Routers
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp/>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jan 2014 17:01:43 -0000

In message <52EAFC54.1000507@labn.net>
Lou Berger writes:
 
> Iftekhar,
>  
> Speaking purely from a process standpoint: adoption is the start of
> work on a topic, not a codification of an end state.  This is why we
> typically ask if a document reflects a "good starting point for WG
> activity" when discussing the adoption of a draft.
>  
> Again, speaking from a general perspective, I certainly don't think
> the process requires discussion/adoption to be blocked while a
> framework (or even requirement) document has some open points.
>  
> Lou


Lou, Iftekhar,

I don't see this as a request to block progress.

Perhaps Iftekhar (or someone) could first outline the control plane
requirements and "other areas" that need to be addressed and suggest
text to address them in the framework.

Curtis


> On January 30, 2014 6:26:40 PM Iftekhar Hussain <IHussain@infinera.com>
> wrote:
>  
> > Hi Dan,
> >
> > Thanks for the update. In my view, there are number of areas which still 
> > needs to be addressed in the framework document (e.g., control plane 
> > requirements) before we move toward solution drafts.
> >
> > BR,
> > Iftekhar
> > -----Original Message-----
> > From: Daniel King [mailto:daniel@olddog.co.uk] Sent: Wednesday, January 29, 
> > 2014 9:06 AM
> > To: 'CCAMP'
> > Subject: [CCAMP] Generalized Labels for the Flexi-Grid in LSC Label 
> > Switching Routers
> >
> > Hi CCAMP'rs,
> >
> > The authors are planning a revision of this I-D before London, but the only 
> > changes will be the addition of an Implementation Status section as per 
> > RFC6982.
> >
> > It seems to us that this I-D is stable and that there are no further 
> > technical issues. The label format documented in the I-D has been picked up 
> > by the RSVP-TE extensions draft and the ongoing OSPF work.
> > We would like to take this opportunity to solicit feedback from the working
> > group:
> >
> > - Are there any changes you would like to see in the draft? - Are you happy 
> > with the label format described? - What do you think the next steps should 
> > be for this draft?
> >
> > Thanks,
> > Dan (for the authors)