--- 1/draft-ietf-idr-flowspec-srv6-00.txt 2022-04-08 10:13:13.600795263 -0700 +++ 2/draft-ietf-idr-flowspec-srv6-01.txt 2022-04-08 10:13:13.624795871 -0700 @@ -1,32 +1,32 @@ Network Working Group Z. Li Internet-Draft L. Li Intended status: Standards Track Huawei -Expires: 11 April 2022 H. Chen +Expires: October 10, 2022 H. Chen Futurewei C. Loibl Next Layer Communications G. Mishra Verizon Inc. Y. Fan Casa Systems Y. Zhu China Telecom L. Liu Fujitsu X. Liu Volta Networks - 8 October 2021 + April 8, 2022 BGP Flow Specification for SRv6 - draft-ietf-idr-flowspec-srv6-00 + draft-ietf-idr-flowspec-srv6-01 Abstract This document proposes extensions to BGP Flow Specification for SRv6 for filtering packets with a SRv6 SID that matches a sequence of conditions. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", @@ -43,35 +43,36 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on 11 April 2022. + This Internet-Draft will expire on October 10, 2022. Copyright Notice - Copyright (c) 2021 IETF Trust and the persons identified as the + Copyright (c) 2022 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal - Provisions Relating to IETF Documents (https://trustee.ietf.org/ - license-info) in effect on the date of publication of this document. - Please review these documents carefully, as they describe your rights - and restrictions with respect to this document. Code Components - extracted from this document must include Simplified BSD License text - as described in Section 4.e of the Trust Legal Provisions and are - provided without warranty as described in the Simplified BSD License. + Provisions Relating to IETF Documents + (https://trustee.ietf.org/license-info) in effect on the date of + publication of this document. Please review these documents + carefully, as they describe your rights and restrictions with respect + to this document. Code Components extracted from this document must + include Simplified BSD License text as described in Section 4.e of + the Trust Legal Provisions and are provided without warranty as + described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Definitions and Acronyms . . . . . . . . . . . . . . . . . . 4 3. The Flow Specification Encoding for SRv6 . . . . . . . . . . 4 3.1. Type TBD1 - Some Parts of SID . . . . . . . . . . . . . . 4 3.2. Encoding Examples . . . . . . . . . . . . . . . . . . . . 6 3.2.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 @@ -99,22 +100,21 @@ Routing Header (SRH) [I-D.ietf-6man-segment-routing-header]. SRv6 Network Programming [RFC8986] defines the SRv6 network programming concept and its most basic functions. An SRv6 SID may have the form of LOC:FUNCT:ARG::. LOC: Each operator is free to use the locator length it chooses. Most often the LOC part of the SID is routable and leads to the node which instantiates that SID. FUNCT: The FUNCT part of the SID is an opaque identification of a - local function bound to the SID. (e.g. End: Endpoint, End.X, End.T, - End.DX2 etc.). + local function bound to the SID. E.g., End.X, End.T, End.DX2, etc. ARG: A function may require additional arguments that would be placed immediately after the FUNCT. This document specifies one new BGP Flow Specification (FS) component type to support Segment Routing over IPv6 data plane (SRv6) filtering for BGP Flow Specification Version 2. The match field is destination address of IPv6 header, but it's a SRv6 SID from SRH rather than a traditional IPv6 address (refer to Figure 1). To support these features, a Flowspec version that is IPv6 capable (i.e., AFI = 2) @@ -132,38 +132,39 @@ | | Segment[1] | | | +-------------+ | | | ... | | SR Header| +-------------+ | | | Segment[n] | | | +-------------+ | | +-------------+ | | ~ Option TLV ~ | | +-------------+ | +-----------------------------+ + Figure 1: Match Field 2. Definitions and Acronyms - * FS: Flow Specification + o FS: Flow Specification - * BGP-FS: Border Gateway Protocol (BGP) Flow Specification (FS) + o BGP-FS: Border Gateway Protocol (BGP) Flow Specification (FS) - * SR: Segment Routing + o SR: Segment Routing - * SRH: SR Header. + o SRH: SR Header. - * SRv6: IPv6 Segment Routing, SRv6 is a method of forwarding IPv6 + o SRv6: IPv6 Segment Routing, SRv6 is a method of forwarding IPv6 packets on the network based on the concept of source routing. - * SID: Segment Identifier + o SID: Segment Identifier - * BSID: Binding SID + o BSID: Binding SID 3. The Flow Specification Encoding for SRv6 The Flow Specification NLRI-type consists of several optional components, each of which begins with a type field (1 octet) followed by a variable length parameter. 13 component types are defined in [RFC8955] and [RFC8956] for IPv4 and IPv6. This document defines one component type for SRv6. 3.1. Type TBD1 - Some Parts of SID @@ -315,24 +316,23 @@ The authors would like to thank Joel Halpern, Jeffrey Haas, Ketan Talaulikar, Aijun Wang, Dhruv Dhody, Shunwan Zhuang and Rainsword Wang for their valuable suggestions and comments on this draft. 7. References 7.1. Normative References [I-D.hares-idr-flowspec-v2] - Hares, S. and D. Eastlake, "BGP Flow Specification Version - 2", Work in Progress, Internet-Draft, draft-hares-idr- - flowspec-v2-02, 26 July 2021, . + Hares, S., Eastlake, D., Yadlapalli, C., and S. Maduschke, + "BGP Flow Specification Version 2", draft-hares-idr- + flowspec-v2-05 (work in progress), February 2022. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, "Multiprotocol Extensions for BGP-4", RFC 4760, DOI 10.17487/RFC4760, January 2007, . @@ -358,97 +358,92 @@ [RFC8956] Loibl, C., Ed., Raszuk, R., Ed., and S. Hares, Ed., "Dissemination of Flow Specification Rules for IPv6", RFC 8956, DOI 10.17487/RFC8956, December 2020, . 7.2. Informative References [I-D.ietf-6man-segment-routing-header] Filsfils, C., Dukes, D., Previdi, S., Leddy, J., Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header - (SRH)", Work in Progress, Internet-Draft, draft-ietf-6man- - segment-routing-header-26, 22 October 2019, - . + (SRH)", draft-ietf-6man-segment-routing-header-26 (work in + progress), October 2019. [I-D.ietf-idr-flowspec-l2vpn] Hao, W., Eastlake, D. E., Litkowski, S., and S. Zhuang, - "BGP Dissemination of L2 Flow Specification Rules", Work - in Progress, Internet-Draft, draft-ietf-idr-flowspec- - l2vpn-17, 12 May 2021, . + "BGP Dissemination of L2 Flow Specification Rules", draft- + ietf-idr-flowspec-l2vpn-18 (work in progress), October + 2021. [RFC8986] Filsfils, C., Ed., Camarillo, P., Ed., Leddy, J., Voyer, D., Matsushima, S., and Z. Li, "Segment Routing over IPv6 (SRv6) Network Programming", RFC 8986, DOI 10.17487/RFC8986, February 2021, . Authors' Addresses Zhenbin Li Huawei 156 Beiqing Road Beijing, 100095 P.R. China Email: lizhenbin@huawei.com Lei Li Huawei 156 Beiqing Road - Beijing - 100095 + Beijing 100095 P.R. China Email: lily.lilei@huawei.com Huaimo Chen Futurewei - Boston, MA, - United States of America + Boston, MA + USA Email: Huaimo.chen@futurewei.com Christoph Loibl Next Layer Communications Mariahilfer Guertel 37/7 - 1150 Vienna - Austria - Email: cl@tix.at + Vienna 1150 + AT + Email: cl@tix.at Gyan S. Mishra Verizon Inc. 13101 Columbia Pike - Silver Spring, MD 20904 - United States of America + Silver Spring MD 20904 + USA Phone: 301 502-1347 Email: gyan.s.mishra@verizon.com Yanhe Fan Casa Systems - United States of America + USA Email: yfan@casa-systems.com Yongqing Zhu China Telecom 109, West Zhongshan Road, Tianhe District - Guangzhou - 510000 + Guangzhou 510000 China Email: zhuyq8@chinatelecom.cn Lei Liu Fujitsu - United States of America + USA Email: liulei.kddi@gmail.com Xufeng Liu Volta Networks McLean, VA - United States of America + USA Email: xufeng.liu.ietf@gmail.com