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

["Giovanni Martinelli (giomarti)" <[e-mail]>]

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, [e-mail] 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
>>>>>>> [e-mail]
>>>>>>> https://www.ietf.org/mailman/listinfo/ccamp
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>> _______________________________________________
>>>>>> CCAMP mailing list
>>>>>> [e-mail]
>>>>>> https://www.ietf.org/mailman/listinfo/ccamp
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 
>> 
> _______________________________________________
> CCAMP mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/ccamp