Dissemination of Flow Specification Rules for IPv6
draft-ietf-idr-flow-spec-v6-17

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-10-22 (latest revision 2020-10-20)
Replaces draft-raszuk-idr-flow-spec-v6
Stream Internent Engineering Task Force (IETF)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Jie Dong
Shepherd write-up Show (last changed 2020-06-23)
IESG IESG state IESG Evaluation
Consensus Boilerplate Yes
Telechat date
Has enough positions to pass.
Responsible AD Alvaro Retana
Send notices to Jie Dong <jie.dong@huawei.com>, aretana.ietf@gmail.com
IANA IANA review state IANA OK - Actions Needed
IDR Working Group                                          C. Loibl, Ed.
Internet-Draft                                   next layer Telekom GmbH
Updates: I-D.ietf-idr-rfc5575bis (if                      R. Raszuk, Ed.
         approved)                                          Bloomberg LP
Intended status: Standards Track                           S. Hares, Ed.
Expires: April 23, 2021                                           Huawei
                                                        October 20, 2020

           Dissemination of Flow Specification Rules for IPv6
                     draft-ietf-idr-flow-spec-v6-17

Abstract

   Dissemination of Flow Specification Rules provides a Border Gateway
   Protocol extension for the propagation of traffic flow information
   for the purpose of rate limiting or filtering IPv4 protocol data
   packets.

   This document extends I-D.ietf-idr-rfc5575bis with IPv6
   functionality.  It also updates I-D.ietf-idr-rfc5575bis by changing
   the IANA Flow Spec Component Types registry.

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 April 23, 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
   (https://trustee.ietf.org/license-info) in effect on the date of

Loibl, et al.            Expires April 23, 2021                 [Page 1]
Internet-Draft           IPv6 Flow Specification            October 2020

   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  . . . . . . . . . . . . .   3
     3.1.  Type 1 - Destination IPv6 Prefix  . . . . . . . . . . . .   4
     3.2.  Type 2 - Source IPv6 Prefix . . . . . . . . . . . . . . .   4
     3.3.  Type 3 - Upper-Layer Protocol . . . . . . . . . . . . . .   4
     3.4.  Type 7 - ICMPv6 Type  . . . . . . . . . . . . . . . . . .   5
     3.5.  Type 8 - ICMPv6 Code  . . . . . . . . . . . . . . . . . .   5
     3.6.  Type 12 - Fragment  . . . . . . . . . . . . . . . . . . .   6
     3.7.  Type 13 - Flow Label (new)  . . . . . . . . . . . . . . .   6
     3.8.  Encoding Example  . . . . . . . . . . . . . . . . . . . .   7
   4.  Ordering of Flow Specifications . . . . . . . . . . . . . . .   8
   5.  Validation Procedure  . . . . . . . . . . . . . . . . . . . .   9
   6.  IPv6 Traffic Filtering Action changes . . . . . . . . . . . .   9
     6.1.  Redirect IPv6 (rt-redirect-ipv6) Type/Sub-Type 0x80/TBD .   9
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
     8.1.  Flow Spec IPv6 Component Types  . . . . . . . . . . . . .  10
       8.1.1.  Registry Template . . . . . . . . . . . . . . . . . .  10
       8.1.2.  Registry Contents . . . . . . . . . . . . . . . . . .  10
     8.2.  Extended Community Flow Spec IPv6 Actions . . . . . . . .  12
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  13
   10. Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  13
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  13
     11.2.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .  14
   Appendix A.  Example python code: flow_rule_cmp_v6  . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Introduction

   The growing amount of IPv6 traffic in private and public networks
   requires the extension of tools used in IPv4-only networks to be also
   capable of supporting IPv6 data packets.

   This document analyzes the differences of IPv6 [RFC8200] flows
Show full document text