draft-ietf-idr-rfc5575bis-26.txt   draft-ietf-idr-rfc5575bis-27.txt 
IDR Working Group C. Loibl IDR Working Group C. Loibl
Internet-Draft next layer Telekom GmbH Internet-Draft next layer Telekom GmbH
Obsoletes: 5575,7674 (if approved) S. Hares Obsoletes: 5575,7674 (if approved) S. Hares
Intended status: Standards Track Huawei Intended status: Standards Track Huawei
Expires: February 13, 2021 R. Raszuk Expires: April 18, 2021 R. Raszuk
Bloomberg LP Bloomberg LP
D. McPherson D. McPherson
Verisign Verisign
M. Bacher M. Bacher
T-Mobile Austria T-Mobile Austria
August 12, 2020 October 15, 2020
Dissemination of Flow Specification Rules Dissemination of Flow Specification Rules
draft-ietf-idr-rfc5575bis-26 draft-ietf-idr-rfc5575bis-27
Abstract Abstract
This document defines a Border Gateway Protocol Network Layer This document defines a Border Gateway Protocol Network Layer
Reachability Information (BGP NLRI) encoding format that can be used Reachability Information (BGP NLRI) encoding format that can be used
to distribute traffic Flow Specifications. This allows the routing to distribute traffic Flow Specifications. This allows the routing
system to propagate information regarding more specific components of system to propagate information regarding more specific components of
the traffic aggregate defined by an IP destination prefix. the traffic aggregate defined by an IP destination prefix.
It also specifies BGP Extended Community encoding formats, that can It also specifies BGP Extended Community encoding formats, that can
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 February 13, 2021. This Internet-Draft will expire on April 18, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 7, line 40 skipping to change at page 7, line 40
Components MUST follow strict type ordering by increasing numerical Components MUST follow strict type ordering by increasing numerical
order. A given component type MAY (exactly once) be present in the order. A given component type MAY (exactly once) be present in the
Flow Specification. If present, it MUST precede any component of Flow Specification. If present, it MUST precede any component of
higher numeric type value. higher numeric type value.
All combinations of components within a single Flow Specification are All combinations of components within a single Flow Specification are
allowed. However, some combinations cannot match any packets (e.g. allowed. However, some combinations cannot match any packets (e.g.
"ICMP Type AND Port" will never match any packets), and thus SHOULD "ICMP Type AND Port" will never match any packets), and thus SHOULD
NOT be propagated by BGP. NOT be propagated by BGP.
A NLRI value not encoded as specified specified here is considered A NLRI value not encoded as specified here, including a NLRI that
malformed and error handling according to Section 10 is performed. contains an unknown component type, is considered malformed and error
handling according to Section 10 is performed.
4.2.1. Operators 4.2.1. Operators
Most of the components described below make use of comparison Most of the components described below make use of comparison
operators. Which of the two operators is used is defined by the operators. Which of the two operators is used is defined by the
components in Section 4.2.2. The operators are encoded as a single components in Section 4.2.2. The operators are encoded as a single
octet. octet.
4.2.1.1. Numeric Operator (numeric_op) 4.2.1.1. Numeric Operator (numeric_op)
skipping to change at page 14, line 5 skipping to change at page 14, line 5
| 0 | 0 | 0 | 0 |LF |FF |IsF|DF | | 0 | 0 | 0 | 0 |LF |FF |IsF|DF |
+---+---+---+---+---+---+---+---+ +---+---+---+---+---+---+---+---+
Figure 4: Fragment Bitmask Operand Figure 4: Fragment Bitmask Operand
Bitmask values: Bitmask values:
DF - Don't fragment - match if [RFC0791] IP Header Flags Bit-1 (DF) DF - Don't fragment - match if [RFC0791] IP Header Flags Bit-1 (DF)
is 1 is 1
IsF - Is a fragment - match if [RFC0791] IP Header Fragment Offset IsF - Is a fragment other than the first - match if [RFC0791] IP
is not 0 Header Fragment Offset is not 0
FF - First fragment - match if [RFC0791] IP Header Fragment Offset FF - First fragment - match if [RFC0791] IP Header Fragment Offset
is 0 AND Flags Bit-2 (MF) is 1 is 0 AND Flags Bit-2 (MF) is 1
LF - Last fragment - match if [RFC0791] IP Header Fragment Offset is LF - Last fragment - match if [RFC0791] IP Header Fragment Offset is
not 0 AND Flags Bit-2 (MF) is 0 not 0 AND Flags Bit-2 (MF) is 0
0 - MUST be set to 0 on NLRI encoding, and MUST be ignored during 0 - MUST be set to 0 on NLRI encoding, and MUST be ignored during
decoding decoding
skipping to change at page 34, line 33 skipping to change at page 34, line 33
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>. May 2017, <https://www.rfc-editor.org/info/rfc8174>.
15.2. Informative References 15.2. Informative References
[I-D.ietf-idr-flow-spec-v6] [I-D.ietf-idr-flow-spec-v6]
Loibl, C., Raszuk, R., and S. Hares, "Dissemination of Loibl, C., Raszuk, R., and S. Hares, "Dissemination of
Flow Specification Rules for IPv6", draft-ietf-idr-flow- Flow Specification Rules for IPv6", draft-ietf-idr-flow-
spec-v6-13 (work in progress), July 2020. spec-v6-15 (work in progress), September 2020.
[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,
<https://www.rfc-editor.org/info/rfc4303>. <https://www.rfc-editor.org/info/rfc4303>.
[RFC5575] Marques, P., Sheth, N., Raszuk, R., Greene, B., Mauch, J., [RFC5575] Marques, P., Sheth, N., Raszuk, R., Greene, B., Mauch, J.,
and D. McPherson, "Dissemination of Flow Specification and D. McPherson, "Dissemination of Flow Specification
Rules", RFC 5575, DOI 10.17487/RFC5575, August 2009, Rules", RFC 5575, DOI 10.17487/RFC5575, August 2009,
<https://www.rfc-editor.org/info/rfc5575>. <https://www.rfc-editor.org/info/rfc5575>.
 End of changes. 7 change blocks. 
9 lines changed or deleted 10 lines changed or added

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