draft-ietf-idr-flow-spec-v6-04.txt   draft-ietf-idr-flow-spec-v6-05.txt 
IDR Working Group R. Raszuk, Ed. IDR Working Group R. Raszuk, Ed.
Internet-Draft NTT MCL Inc. Internet-Draft NTT MCL Inc.
Updates: RFC5575 (if approved) B. Pithawala Updates: RFC5575 (if approved) B. Pithawala
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: August 1, 2014 D. McPherson Expires: September 21, 2014 D. McPherson
Verisign, Inc. Verisign, Inc.
A. Karch A. Karch
Cisco Systems Cisco Systems
January 28, 2014 March 20, 2014
Dissemination of Flow Specification Rules for IPv6 Dissemination of Flow Specification Rules for IPv6
draft-ietf-idr-flow-spec-v6-04 draft-ietf-idr-flow-spec-v6-05
Abstract Abstract
Dissemination of Flow Specification Rules [RFC5575] provides a Dissemination of Flow Specification Rules [RFC5575] provides a
protocol extension for propagation of traffic flow information for protocol extension for propagation of traffic flow information for
the purpose of rate limiting or filtering. The [RFC5575] specifies the purpose of rate limiting or filtering. The [RFC5575] specifies
those extensions for IPv4 protocol data packets. those extensions for IPv4 protocol data packets.
This specification extends the current [RFC5575] and defines changes This specification extends the current [RFC5575] and defines changes
to the original document in order to make it also usable and to the original document in order to make it also usable and
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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 August 1, 2014. This Internet-Draft will expire on September 21, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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
skipping to change at page 2, line 24 skipping to change at page 2, line 24
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. IPv6 Flow Specification encoding in BGP . . . . . . . . . . . 2 2. IPv6 Flow Specification encoding in BGP . . . . . . . . . . . 2
3. IPv6 Flow Specification types changes . . . . . . . . . . . . 3 3. IPv6 Flow Specification types changes . . . . . . . . . . . . 3
3.1. Order of Traffic Filtering Rules . . . . . . . . . . . . 5 3.1. Order of Traffic Filtering Rules . . . . . . . . . . . . 5
4. IPv6 Flow Specification Traffic Filtering Action changes . . 6 4. IPv6 Flow Specification Traffic Filtering Action changes . . 6
5. Security considerations . . . . . . . . . . . . . . . . . . . 7 5. Security considerations . . . . . . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 8 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
8.1. Normative References . . . . . . . . . . . . . . . . . . 8 8.1. Normative References . . . . . . . . . . . . . . . . . . 8
8.2. Informative References . . . . . . . . . . . . . . . . . 8 8.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
The growing amount of IPv6 traffic in private and public networks The growing amount of IPv6 traffic in private and public networks
requires the extension of tools used in the IPv4 only networks to be requires the extension of tools used in the IPv4 only networks to be
also capable of supporting IPv6 data packets. also capable of supporting IPv6 data packets.
In this document authors analyze the differences of IPv6 [RFC2460] In this document authors analyze the differences of IPv6 [RFC2460]
flows description from those of traditional IPv4 packets and propose flows description from those of traditional IPv4 packets and propose
subset of new encoding formats to enable Dissemination of Flow subset of new encoding formats to enable Dissemination of Flow
skipping to change at page 5, line 26 skipping to change at page 5, line 26
+ Bit 4 - Last fragment (LF) + Bit 4 - Last fragment (LF)
Type 13 - Flow Label - New type Type 13 - Flow Label - New type
Encoding: <type (1 octet), [op, value]+> Encoding: <type (1 octet), [op, value]+>
Contains a set of {operator, value} pairs that are used to match Contains a set of {operator, value} pairs that are used to match
the 20-bit Flow Label field [RFC2460]. The operator byte is the 20-bit Flow Label field [RFC2460]. The operator byte is
encoded as specified in the component type 3 of [RFC5575]. encoded as specified in the component type 3 of [RFC5575].
Type 14 - Traffic Class - New type
Encoding: <type (1 octet), [op, value]+>
Contains a set of {operator, value} pairs that are used to match
the full Traffic Class 8-bit field [RFC2460] encoded in a single
octet. The operator byte is encoded as specified in component
type 3 of [RFC5575].
The following example demonstrates the new prefix encoding for: "all The following example demonstrates the new prefix encoding for: "all
packets to ::1234:5678:9A00:0/80-104 from 192::/8 and port {range packets to ::1234:5678:9A00:0/80-104 from 192::/8 and port {range
[137, 139] or 8080}". [137, 139] or 8080}". In the destination prefix, "80-" represents
the prefix offset of 80 bits. In this exmaple, the 0 offset is
omitted from the printed source prefix.
+---------------------------+-------------+-------------------------+ +---------------------------+-------------+-------------------------+
| destination | source | port | | destination | source | port |
+---------------------------+-------------+-------------------------+ +---------------------------+-------------+-------------------------+
| 0x01 40 68 12 34 56 78 9A | 02 00 08 c0 | 04 03 89 45 8b 91 1f 90 | | 0x01 40 68 12 34 56 78 9A | 02 00 08 c0 | 04 03 89 45 8b 91 1f 90 |
+---------------------------+-------------+-------------------------+ +---------------------------+-------------+-------------------------+
3.1. Order of Traffic Filtering Rules 3.1. Order of Traffic Filtering Rules
The orignal definition for the order of traffic filtering rules can The orignal definition for the order of traffic filtering rules can
skipping to change at page 8, line 8 skipping to change at page 7, line 50
Type 4 - Port Type 4 - Port
Type 5 - Destination port Type 5 - Destination port
Type 6 - Source port Type 6 - Source port
Type 7 - ICMP type Type 7 - ICMP type
Type 8 - ICMP code Type 8 - ICMP code
Type 9 - TCP flags Type 9 - TCP flags
Type 10 - Packet length Type 10 - Packet length
Type 11 - DSCP Type 11 - DSCP
Type 12 - Fragment Type 12 - Fragment
Type 13 - Flow Label Type 13 - Flow Label
Type 14 - Traffic Class
7. Acknowledgments 7. Acknowledgments
Authors would like to thank Pedro Marques, Hannes Gredler and Bruno Authors would like to thank Pedro Marques, Hannes Gredler and Bruno
Rijsman, Brian Carpenter, and Thomas Mangin for their valuable input. Rijsman, Brian Carpenter, and Thomas Mangin for their valuable input.
8. References 8. References
8.1. Normative References 8.1. Normative References
[I-D.ietf-6man-flow-3697bis] [I-D.ietf-6man-flow-3697bis]
Amante, S., Carpenter, B., Jiang, S., and J. Rajahalme, Amante, S., Carpenter, B., Jiang, S., and J. Rajahalme,
"IPv6 Flow Label Specification", draft-ietf-6man-flow- "IPv6 Flow Label Specification", draft-ietf-6man-flow-
 End of changes. 10 change blocks. 
18 lines changed or deleted 9 lines changed or added

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