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

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 13 December 2012 13:32 UTC

Return-Path: <dromasca@avaya.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CAF721F89A5 for <xrblock@ietfa.amsl.com>; Thu, 13 Dec 2012 05:32:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.863
X-Spam-Level:
X-Spam-Status: No, score=-102.863 tagged_above=-999 required=5 tests=[AWL=-0.264, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C0FpOosAU9RC for <xrblock@ietfa.amsl.com>; Thu, 13 Dec 2012 05:32:05 -0800 (PST)
Received: from p-us1-iereast-outbound.us1.avaya.com (p-us1-iereast-outbound.us1.avaya.com [135.11.29.13]) by ietfa.amsl.com (Postfix) with ESMTP id 1AC1621F8980 for <xrblock@ietf.org>; Thu, 13 Dec 2012 05:32:05 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEKAAEvoFDGmAcF/2dsb2JhbABEgmzAaYEBB4IeAQEBAQMBAQEPCwoTNBcEAgEIDQQEAQELFAkHJwsUCQgBAQQTCAEZh2gBCp4mnAGMFYVpYQOcCYo2gm+CGQ
X-IronPort-AV: E=Sophos;i="4.80,759,1344225600"; d="scan'208";a="40365086"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by p-us1-iereast-outbound.us1.avaya.com with ESMTP; 13 Dec 2012 08:22:49 -0500
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by co300216-co-erhwest-out.avaya.com with ESMTP; 13 Dec 2012 08:29:15 -0500
Received: from AZ-FFEXHC01.global.avaya.com (135.64.58.11) by DC-US1HCEX1.global.avaya.com (135.11.52.36) with Microsoft SMTP Server (TLS) id 8.3.106.1; Thu, 13 Dec 2012 08:32:03 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC01.global.avaya.com ([135.64.58.11]) with mapi id 14.02.0318.004; Thu, 13 Dec 2012 08:32:01 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: WGLC - draft-ietf-xrblock-rtcp-xr-jb-02.txt
Thread-Index: Ac3OL9JJ1DarvDWNSB6u3iE3PFj7mQLBJ6GwAABXu0A=
Date: Thu, 13 Dec 2012 13:31:25 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA03F848@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA024844@AZ-FFEXMB04.global.avaya.com> <9904FB1B0159DA42B0B887B7FA8119CA03F828@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA03F828@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-jb-02.txt
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Dec 2012 13:32:06 -0000

A couple of more editorial issues: 

3. In the Reserved (rsv) bits description - please put the reference RFC6709 in brackets -> [RFC6709]

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

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