[ippm] R: Comments on draft-tempia-ippm-p3m-02
Fioccola Giuseppe <giuseppe.fioccola@telecomitalia.it> Wed, 24 February 2016 17:13 UTC
Return-Path: <giuseppe.fioccola@telecomitalia.it>
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 238011B3829; Wed, 24 Feb 2016 09:13:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.427
X-Spam-Level:
X-Spam-Status: No, score=-0.427 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001] 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 Hx6qUx76U1pn; Wed, 24 Feb 2016 09:13:37 -0800 (PST)
Received: from teledg002ba020.telecomitalia.it (teledg002ba020.telecomitalia.it [156.54.233.211]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C01D71B3600; Wed, 24 Feb 2016 09:13:33 -0800 (PST)
Content-Type: multipart/mixed; boundary="_95c4e631-e3b1-4a12-9c5d-22a177abe720_"
Received: from TELCAH005BA020.telecomitalia.local (10.188.101.222) by teledg002ba020.telecomitalia.it (10.188.101.211) with Microsoft SMTP Server (TLS) id 14.3.266.1; Wed, 24 Feb 2016 18:13:30 +0100
Received: from TELMBB001BA020.telecomitalia.local ([169.254.2.43]) by telcah005ba020.telecomitalia.local ([10.188.101.222]) with mapi id 14.03.0266.001; Wed, 24 Feb 2016 18:13:30 +0100
From: Fioccola Giuseppe <giuseppe.fioccola@telecomitalia.it>
To: "Alexander Clemm (alex)" <alex@cisco.com>, "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+VeLYXUQDPjRug
Date: Wed, 24 Feb 2016 17:13:30 +0000
Message-ID: <23126F6FC5CA3E44916CF99D4E0B878B44F72FCB@TELMBB001BA020.telecomitalia.local>
References: <983d4297610946fe837c24f74c0f09bc@XCH-RCD-001.cisco.com>
In-Reply-To: <983d4297610946fe837c24f74c0f09bc@XCH-RCD-001.cisco.com>
Accept-Language: it-IT, en-US
Content-Language: it-IT
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.188.101.189]
x-ti-disclaimer: Disclaimer1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ippm/YplytX14hwLHO767bD1IV0DEBg8>
Cc: "ippm@ietf.org" <ippm@ietf.org>
Subject: [ippm] R: 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: Wed, 24 Feb 2016 17:13:42 -0000
Hi Alex, We are glad that you consider this document a very relevant draft and support WG adoption. Greatly appreciate your valuable and thoughtful considerations. I'm working on a proposed update to the draft that addresses your comments in addition to the comments we recently received. Please see my response inline... Best Regards, Giuseppe Da: Alexander Clemm (alex) [mailto:alex@cisco.com] Inviato: venerdì 19 febbraio 2016 09:43 A: draft-tempia-ippm-p3m@ietf.org<mailto:draft-tempia-ippm-p3m@ietf.org> Cc: ippm@ietf.org<mailto:ippm@ietf.org> Oggetto: Comments on draft-tempia-ippm-p3m-02 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. GF: I agree, a terminology section is necessary. - 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). GF: The way of exporting the measures is outside the scope of this document, because it would be a general reference for alternate marking technique. Other related documents should address these topics depending on the application of the methodology. But you are right, we need to specify what we are looking for and what 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). GF: Certainly, a more detailed paragraph will be added. - 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) GF: Yes, I agree. - 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. GF: For sure. In this document the authors would like to describe marking and counting methodology. The exporting of records is out of scope and is in charge of the related documents. - 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. GF: Of course. It will be address in the new version of the document. Kind regards --- Alex Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. [rispetta l'ambiente]Rispetta l'ambiente. Non stampare questa mail se non è necessario.
- [ippm] Comments on draft-tempia-ippm-p3m-02 Alexander Clemm (alex)
- [ippm] R: Comments on draft-tempia-ippm-p3m-02 Fioccola Giuseppe