--- 1/draft-ietf-idr-rfc5575bis-13.txt 2019-04-24 14:13:11.119774385 -0700 +++ 2/draft-ietf-idr-rfc5575bis-14.txt 2019-04-24 14:13:11.187776110 -0700 @@ -1,25 +1,25 @@ IDR Working Group S. Hares Internet-Draft Huawei Obsoletes: 5575,7674 (if approved) C. Loibl Intended status: Standards Track Next Layer Communications -Expires: October 14, 2019 R. Raszuk +Expires: October 26, 2019 R. Raszuk Bloomberg LP D. McPherson Verisign M. Bacher T-Mobile Austria - April 12, 2019 + April 24, 2019 Dissemination of Flow Specification Rules - draft-ietf-idr-rfc5575bis-13 + draft-ietf-idr-rfc5575bis-14 Abstract This document defines a Border Gateway Protocol Network Layer Reachability Information (BGP NLRI) encoding format that can be used to distribute traffic Flow Specifications. This allows the routing system to propagate information regarding more specific components of the traffic aggregate defined by an IP destination prefix. It specifies IPv4 traffic Flow Specifications via a BGP NLRI which @@ -50,21 +50,21 @@ 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 October 14, 2019. + This Internet-Draft will expire on October 26, 2019. Copyright Notice Copyright (c) 2019 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 publication of this document. Please review these documents @@ -383,23 +383,23 @@ e - end-of-list bit. Set in the last {op, value} pair in the list. a - AND bit. If unset, the previous term is logically ORed with the current one. If set, the operation is a logical AND. In the first operator byte of a sequence it SHOULD be encoded as unset and and MUST be treated as always unset on decoding. The AND operator has higher priority than OR for the purposes of evaluating logical expressions. - len - length of the value field for this operand encodes 1 (00) - - 4 (11) bytes. Type 3 flow component values SHOULD be encoded as - single byte (len = 00). + len - length of the value field for this operand given as (1 << + len). This encodes 1 (00) - 8 (11) bytes. Type 3 flow component + values SHOULD be encoded as single byte (len = 00). 0 - SHOULD be set to 0 on NLRI encoding, and MUST be ignored during decoding lt - less than comparison between data and value. gt - greater than comparison between data and value. eq - equality between data and value. @@ -1353,20 +1353,24 @@ 16. Acknowledgements The authors would like to thank Yakov Rekhter, Dennis Ferguson, Chris Morrow, Charlie Kaufman, and David Smith for their comments for the comments on the original RFC5575. Chaitanya Kodeboyina helped design the flow validation procedure; and Steven Lin and Jim Washburn ironed out all the details necessary to produce a working implementation in the original RFC5575. + A packet rate flowspec action was also discribed in a flowspec + extention draft and the authors like to thank Wesley Eddy, Justin + Dailey and Gilbert Clark for their work. + Additional the authors would like to thank Alexander Mayrhofer, Nicolas Fevrier, Job Snijders, Jeffrey Haas and Adam Chappell for their comments and review. 17. References 17.1. Normative References [IEEE.754.1985] IEEE, "Standard for Binary Floating-Point Arithmetic",