[Idr] WG LC on draft-ietf-idr-bgp-flowspec-oid-10.txt [8/9 to 8/24/2019]
"Susan Hares" <shares@ndzh.com> Fri, 09 August 2019 14:55 UTC
Return-Path: <shares@ndzh.com>
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 470F5120150 for <idr@ietfa.amsl.com>; Fri, 9 Aug 2019 07:55:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.947
X-Spam-Level:
X-Spam-Status: No, score=0.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 iFgqD-wBOtul for <idr@ietfa.amsl.com>; Fri, 9 Aug 2019 07:55:26 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-100-static.hfc.comcastbusiness.net [50.245.122.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 577BC120148 for <idr@ietf.org>; Fri, 9 Aug 2019 07:55:26 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=97.112.26.170;
From: Susan Hares <shares@ndzh.com>
To: 'idr wg' <idr@ietf.org>
Date: Fri, 09 Aug 2019 10:55:21 -0400
Message-ID: <01a501d54ec2$78335670$689a0350$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdVOwctpm51ZalEESYutdODWLBbXYQ==
Content-Language: en-us
X-Antivirus: AVG (VPS 190809-0, 08/09/2019), Outbound message
X-Antivirus-Status: Not-Tested
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/0UATfKv4fxP0l5U1VDgCDyU6ros>
Subject: [Idr] WG LC on draft-ietf-idr-bgp-flowspec-oid-10.txt [8/9 to 8/24/2019]
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, 09 Aug 2019 14:55:29 -0000
This begins a 2 week WG LC for draft-ietf-idr-bgp-flowspec-oid-10.txt [8/9 to 8/24/2019] In your comments, please consider: 1) including "support" or "no support" 2) if this addition to RFC5575bis which allows a route controller in an AS to originate Flow Specifications is useful in deployments, and 3) if there are any technical issues or editorial Issues that need to be adjusted in this specification prior to publication. If you think adjustments need to be made in the text, Indicate whether you think the adjustments are Technical or editorial in nature. Cheerily, Sue ============= 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 : Revised Validation Procedure for BGP Flow Specifications Authors : James Uttaro Juan Alcaide Clarence Filsfils David Smith Pradosh Mohapatra Filename : draft-ietf-idr-bgp-flowspec-oid-10.txt Pages : 11 Date : 2019-08-09 Abstract: This document describes a modification to the validation procedure defined in [RFC5575bis] for the dissemination of BGP Flow Specifications. [RFC5575bis] requires that the originator of the Flow Specification matches the originator of the best-match unicast route for the destination prefix embedded in the Flow Specification. This allows only BGP speakers within the data forwarding path (such as autonomous system border routers) to originate BGP Flow Specifications. Though it is possible to disseminate such Flow Specifications directly from border routers, it may be operationally cumbersome in an autonomous system with a large number of border routers having complex BGP policies. The modification proposed herein enables Flow Specifications to be originated from a centralized BGP route controller. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-flowspec-oid/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-idr-bgp-flowspec-oid-10 https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-flowspec-oid-10 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-bgp-flowspec-oid-10 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
- [Idr] WG LC on draft-ietf-idr-bgp-flowspec-oid-10… Susan Hares
- Re: [Idr] WG LC on draft-ietf-idr-bgp-flowspec-oi… Jeffrey Haas
- Re: [Idr] WG LC on draft-ietf-idr-bgp-flowspec-oi… Christoph Loibl
- Re: [Idr] WG LC on draft-ietf-idr-bgp-flowspec-oi… UTTARO, JAMES
- Re: [Idr] WG LC on draft-ietf-idr-bgp-flowspec-oi… Christoph Loibl
- Re: [Idr] WG LC on draft-ietf-idr-bgp-flowspec-oi… Susan Hares