< draft-ietf-ippm-multipoint-alt-mark-00.txt   draft-ietf-ippm-multipoint-alt-mark-01.txt >
IPPM Working Group G. Fioccola, Ed. IPPM Working Group G. Fioccola, Ed.
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Intended status: Experimental M. Cociglio Intended status: Experimental M. Cociglio
Expires: May 9, 2019 Telecom Italia Expires: September 5, 2019 Telecom Italia
A. Sapio A. Sapio
R. Sisto R. Sisto
Politecnico di Torino Politecnico di Torino
November 5, 2018 March 4, 2019
Multipoint Alternate Marking method for passive and hybrid performance Multipoint Alternate Marking method for passive and hybrid performance
monitoring monitoring
draft-ietf-ippm-multipoint-alt-mark-00 draft-ietf-ippm-multipoint-alt-mark-01
Abstract Abstract
The Alternate Marking method, as presented in RFC 8321 [RFC8321], can The Alternate Marking method, as presented in RFC 8321 [RFC8321], can
be applied only to point-to-point flows because it assumes that all 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 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 single second node. This document aims to generalize and expand this
methodology to measure any kind of unicast flows, whose packets can methodology to measure any kind of unicast flows, whose packets can
follow several different paths in the network, in wider terms a follow several different paths in the network, in wider terms a
multipoint-to-multipoint network. For this reason the technique here multipoint-to-multipoint network. For this reason the technique here
skipping to change at page 2, line 4 skipping to change at page 2, line 4
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 9, 2019. This Internet-Draft will expire on September 5, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 33 skipping to change at page 3, line 33
monitoring more flexible in case a detailed analysis is not needed. monitoring more flexible in case a detailed analysis is not needed.
For instance, by considering n measurement points and m monitored For instance, by considering n measurement points and m monitored
flows,the order of magnitude of the packet counters for each time flows,the order of magnitude of the packet counters for each time
interval is n*m*2 (1 per color). If both n and m are high values the interval is n*m*2 (1 per color). If both n and m are high values the
packet counters increase a lot and Multipoint Alternate Marking packet counters increase a lot and Multipoint Alternate Marking
offers a tool to control these parameters. offers a tool to control these parameters.
The approach presented in this document is applied only to unicast The approach presented in this document is applied only to unicast
flows and not to multicast. BUM (Boradcast Unkown Unicast Multicast) flows and not to multicast. BUM (Boradcast Unkown Unicast Multicast)
traffic is not considered here, because traffic replication is not traffic is not considered here, because traffic replication is not
covered by the Multipoint Alternate Marking method. covered by the Multipoint Alternate Marking method. Furthermore it
can be applicable to anycast flows.
Alternate Marking method works by definition for multipoint to Alternate Marking method works by definition for multipoint to
multipoint paths but the network clustering approach presented in multipoint paths but the network clustering approach presented in
this document is the formalization of how to implement this property this document is the formalization of how to implement this property
and it allows a flexible and optimized performance measurement and it allows a flexible and optimized performance measurement
support. support.
Without network clustering, it is possible to apply alternate marking Without network clustering, it is possible to apply alternate marking
only for all the network or per single flow. Instead, with network only for all the network or per single flow. Instead, with network
clustering, it is possible to use the network clusters partition at clustering, it is possible to use the network clusters partition at
skipping to change at page 7, line 5 skipping to change at page 6, line 47
+------+ \ / +------+ +------+ \ / +------+
\ +------+ / \ +------+ /
<> R5 <> <> R5 <>
/ +------+ \ / +------+ \
+------+ / \ +------+ +------+ / \ +------+
---<> R3 <> <> R8 <>--- ---<> R3 <> <> R8 <>---
+------+ +------+ +------+ +------+
Figure 1: Flow classification Figure 1: Flow classification
The case of unicast flow is considered in the previous figure.
Anyway the anycast flow is also in scope because there is no
replication and only a single node from the anycast group receives
the traffic, so it can be viewed as a special case of unicast flow.
4. Multipoint Performance Measurement 4. Multipoint Performance Measurement
By Using the "traditional" alternate marking method only point-to- By Using the "traditional" alternate marking method only point-to-
point paths can be monitored. To have an IP (TCP/UDP) flow that point paths can be monitored. To have an IP (TCP/UDP) flow that
follows a point-to-point path we have to define, with a specific follows a point-to-point path we have to define, with a specific
value, 5 identification fields (IP Source, IP Destination, Transport value, 5 identification fields (IP Source, IP Destination, Transport
Protocol, Source Port, Destination Port). Protocol, Source Port, Destination Port).
Multipoint Alternate Marking enables the performance measurement for Multipoint Alternate Marking enables the performance measurement for
multipoint flows selected by identification fields without any multipoint flows selected by identification fields without any
 End of changes. 7 change blocks. 
6 lines changed or deleted 12 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/