draft-ietf-idr-rfc5575bis-03.txt   draft-ietf-idr-rfc5575bis-04.txt 
IDR Working Group S. Hares IDR Working Group S. Hares
Internet-Draft Huawei Internet-Draft Huawei
Obsoletes: 5575,7674 (if approved) R. Raszuk Obsoletes: 5575,7674 (if approved) C. Loibl
Intended status: Standards Track Bloomberg LP Intended status: Standards Track Next Layer Communications
Expires: December 31, 2017 D. McPherson Expires: January 3, 2018 R. Raszuk
Bloomberg LP
D. McPherson
Verisign Verisign
C. Loibl
Next Layer Communications
M. Bacher M. Bacher
T-Mobile Austria T-Mobile Austria
June 29, 2017 July 2, 2017
Dissemination of Flow Specification Rules Dissemination of Flow Specification Rules
draft-ietf-idr-rfc5575bis-03 draft-ietf-idr-rfc5575bis-04
Abstract Abstract
This document updates RFC5575 which defines a Border Gateway Protocol This document updates RFC5575 which defines a Border Gateway Protocol
Network Layer Reachability Information (BGP NLRI) encoding format Network Layer Reachability Information (BGP NLRI) encoding format
that can be used to distribute traffic flow specifications. This that can be used to distribute traffic flow specifications. This
allows the routing system to propagate information regarding more allows the routing system to propagate information regarding more
specific components of the traffic aggregate defined by an IP specific components of the traffic aggregate defined by an IP
destination prefix. This draft specifies IPv4 traffic flow destination prefix. This draft specifies IPv4 traffic flow
specifications via a BGP NLRI which carries traffic flow specifications via a BGP NLRI which carries traffic flow
skipping to change at page 2, line 20 skipping to change at page 2, line 20
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 31, 2017. This Internet-Draft will expire on January 3, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 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 38 skipping to change at page 3, line 38
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 24
11.1. AFI/SAFI Definitions . . . . . . . . . . . . . . . . . . 24 11.1. AFI/SAFI Definitions . . . . . . . . . . . . . . . . . . 24
11.2. Flow Component Definitions . . . . . . . . . . . . . . . 24 11.2. Flow Component Definitions . . . . . . . . . . . . . . . 24
11.3. Extended Community Flow Specification Actions . . . . . 25 11.3. Extended Community Flow Specification Actions . . . . . 25
12. Security Considerations . . . . . . . . . . . . . . . . . . . 28 12. Security Considerations . . . . . . . . . . . . . . . . . . . 28
13. Original authors . . . . . . . . . . . . . . . . . . . . . . 28 13. Original authors . . . . . . . . . . . . . . . . . . . . . . 28
14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 29 14. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 29
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 29 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 29
15.1. Normative References . . . . . . . . . . . . . . . . . . 29 15.1. Normative References . . . . . . . . . . . . . . . . . . 29
15.2. Informative References . . . . . . . . . . . . . . . . . 31 15.2. Informative References . . . . . . . . . . . . . . . . . 31
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 31 Appendix A. Comparison with RFC 5575 . . . . . . . . . . . . . . 31
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 32
1. Introduction 1. Introduction
Modern IP routers contain both the capability to forward traffic Modern IP routers contain both the capability to forward traffic
according to IP prefixes as well as to classify, shape, rate limit, according to IP prefixes as well as to classify, shape, rate limit,
filter, or redirect packets based on administratively defined filter, or redirect packets based on administratively defined
policies. policies.
These traffic policy mechanisms allow the router to define match These traffic policy mechanisms allow the router to define match
rules that operate on multiple fields of the packet header. Actions rules that operate on multiple fields of the packet header. Actions
skipping to change at page 31, line 21 skipping to change at page 31, line 21
[I-D.ietf-idr-flow-spec-v6] [I-D.ietf-idr-flow-spec-v6]
McPherson, D., Raszuk, R., Pithawala, B., McPherson, D., Raszuk, R., Pithawala, B.,
akarch@cisco.com, a., and S. Hares, "Dissemination of Flow akarch@cisco.com, a., and S. Hares, "Dissemination of Flow
Specification Rules for IPv6", draft-ietf-idr-flow-spec- Specification Rules for IPv6", draft-ietf-idr-flow-spec-
v6-08 (work in progress), March 2017. v6-08 (work in progress), March 2017.
[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)", [RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)",
RFC 4303, DOI 10.17487/RFC4303, December 2005, RFC 4303, DOI 10.17487/RFC4303, December 2005,
<http://www.rfc-editor.org/info/rfc4303>. <http://www.rfc-editor.org/info/rfc4303>.
Appendix A. Comparison with RFC 5575
This document includes numerous editorial changes to [RFC5575]. It
is recommended to read the entire document. The authors, however
want to point out the following technical changes to [RFC5575]:
Section 4.2.3 defines a numeric operator and comparison bit
combinations. In [RFC5575] the meaning of those bit combination
was not explicitly defined and left open to the reader.
Section 4.2.3 - Section 4.2.8, Section 4.2.10, Section 4.2.11 make
use of the above numeric operator. The allowed length of the
comparison value was not consistently defined in [RFC5575].
Section 7 defines all traffic action extended communities as
transitive extended communities. [RFC5575] defined the traffic-
rate action to be non-transitive and did not define the
transitivity of the other action communities at all.
Section 7.2 introduces a new traffic filtering action (traffic-
rate-packets). This action did not exist in [RFC5575].
Section 7.4 contains the same redirect actions already defined in
[RFC5575] however, these actions have been renamed to "rt-
redirect" to make it clearer that the redirection is based on
route-target.
Section 7.6 introduces rules how updates of flow specifications
shall be handled in case they contain interfering actions.
Section 7.3 also cross-references this section. [RFC5575] did not
define this.
Authors' Addresses Authors' Addresses
Susan Hares Susan Hares
Huawei Huawei
7453 Hickory Hill 7453 Hickory Hill
Saline, MI 48176 Saline, MI 48176
USA USA
Email: shares@ndzh.com Email: shares@ndzh.com
Christoph Loibl
Next Layer Communications
Mariahilfer Guertel 37/7
Vienna 1150
AT
Phone: +43 664 1176414
Email: cl@tix.at
Robert Raszuk Robert Raszuk
Bloomberg LP Bloomberg LP
731 Lexington Ave 731 Lexington Ave
New York City, NY 10022 New York City, NY 10022
USA USA
Email: robert@raszuk.net Email: robert@raszuk.net
Danny McPherson Danny McPherson
Verisign Verisign
USA USA
Email: dmcpherson@verisign.com Email: dmcpherson@verisign.com
Christoph Loibl
Next Layer Communications
Mariahilfer Guertel 37/7
Vienna 1150
AT
Phone: +43 664 1176414
Email: cl@tix.at
Martin Bacher Martin Bacher
T-Mobile Austria T-Mobile Austria
Rennweg 97-99 Rennweg 97-99
Vienna 1030 Vienna 1030
AT AT
Email: mb.ietf@gmail.com Email: mb.ietf@gmail.com
 End of changes. 9 change blocks. 
17 lines changed or deleted 51 lines changed or added

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