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

"Ackermann, Michael" <MAckermann@bcbsm.com> Fri, 19 June 2015 14:53 UTC

Return-Path: <mackermann@bcbsm.com>
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 E31F91A854B for <ippm@ietfa.amsl.com>; Fri, 19 Jun 2015 07:53:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level:
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3] 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 ttB5isf1WPIU for <ippm@ietfa.amsl.com>; Fri, 19 Jun 2015 07:53:31 -0700 (PDT)
Received: from mx.z120.zixworks.com (mx.z120.zixworks.com [199.30.235.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAE041A86EF for <ippm@ietf.org>; Fri, 19 Jun 2015 07:53:30 -0700 (PDT)
Received: from 127.0.0.1 (ZixVPM [127.0.0.1]) by Outbound.z120.zixworks.com (Proprietary) with SMTP id 6DB84102FA3 for <ippm@ietf.org>; Fri, 19 Jun 2015 09:53:29 -0500 (CDT)
Received: from imsva2.bcbsm.com (unknown [12.107.172.81]) by mx.z120.zixworks.com (Proprietary) with SMTP id 986B913751D; Fri, 19 Jun 2015 09:53:28 -0500 (CDT)
Received: from imsva2.bcbsm.com (unknown [127.0.0.1]) by IMSVA80 (Postfix) with ESMTP id 90DAA2F6AC6; Fri, 19 Jun 2015 10:47:32 -0400 (EDT)
Received: from pwn401ea105.ent.corp.bcbsm.com (unknown [10.64.102.241]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by imsva2.bcbsm.com (Postfix) with ESMTP id 823152F6A7E; Fri, 19 Jun 2015 10:47:32 -0400 (EDT)
Received: from PWN401EA160.ent.corp.bcbsm.com ([fe80::fdcb:603d:469e:b1db]) by PWN401EA105.ent.corp.bcbsm.com ([fe80::f13e:83e4:1dae:5345%10]) with mapi id 14.01.0438.000; Fri, 19 Jun 2015 10:53:27 -0400
From: "Ackermann, Michael" <MAckermann@bcbsm.com>
To: Bill Cerveny <ippm@wjcerveny.com>, "ippm@ietf.org" <ippm@ietf.org>
Thread-Topic: [ippm] draft-morton-ippm-owamp-registry call for adoption and draft-elkins-ippm-6man-pdm-option accepted for adoption
Thread-Index: AQHQo7/G0u+tIIeA602s5+rqkRR0y52z95qw
Date: Fri, 19 Jun 2015 14:53:27 +0000
Message-ID: <4FC37E442D05A748896589E468752CAA0CE046F6@PWN401EA160.ent.corp.bcbsm.com>
References: <A70677AE-2C1F-46F0-86F1-797E5F2D6E34@wjcerveny.com>
In-Reply-To: <A70677AE-2C1F-46F0-86F1-797E5F2D6E34@wjcerveny.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.10.35]
Content-Type: multipart/alternative; boundary="_000_4FC37E442D05A748896589E468752CAA0CE046F6PWN401EA160entc_"
MIME-Version: 1.0
X-VPM-HOST: vmvpm01.z120.zixworks.com
X-VPM-GROUP-ID: 2b6573c7-334a-4ca0-b257-d9e7ca3a0007
X-VPM-MSG-ID: 4ddb0d5d-425e-4008-9813-6f058b547176
X-VPM-ENC-REGIME: Plaintext
X-VPM-CERT-FLAG: 0
X-VPM-IS-HYBRID: 0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ippm/W3EU1mrh6yyrijWqaMnOnbFMthA>
Cc: "MORTON, ALFRED C (AL)" <acmorton@att.com>
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: Fri, 19 Jun 2015 14:53:34 -0000

HI Bill

I did read the draft.   My initial comments (hopefully in the format you wanted),  are below.


a.)    I do support the addition of the milestone and believe  the adoption
of this draft as a WG item will fulfill that milestone .

b.)    Yes,  I have read the draft.

c.)     I pledge to review the draft during the WG Process.

I also have the following related questions/comments:

1.       In 3.1.4, is the Command Control Numbers listing exhaustive?    Can it be added to or changed as needed later?

2.       Same question as above, only for 3.2.4.   Are the Modes exhaustive or granular enough?   Do we need to differentiate:   specific types of Authentication or Encryption, or modes of IPsec operation?  (random examples).   And once again can this be added to as needed at a later time?

3.       Again in 3.2.4, the statement about the OWAMP and TWAMP registry value assignments functioning differently.   In general, for simplicity and ease of use purposes, I would be in favor of keeping  as many registry functions and values as similar as possible, across all disciplines utilizing registry functions.   This particular area of registry value assignment sounds to me to be more effectively performed in OWAMP and hence I would encourage TWAMP to change.     I am hoping this would have precedent setting influence.



From: ippm [mailto:ippm-bounces@ietf.org] On Behalf Of Bill Cerveny
Sent: Wednesday, June 10, 2015 4:55 PM
To: ippm@ietf.org
Subject: [ippm] draft-morton-ippm-owamp-registry call for adoption and draft-elkins-ippm-6man-pdm-option accepted for adoption

Dear IPPM participants,

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.  The first mission of an OWAMP registry would be to support a registry entry for draft-ietf-ippm-ipsec, which is currently in IESG evaluation.

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
(b) whether you have read the draft
(c) whether you pledge to review the draft during the WG process.

This working group last call runs for 2 weeks, but if there is sufficient support the draft may be accepted earlier so that draft-ietf-ippm-ipsec can progress.

Also, draft-elkins-ippm-6man-pdm-option has been accepted for adoption by the IPPM working group.

Regards,

Bill Cerveny
IPPM WG co-chair


The information contained in this communication is highly confidential and is intended solely for the use of the individual(s) to whom this communication is directed. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information is prohibited. Please notify the sender, by electronic mail or telephone, of any unintended receipt and delete the original message without making any copies.
 
 Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are nonprofit corporations and independent licensees of the Blue Cross and Blue Shield Association.