Re: [CCAMP] I-D Action: draft-ietf-ccamp-rwa-wson-encode-16.txt

Greg Bernstein <gregb@grotto-networking.com> Tue, 11 September 2012 20:22 UTC

Return-Path: <gregb@grotto-networking.com>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E3E521F86B2 for <ccamp@ietfa.amsl.com>; Tue, 11 Sep 2012 13:22:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2J1hhPN13HnV for <ccamp@ietfa.amsl.com>; Tue, 11 Sep 2012 13:22:24 -0700 (PDT)
Received: from smtp.webfaction.com (mail6.webfaction.com [74.55.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 0007421F871D for <ccamp@ietf.org>; Tue, 11 Sep 2012 13:22:23 -0700 (PDT)
Received: from [10.0.0.4] (c-24-7-86-163.hsd1.ca.comcast.net [24.7.86.163]) by smtp.webfaction.com (Postfix) with ESMTP id B31AE20781E8; Tue, 11 Sep 2012 15:22:22 -0500 (CDT)
Message-ID: <504F9D7C.2040302@grotto-networking.com>
Date: Tue, 11 Sep 2012 13:22:20 -0700
From: Greg Bernstein <gregb@grotto-networking.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: "Giovanni Martinelli (giomarti)" <giomarti@cisco.com>
References: <20120816231453.15922.4595.idtracker@ietfa.amsl.com> <503273AE.8000700@labn.net> <50327B42.2010108@grotto-networking.com> <50465D6B.1060809@grotto-networking.com> <504661AC.3040109@labn.net> <504769D3.5020704@grotto-networking.com> <50476D56.6000108@labn.net> <7D9D17F0-3B67-41CF-8484-8EA7BE3B610D@cisco.com>
In-Reply-To: <7D9D17F0-3B67-41CF-8484-8EA7BE3B610D@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "<ccamp@ietf.org>" <ccamp@ietf.org>
Subject: Re: [CCAMP] I-D Action: draft-ietf-ccamp-rwa-wson-encode-16.txt
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Tue, 11 Sep 2012 20:22:25 -0000

Hi Giovanni we updated the WSON encode draft back on September 5th to 
put the interface class encoding into the draft. This was in response to 
the question raised by Lou in a August 20th email.  Lou, Deborah and OIC 
draft authors do we need to change this back?
Please let us know ASAP as we are trying to get all the WSON drafts into 
last call and this seems to be the last outstanding issue.

Best Regards
Greg
On 9/10/2012 10:02 AM, Giovanni Martinelli (giomarti) wrote:
> Hi Greg, Lou,
>
> having a quick look to wson draft update I generally agree on content (as expected) what I'm wandering if it worth moving the interface class encoding within  the draft-ieft-ccamp-rwa-wson-encode.
>
> Here an alternate proposal on the table:
> leave the generic OIC container definition within current wson-encode draft and put specific OIC encoding (with related ITU references) in a separate draft (which could be a new version of draft-martinelli-wson-interface-class or a brand new draft). This separation will probably allow finalizing the wson-info-model and wson-encoding separately from specific OIC content (so we'll collect most updated ITU references as already mentioned we still miss few of them.
>
>
> I guess is for  WG chairs to decide.
>
> If we stay with current doc splitting I'll go for a detailed review on latest updates. Sorry for raising it with a bit of delay but, just want to make sure was an option consciously avoided.
>
> Cheers
> G
>
>
>
> On Sep 5, 2012, at 17:18 , Lou Berger wrote:
>
>> Greg,
>> 	Okay.  Based on the meeting/discussions and the draft, I had expected
>> there was sufficient consensus & text to work from.  As editors, you're
>> free to document your perspective on consensus as works best for you.
>> Let us (chairs) know if you need assistance and we'll figure out how to
>> help.
>>
>> Lou
>>
>> On 9/5/2012 11:03 AM, Greg Bernstein wrote:
>>> Hi Lou, I'll look at that text.  I added to our document what the QIC
>>> authors suggested.  Maybe they were planning something else?
>>> Greg
>>> On 9/4/2012 1:16 PM, Lou Berger wrote:
>>>> Greg,
>>>> 	Why not start with the concrete proposal that's already on the table,
>>>> i.e., the text in
>>>> http://tools.ietf.org/html/draft-martinelli-wson-interface-class-03?
>>>> Frankly, I'm not sure why that text wasn't incorporated in the first
>>>> place and figured I missed something -- which is why I sent my earlier mail.
>>>>
>>>> Lou
>>>>
>>>> On 9/4/2012 3:58 PM, Greg Bernstein wrote:
>>>>> Hi Lou and CCAMPers.  I haven't heard anything on this issue in two
>>>>> weeks.  One simple way out of this would be to just use a variable
>>>>> length field for the OIC using the ITU-T application string rather than
>>>>> a fixed 64 bit field.
>>>>> If the ITU-T comes up with another specific encoding (64 bit or
>>>>> otherwise) in the future we can make sure to have a place holder.
>>>>> However, currently the ITU-T only defines application strings for this
>>>>> purpose.
>>>>>
>>>>> If I don't hear any other suggestions in two weeks, I'll make the change
>>>>> to incorporate variable length strings and keep place holders for
>>>>> defining fixed length fields.  Then we can move this and related WSON
>>>>> documents into last call.
>>>>>
>>>>> Best Regards
>>>>> Greg B.
>>>>>
>>>>> On 8/20/2012 11:00 AM, Greg Bernstein wrote:
>>>>>> Optical Interface Class draft authors can you respond to Lou/List.
>>>>>> Let me know if we need to update the text.  We are trying to get this
>>>>>> into last call.
>>>>>> Best Regards
>>>>>> Greg
>>>>>> On 8/20/2012 10:28 AM, Lou Berger wrote:
>>>>>>> Authors,
>>>>>>>
>>>>>>> I see that the draft says:
>>>>>>>        In case of ITU Application Code, there should be a mapping between
>>>>>>>        the string defining the application code and the 64 bits number
>>>>>>>        implementing the optical interface class.
>>>>>>>
>>>>>>> Where is this mapping defined?  Doesn't it have to be either in this
>>>>>>> draft or a normative reference?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Lou
>>>>>>>
>>>>>>> On 8/16/2012 7:14 PM, internet-drafts@ietf.org wrote:
>>>>>>>> A New Internet-Draft is available from the on-line Internet-Drafts
>>>>>>>> directories.
>>>>>>>>    This draft is a work item of the Common Control and Measurement
>>>>>>>> Plane Working Group of the IETF.
>>>>>>>>
>>>>>>>>      Title           : Routing and Wavelength Assignment Information
>>>>>>>> Encoding for Wavelength Switched Optical Networks
>>>>>>>>      Author(s)       : Greg M. Bernstein
>>>>>>>>                             Young Lee
>>>>>>>>                             Dan Li
>>>>>>>>                             Wataru Imajuku
>>>>>>>>      Filename        : draft-ietf-ccamp-rwa-wson-encode-16.txt
>>>>>>>>      Pages           : 33
>>>>>>>>      Date            : 2012-08-16
>>>>>>>>
>>>>>>>> Abstract:
>>>>>>>>      A wavelength switched optical network (WSON) requires that certain
>>>>>>>>      key information elements are made available to facilitate path
>>>>>>>>      computation and the establishment of label switching paths (LSPs).
>>>>>>>>      The information model described in "Routing and Wavelength
>>>>>>>>      Assignment Information for Wavelength Switched Optical Networks"
>>>>>>>>      shows what information is required at specific points in the WSON.
>>>>>>>>      Part of the WSON information model contains aspects that may be of
>>>>>>>>      general applicability to other technologies, while other parts are
>>>>>>>>      fairly specific to WSONs.
>>>>>>>>
>>>>>>>>      This document provides efficient, protocol-agnostic encodings for
>>>>>>>>      the WSON specific information elements. It is intended that
>>>>>>>>      protocol-specific documents will reference this memo to describe
>>>>>>>> how
>>>>>>>>      information is carried for specific uses. Such encodings can be
>>>>>>>> used
>>>>>>>>      to extend GMPLS signaling and routing protocols. In addition these
>>>>>>>>      encodings could be used by other mechanisms to convey this same
>>>>>>>>      information to a path computation element (PCE).
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> The IETF datatracker status page for this draft is:
>>>>>>>> https://datatracker.ietf.org/doc/draft-ietf-ccamp-rwa-wson-encode
>>>>>>>>
>>>>>>>> There's also a htmlized version available at:
>>>>>>>> http://tools.ietf.org/html/draft-ietf-ccamp-rwa-wson-encode-16
>>>>>>>>
>>>>>>>> A diff from the previous version is available at:
>>>>>>>> http://www.ietf.org/rfcdiff?url2=draft-ietf-ccamp-rwa-wson-encode-16
>>>>>>>>
>>>>>>>>
>>>>>>>> Internet-Drafts are also available by anonymous FTP at:
>>>>>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> CCAMP mailing list
>>>>>>>> CCAMP@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/ccamp
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> CCAMP mailing list
>>>>>>> CCAMP@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/ccamp
>>>>>>>
>>>>>>>
>>>
>> _______________________________________________
>> CCAMP mailing list
>> CCAMP@ietf.org
>> https://www.ietf.org/mailman/listinfo/ccamp
>
>


-- 
===================================================
Dr Greg Bernstein, Grotto Networking (510) 573-2237