Re: [ippm] New Version Notification for draft-fioccola-ippm-multipoint-alt-mark-01.txt

"MORTON, ALFRED C (AL)" <acmorton@att.com> Tue, 31 October 2017 14:01 UTC

Return-Path: <acmorton@att.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AC0113F542; Tue, 31 Oct 2017 07:01:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level:
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 7PC2t2CtAV51; Tue, 31 Oct 2017 07:01:03 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 BA9DF13F3C8; Tue, 31 Oct 2017 07:01:03 -0700 (PDT)
Received: from pps.filterd (m0049297.ppops.net [127.0.0.1]) by m0049297.ppops.net-00191d01. (8.16.0.21/8.16.0.21) with SMTP id v9VDsK8q023373; Tue, 31 Oct 2017 10:01:00 -0400
Received: from tlpd255.enaf.dadc.sbc.com (sbcsmtp3.sbc.com [144.160.112.28]) by m0049297.ppops.net-00191d01. with ESMTP id 2dxfbg0re5-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 31 Oct 2017 10:01:00 -0400
Received: from enaf.dadc.sbc.com (localhost [127.0.0.1]) by tlpd255.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id v9VE0w8L030411; Tue, 31 Oct 2017 09:00:58 -0500
Received: from dalint01.pst.cso.att.com (dalint01.pst.cso.att.com [135.31.133.159]) by tlpd255.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id v9VE0rvp030292 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 31 Oct 2017 09:00:53 -0500
Received: from clpi183.sldc.sbc.com (clpi183.sldc.sbc.com [135.41.1.46]) by dalint01.pst.cso.att.com (RSA Interceptor); Tue, 31 Oct 2017 14:00:39 GMT
Received: from sldc.sbc.com (localhost [127.0.0.1]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id v9VE0dxY008883; Tue, 31 Oct 2017 09:00:39 -0500
Received: from mail-green.research.att.com (mail-green.research.att.com [135.207.255.15]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id v9VE0LTQ030314; Tue, 31 Oct 2017 09:00:21 -0500
Received: from exchange.research.att.com (njmtcas2.research.att.com [135.207.255.47]) by mail-green.research.att.com (Postfix) with ESMTP id 28FB2E1330; Tue, 31 Oct 2017 09:59:21 -0400 (EDT)
Received: from njmtexg5.research.att.com ([fe80::b09c:ff13:4487:78b6]) by njmtcas2.research.att.com ([fe80::d550:ec84:f872:cad9%15]) with mapi id 14.03.0361.001; Tue, 31 Oct 2017 10:00:20 -0400
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: Fioccola Giuseppe <giuseppe.fioccola@telecomitalia.it>, "ippm@ietf.org" <ippm@ietf.org>, "ippm-chairs@ietf.org" <ippm-chairs@ietf.org>
CC: "'draft-fioccola-ippm-multipoint-alt-mark@ietf.org'" <draft-fioccola-ippm-multipoint-alt-mark@ietf.org>
Thread-Topic: New Version Notification for draft-fioccola-ippm-multipoint-alt-mark-01.txt
Thread-Index: AQHTUWooNh6lKMP820apn9zu1vJ01qL8Ma3ggAG35oA=
Date: Tue, 31 Oct 2017 14:00:19 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CF490276C1@njmtexg5.research.att.com>
References: <150935944833.3357.13207424476365361971.idtracker@ietfa.amsl.com> <1b8d96f8c276421baec6620c404a31cb@TELMBXB02RM001.telecomitalia.local>
In-Reply-To: <1b8d96f8c276421baec6620c404a31cb@TELMBXB02RM001.telecomitalia.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.70.199.136]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-10-31_05:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1710310181
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/YL_RZWqbZRGW3HbA5CZGSfUNFGE>
Subject: Re: [ippm] New Version Notification for draft-fioccola-ippm-multipoint-alt-mark-01.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 31 Oct 2017 14:01:13 -0000

Hi Guiseppe,

> -----Original Message-----
> From: ippm [mailto:ippm-bounces@ietf.org] On Behalf Of Fioccola Giuseppe
> Sent: Monday, October 30, 2017 7:29 AM
> To: ippm@ietf.org; ippm-chairs@ietf.org
> Cc: 'draft-fioccola-ippm-multipoint-alt-mark@ietf.org'
> Subject: [ippm] I: New Version Notification for draft-fioccola-ippm-
> multipoint-alt-mark-01.txt
> 
> Hi IPPM,
> 
> We have updated the draft to address the comment received in Prague from
> Al Morton about considering RFC5644 relevant for this work.
> 
> The feeling is that the multipoint alternate marking considerations
> extend the scope of RFC5644 to Passive/Hybrid Performance Measurements
> and also to multi source stream. A new section "Correlation with
> RFC5644" has been added. Some terminologies and definitions can be re-
> used from RFC5644 (e.g. spatial, segment, multiparty, one-to-group
> metrics and also group-to-group topologies), but they have to be
> rephrased to be applied to the alternate marking schema.

[ACM] 
Thanks for addressing my comment. It is certainly worthwhile
to re-use what you can. It will be useful to recognize the 
overlap between one-to-group and group-to-group metrics, and
that some group-to-group metrics consolidate many one-to-group
observations, and those are built on one-to-one observations...

In section 3, you indicate the possibility of multi-paths
appearing in the measurements, and then
you raise an important point about specifying
single IP addresses, that: 
 " ... a single source address selects flows following a point-to-
   multipoint, while a multipoint-to-point can be the result of a
   matching on a single destination address."

If specifying a single Source address, for example, the 
point-to-multipoint graph would almost certainly include
multiple paths as well. The risk of combining measurements
on the basis of Source IP-only, is that delay variations
observed across multiple paths would be larger than those 
experienced by single flows. Common Flow classification keeps 
each flow on *one* route through the multi-path topology.

"...alternate marking method is applicable only to a single path",
so it appears you start with the flow-specific information,
just be careful with the aggregations in the multipoint cases.

Measurements of Route variation/sensitivities are on (some of) our minds:
https://tools.ietf.org/html/draft-amf-ippm-route-01
and this is a possible area of interaction where we all benefit:
from your Section 4.1:
   "The Monitoring Network is deduced from the Production Network, by
   identifying the nodes of the graph, that are the measurement points,
   and the links, that are the connections between measurement points."
Even if your org. owns the production network, you may still be 
surprised how packets flow through it when routing choices are made
on IP and higher-layer info.

  "4.4.2.  Mean Delay and Jitter

   Mean delay and jitter measurements can also be generalized to the
   case of multipoint flows."
This is where my comments above on combining measurements across
flows are relevant. Also, we prefer "Packet Delay Variation" over the 
term "Jitter" in IPPM, and RFC 3393 explains why.

hope this helps,
Al


> 
> 
> 
> Also, the description of how to use RFC5474 and RFC5475 coupled with
> alternate marking has been detailed (section "Hashing selection
> method"). It can be applied to both point-to-point (described in draft-
> mizrahi-ippm-compact-alternate-marking) and to multipoint-to-multipoint
> (described in this new version).
> 
> 
> 
> In addition, new considerations inspired from Last Call discussion on
> the foundation draft-ietf-ippm-alt-mark have been included also in this
> new version.
> 
> 
> 
> Best Regards,
> 
> 
> 
> Giuseppe
> 
> 
> 
> -----Messaggio originale-----
> 
> Da: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> 
> Inviato: lunedì 30 ottobre 2017 11:31
> 
> A: Riccardo Sisto; Fioccola Giuseppe; Cociglio Mauro; Amedeo Sapio
> 
> Oggetto: New Version Notification for draft-fioccola-ippm-multipoint-
> alt-mark-01.txt
> 
> 
> 
> 
> 
> A new version of I-D, draft-fioccola-ippm-multipoint-alt-mark-01.txt
> 
> has been successfully submitted by Giuseppe Fioccola and posted to the
> IETF repository.
> 
> 
> 
> Name:		draft-fioccola-ippm-multipoint-alt-mark
> 
> Revision:	01
> 
> Title:		Multipoint Alternate Marking method for passive and
> hybrid performance monitoring
> 
> Document date:	2017-10-30
> 
> Group:		Individual Submission
> 
> Pages:		15
> 
> URL:            https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_internet-2Ddrafts_draft-2Dfioccola-2Dippm-2Dmultipoint-
> 2Dalt-2Dmark-2D01.txt&d=DwIGaQ&c=LFYZ-
> o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=suU4T_2RZzOwGp0SQv4djBq7_f7
> o0xSry1botNlPQwo&s=tyA_g2awBepo0xLRkexAz6QGn95n8OsVRPX2uXtim_8&e=
> 
> Status:         https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__datatracker.ietf.org_doc_draft-2Dfioccola-2Dippm-2Dmultipoint-2Dalt-
> 2Dmark_&d=DwIGaQ&c=LFYZ-
> o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=suU4T_2RZzOwGp0SQv4djBq7_f7
> o0xSry1botNlPQwo&s=nilgR7KGeMnGnZZEino7Eh5bGKNWVqKI_qSQh9oWjiY&e=
> 
> Htmlized:       https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__tools.ietf.org_html_draft-2Dfioccola-2Dippm-2Dmultipoint-2Dalt-
> 2Dmark-2D01&d=DwIGaQ&c=LFYZ-
> o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=suU4T_2RZzOwGp0SQv4djBq7_f7
> o0xSry1botNlPQwo&s=VLHIDWRJhVWmcY3a_H7varSbbkn8YHRhIuqIm94cSss&e=
> 
> Htmlized:       https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__datatracker.ietf.org_doc_html_draft-2Dfioccola-2Dippm-2Dmultipoint-
> 2Dalt-2Dmark-2D01&d=DwIGaQ&c=LFYZ-
> o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=suU4T_2RZzOwGp0SQv4djBq7_f7
> o0xSry1botNlPQwo&s=ElLFZugckE4UuIjKvBchXfLJy4pBp6mN2h36_FDJ1_A&e=
> 
> Diff:           https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_rfcdiff-3Furl2-3Ddraft-2Dfioccola-2Dippm-2Dmultipoint-
> 2Dalt-2Dmark-2D01&d=DwIGaQ&c=LFYZ-
> o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=suU4T_2RZzOwGp0SQv4djBq7_f7
> o0xSry1botNlPQwo&s=AOC587l3llHlTLOLAMr_worZBB9pM2xdHSicpvIBafc&e=
> 
> 
> 
> Abstract:
> 
>    The Alternate Marking method, as presented in
> 
>    [I-D.ietf-ippm-alt-mark], can be applied only to point-to-point flows
> 
>    because it assumes that all the packets of the flow measured on one
> 
>    node are measured again by a single second node.  This document aims
> 
>    to generalize and expand this methodology to measure any kind of
> 
>    unicast flows, whose packets can follow several different paths in
> 
>    the network, in wider terms a multipoint-to-multipoint network.  For
> 
>    this reason the technique here described is called Multipoint
> 
>    Alternate Marking.  Some definitions here introduced extend the scope
> 
>    of RFC 5644 [RFC5644] in the context of alternate marking schema.
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of
> submission until the htmlized version and diff are available at
> tools.ietf.org.
> 
> 
> 
> The IETF Secretariat
> 
> 
> 
> 
> 
> 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. Non stampare questa mail se non è necessario.
> 
> _______________________________________________
> ippm mailing list
> ippm@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mailman_listinfo_ippm&d=DwIGaQ&c=LFYZ-
> o9_HUMeMTSQicvjIg&r=OfsSu8kTIltVyD1oL72cBw&m=suU4T_2RZzOwGp0SQv4djBq7_f7
> o0xSry1botNlPQwo&s=eZZXGlSoCg5W4X2VxeWZKmuYkX9zcv2XO6ibfa9lUE4&e=