draft-ietf-idr-bgp-flowspec-label-00.txt   draft-ietf-idr-bgp-flowspec-label-01.txt 
Idr Working Group Q. Liang Idr Working Group Q. Liang
Internet-Draft S. Hares Internet-Draft S. Hares
Intended status: Standards Track J. You Intended status: Standards Track J. You
Expires: December 3, 2016 Huawei Expires: June 9, 2017 Huawei
R. Raszuk R. Raszuk
Nozomi Nozomi
D. Ma D. Ma
Cisco Systems Cisco Systems
June 1, 2016 December 6, 2016
Carrying Label Information for BGP FlowSpec Carrying Label Information for BGP FlowSpec
draft-ietf-idr-bgp-flowspec-label-00 draft-ietf-idr-bgp-flowspec-label-01
Abstract Abstract
This document specifies a method in which the label mapping This document specifies a method in which the label mapping
information for a particular FlowSpec rule is piggybacked in the same information for a particular FlowSpec rule is piggybacked in the same
Border Gateway Protocol (BGP) Update message that is used to Border Gateway Protocol (BGP) Update message that is used to
distribute the FlowSpec rule. Based on the proposed method, the distribute the FlowSpec rule. Based on the proposed method, the
Label Switching Routers (LSRs) (except the ingress LSR) on the Label Label Switching Routers (LSRs) (except the ingress LSR) on the Label
Switched Path (LSP) can use label to indentify the traffic matching a Switched Path (LSP) can use label to indentify the traffic matching a
particular FlowSpec rule; this facilitates monitoring and traffic particular FlowSpec rule; this facilitates monitoring and traffic
skipping to change at page 1, line 48 skipping to change at page 1, line 48
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 http://datatracker.ietf.org/drafts/current/. Drafts is at http://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 3, 2016. This Internet-Draft will expire on June 9, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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 . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Background . . . . . . . . . . . . . . . . . . . . . . . 2 1.1. Background . . . . . . . . . . . . . . . . . . . . . . . 3
1.2. MPLS Flow Specification Deployment . . . . . . . . . . . 3 1.2. MPLS Flow Specification Deployment . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Overview of Proposal . . . . . . . . . . . . . . . . . . . . 3 3. Overview of Proposal . . . . . . . . . . . . . . . . . . . . 4
4. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . 5 4. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
6. Security considerations . . . . . . . . . . . . . . . . . . . 7 6. Security considerations . . . . . . . . . . . . . . . . . . . 7
7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 7 7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
8.1. Normative References . . . . . . . . . . . . . . . . . . 7 8.1. Normative References . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 8 8.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9
1. Introduction 1. Introduction
This section provides the background for proposing a new action for This section provides the background for proposing a new action for
BGP Flow specification that push/pops MPLS or swaps MPLS tags. For BGP Flow specification that push/pops MPLS or swaps MPLS tags. For
those familiar with BGP Flow specification ([RFC5575], [RFC7674], those familiar with BGP Flow specification ([RFC5575], [RFC7674],
[I-D.ietf-idr-flow-spec-v6], [I-D.ietf-idr-flowspec-l2vpn], [I-D.ietf-idr-flow-spec-v6], [I-D.ietf-idr-flowspec-l2vpn],
[I-D.ietf-idr-bgp-flowspec-oid] and MPLS ([RFC3107]) can skip this [I-D.ietf-idr-bgp-flowspec-oid] and MPLS ([RFC3107]) can skip this
background section. background section.
[I-D.hr-idr-rfc5575bis] provides updates to [RFC5575] to resolve
unclear sections in text and conflicts with interactions of filtering
actions.
1.1. Background 1.1. Background
[RFC5575] defines the flow specification (FlowSpec) that is an [RFC5575] defines the flow specification (FlowSpec) that is an
n-tuple consisting of several matching criteria that can be applied n-tuple consisting of several matching criteria that can be applied
to IP traffic. The matching criteria can include elements such as to IP traffic. The matching criteria can include elements such as
source and destination address prefixes, IP protocol, and transport source and destination address prefixes, IP protocol, and transport
protocol port numbers. A given IP packet is said to match the protocol port numbers. A given IP packet is said to match the
defined flow if it matches all the specified criteria. [RFC5575] defined flow if it matches all the specified criteria. [RFC5575]
also defines a set of filtering actions, such as rate limit, also defines a set of filtering actions, such as rate limit,
redirect, marking, associated with each flow specification. A new redirect, marking, associated with each flow specification. A new
Border Gateway Protocol Network Layer Reachability Information (BGP Border Gateway Protocol Network Layer Reachability Information (BGP
NLRI) (AFI/SAFI: 1/133 for IPv4, AFI/SAFI: 1/134 for VPNv4) encoding NLRI) (AFI/SAFI: 1/133 for IPv4, AFI/SAFI: 1/134 for VPNv4) encoding
format is used to distribute traffic flow specifications. format is used to distribute traffic flow specifications.
[Note: [I-D.hr-idr-rfc5575bis] updates [RFC5575].]
[RFC3107] specifies the way in which the label mapping information [RFC3107] specifies the way in which the label mapping information
for a particular route is piggybacked in the same Border Gateway for a particular route is piggybacked in the same Border Gateway
Protocol Update message that is used to distribute the route itself. Protocol Update message that is used to distribute the route itself.
Label mapping information is carried as part of the Network Layer Label mapping information is carried as part of the Network Layer
Reachability Information (NLRI) in the Multiprotocol Extensions Reachability Information (NLRI) in the Multiprotocol Extensions
attributes. The Network Layer Reachability Information is encoded as attributes. The Network Layer Reachability Information is encoded as
one or more triples of the form <length, label, prefix>. The NLRI one or more triples of the form <length, label, prefix>. The NLRI
contains a label is indicated by using Subsequent Address Family contains a label is indicated by using Subsequent Address Family
Identifier (SAFI) value 4. Identifier (SAFI) value 4.
skipping to change at page 8, line 26 skipping to change at page 8, line 45
October 2015, <http://www.rfc-editor.org/info/rfc7674>. October 2015, <http://www.rfc-editor.org/info/rfc7674>.
8.2. Informative References 8.2. Informative References
[I-D.filsfils-spring-segment-routing-central-epe] [I-D.filsfils-spring-segment-routing-central-epe]
Filsfils, C., Previdi, S., Patel, K., Shaw, S., Ginsburg, Filsfils, C., Previdi, S., Patel, K., Shaw, S., Ginsburg,
D., and D. Afanasiev, "Segment Routing Centralized Egress D., and D. Afanasiev, "Segment Routing Centralized Egress
Peer Engineering", draft-filsfils-spring-segment-routing- Peer Engineering", draft-filsfils-spring-segment-routing-
central-epe-05 (work in progress), August 2015. central-epe-05 (work in progress), August 2015.
[I-D.hr-idr-rfc5575bis]
Hares, S., Raszuk, R., McPherson, D., Loibl, C., and M.
Bacher, "Dissemination of Flow Specification Rules",
draft-hr-idr-rfc5575bis-02 (work in progress), November
2016.
[I-D.ietf-idr-bgp-flowspec-oid] [I-D.ietf-idr-bgp-flowspec-oid]
Uttaro, J., Filsfils, C., Smith, D., Alcaide, J., and P. Uttaro, J., Filsfils, C., Smith, D., Alcaide, J., and P.
Mohapatra, "Revised Validation Procedure for BGP Flow Mohapatra, "Revised Validation Procedure for BGP Flow
Specifications", draft-ietf-idr-bgp-flowspec-oid-03 (work Specifications", draft-ietf-idr-bgp-flowspec-oid-03 (work
in progress), March 2016. in progress), March 2016.
[I-D.ietf-idr-flow-spec-v6] [I-D.ietf-idr-flow-spec-v6]
McPherson, D., Raszuk, R., Pithawala, B., Andy, A., and S. McPherson, D., Raszuk, R., Pithawala, B.,
Hares, "Dissemination of Flow Specification Rules for akarch@cisco.com, a., and S. Hares, "Dissemination of Flow
IPv6", draft-ietf-idr-flow-spec-v6-07 (work in progress), Specification Rules for IPv6", draft-ietf-idr-flow-spec-
March 2016. v6-07 (work in progress), March 2016.
[I-D.ietf-idr-flowspec-l2vpn] [I-D.ietf-idr-flowspec-l2vpn]
Weiguo, H., Litkowski, S., and S. Zhuang, "Dissemination Weiguo, H., liangqiandeng, l., Litkowski, S., and S.
of Flow Specification Rules for L2 VPN", draft-ietf-idr- Zhuang, "Dissemination of Flow Specification Rules for L2
flowspec-l2vpn-04 (work in progress), May 2016. VPN", draft-ietf-idr-flowspec-l2vpn-04 (work in progress),
May 2016.
[I-D.ietf-idr-flowspec-mpls-match] [I-D.ietf-idr-flowspec-mpls-match]
Yong, L., Hares, S., and J. You, "BGP Flow Specification Yong, L., Hares, S., liangqiandeng, l., and J. You, "BGP
Filter for MPLS Label", draft-ietf-idr-flowspec-mpls- Flow Specification Filter for MPLS Label", draft-ietf-idr-
match-00 (work in progress), May 2016. flowspec-mpls-match-00 (work in progress), May 2016.
Authors' Addresses Authors' Addresses
Qiandeng Liang Qiandeng Liang
Huawei Huawei
101 Software Avenue, Yuhuatai District 101 Software Avenue, Yuhuatai District
Nanjing, 210012 Nanjing, 210012
China China
Email: liangqiandeng@huawei.com Email: liangqiandeng@huawei.com
Susan Hares Susan Hares
Huawei Huawei
 End of changes. 15 change blocks. 
18 lines changed or deleted 32 lines changed or added

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