Marco Liebsch | 10 Sep 2004 17:42
Picon

issue about the L2-type 0x00 as list termination indication


James,

I want to point to one technical inconsistency when
comparing to some versions ago: The specification of the
L2 ID sub-option (section 5.1.3.1) refers to a L2-type of 0x00
to indicate the end of a list of L2 IDs. Well, intention was not
to transmit multiple L2 IDs in one L2 ID sub-option, rather each
L2 ID comes with a single L2 ID sub-option. This makes indication
of a list's end with L2-type=0x00 superfluous. Only single L2 ID
sub-options support unique correlation of other sub-options'
context-id to a single L2-ID.

What do you think?

I have some editorial comments and send them to you
within the next hour.

marco
James Kempf | 10 Sep 2004 18:06

Re: issue about the L2-type 0x00 as list termination indication

> I want to point to one technical inconsistency when
> comparing to some versions ago: The specification of the
> L2 ID sub-option (section 5.1.3.1) refers to a L2-type of 0x00
> to indicate the end of a list of L2 IDs. Well, intention was not
> to transmit multiple L2 IDs in one L2 ID sub-option, rather each
> L2 ID comes with a single L2 ID sub-option. This makes indication
> of a list's end with L2-type=0x00 superfluous. Only single L2 ID
> sub-options support unique correlation of other sub-options'
> context-id to a single L2-ID.
> 
> What do you think?
> 

I'll fix it.

> I have some editorial comments and send them to you
> within the next hour.
> 

Please get them to me today. I want to get this thing done.

Thanx.

            jak

Gmane