draft-ietf-mpls-rfc6374-sfl-05.txt   draft-ietf-mpls-rfc6374-sfl-06.txt 
MPLS Working Group S. Bryant MPLS Working Group S. Bryant (Ed)
Internet-Draft S. Bryant Internet-Draft Futurewei Technologies Inc.
Intended status: Standards Track Futurewei Technologies Inc. Intended status: Standards Track G. Swallow
Expires: October 9, 2020 M. Chen Expires: November 27, 2020 Southend Technical Center
Z. Li M. Chen
Huawei Huawei
G. Swallow
Southend Technical Center
S. Sivabalan
Cisco Systems
G. Mirsky
ZTE Corp.
G. Fioccola G. Fioccola
Huawei Technologies Huawei Technologies
April 07, 2020 G. Mirsky
ZTE Corp.
May 26, 2020
RFC6374 Synonymous Flow Labels RFC6374 Synonymous Flow Labels
draft-ietf-mpls-rfc6374-sfl-05 draft-ietf-mpls-rfc6374-sfl-06
Abstract Abstract
This document describes a method of making RFC6374 performance This document describes a method of making RFC6374 performance
measurements on flows carried over an MPLS Label Switched path. This measurements on flows carried over an MPLS Label Switched path. This
allows loss and delay measurements to be made on multi-point to point allows loss and delay measurements to be made on multi-point to point
LSPs and allows the measurement of flows within an MPLS construct LSPs and allows the measurement of flows within an MPLS construct
using RFC6374. using RFC6374.
Status of This Memo Status of This Memo
skipping to change at page 1, line 45 skipping to change at page 1, line 41
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 October 9, 2020. This Internet-Draft will expire on November 27, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4
3. RFC6374 Packet Loss Measurement with SFL . . . . . . . . . . 4 3. RFC6374 Packet Loss Measurement with SFL . . . . . . . . . . 4
4. RFC6374 Single Packet Delay Measurement . . . . . . . . . . . 4 4. RFC6374 Single Packet Delay Measurement . . . . . . . . . . . 4
5. Data Service Packet Delay Measurement . . . . . . . . . . . . 5 5. Data Service Packet Delay Measurement . . . . . . . . . . . . 4
6. Some Simplifying Rules . . . . . . . . . . . . . . . . . . . 6 6. Some Simplifying Rules . . . . . . . . . . . . . . . . . . . 6
7. Multiple Packet Delay Characteristics . . . . . . . . . . . . 7 7. Multiple Packet Delay Characteristics . . . . . . . . . . . . 6
7.1. Method 1: Time Buckets . . . . . . . . . . . . . . . . . 7 7.1. Method 1: Time Buckets . . . . . . . . . . . . . . . . . 7
7.2. Method 2 Classic Standard Deviation . . . . . . . . . . . 9 7.2. Method 2 Classic Standard Deviation . . . . . . . . . . . 9
7.2.1. RFC6374 Multi-Packet Delay Measurement Message Format 10 7.2.1. RFC6374 Multi-Packet Delay Measurement Message Format 10
7.3. Per Packet Delay Measurement . . . . . . . . . . . . . . 11 7.3. Per Packet Delay Measurement . . . . . . . . . . . . . . 11
7.4. Average Delay . . . . . . . . . . . . . . . . . . . . . . 11 7.4. Average Delay . . . . . . . . . . . . . . . . . . . . . . 11
8. Sampled Measurement . . . . . . . . . . . . . . . . . . . . . 13 8. Sampled Measurement . . . . . . . . . . . . . . . . . . . . . 13
9. Carrying RFC6374 Packets over an LSP using an SFL . . . . . . 13 9. Carrying RFC6374 Packets over an LSP using an SFL . . . . . . 13
9.1. RFC6374 SFL TLV . . . . . . . . . . . . . . . . . . . . . 15 9.1. RFC6374 SFL TLV . . . . . . . . . . . . . . . . . . . . . 15
10. Applicability to Pro-active and On-demand Measurement . . . . 16 10. Applicability to Pro-active and On-demand Measurement . . . . 16
11. RFC6374 Combined Loss-Delay Measurement . . . . . . . . . . . 16 11. RFC6374 Combined Loss-Delay Measurement . . . . . . . . . . . 16
12. Privacy Considerations . . . . . . . . . . . . . . . . . . . 16 12. Privacy Considerations . . . . . . . . . . . . . . . . . . . 16
13. Security Considerations . . . . . . . . . . . . . . . . . . . 17 13. Security Considerations . . . . . . . . . . . . . . . . . . . 17
14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
14.1. Allocation of PW Associated Channel Type . . . . . . . . 17 14.1. Allocation of PW Associated Channel Type . . . . . . . . 17
14.2. MPLS Loss/Delay TLV Object . . . . . . . . . . . . . . . 17 14.2. MPLS Loss/Delay TLV Object . . . . . . . . . . . . . . . 17
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 15. Contributing Authors . . . . . . . . . . . . . . . . . . . . 18
15.1. Normative References . . . . . . . . . . . . . . . . . . 18 16. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
15.2. Informative References . . . . . . . . . . . . . . . . . 18 16.1. Normative References . . . . . . . . . . . . . . . . . . 18
16.2. Informative References . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
[RFC6374] was originally designed for use as an OAM protocol for use [RFC6374] was originally designed for use as an OAM protocol for use
with MPLS Transport Profile (MPLS-TP) [RFC5921] LSPs. MPLS-TP only with MPLS Transport Profile (MPLS-TP) [RFC5921] LSPs. MPLS-TP only
supports point-to-point and point-to-multi-point LSPs. This document supports point-to-point and point-to-multi-point LSPs. This document
describes how to use RFC6374 in the general MPLS case, and also describes how to use RFC6374 in the general MPLS case, and also
introduces a number of more sophisticated measurements of introduces a number of more sophisticated measurements of
applicability to both cases. applicability to both cases.
skipping to change at page 18, line 5 skipping to change at page 18, line 5
Type Description Reference Type Description Reference
---- --------------------------------- --------- ---- --------------------------------- ---------
TBD Synonymous Flow Label This TBD Synonymous Flow Label This
A value of 4 is recommended. A value of 4 is recommended.
RFC Editor please delete this line RFC Editor please delete this line
[RFC3032][I-D.bryant-mpls-sfl-control] [RFC3032][I-D.bryant-mpls-sfl-control]
15. References 15. Contributing Authors
15.1. Normative References Zhenbin Li
Huawei
Email: lizhenbin@huawei.com
Siva Sivabalan
Cisco Systems
Email: msiva@cisco.com
16. References
16.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y.,
Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack
Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001, Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001,
<https://www.rfc-editor.org/info/rfc3032>. <https://www.rfc-editor.org/info/rfc3032>.
skipping to change at page 18, line 38 skipping to change at page 18, line 48
[RFC7876] Bryant, S., Sivabalan, S., and S. Soni, "UDP Return Path [RFC7876] Bryant, S., Sivabalan, S., and S. Soni, "UDP Return Path
for Packet Loss and Delay Measurement for MPLS Networks", for Packet Loss and Delay Measurement for MPLS Networks",
RFC 7876, DOI 10.17487/RFC7876, July 2016, RFC 7876, DOI 10.17487/RFC7876, July 2016,
<https://www.rfc-editor.org/info/rfc7876>. <https://www.rfc-editor.org/info/rfc7876>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
15.2. Informative References 16.2. Informative References
[I-D.bryant-mpls-sfl-control] [I-D.bryant-mpls-sfl-control]
Bryant, S., Swallow, G., and S. Sivabalan, "A Simple Bryant, S., Swallow, G., and S. Sivabalan, "A Simple
Control Protocol for MPLS SFLs", draft-bryant-mpls-sfl- Control Protocol for MPLS SFLs", draft-bryant-mpls-sfl-
control-06 (work in progress), January 2020. control-06 (work in progress), January 2020.
[I-D.ietf-mpls-sfl-framework] [I-D.ietf-mpls-sfl-framework]
Bryant, S., Chen, M., Li, Z., Swallow, G., Sivabalan, S., Bryant, S., Chen, M., Li, Z., Swallow, G., Sivabalan, S.,
and G. Mirsky, "Synonymous Flow Label Framework", draft- and G. Mirsky, "Synonymous Flow Label Framework", draft-
ietf-mpls-sfl-framework-06 (work in progress), October ietf-mpls-sfl-framework-06 (work in progress), October
skipping to change at page 19, line 34 skipping to change at page 19, line 45
RFC 8372, DOI 10.17487/RFC8372, May 2018, RFC 8372, DOI 10.17487/RFC8372, May 2018,
<https://www.rfc-editor.org/info/rfc8372>. <https://www.rfc-editor.org/info/rfc8372>.
Authors' Addresses Authors' Addresses
Stewart Bryant Stewart Bryant
Futurewei Technologies Inc. Futurewei Technologies Inc.
Email: sb@stewartbryant.com Email: sb@stewartbryant.com
Stewart Bryant George Swallow
Futurewei Technologies Inc. Southend Technical Center
Email: stewart.bryant@gmail.com
Email: swallow.ietf@gmail.com
Mach Chen Mach Chen
Huawei Huawei
Email: mach.chen@huawei.com Email: mach.chen@huawei.com
Zhenbin Li Giuseppe Fioccola
Huawei Huawei Technologies
Email: lizhenbin@huawei.com
George Swallow
Southend Technical Center
Email: swallow.ietf@gmail.com
Siva Sivabalan
Cisco Systems
Email: msiva@cisco.com Email: giuseppe.fioccola@huawei.com
Gregory Mirsky Gregory Mirsky
ZTE Corp. ZTE Corp.
Email: gregimirsky@gmail.com Email: gregimirsky@gmail.com
Giuseppe Fioccola
Huawei Technologies
Email: giuseppe.fioccola@huawei.com
 End of changes. 17 change blocks. 
39 lines changed or deleted 36 lines changed or added

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