| < draft-ietf-bier-pmmm-oam-04.txt | draft-ietf-bier-pmmm-oam-05.txt > | |||
|---|---|---|---|---|
| BIER Working Group G. Mirsky | BIER Working Group G. Mirsky | |||
| Internet-Draft ZTE Corp. | Internet-Draft ZTE Corp. | |||
| Intended status: Standards Track L. Zheng | Intended status: Standards Track L. Zheng | |||
| Expires: December 21, 2018 M. Chen | Expires: June 13, 2019 M. Chen | |||
| Huawei Technologies | Huawei Technologies | |||
| G. Fioccola | G. Fioccola | |||
| Telecom Italia | Telecom Italia | |||
| June 19, 2018 | December 10, 2018 | |||
| Performance Measurement (PM) with Marking Method in Bit Index Explicit | Performance Measurement (PM) with Marking Method in Bit Index Explicit | |||
| Replication (BIER) Layer | Replication (BIER) Layer | |||
| draft-ietf-bier-pmmm-oam-04 | draft-ietf-bier-pmmm-oam-05 | |||
| Abstract | Abstract | |||
| This document describes a hybrid performance measurement method for | This document describes a hybrid performance measurement method for | |||
| multicast service over Bit Index Explicit Replication (BIER) domain. | multicast service over Bit Index Explicit Replication (BIER) domain. | |||
| Status of This Memo | Status of This Memo | |||
| This Internet-Draft is submitted in full conformance with the | This Internet-Draft is submitted in full conformance with the | |||
| provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
| skipping to change at page 1, line 36 ¶ | skipping to change at page 1, line 36 ¶ | |||
| 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 December 21, 2018. | This Internet-Draft will expire on June 13, 2019. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2018 IETF Trust and the persons identified as the | Copyright (c) 2018 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 | |||
| skipping to change at page 2, line 22 ¶ | skipping to change at page 2, line 22 ¶ | |||
| 2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 | 2.2. Requirements Language . . . . . . . . . . . . . . . . . . 3 | |||
| 3. OAM Field in BIER Header . . . . . . . . . . . . . . . . . . 3 | 3. OAM Field in BIER Header . . . . . . . . . . . . . . . . . . 3 | |||
| 4. Theory of Operation . . . . . . . . . . . . . . . . . . . . . 3 | 4. Theory of Operation . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 4.1. Single Mark Enabled Measurement . . . . . . . . . . . . . 4 | 4.1. Single Mark Enabled Measurement . . . . . . . . . . . . . 4 | |||
| 4.2. Double Mark Enabled Measurement . . . . . . . . . . . . . 5 | 4.2. Double Mark Enabled Measurement . . . . . . . . . . . . . 5 | |||
| 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 | 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 | 6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 | |||
| 7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 6 | 7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 | 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 | |||
| 8.1. Normative References . . . . . . . . . . . . . . . . . . 6 | 8.1. Normative References . . . . . . . . . . . . . . . . . . 6 | |||
| 8.2. Informative References . . . . . . . . . . . . . . . . . 6 | 8.2. Informative References . . . . . . . . . . . . . . . . . 7 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 | |||
| 1. Introduction | 1. Introduction | |||
| [RFC8279] introduces and explains Bit Index Explicit Replication | [RFC8279] introduces and explains Bit Index Explicit Replication | |||
| (BIER) architecture and how it supports forwarding of multicast data | (BIER) architecture and how it supports forwarding of multicast data | |||
| packets. [RFC8296] specified that in case of BIER encapsulation in | packets. [RFC8296] specified that in case of BIER encapsulation in | |||
| MPLS network a BIER-MPLS label, the label that is at the bottom of | MPLS network a BIER-MPLS label, the label that is at the bottom of | |||
| the label stack, uniquely identifies the multicast flow. [RFC8321] | the label stack, uniquely identifies the multicast flow. [RFC8321] | |||
| describes hybrid performance measurement method, per [RFC7799] | describes hybrid performance measurement method, per [RFC7799] | |||
| skipping to change at page 4, line 25 ¶ | skipping to change at page 4, line 25 ¶ | |||
| | A |--- ----- | | A |--- ----- | |||
| ----- \ --| F | | ----- \ --| F | | |||
| \ ----- / ----- | \ ----- / ----- | |||
| --| C |-- | --| C |-- | |||
| ----- \ ----- | ----- \ ----- | |||
| --| G | | --| G | | |||
| ----- | ----- | |||
| Figure 2: Multicast network | Figure 2: Multicast network | |||
| Using the marking method a BFR creates distinct sub-flows in the | Using the marking method, a BFR creates distinct sub-flows in the | |||
| particular multicast traffic over BIER layer. Each sub-flow consists | particular multicast traffic over BIER layer. Each sub-flow consists | |||
| of consecutive blocks that are unambiguously recognizable by a | of consecutive blocks, consisting of identically marked packets, that | |||
| monitoring point at any BFR and can be measured to calculate packet | are unambiguously recognizable by a monitoring point at any BFR and | |||
| loss and/or packet delay metrics. | can be measured to calculate packet loss and/or packet delay metrics. | |||
| It is expected that the marking values be set and cleared at the edge | ||||
| of BIER domain. Thus for the scenario presented in Figure 2 if the | ||||
| operator initially monitors A-C-G and A-B-D segments he may enable | ||||
| measurements on segments C-F and B-E at any time. | ||||
| 4.1. Single Mark Enabled Measurement | 4.1. Single Mark Enabled Measurement | |||
| As explained in the [RFC8321], marking can be applied to delineate | As explained in the [RFC8321], marking can be applied to delineate | |||
| blocks of packets based either on the equal number of packets in a | blocks of packets based either on the equal number of packets in a | |||
| block or based on equal time interval. The latter method offers | block or based on equal time interval. The latter method offers | |||
| better control as it allows better account for capabilities of | better control as it allows better account for capabilities of | |||
| downstream nodes to report statistics related to batches of packets | downstream nodes to report statistics related to batches of packets | |||
| and, at the same time, time resolution that affects defect detection | and, at the same time, time resolution that affects defect detection | |||
| interval. | interval. | |||
| End of changes. 7 change blocks. | ||||
| 9 lines changed or deleted | 13 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/ | ||||