Destination-IP-Origin-AS Filter for BGP Flow Specification
draft-wang-idr-flowspec-dip-origin-as-filter-00
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-11-04
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group H. Wang
Internet-Draft Huawei
Intended status: Standards Track A. Wang
Expires: May 7, 2020 China Telecom
S. Zhuang
Huawei
November 04, 2019
Destination-IP-Origin-AS Filter for BGP Flow Specification
draft-wang-idr-flowspec-dip-origin-as-filter-00
Abstract
This document specifies a new BGP-FS component type to support AS-
level filtering. The match field is the origin AS number of the
destination IP address that is encoded in the Flowspec NLRI.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
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 May 7, 2020.
Copyright Notice
Copyright (c) 2019 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
Wang, et al. Expires May 7, 2020 [Page 1]
Internet-Draft Destination-Origin-AS Filter November 2019
(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 . . . . . . . . . . . . . . . . . . 2
3. The Flow Specification Encoding for Destination-Origin-AS
Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Use Case . . . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. IANA . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 6
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
BGP Flow Specification (BGP-FS) [RFC5575] defines a new BGP NLRI to
distribute traffic flow specification rules via BGP ([RFC4271]).
BGP-FS policies have a match condition that may be n-tuple match in a
policy, and an action that modifies the packet and forwards/drops the
packet. Via BGP, new filter rules can be sent to all BGP peers
simultaneously without changing router configuration, and the BGP
peer can install these routes in the forwarding table. BGP-FS
defines Network Layer Reachability Information (NLRI) format used to
distribute traffic flow specification rules. NLRI (AFI=1, SAFI=133)
is for IPv4 unicast filtering. NLRI (AFI=1, SAFI=134) is for BGP/
MPLS VPN filtering.[I-D.ietf-idr-flowspec-l2vpn][I-D.ietf-idr-
flowspec-l2vpn] extends the flow-spec rules for layer 2 Ethernet
packets.
This document specifies a new BGP-FS component type to support AS-
level filtering. The match field is the origin AS number of the
destination IP address that is encoded in the Flowspec NLRI.
2. Definitions and Acronyms
o FS: Flow Specification
o Destination-Origin-AS: The origin AS number of the destination IP
address
Wang, et al. Expires May 7, 2020 [Page 2]
Internet-Draft Destination-Origin-AS Filter November 2019
3. The Flow Specification Encoding for Destination-Origin-AS Filter
This document proposes a new flow specification rule that is encoded
in the NLRI. The following new component type is defined.
Show full document text