draft-ietf-idr-flowspec-interfaceset-02.txt   draft-ietf-idr-flowspec-interfaceset-03.txt 
Routing Area Working Group S. Litkowski Routing Area Working Group S. Litkowski
Internet-Draft Orange Internet-Draft Orange
Intended status: Standards Track A. Simpson Intended status: Standards Track A. Simpson
Expires: April 28, 2017 Nokia Expires: September 12, 2017 Nokia
K. Patel K. Patel
Arrcus, Inc Arrcus, Inc
J. Haas J. Haas
Juniper Networks Juniper Networks
L. Yong L. Yong
Huawei Huawei
October 25, 2016 March 11, 2017
Applying BGP flowspec rules on a specific interface set Applying BGP flowspec rules on a specific interface set
draft-ietf-idr-flowspec-interfaceset-02 draft-ietf-idr-flowspec-interfaceset-03
Abstract Abstract
BGP flowspec is an extension to BGP that allows for the dissemination BGP flowspec is an extension to BGP that allows for the dissemination
of traffic flow specification rules. The primary application of this of traffic flow specification rules. The primary application of this
extension is DDoS mitigation where the flowspec rules are applied in extension is DDoS mitigation where the flowspec rules are applied in
most cases to all peering routers of the network. most cases to all peering routers of the network.
This document will present another use case of BGP flowspec where This document will present another use case of BGP flowspec where
flow specifications are used to maintain some access control lists at flow specifications are used to maintain some access control lists at
skipping to change at page 2, line 29 skipping to change at page 2, line 29
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 April 28, 2017. This Internet-Draft will expire on September 12, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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
skipping to change at page 3, line 24 skipping to change at page 3, line 24
6. Handling rules from different sources in the processing pipe 9 6. Handling rules from different sources in the processing pipe 9
6.1. Combining Policy Based Routing with BGP flowspec and 6.1. Combining Policy Based Routing with BGP flowspec and
interface-set . . . . . . . . . . . . . . . . . . . . . . 10 interface-set . . . . . . . . . . . . . . . . . . . . . . 10
6.2. Combining flow collection with BGP flowspec and 6.2. Combining flow collection with BGP flowspec and
interface-set . . . . . . . . . . . . . . . . . . . . . . 11 interface-set . . . . . . . . . . . . . . . . . . . . . . 11
7. Scaling of per interface rules . . . . . . . . . . . . . . . 11 7. Scaling of per interface rules . . . . . . . . . . . . . . . 11
8. Deployment considerations . . . . . . . . . . . . . . . . . . 12 8. Deployment considerations . . . . . . . . . . . . . . . . . . 12
9. Security Considerations . . . . . . . . . . . . . . . . . . . 12 9. Security Considerations . . . . . . . . . . . . . . . . . . . 12
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 11.1. FlowSpec Transitive Extended Communities . . . . . . . . 13
12.1. Normative References . . . . . . . . . . . . . . . . . . 13 11.2. FlowSpec Non-Transitive Extended Communities . . . . . . 13
11.3. FlowSpec interface-set Extended Community . . . . . . . 13
11.4. Allocation Advice to IANA . . . . . . . . . . . . . . . 13
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 14
12.1. Normative References . . . . . . . . . . . . . . . . . . 14
12.2. Informative References . . . . . . . . . . . . . . . . . 14 12.2. Informative References . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Use case 1. Use case
1.1. Specific filtering for DDoS 1.1. Specific filtering for DDoS
----------------- --- (ebgp) - Peer3 (BW 10G) ----------------- --- (ebgp) - Peer3 (BW 10G)
/ \/ / \/
| /| | /|
skipping to change at page 13, line 7 skipping to change at page 13, line 7
of flowspec rules would be retained and the flowspec action will be of flowspec rules would be retained and the flowspec action will be
retained. retained.
10. Acknowledgements 10. Acknowledgements
Authors would like to thanks Wim Hendrickx and Robert Raszuk for Authors would like to thanks Wim Hendrickx and Robert Raszuk for
their valuable comments. their valuable comments.
11. IANA Considerations 11. IANA Considerations
11.1. FlowSpec Transitive Extended Communities
This document requests a new type from the "BGP Transitive Extended This document requests a new type from the "BGP Transitive Extended
Community Types" extended community registry. This type name shall Community Types" extended community registry from the First Come
be 'FlowSpec'. First Served range. This type name shall be 'FlowSpec Transitive
Extended Communities'.
This document requests creation of a new registry called "FlowSpec
Transitive Extended Community Sub-Types". This registry contains
values of the second octet (the "Sub-Type" field) of an extended
community when the value of the first octet (the "Type" field) is the
value allocated in this document. The registration procedure for
values in this registry shall be First Come First Served.
11.2. FlowSpec Non-Transitive Extended Communities
This document requests a new type from the "BGP Non-Transitive This document requests a new type from the "BGP Non-Transitive
Extended Community Types" extended community registry. This type Extended Community Types" extended community registry from the First
name shall be 'FlowSpec'. Come First Served range. This type name shall be 'FlowSpec Non-
Transitive Extended Communities'.
This document requests creation of a new registry called "FlowSpec This document requests creation of a new registry called "FlowSpec
Extended Community Sub-Types". This registry contains values of the Non-Transitive Extended Community Sub-Types". This registry contains
second octet (the "Sub-Type" field) of an extended community when the values of the second octet (the "Sub-Type" field) of an extended
value of the first octet (the "Type" field) is to one of those community when the value of the first octet (the "Type" field) is the
allocated in this document. value allocated in this document. The registration procedure for
values in this registry shall be First Come First Served.
Within this new registry, this document requests a new subtype 11.3. FlowSpec interface-set Extended Community
(suggested value 0x02), this sub-type shall be named "interface-set".
Within the two new registries above, this document requests a new
subtype (suggested value 0x02). This sub-type shall be named
"interface-set", with a reference to this document.
11.4. Allocation Advice to IANA
IANA is requested to allocate the values of the FlowSpec Transitive
and Non-Transitive Extended Communities such that their values are
identical when ignoring the second high-order bit (Transitive). See
section 2, [RFC4360]. An example allocation would be 0x09/0x49.
It is suggested to IANA that, when possible, allocations from the
FlowSpec Transitive/Non-Transitive Extended Community Sub-Types
registries are made for transitive or non-transitive versions of
features (section 2, [RFC4360]) that their code point in both
registries is identical.
12. References 12. References
12.1. Normative References 12.1. Normative References
[I-D.ietf-idr-rtc-no-rt] [I-D.ietf-idr-rtc-no-rt]
Rosen, E., Patel, K., Haas, J., and R. Raszuk, "Route Rosen, E., Patel, K., Haas, J., and R. Raszuk, "Route
Target Constrained Distribution of Routes with no Route Target Constrained Distribution of Routes with no Route
Targets", draft-ietf-idr-rtc-no-rt-05 (work in progress), Targets", draft-ietf-idr-rtc-no-rt-06 (work in progress),
May 2016. November 2016.
[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,
<http://www.rfc-editor.org/info/rfc2119>. <http://www.rfc-editor.org/info/rfc2119>.
[RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended
Communities Attribute", RFC 4360, DOI 10.17487/RFC4360, Communities Attribute", RFC 4360, DOI 10.17487/RFC4360,
February 2006, <http://www.rfc-editor.org/info/rfc4360>. February 2006, <http://www.rfc-editor.org/info/rfc4360>.
skipping to change at page 14, line 23 skipping to change at page 15, line 4
Hares, S., "BGP Flow Specification Version 2", draft- Hares, S., "BGP Flow Specification Version 2", draft-
hares-idr-flowspec-v2-00 (work in progress), June 2016. hares-idr-flowspec-v2-00 (work in progress), June 2016.
[I-D.uttaro-idr-bgp-persistence] [I-D.uttaro-idr-bgp-persistence]
Uttaro, J., Chen, E., Decraene, B., and J. Scudder, Uttaro, J., Chen, E., Decraene, B., and J. Scudder,
"Support for Long-lived BGP Graceful Restart", draft- "Support for Long-lived BGP Graceful Restart", draft-
uttaro-idr-bgp-persistence-03 (work in progress), November uttaro-idr-bgp-persistence-03 (work in progress), November
2013. 2013.
Authors' Addresses Authors' Addresses
Stephane Litkowski Stephane Litkowski
Orange Orange
Email: stephane.litkowski@orange.com Email: stephane.litkowski@orange.com
Adam Simpson Adam Simpson
Nokia Nokia
Email: adam.simpson@nokia.com Email: adam.1.simpson@nokia.com
Keyur Patel Keyur Patel
Arrcus, Inc Arrcus, Inc
Email: keyur@arrcus.com Email: keyur@arrcus.com
Jeff Haas Jeff Haas
Juniper Networks Juniper Networks
Email: jhaas@juniper.net Email: jhaas@juniper.net
 End of changes. 14 change blocks. 
21 lines changed or deleted 54 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/