Re: [xrblock] 2nd WGLC for draft-ietf-xrblock-rtcp-xr-synchronization

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 23 May 2013 10:34 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 B8A4811E8132 for <xrblock@ietfa.amsl.com>; Thu, 23 May 2013 03:34:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.411
X-Spam-Level:
X-Spam-Status: No, score=-103.411 tagged_above=-999 required=5 tests=[AWL=0.187, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z7Q+PrB2x6BL for <xrblock@ietfa.amsl.com>; Thu, 23 May 2013 03:34:28 -0700 (PDT)
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 B10D911E8190 for <xrblock@ietf.org>; Thu, 23 May 2013 03:34:27 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuwFAAvwnVHGmAcF/2dsb2JhbABagkQjITDCK4EKFnSCIwEBAQEDEhtMEAIBCA0EBAEBCx0HMhQJCAIEAQ0FCAEZh2sBC54ZnAYXjmwxBgGCc2EDnXmKf4MPgiY
X-IronPort-AV: E=Sophos; i="4.87,727,1363147200"; d="scan'208,217"; a="10373293"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 23 May 2013 06:34:25 -0400
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 23 May 2013 06:29:10 -0400
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.0328.009; Thu, 23 May 2013 06:34:24 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>, Shida Schubert <shida@ntt-at.com>, xrblock <xrblock@ietf.org>
Thread-Topic: [xrblock] 2nd WGLC for draft-ietf-xrblock-rtcp-xr-synchronization
Thread-Index: AQHOV6EWG3NZbVVCvEW56gxFjqK+bg==
Date: Thu, 23 May 2013 10:34:22 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA17579E@AZ-FFEXMB04.global.avaya.com>
References: <BA5D79A3-15E9-4038-851F-C4A37A638D25@ntt-at.com> <9904FB1B0159DA42B0B887B7FA8119CA17577A@AZ-FFEXMB04.global.avaya.com>
In-Reply-To: <9904FB1B0159DA42B0B887B7FA8119CA17577A@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: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA17579EAZFFEXMB04globala_"
MIME-Version: 1.0
Cc: xrblock-chairs <xrblock-chairs@tools.ietf.org>
Subject: Re: [xrblock] 2nd WGLC for draft-ietf-xrblock-rtcp-xr-synchronization
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, 23 May 2013 10:34:33 -0000

I should have read the comments already made first. I see Roni caught this already, and the resolution proposed by Qin is OK with me.

Regards,

Dan



From: xrblock-bounces@ietf.org [mailto:xrblock-bounces@ietf.org] On Behalf Of Romascanu, Dan (Dan)
Sent: Thursday, May 23, 2013 1:32 PM
To: Shida Schubert; xrblock
Cc: xrblock-chairs
Subject: Re: [xrblock] 2nd WGLC for draft-ietf-xrblock-rtcp-xr-synchronization

Hi,

Sorry for the delay, but I got only now to reading again the I-D and I noticed the following:


In the Metric Block Structure diagram in section 3.1 the Reserved block occupies 8 bits (from bit 8 to bit 15). However the description in 3.2 says 'Reserved: 6 bits' which seems to be wrong.



Regards,



Dan





From: Shida Schubert [mailto:shida@ntt-at.com]
Sent: Wednesday, May 08, 2013 4:56 AM
To: xrblock
Cc: xrblock-chairs
Subject: 2nd WGLC for draft-ietf-xrblock-rtcp-xr-synchronization

 This is an announcement of a 2 weeks XRBLOCK WG last call on
"Report Block for Synchronization Delay and Offset Metrics Reporting"
priort o requesting publication of the document as a proposed standard.

 As per discussion at the last meeting, we are running a second
WGLC on this draft.

Please send your comments, including nits, to the list by the

22nd of May

If you read the draft and you see no issues, concerns, or nits, please
express the fact that you have no issue progressing the draft on the
list as well.

The latest version can be found here:

http://www.ietf.org/id/draft-ietf-xrblock-rtcp-xr-synchronization-04.txt

Regards

Shida as co-chair