IETF Logo Mail Archive

Re: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-decodability-02

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 13 December 2012 14:06 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 3CF7221F8AE3 for <xrblock@ietfa.amsl.com>; Thu, 13 Dec 2012 06:06:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.362
X-Spam-Level:
X-Spam-Status: No, score=-103.362 tagged_above=-999 required=5 tests=[AWL=0.237, 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 ELzAJArZnmp0 for <xrblock@ietfa.amsl.com>; Thu, 13 Dec 2012 06:06:04 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 7657821F892B for <xrblock@ietf.org>; Thu, 13 Dec 2012 06:06:04 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgEKAKUvoFDGmAcF/2dsb2JhbABEgmzAaYEBB4IeAQEBAQIBAQEBDwsdNBAHBAIBCA0EBAEBCxQJBycLFAkIAQEEEwgBGYdiBgEKniacAIwVhWlhA5wJijaCb4IZ
X-IronPort-AV: E=Sophos;i="4.80,759,1344225600"; d="scan'208";a="336254378"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 13 Dec 2012 08:59:40 -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 09:03:06 -0500
Received: from AZ-FFEXHC03.global.avaya.com (135.64.58.13) by DC-US1HCEX4.global.avaya.com (135.11.52.35) with Microsoft SMTP Server (TLS) id 8.3.83.0; Thu, 13 Dec 2012 09:05:53 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.02.0318.004; Thu, 13 Dec 2012 09:05:52 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: WGLC - draft-ietf-xrblock-rtcp-xr-decodability-02
Thread-Index: Ac3OL9JJ1DarvDWNSB6u3iE3PFj7mQLCTODg
Date: Thu, 13 Dec 2012 14:05:51 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA03F8AC@AZ-FFEXMB04.global.avaya.com>
References: <9904FB1B0159DA42B0B887B7FA8119CA024828@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA024828@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-decodability-02
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 14:06:06 -0000

Hi,

I have a few comments concerning this I-D: 

1. This document relies on ETSI work. Should we not send it to ETSI for review? Is the group were TR 101 290 developped still active? 

2. In the definition of the Reserved field: 

>     This field is reserved for future definition.  In the absence of
      such a definition, the bits in this field MUST be set to zero and
      SHOULD be ignored by the receiver.

Why is the behavior of the receiver defined as a SHOULD and not a MUST?

3. In the definition of the block length field: 

>     The constant 11, in accordance with the definition of this field
      in Section 3 of RFC 3611.

What is the definition of the receiver if a value other than 11 is received? 


4. For all count fields starting with TS_sync_loss_count - there is no definition or reference about what each metric means, and how the measurments or computation of the values are to be performed. Please provide this information for each field, I guess references to the respective sections in TR 101 290 would be fine. 

5. Usage of acronyms (excepting very obvious ones) is discouraged in the title of the documents. Please expand TS - Transport Stream in the title

6. Typo to fix in section 3: s/implentations/implementations/

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:48 PM
> To: xrblock@ietf.org
> Subject: [xrblock] WGLC - draft-ietf-xrblock-rtcp-xr-decodability-02
> 
> 
> This is a Working Group Last Call for http://www.ietf.org/id/draft-ietf-
> xrblock-rtcp-xr-decodability-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

v2.23.0 | Report a Bug | By Email