Re: [CCAMP] Closing Issue #49 (Was: Re: R: Closing G.709 open issues)

[Lou Berger <[e-mail]>]

On 5/23/2013 3:15 PM, Khuzema Pithewan wrote:
> Hi Lou,
> 
> 
> -> C) No G-PID value for unused, reserved, or proprietary 709 Payload Type.
> 
> Let say some vendor uses reserved (80-8F, which will never be
> standardized by ITU, as per Note4 in Table 15-8) payload code point
> and uses some GPid 'x' in Control plane for that code point. Now if
> in future, Control plane defines x for some other client.
> 
> There will be backward compatibility issues.

Khuzema,

	I agree.  Vendors have always used (and continue to use)  standard code
points for proprietary purposes at their own peril.  There is nothing
new or unique about this in the context of the documents we're discussing.

Another way to look at it is to ask/answer the following: What about
this draft (supporting [G709-2012]) is different from [RFC4328]
(supporting g709-2001) or any other technology supported by GMPLS that
has experimental, reserved, and/or unavailable client types?

> 
> Since it is clearly mentioned that these 16 code points in dataplane,
> will not standardized, is a standardization in way, 

> which must be
> followed up in control plane by reserving 16 GPids for the purpose.

Why?  [RFC4328] didn't standardize G-PIDs for the following G.709-2001
defined PTs:

  PT      Interpretation
0x01      Experimental mapping \
0x55      Not available
0x66      Not available
0x80-0x8F Reserved codes for proprietary use
0xFF      Not available

Are you just trying to be exhaustive in your definitions, or do you have
an actual use case?  If the latter, can you elaborate on your desired use?

BTW you might want to look at the current IANA G-PID assignments before
answering.  I suspect you'll find that you can address your concerns
using existing assignments.

Thanks,
Lou

