draft-ietf-idr-flow-spec-v6-00.txt   draft-ietf-idr-flow-spec-v6-01.txt 
IDR Working Group R. Raszuk IDR Working Group R. Raszuk, Ed.
Internet-Draft B. Pithawala Internet-Draft NTT MCL Inc.
Intended status: Standards Track Cisco Systems Intended status: Standards Track B. Pithawala
Expires: December 4, 2011 D. McPherson Expires: April 9, 2012 Cisco Systems
D. McPherson
Verisign, Inc. Verisign, Inc.
June 2, 2011 October 7, 2011
Dissemination of Flow Specification Rules for IPv6 Dissemination of Flow Specification Rules for IPv6
draft-ietf-idr-flow-spec-v6-00 draft-ietf-idr-flow-spec-v6-01
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 39 skipping to change at page 1, line 40
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 December 4, 2011. This Internet-Draft will expire on April 9, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 3, line 34 skipping to change at page 3, line 34
The [RFC5575] defines a new SAFIs (133 for IPv4) and (134 for VPNv4) The [RFC5575] defines a new SAFIs (133 for IPv4) and (134 for VPNv4)
applications in order to carry corresponding to each such application applications in order to carry corresponding to each such application
flow specification. flow specification.
This document will redefine the [RFC5575] SAFIs in order to make them This document will redefine the [RFC5575] SAFIs in order to make them
AFI specific and applicable to both IPv4 and IPv6 applications. AFI specific and applicable to both IPv4 and IPv6 applications.
The following changes are defined: The following changes are defined:
"SAFI 133 for IPv4 dissemination of flow specification rules" to "SAFI 133 for IPv4 dissemination of flow specification rules" to
now be defined as "SAFI 133 for IP dissemination of flow now be defined as "SAFI 133 for dissemination of unicast flow
specification rules" specification rules"
"SAFI 134 for VPNv4 dissemination of flow specification rules" to "SAFI 134 for VPNv4 dissemination of flow specification rules" to
now be defined as "SAFI 134 for L3VPN dissemination of flow now be defined as "SAFI 134 for dissemination of L3VPN flow
specification rules" specification rules"
For both SAFIs the indication to which address family they are For both SAFIs the indication to which address family they are
referring to will be recognized by AFI value (AFI=1 for IPv4 or referring to will be recognized by AFI value (AFI=1 for IPv4 or
VPNv4, AFI=2 for IPv6 and VPNv6 respectively). Such modification is VPNv4, AFI=2 for IPv6 and VPNv6 respectively). Such modification is
fully backwards compatible with existing implementation and fully backwards compatible with existing implementation and
production deployments. production deployments.
It needs to be observed that such choice of proposed encoding is It needs to be observed that such choice of proposed encoding is
compatible with filter validation against routing reachability compatible with filter validation against routing reachability
skipping to change at page 5, line 30 skipping to change at page 5, line 30
Type 11 - Traffic Class Type 11 - Traffic Class
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 Traffic Class 8-bit field [RFC2460] encoded in a single the Traffic Class 8-bit field [RFC2460] encoded in a single
octet.The operator byte is encoded as specified in component type octet.The operator byte is encoded as specified in component type
3 of [RFC5575]. 3 of [RFC5575].
Type 12 - Fragment - Removed Type 12 - Fragment - Not supported for AFI=2
This type is removed for IPv6 flow specification as in IPv6 This type is not supported for AFI=2 as in IPv6 fragmentation does
fragmentation does not happen in the network. not happen in the network.
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 encoded the 20-bit Flow Label field [RFC2460].The operator byte is encoded
as specified in the component type 3 of [RFC5575]. as specified in the component type 3 of [RFC5575].
4. IPv6 Flow Specification Traffic Filtering Action changes 4. IPv6 Flow Specification Traffic Filtering Action changes
skipping to change at page 6, line 45 skipping to change at page 6, line 45
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 - Traffic Class Type 11 - Traffic Class
Type 12 - Reserved Type 12 - Reserved
Type 13 - Flow Label Type 13 - Flow Label
7. Acknowledgments 7. Acknowledgments
Authors would like to thank Pedro Marques and Hannes Gredler for Authors would like to thank Pedro Marques, Hannes Gredler and Bruno
their valuable input. Rijsman for their valuable input.
8. References 8. References
8.1. Normative References 8.1. Normative References
[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, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 [RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6
(IPv6) Specification", RFC 2460, December 1998. (IPv6) Specification", RFC 2460, December 1998.
skipping to change at page 7, line 33 skipping to change at page 7, line 33
Rules", RFC 5575, August 2009. Rules", RFC 5575, August 2009.
8.2. Informative References 8.2. Informative References
[RFC5095] Abley, J., Savola, P., and G. Neville-Neil, "Deprecation [RFC5095] Abley, J., Savola, P., and G. Neville-Neil, "Deprecation
of Type 0 Routing Headers in IPv6", RFC 5095, of Type 0 Routing Headers in IPv6", RFC 5095,
December 2007. December 2007.
Authors' Addresses Authors' Addresses
Robert Raszuk Robert Raszuk (editor)
Cisco Systems NTT MCL Inc.
170 West Tasman Drive 101 S Ellsworth Avenue Suite 350
San Jose, CA 95134 San Mateo, CA 94401
US US
Email: raszuk@cisco.com Email: robert@raszuk.net
Burjiz Pithawala Burjiz Pithawala
Cisco Systems Cisco Systems
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
US US
Email: bpithaw@cisco.com Email: bpithaw@cisco.com
Danny McPherson Danny McPherson
Verisign, Inc. Verisign, Inc.
 End of changes. 11 change blocks. 
19 lines changed or deleted 20 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/