Re: [AVT] RE: I-D ACTION:draft-ash-avt-hc-over-mpls-protocol-00.txt

[Colin Perkins <csp at csperkins.org>]

Jerry,

[snip the points agreed]

On 23 May 2005, at 13:57, Ash, Gerald R ((Jerry)), ALABS wrote:
...
> > Section 2.1, last paragraph: in order to assign a new PW type, the
> > IANA must be given explicit guidance on what to assign. This
> > requires a statement much like those in section 2.1 of the
> > pwe3-iana-allocation draft, listing a numeric type to assign along
> > with a description for that type.
>
> This can be clarified by changing Section 6 'IANA Considerations'  
> in the
> draft to read:
>
> "As discussed in Section 2.1, a new PW type as defined in [IANA] needs
> to be assigned as follows:
>
> PW type      Description
> 0x00??       Header-compressed packets"

This will be sufficient if you specify which PW type number is to be  
assigned. IANA won't do it themselves: the draft needs to specify the  
actual value.

> > Section 2.2: how are the reserved values to be allocated? The draft
> > needs to either define an allocation policy (and IANA registry) or
> > mandate that they MUST NOT be assigned.
>
> You have a good point.  We can change the "RESERVED" codepoint  
> labels to
> "NOT USED", making it clearer that they're not reserved for future
> assignment, but rather will never be used.

It would be clearer if you could use normative language to state that  
the code points MUST NOT be used.

Colin

_______________________________________________
Audio/Video Transport Working Group
avt at ietf.org
https://www1.ietf.org/mailman/listinfo/avt