> Regds
> Khuzema
> 
> -----Original Message-----
> From: Lou Berger [mailto:[e-mail]] 
> Sent: Tuesday, May 21, 2013 6:47 PM
> To: CCAMP
> Cc: [e-mail]
> Subject: Closing Issue #49 (Was: Re: R: Closing G.709 open issues)
> 
> All,
> 
> In the interest of moving this discussion quickly to closure, I spent
> some time trying to come up with the full list of G.709 PT to G-PID
> mappings.  In coming up with this list I tried to be consistent with
> the last consensus point that I can identify on this topic (the
> previously referenced July 2012 thread & presentation), which included:
> 
> A) Defining new G-PIDs for client types not identified by an assigned
> G-PID (per
> http://www.iana.org/assignments/gmpls-sig-parameters/gmpls-sig-parameters.xml)
> 
> B) Reusing G-PID wherever {G-PID, ODU rate} unambiguously identify a
> G.709 payload type, and define new G-PIDs when reuse not possible.
> 
> C) No G-PID value for unused, reserved, or proprietary 709 Payload Type.
> 
> Here's what I've come up with:
> 
>     G.709
>    Payload
>     Type   G-PID   Type/Comment    LSP Encoding
>     ====   =====   ==============  ===================
>     0x01           No standard value
>     0x02    49     CBRa            G.709 ODUk
>     0x03    50     CBRb            G.709 ODUk
>     0x04    32     ATM             G.709 ODUk
>     0x05    TBA1   Framed GFP      G.709 ODUk
>     0x06    ???    Is any valued needed?
>     0x07    55     Ethernet PHY    G.709 ODUk (k=0)
>                    (transparent    G.709 ODUk (k=3)
>                    GFP)            G.709 ODUk (k=4)
>     0x08    58     Fiber Channel   G.709 ODUk (k=2e)
>     0x09    TBA1   Framed GFP      G.709 ODUk (k=2e)
>     0x0A    TBA2   STM-1           G.709 ODUk (k=0)
>     0x0B    TBA3   STM-4           G.709 ODUk (k=0)
>     0x0C    58     Fiber Channel   G.709 ODUk (k=0)
>     0x0D    58     Fiber Channel   G.709 ODUk (k=1)
>     0x0E    58     Fiber Channel   G.709 ODUflex
>     0x0F    58     Fiber Channel   G.709 ODUflex
>     0x10    51     BSOT            G.709 ODUk
>     0x11    52     BSNT            G.709 ODUk
>     0x12    TBA4   InfiniBand      G.709 ODUflex
>     0x13    TBA4   InfiniBand      G.709 ODUflex
>     0x14    TBA4   InfiniBand      G.709 ODUflex
>     0x15    TBA5   Serial Digital  G.709 ODUk (k=0)
>                    Interface
>     0x16    TBA6   Serial Digital  G.709 ODUk (k=1)
>                    Interface/1.001
>     0x17    TBA5   Serial Digital  G.709 ODUk (k=1)
>                    Interface
>     0x18    TBA6   Serial Digital  G.709 ODUflex
>                    Interface/1.001
>     0x19    TBA5   Serial Digital  G.709 ODUflex
>                    Interface
>     0x1A    56     SBCON/ESCON     G.709 ODUk (k=0)
>                    (IANA to update Type field)
>     0x1B    TBA7   DVB_ASI         G.709 ODUk (k=0)
>     0x1C    58     Fiber Channel   G.709 ODUk
>     0x20    47     G.709 ODU-2.5G  G.709 ODUk
>                                      (k=2,3)
>                    (IANA to update Type field)
>             TBA8   G.709 ODU-1.25G G.709 ODUk
>                                      (k=1,2,3)
>     0x21    TBA8   G.709 ODU-1.25G G.709 ODUk
>                                      (k=2,3,4)
>             TBA9   G.709 ODU-Any   G.709 ODUk
>                                    (k=2,3)
>     0x55           No standard value
>     0x66           No standard value
>     0x80-0x8F      No standard value
>     0xFD    TBA10  Null Test       G.709 ODUk
>     0xFE    TBA11  Random Test     G.709 ODUk
>     0xFF           No standard value
> 
> Note that there are a few differences with Fatai's list, which doesn't
> format well in e-mail, but is available in the archive
> http://www.ietf.org/mail-archive/web/ccamp/current/msg14845.html
> 
> Please speak up if you think the above is not aligned with prior
> consensus or if you have an issue with any of the above.
> 
> Much thanks,
> Lou
> 
> 
> On 5/20/2013 5:09 AM, Fatai Zhang wrote:
>> Hi Lou,
>>
>>  
>>
>> I think my mail on March 13rd may have answered your following comments.
>> My response quoted as follows.
>>
>>  
>>
>> In addition, if people look at the full list that I provided, I think
>> people can realize that RFC4328 (section 3.1.3) used the same approach
>> as the current approach of this draft (ie., 1:1 mapping between GPIDs
>> and payload types defined by G.709), ie., we are following what RFC4328
>> did.
>>
>>  
>>
>> BTW, I am not sure if we need spend so much on discussing this point
>> (because there is no issue to stick to the data plane by using the
>> current approach of this draft).
>>
>>  
>>
>> ======================================================================================================================
>>
>> (2) 'Grouped GPID' vs '1:1' mapping (between G.709-2012 and GPIDs
>> defined in this draft)
>>
>>  
>>
>> We realize that it is safe to use 1:1 mapping approach to avoid some
>> potential issues after investigation. We know this payload types have
>> been defined by G.709 (data plane), so physically it is better to use
>> 1:1 mapping approach.
>>
>> For the potential issues I mentioned above, for example, we cannot use
>> the existing 34 to represent 'STM-1' and 'STM-4 ', because it is
>> impossible to differentiate which one is 'STM-1' or 'STM-4'. In
>> addition, from the concept of payload type, we know that e.g, FC-100 is
>> different from FC-800, right? So, it is better to assign different GPIDs
>> to these different payload types defined by the data plane.
>>
>>  
>>
>> Furthermore, I think it is much cheaper to create new GPIDs in the
>> control plane than in the data plane (these payload types will be
>> carried in the OH).
>>
>>  
>>
>>  
>>
>>  
>>
>>  
>>
>> Best Regards
>>
>>  
>>
>> Fatai
>>
>>  
>>
>> -----Original Message-----
>> From: Lou Berger [mailto:[e-mail]]
>> Sent: Friday, May 17, 2013 11:16 PM
>> To: Fatai Zhang
>> Cc: BELOTTI, SERGIO (SERGIO); Daniele Ceccarelli; CCAMP;
>> [e-mail]
>> Subject: Re: R: Closing G.709 open issues
>>
>>  
>>
>> Fatai,
>>
>>         
>>
>> That's a great start for the WG.  Thank you.
>>
>>  
>>
>> To answer your implied question as to why my request for the full list.
>>
>> My feeling is that there have been too many "surprises" on the 709
>>
>> documents in areas that I thought were either obvious (but from the IETF
>>
>> & GMPLS context, not ITU-T or G.709 perspectives) or resolved by past
>>
>> discussions.  At this point, as co-chair and Document shepherd, I want
>>
>> to ensure that any open point on the documents are unambiguously closed
>>
>> and that past discussions (i.e., points of consensus) are 100% captured,
>>
>> so that we can smoothly move through the planned second LC and
>>
>> publication request.
>>
>>  
>>
>> To that end, in my previous message I asked two questions about points
>>
>> where it seems you are proposing moving away from what has been
>>
>> previously been discussed & agreed to by the WG.  Can you answer the
>>
>> following:
>>
>>  
>>
>>>> My questions on the new G-PIDs come down to:
>>
>>>> - Why are rate specific G-PIDs being proposed (rather than
>>
>>>>   continuing to use the previous approach documented in the draft
>>
>>>>   and in Section 3.1.3 of rfc4328)?
>>
>>  
>>
>>>> - Why are new values being defined rather than using existing
>>
>>>>   values, e.g., G-PID 56?
>>
>>>>
>>
>>  
>>
>> Much thanks,
>>
>> Lou
>>
>>  
>>
>>  
>>
> 
> 
> 
>