Re: [Idr] I-D Action: draft-ietf-idr-rfc5575bis-13.txt

Christoph Loibl <c@tix.at> Fri, 12 April 2019 12:04 UTC

Return-Path: <c@tix.at>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63B951202AC for <idr@ietfa.amsl.com>; Fri, 12 Apr 2019 05:04:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CpcRsANwjI0e for <idr@ietfa.amsl.com>; Fri, 12 Apr 2019 05:04:01 -0700 (PDT)
Received: from mail.hated.at (mail.hated.at [IPv6:2001:858:2:8::235]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E27881201AF for <idr@ietf.org>; Fri, 12 Apr 2019 05:04:00 -0700 (PDT)
Received: from p200300c3ff1e09339d6e2d7a000c3387.dip0.t-ipconnect.de ([2003:c3:ff1e:933:9d6e:2d7a:c:3387]) by mail.hated.at with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from <c@tix.at>) id 1hEuqM-0008K5-QC for idr@ietf.org; Fri, 12 Apr 2019 13:59:46 +0200
From: Christoph Loibl <c@tix.at>
Content-Type: multipart/alternative; boundary="Apple-Mail=_AF1CA4EF-4948-4111-A9A4-61BF553417AF"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Date: Fri, 12 Apr 2019 14:03:54 +0200
References: <155507028009.16955.13309371600540742366@ietfa.amsl.com>
To: idr wg <idr@ietf.org>
In-Reply-To: <155507028009.16955.13309371600540742366@ietfa.amsl.com>
Message-Id: <744B6CA8-F916-422C-B1E3-F0DE7E7C68D6@tix.at>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/aRXDNjraD_dR4-ch6GwLvWWXzlk>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-rfc5575bis-13.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Apr 2019 12:04:05 -0000

Hi IDR,

I uploaded draft-ietf-idr-rfc5575bis-13.txt containing editorial changes. 

Thank you Adam Chappell, you found xrefs in the document that where hardcoded (not using xref tags) and thus pointing to the wrong sections.

Cheers Christoph

-- 
Christoph Loibl
c@tix.at | CL8-RIPE | PGP-Key-ID: 0x4B2C0055 | http://www.nextlayer.at



> On 12.04.2019, at 13:58, internet-drafts@ietf.org wrote:
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Inter-Domain Routing WG of the IETF.
> 
>        Title           : Dissemination of Flow Specification Rules
>        Authors         : Susan Hares
>                          Christoph Loibl
>                          Robert Raszuk
>                          Danny McPherson
>                          Martin Bacher
> 	Filename        : draft-ietf-idr-rfc5575bis-13.txt
> 	Pages           : 34
> 	Date            : 2019-04-12
> 
> 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
>   carries traffic Flow Specification filter, and an Extended community
>   value which encodes actions a routing system can take if the packet
>   matches the traffic flow filters.  The flow filters and the actions
>   are processed in a fixed order.  Other drafts specify IPv6, MPLS
>   addresses, L2VPN addresses, and NV03 encapsulation of IP addresses.
> 
>   This document obsoletes RFC5575 and RFC7674 to correct unclear
>   specifications in the flow filters.
> 
>   Applications which use the bgp Flow Specification are: 1) application
>   which automate inter-domain coordination of traffic filtering, such
>   as what is required in order to mitigate (distributed) denial-of-
>   service attacks; 2) applications which control traffic filtering in
>   the context of a BGP/MPLS VPN service, and 3) applications with
>   centralized control of traffic in a SDN or NFV context.  Some
>   deployments of these three applications can be handled by the strict
>   ordering of the BGP NLRI traffic flow filters, and the strict actions
>   encoded in the extended community Flow Specification actions.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-idr-rfc5575bis/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-idr-rfc5575bis-13
> https://datatracker.ietf.org/doc/html/draft-ietf-idr-rfc5575bis-13
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-rfc5575bis-13
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr