Re: [CCAMP] Poll on ODUFlex-related encoding

Hi Lou,

You said:

>Is this correct (always 100ppm)?  Fatai/Sergio referred to table 7-2 in G709 which has 20ppm for most signal types and 100ppm for others.  And it seems there is some text that 
>got dropped in the latest rev of G.874.1 (from an earlier amendment).

[Fatai] I think you mixed ODUflex and ODUj(j=0,1,2,3,4) together, so I would like to clarify a little more. 

For ODUj, the tolerance is fixed and it is 20ppm as in table 7-2 (In the draft, for the text to explain "Tolerance" field, it says "For other signal types (ie., non-ODUflex(CBR)), this field is not necessary and MUST be set to 0"). However, we are talking about ODUflex(CBR), whoes tolerance is also fixed and it is always 100ppm as in table 7-2. (Note that for ODU2e, its tolerance is fixed and is 100ppm as well).

Best Regards

Fatai

-----Original Message-----
From: Lou Berger [mailto:lberger@labn.net] 
Sent: Wednesday, February 06, 2013 6:39 AM
To: John E Drake
Cc: Zafar Ali (zali); Fatai Zhang; CCAMP; draft-ietf-ccamp-gmpls-ospf-g709v3@tools.ietf.org; draft-ietf-ccamp-gmpls-signaling-g709v3@tools.ietf.org
Subject: Re: [CCAMP] Poll on ODUFlex-related encoding

John,

See question in-line below.

On 2/5/2013 2:19 PM, John E Drake wrote:
> Snipped, comment inline
> 
> Irrespectively Yours,
> 
> John
> 
>>>    0             1             2             3
>>>   0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>  |  Signal Type  |       N       |        Reserved       |
>>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>  |              NVC           |      Multiplier (MT)     |
>>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>>  |                      Bit_Rate                       |
>>>  +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>
>> I just wonder are we not better off keeping Tolerance field in
>> signaling and adding a statement in v7 that this field is hardcoded to
>> 100ppm.
>>
>> This has advantage of interworking with earlier draft implementations
>> and is also flexible for various (future/ unknown) client signal types.
>> I.e., we use the same encoding as defined thus far in the document
>> (copying from
>> v6):
>>
>>       0                   1                   2                   3
>>       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>      |  Signal Type  |       N       |           Tolerance           |
>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>      |              NVC              |        Multiplier (MT)        |
>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>      |                            Bit_Rate                           |
>>      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>>
>> And state that Tolerance MUST be set to 100 ppm.
> 
> 
> JD: This is a very good idea.  

Great.  Thanks for being clear on which option you support.

> 'Per [G.874.1/2011] (or whatever is
> the correct reference) Tolerance MUST be set to 100 ppm.'
> 

Is this correct (always 100ppm)?  Fatai/Sergio referred to table 7-2 in
G709 which has 20ppm for most signal types and 100ppm for others.  And
it seems there is some text that got dropped in the latest rev of
G.874.1 (from and earlier amendment).

In your role as ITU-T SG15 liaison manager, can you either figure out
what the right text & reference should be or propose a liaison that we
can send asking the ITU-T for whatever information we need to close this
issue/document?

Thanks,
Lou

>  
>>
>>
>> Thanks
>>
>> Regards...Zafar
>>
>>> <snip>
>>
>> _______________________________________________
>> CCAMP mailing list
>> CCAMP@ietf.org
>> https://www.ietf.org/mailman/listinfo/ccamp
> 
> 
> 
> 
> 
> 