Re: [xrblock] FW: I-D Action: draft-ietf-xrblock-rtcp-xr-pdv-06.txt

[Qin Wu <[e-mail]>]

Hi,
----- Original Message ----- 
From: "Glen Zorn" <[e-mail]>
To: "Qin Wu" <[e-mail]>
Cc: "Glen Zorn" <[e-mail]>; "Romascanu, Dan (Dan)" <[e-mail]>; <[e-mail]>
Sent: Saturday, September 22, 2012 2:36 PM
Subject: Re: [xrblock] FW: I-D Action: draft-ietf-xrblock-rtcp-xr-pdv-06.txt


> On 09/22/2012 11:41 AM, Qin Wu wrote:
> 
> ...
> 
>>>>> Section 5.4 COMMENT  o Initial assignments are as follows:
> >>>>
> >>>> * 0: MAPDV2, Clause 6.2.3.2 of [G.1020],
> >>>>
> >>>> * 1: 2-point PDV, Clause 6.2.4 of [Y.1540]
> >>>>
> >>>> Are the rest of the values reserved?
> >>>
> >>> [Qin]: Yes. Here we just give initial assignments.
> >>
> >> OK, but the initial assignments include the reservation of
> >> unassigned values, right? I'm pretty sure that IANA will ask this
> >> question later , so why not save time now?
> >
> > [Qin]: Okay, how about add one statement at the end of initial
> > assignment part to say. value 2-15 are valid and reserved for future
> > use.
> 
> OK, I suggest this:
> 
>     0:        MAPDV2, Clause 6.2.3.2 of [G.1020]
>     1:        2-point PDV, Clause 6.2.4 of [Y.1540]
>     2-15:  Reserved for future use
> 
> I.e., lose the asterisks ;-).  Also, in the same section, s/Entries in 
> the registry are integers./Entries in the registry are unsigned 4-bit 
> integers.

[Qin]: Okay. Thank for your proposed text.

> ...
>