Re: LMP

[S Ramesh <rashanmu@npd.hcltech.com>]

Also, In LMP why do we need a IPv6 extension for interface ID.
Interface ID is a logical identifier that identifies a specific port.
In in-fiber signalling where the control channel is within the data
channel there is no need for having seperately two ID's for a same
physical link ( which contains the control channel as well as data
link ). The CCID can be the same as the Interface ID in this case.(
Mentioned in OIF UNI too ).

If so, then if the Interface ID is a IPv6 address means how it can be
used as CCID too, because the CCID is a 32bit field.

Does that means there will be two seperate IDs of termination, even
the control channel and data channel are within the same fiber. Is
this acceptable?

Thanks
Ramesh

"Wijnen, Bert (Bert)" wrote:

> When I look at section 14, then I wonder:
>
>   LOCAL_CCID:  Class = 1, C-Type = 1, 4 byte CC_id
>   REMOTE_CCID: Class = 2, C-Type = 1, 4 byte CC_id
>
> Why is that not:
>
>   CCID: Class = 1, LOCAL: C-Type = 1, 4 byte CC_id
>   CCID: Class = 1, LOCAL: C-Type = 2, 4 byte CC_id
>
> The above is just an example. this is type of definitions
> occur throughout section 14, and it seems we are using
> many more name space code points than really needed.
> Is this handy? Wise? Good design?
>
> Bert