Re: [CCAMP] AD review of draft-ietf-ccamp-rwa-wson-encode

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

Specifically to the Interface class here below… 

In the initial draft merged to this one there was the usage of OUI however (I guess after chatting with Lou) we decided to remove any encoding when the Interface class is not standard. 
In term of semantic the protcol does not need to decode the Interface class since it only assess the interface compatibility if two interfaces has a class value that match two interfaces cann be connected.  

Having saying that I don’t have strong opinion in adding the OUI or leaving room for maybe future public interfaces database. For sure there’s a need to leave room for specific compatibility assesment since there optical multivendor compatibility has been already demonstrated. 

hope this help …

Cheers
G


On 21 Jan 2015, at 21:57, Adrian Farrel <[e-mail]> wrote:

>>> 
>>> Section 4.1
>>> How do I interpret a Vendor-Specific Application Code? Is there an OUI
>>> I'm missing?
>> 
>> [YOUNG] Not sure if I understood this question. What is "OUI"?
> 
> http://en.wikipedia.org/wiki/Organizationally_unique_identifier
> http://www.iana.org/assignments/ieee-802-numbers/ieee-802-numbers.xhtml#ieee-802
> -numbers-2
> 
> Or perhaps an Enterprise Number
> http://www.iana.org/assignments/enterprise-numbers/enterprise-numbers
> 
> The question is:
> 
> You have sections 4.1.1 through 4.1.4 to tell me how to interpret the Optical
> Interface Class field when it contains an ITU-T Application Mapping.
> When I received s=0 and OI=1 it means that the Optical Interface Class contains
> a "Vendor Specific Optical Interface Class".
> How do I interpret that Optical Interface Class?
> Which vendor does it apply to?
> Is there some information elsewhere that gives me a clue as to which vendor has
> encoded the information?
> Or is the information supposed to be encoded in the Optical Interface Class,
> perhaps as the first 48 bits?
> Or am I supposed to know by context?