[xrblock] consistency of Introductions sections

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Thu, 13 December 2012 13:10 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 578CD21F88A9 for <xrblock@ietfa.amsl.com>; Thu, 13 Dec 2012 05:10:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.345
X-Spam-Level:
X-Spam-Status: No, score=-103.345 tagged_above=-999 required=5 tests=[AWL=0.254, 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 zIOZLQd-n0LO for <xrblock@ietfa.amsl.com>; Thu, 13 Dec 2012 05:10:00 -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 924AC21F88A6 for <xrblock@ietf.org>; Thu, 13 Dec 2012 05:10:00 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvwJAKUvoFDGmAcF/2dsb2JhbABEgmzAaYEBB4IgAQEDEihRARUVFEImAQQbGodoAZoFhCucAJF+YQOcCYo2gm+CGQ
X-IronPort-AV: E=Sophos;i="4.80,759,1344225600"; d="scan'208";a="336245177"
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:03:37 -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:07:10 -0500
Received: from AZ-FFEXHC02.global.avaya.com (135.64.58.12) 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:09:58 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC02.global.avaya.com ([135.64.58.12]) with mapi id 14.02.0318.004; Thu, 13 Dec 2012 08:09:56 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: consistency of Introductions sections
Thread-Index: Ac3ZMyXMCurnCvinTUOoR+rsGwoETg==
Date: Thu, 13 Dec 2012 13:09:56 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA03F7F0@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: [xrblock] consistency of Introductions sections
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:10:01 -0000

I am reviewing now the I-Ds in WGLC. There are three with the deadline of today. 

Each one has a different structure for the Introduction section. Personally I like the one in draft-ietf-xrblock-rtcp-xr-jb-02.txt which I believe contains the necessary information structured as: 

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Jitter Buffer Metrics Block  . . . . . . . . . . . . . . .  3
     1.2.  RTCP and RTCP XR Reports . . . . . . . . . . . . . . . . .  3
     1.3.  Performance Metrics Framework  . . . . . . . . . . . . . .  3
     1.4.  Applicability  . . . . . . . . . . . . . . . . . . . . . .  3

1.1 of course varies from memo to memo. 1.2 and 1.3 provides useful information that applies to all xrblock I-Ds. 1.4 is again specific information, very useful for the reader to understand why we decided to define the block(s) and what can be done with them. 

Should we adopt this for all documents? 

Dan