Re: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-summary-stat-03

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 13 December 2012 13:35 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 3143521F89D2 for <xrblock@ietfa.amsl.com>; Thu, 13 Dec 2012 05:35:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.354
X-Spam-Level:
X-Spam-Status: No, score=-103.354 tagged_above=-999 required=5 tests=[AWL=0.245, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 LtNCqDpV8-Wc for <xrblock@ietfa.amsl.com>; Thu, 13 Dec 2012 05:35:55 -0800 (PST)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 342A021F85A4 for <xrblock@ietf.org>; Thu, 13 Dec 2012 05:35:47 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiILAIbQt1DGmAcF/2dsb2JhbABEgmy9GRZsB4IeAQEBAQMBAQEPCx00FwQCAQgNBAQBAQsUCQcnCxQJCAEBBBMIARmHbgELoXudDIxAg2BhA5JPiT+KN4JygiE
X-IronPort-AV: E=Sophos;i="4.84,186,1355115600"; d="scan'208";a="380473683"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 13 Dec 2012 08:26:57 -0500
Received: from unknown (HELO DC-US1HCEX4.global.avaya.com) ([135.11.52.35]) by co300216-co-erhwest-out.avaya.com with ESMTP; 13 Dec 2012 08:32:57 -0500
Received: from AZ-FFEXHC04.global.avaya.com (135.64.58.14) by DC-US1HCEX4.global.avaya.com (135.11.52.39) with Microsoft SMTP Server (TLS) id 8.3.83.0; Thu, 13 Dec 2012 08:35:45 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC04.global.avaya.com ([135.64.58.14]) with mapi id 14.02.0318.004; Thu, 13 Dec 2012 08:35:44 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: WGLC - draft-ietf-xrblock-rtcp-xr-summary-stat-03
Thread-Index: Ac3OL9JJ1DarvDWNSB6u3iE3PFj7mQK/jUIgAAIJBkA=
Date: Thu, 13 Dec 2012 13:35:43 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA03F868@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA024853@AZ-FFEXMB04.global.avaya.com> <9904FB1B0159DA42B0B887B7FA8119CA03F7D4@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA03F7D4@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-summary-stat-03
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:35:56 -0000

One more comment on this document: 

6. what is the behavior of the receiver if a value other than 3 or 7 respectively is received? 

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 2:52 PM
> To: xrblock@ietf.org
> Subject: Re: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-summary-stat-03
> 
> 
> I have a few comments, please see below:
> 
> 1. I believe that [I-D.ietf-xrblock-rtcp-xr-burst-gap-discard], [I-
> D.ietf-xrblock-rtcp-xr-burst-gap-loss], [I-D.ietf-xrblock-rtcp-xr-
> discard], and [RFC6776] must be Normative references.
> 
> - Burst gap loss metrics defined in [I-D.ietf-xrblock-rtcp-xr-burst-gap-
> discard] are used in calculation of fields in Burst/Gap Discard Summary
> Statistics Block.
> - Burst/Gap Loss Block defined in [I-D.ietf-xrblock-rtcp-xr-burst-gap-
> loss] is used in the calculation of Burst Duration Mean and Burst
> Duration variance
> - Discard Count Block defined in [I-D.ietf-xrblock-rtcp-xr-discard] is
> used in the calculation of Gap Discard Rate
> - Also in the formula of Gap Discard Rate "extended last sequence
> number" and "extended first sequence number" provided in the Measurement
> Information block from [RFC6776] are used
> 
> In order to understand and the formulas and build the implementations
> for this I-D these references are mandatory reading, and for this
> document to be stable the references also need to be stable - so they
> must be Normative
> 
> 2. Sections 3.1.2 - the definition of Interval Metric Flag is 2 bits,
> three values codified to send. What happens at the receiver if the 4th
> (illegal) value I=00 is received?
> 
> 3. Same question about the Interval Metric Type defined in 3.2.2. And if
> we are here, why is one named Interval Metric Flag (3.1.2) and the other
> Interval Metric Type (3.2.2)? they seem to be the same thing
> 
> 4. The introduction section makes no reference to the definition of the
> associated SDP parameters (which is mentioned in the Abstract but not
> here)
> 
> 5. No need to mention the authors names in the Introduction when
> refering to [RFC3611] and [RFC 6792]
> 
> 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:55 PM
> > To: xrblock@ietf.org
> > Subject: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-summary-stat-03
> >
> >
> > This is a Working Group Last Call for
> > http://www.ietf.org/id/draft-ietf-
> > xrblock-rtcp-xr-summary-stat-03.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