Re: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-jb-02.txt

----- Original Message ----- 
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: <xrblock@ietf.org>
Sent: Thursday, December 13, 2012 9:31 PM
Subject: Re: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-jb-02.txt

>A couple of more editorial issues: 
> 
> 3. In the Reserved (rsv) bits description - please put the reference RFC6709 in brackets -> [RFC6709]

[Qin]: Okay.
> 
> 4. No [RFC2119] keywords are used in this memo, so please drop [RFC2119] from the list of references. 

[Qin]: We did use RFC229 keywork like "SHOULD" which will be replaced with "MUST" as you suggested.
Rather than  drop RFC2119,I believe we should add the same"standard language "  section in this memo as we
 did in the other recently published draft .

> Thanks and Regards,
> 
> Dan
> 
> 
> 
> 
>> -----Original Message-----
>> From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On
>> Behalf Of Romascanu, Dan (Dan)
>> Sent: Thursday, December 13, 2012 3:24 PM
>> To: xrblock@ietf.org
>> Subject: Re: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-jb-02.txt
>> 
>> This document is in good shape, I have a couple of issues that need
>> clarification:
>> 
>> 1. for all delay and water mark fields I see the following:
>> 
>> >     If the measured value exceeds 0xFFFD, the value 0xFFFE SHOULD be
>>       reported to indicate an over-range measurement.  If the
>>       measurement is unavailable, the value 0xFFFF SHOULD be reported.
>> 
>> What are these SHOULD and not MUST? If there are exception cases please
>> explain, if not s/SHOULD/MUST
>> 
>> 2. in the jitter buffer maximum delay description the following sentence
>> seems crippled:
>> 
>> > In adaptive jitter buffer implementations,
>>       this value may dynamically.
>> 
>> Something is missing here, please fix.
>> 
>> Thanks and Regards,
>> 
>> Dan
>> 
>> 
>> 
>> 
>> > -----Original Message-----
>> > From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On
>> > Behalf Of Romascanu, Dan (Dan)
>> > Sent: Thursday, November 29, 2012 2:52 PM
>> > To: xrblock@ietf.org
>> > Subject: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-jb-02.txt
>> >
>> >
>> > This is a Working Group Last Call for
>> > http://www.ietf.org/id/draft-ietf-
>> > xrblock-rtcp-xr-jb-02.txt.
>> >
>> > Please read and review this document, and send your comments,
>> > questions and concerns to the WG list before December 13, 2012. If you
>> > have no comments and you believe that the document is ready for
>> > submission to the IESG as a Standards Track document please send a
>> > short message as well to help us in determining the level of review
>> and consensus.
>> >
>> > Thanks and Regards,
>> >
>> > Dan
>> >
>> >
>> >
>> > _______________________________________________
>> > xrblock mailing list
>> > xrblock@ietf.org
>> > https://www.ietf.org/mailman/listinfo/xrblock
>> _______________________________________________
>> xrblock mailing list
>> xrblock@ietf.org
>> https://www.ietf.org/mailman/listinfo/xrblock
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock