Re: [ippm] draft-morton-ippm-owamp-registry call for adoption and draft-elkins-ippm-6man-pdm-option accepted for adoption

Kostas Pentikousis <k.pentikousis@eict.de> Thu, 18 June 2015 15:22 UTC

Return-Path: <k.pentikousis@eict.de>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DC9D1ACE1C for <ippm@ietfa.amsl.com>; Thu, 18 Jun 2015 08:22:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.44
X-Spam-Level:
X-Spam-Status: No, score=0.44 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id liBcETkJm39m for <ippm@ietfa.amsl.com>; Thu, 18 Jun 2015 08:22:34 -0700 (PDT)
Received: from mx2.eict.de (mx2.eict.de [212.91.241.168]) by ietfa.amsl.com (Postfix) with ESMTP id 920871A92FC for <ippm@ietf.org>; Thu, 18 Jun 2015 08:22:34 -0700 (PDT)
Received: by mx2.eict.de (Postfix, from userid 481) id F06551FF56; Thu, 18 Jun 2015 17:22:32 +0200 (CEST)
Received: from mail.eict.de (mx1 [172.16.6.1]) by mx2.eict.de (Postfix) with ESMTP id A1C6C1FF52; Thu, 18 Jun 2015 17:22:32 +0200 (CEST)
Received: from sbs2008.eict.local (sbs2008.intern.eict.de [192.168.2.11]) by mail.eict.de (Postfix) with ESMTP id 6EC34378269; Thu, 18 Jun 2015 17:22:32 +0200 (CEST)
Received: from SBS2008.eict.local ([fe80::2051:ef24:c7c9:f298]) by SBS2008.eict.local ([fe80::2051:ef24:c7c9:f298%13]) with mapi; Thu, 18 Jun 2015 17:21:17 +0200
From: Kostas Pentikousis <k.pentikousis@eict.de>
To: Bill Cerveny <ippm@wjcerveny.com>, "ippm@ietf.org" <ippm@ietf.org>
Date: Thu, 18 Jun 2015 17:21:15 +0200
Thread-Topic: [ippm] draft-morton-ippm-owamp-registry call for adoption and draft-elkins-ippm-6man-pdm-option accepted for adoption
Thread-Index: AdCkeK8y6dW376fTQ1CPVbruN+Y/sQFYOY+w
Message-ID: <0C7EDCF89AB9E2478B5D010026CFF4AEB5AB9052F7@SBS2008.eict.local>
References: <A70677AE-2C1F-46F0-86F1-797E5F2D6E34@wjcerveny.com>
In-Reply-To: <A70677AE-2C1F-46F0-86F1-797E5F2D6E34@wjcerveny.com>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ippm/GLTUUmpc6yPGzmc7F4IaVwqxuh4>
Subject: Re: [ippm] draft-morton-ippm-owamp-registry call for adoption and draft-elkins-ippm-6man-pdm-option accepted for adoption
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jun 2015 15:22:36 -0000

Dear Bill, all,

| As noted in discussions for which the IPPM working group has been cc’ed on,
| draft draft-morton-ippm-owamp-registry-00, "Registries for the One-Way
| Active Measurement Protocol - OWAMP" has been proposed to establish
| an OWAMP registry.

<snip>

| Please indicate:
| (a) whether you support the addition of the milestone and the adoption
| of the draft as a WG item to fulfill that milestone 

I support both the milestone addition and draft adoption as a WG item.

| (b) whether you have read the draft 

I did. Overall reads well, but needs some further editing. But it is a perfect start for the WG document. Some editorial suggestions/nits:

s/Metrics (WG in/Metrics WG in

s/for OMAMP until/for OWAMP until

s/OWAMP Control/OWAMP-Control/g

Should the reference to "section 3" in Sec. 3.1 of this draft ("Control Command Number Registry") be more specific, pointing instead to sec. 3.4 of RFC4656?

In the table of sec. 3.2.4, perhaps it's better to be more specific and s/IPsec mode/IKEv2-derived Shared Secret Key


| (c) whether you pledge to review the draft during the WG process. 

Sure. 

Best regards,

Kostas