[ippm] Comments on draft-tempia-ippm-p3m-02
"Alexander Clemm (alex)" <alex@cisco.com> Fri, 19 February 2016 08:43 UTC
Return-Path: <alex@cisco.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 61AF31A9066; Fri, 19 Feb 2016 00:43:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.506
X-Spam-Level:
X-Spam-Status: No, score=-14.506 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 QaAVUQFpkpJZ; Fri, 19 Feb 2016 00:43:14 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 342181A905E; Fri, 19 Feb 2016 00:43:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11553; q=dns/txt; s=iport; t=1455871394; x=1457080994; h=from:to:cc:subject:date:message-id:mime-version; bh=4ni2l0GL03/M2IkvTDszN2C+dD2oSqv6nGflQHL6gVk=; b=foXhX6mZQ0+jQhYg/GkAngk9sATt+L4EqcEHc91AKxQ4u+99lIyJ/9Ie ZEOQk+AhoWzbrFOr3kJitankBqXmmtJBERkkLuK6Q2dZRZJkD9r+9u+cR 6KMg7ZMRTI2jdmWliMrb8sIvEsIiTo51CZvLTTagujaABk5z0ckERS+Qb k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AAAgAT1cZW/5xdJa1egm5MUnO6NgENgWiGDYFVOBQBAQEBAQEBZBwLhEQELTsREgE1SyYBBA4NiBK8FwEBAQEBAQEBAgEBAQEBAQEBARePQYN7BZcHAYEZjD2Oeo5GAR4BAUKCAxmBSIgpfQEBAQ
X-IronPort-AV: E=Sophos; i="5.22,469,1449532800"; d="scan'208,217"; a="72684816"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Feb 2016 08:43:06 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u1J8h6hd024622 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 19 Feb 2016 08:43:06 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 19 Feb 2016 02:43:05 -0600
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1104.009; Fri, 19 Feb 2016 02:43:05 -0600
From: "Alexander Clemm (alex)" <alex@cisco.com>
To: "draft-tempia-ippm-p3m@ietf.org" <draft-tempia-ippm-p3m@ietf.org>
Thread-Topic: Comments on draft-tempia-ippm-p3m-02
Thread-Index: AdFq8YDYvT8DphYxR8+0kC+VeLYXUQ==
Date: Fri, 19 Feb 2016 08:43:05 +0000
Message-ID: <983d4297610946fe837c24f74c0f09bc@XCH-RCD-001.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.241.46]
Content-Type: multipart/alternative; boundary="_000_983d4297610946fe837c24f74c0f09bcXCHRCD001ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ippm/cd4kkysE__4hl2zlw7mGVBFxcXo>
Cc: "ippm@ietf.org" <ippm@ietf.org>
Subject: [ippm] Comments on draft-tempia-ippm-p3m-02
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: <https://mailarchive.ietf.org/arch/browse/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 Feb 2016 08:43:17 -0000
Hi, I have a few comments on draft-tempia-ippm-p3m-02. I find this a very relevant draft that I hope will get adopted by the the WG. That said, I do have a couple of comments and suggestions: - It would be a good idea to establish some terminology, and add a corresponding terminology section. For example, we need a term for the "flow blocks" in which a particular marking applies, for the data records that are generated for each flow block, for the coloring intervals and block duration, etc. - Section 2: It would be useful to indicate what you do with the colored "blocks" respectively the measurements associated with them, and what the potential interoperability issues are: for example, are you looking at a standard way of controlling the marking, or a standard way of exporting the measures being taken? Even if you consider this outside the scope of the document, it would be good to still mention that (even if just to state this is out of scope). - It would be good to add a paragraph specifically on the problem of how to determine when a block is terminated, probably around section 3.1. It would be good to add a little further discussion on assumptions choices, most specifically the lower bound that an interval can have for measurements to still be accurate. Presumably that would be something like 2*max jitter that can occur (to account for the possibilility of laggards). - It would be useful to add an additional diagram, showing the deployment of how/where you perform the measurements (i.e. where the packets are captured, time stamped, etc) - It would be useful to add a section at the end regarding interoperability considerations, per the earlier comment, e.g. the control of the markings, the counting, the exporting of the records. This can be accompanied by an explanation that this is out of scope, but mentioning this would be good. - The draft is written as too Telecom Italia specific. This needs to be framed as a general-purpose problem that is of broader interest across the industry. There are various associated edits that should be made, perhaps most importantly in the abstract and the introduction. If you would want to refer to Telecom Italia specifics, you might consider simply referencing a publication (in a conference, journal or such) in the reference section instead. Kind regards --- Alex
- [ippm] Comments on draft-tempia-ippm-p3m-02 Alexander Clemm (alex)
- [ippm] R: Comments on draft-tempia-ippm-p3m-02 Fioccola Giuseppe