Dissemination of Flow Specification Rules for IPv6
draft-ietf-idr-flow-spec-v6-12
The information below is for an old version of the document |
Document |
Type |
|
Active Internet-Draft (idr WG)
|
|
Authors |
|
Christoph Loibl
,
Robert Raszuk
,
Susan Hares
|
|
Last updated |
|
2020-07-10
(latest revision 2020-04-20)
|
|
Replaces |
|
draft-raszuk-idr-flow-spec-v6
|
|
Stream |
|
Internent Engineering Task Force (IETF)
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
|
Reviews |
|
|
Stream |
WG state
|
|
WG Consensus: Waiting for Write-Up
Waiting for Referenced Document
|
|
Document shepherd |
|
Jie Dong
|
|
Shepherd write-up |
|
Show
(last changed 2020-06-23)
|
IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
Jie Dong <jie.dong@huawei.com>
|
IDR Working Group C. Loibl, Ed.
Internet-Draft next layer Telekom GmbH
Intended status: Standards Track R. Raszuk, Ed.
Expires: January 11, 2021 Bloomberg LP
S. Hares, Ed.
Huawei
July 10, 2020
Dissemination of Flow Specification Rules for IPv6
draft-ietf-idr-flow-spec-v6-12
Abstract
Dissemination of Flow Specification Rules I-D.ietf-idr-rfc5575bis
provides a protocol extension for propagation of traffic flow
information for the purpose of rate limiting or filtering. I-D.ietf-
idr-rfc5575bis specifies those extensions for IPv4 protocol data
packets only.
This specification extends I-D.ietf-idr-rfc5575bis and defines
changes to the original document in order to make it also usable and
applicable to IPv6 data packets.
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 January 11, 2021.
Copyright Notice
Copyright (c) 2020 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
Loibl, et al. Expires January 11, 2021 [Page 1]
Internet-Draft IPv6 Flow Specification July 2020
(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
1.1. Definitions of Terms Used in This Memo . . . . . . . . . 3
2. IPv6 Flow Specification encoding in BGP . . . . . . . . . . . 3
3. IPv6 Flow Specification components . . . . . . . . . . . . . 4
3.1. Type 1 - Destination IPv6 Prefix . . . . . . . . . . . . 4
3.2. Type 2 - Source IPv6 Prefix . . . . . . . . . . . . . . . 4
3.3. Type 3 - Next Header . . . . . . . . . . . . . . . . . . 4
3.4. Type 7 - ICMPv6 type . . . . . . . . . . . . . . . . . . 5
3.5. Type 8 - ICMPv6 code . . . . . . . . . . . . . . . . . . 5
3.6. Type 12 - Fragment . . . . . . . . . . . . . . . . . . . 5
3.7. Type 13 - Flow Label (new) . . . . . . . . . . . . . . . 6
3.8. Encoding Example . . . . . . . . . . . . . . . . . . . . 6
4. Ordering of Flow Specifications . . . . . . . . . . . . . . . 8
5. Validation Procedure . . . . . . . . . . . . . . . . . . . . 8
6. IPv6 Traffic Filtering Action changes . . . . . . . . . . . . 8
6.1. Redirect IPv6 (rt-redirect-ipv6) Type/Sub-Type 0x80/TBD . 9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 9
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 11
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
11.1. Normative References . . . . . . . . . . . . . . . . . . 12
11.2. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Appendix A. Example python code: flow_rule_cmp_v6 . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction
The growing amount of IPv6 traffic in private and public networks
requires the extension of tools used in the IPv4 only networks to be
also capable of supporting IPv6 data packets.
In this document authors analyze the differences of IPv6 [RFC8200]
flows description from those of traditional IPv4 packets and propose
subset of new encoding formats to enable Dissemination of Flow
Specification Rules [I-D.ietf-idr-rfc5575bis] for IPv6.
Show full document text