Re: [Idr] I-D Action: draft-ietf-idr-rfc5575bis-11.txt
"Smith, Donald" <Donald.Smith@CenturyLink.com> Thu, 17 January 2019 20:06 UTC
Return-Path: <Donald.Smith@CenturyLink.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 CFDD9130FF8 for <idr@ietfa.amsl.com>; Thu, 17 Jan 2019 12:06:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 7neNXxdEZOSO for <idr@ietfa.amsl.com>; Thu, 17 Jan 2019 12:06:27 -0800 (PST)
Received: from lxomp52w.centurylink.com (lxomp52w.centurylink.com [155.70.50.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E085F130F80 for <idr@ietf.org>; Thu, 17 Jan 2019 12:06:26 -0800 (PST)
Received: from lxdnp04n.corp.intranet (lxdnp04n.corp.intranet [151.119.92.83]) by lxomp52w.centurylink.com (8.14.8/8.14.8) with ESMTP id x0HK6Opb031138 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for <idr@ietf.org>; Thu, 17 Jan 2019 14:06:24 -0600
Received: from lxdnp04n.corp.intranet (localhost [127.0.0.1]) by lxdnp04n.corp.intranet (8.14.8/8.14.8) with ESMTP id x0HK6JAe007728 for <idr@ietf.org>; Thu, 17 Jan 2019 13:06:19 -0700
Received: from lxdnp32k.corp.intranet (lxdnp23m.corp.intranet [151.119.92.134]) by lxdnp04n.corp.intranet (8.14.8/8.14.8) with ESMTP id x0HK6J8c007725 (version=TLSv1/SSLv3 cipher=AES256-SHA256 bits=256 verify=NO) for <idr@ietf.org>; Thu, 17 Jan 2019 13:06:19 -0700
Received: from lxdnp32k.corp.intranet (localhost [127.0.0.1]) by lxdnp32k.corp.intranet (8.14.8/8.14.8) with ESMTP id x0HK6JRT044069 for <idr@ietf.org>; Thu, 17 Jan 2019 13:06:19 -0700
Received: from vddcwhubex502.ctl.intranet (vddcwhubex502.ctl.intranet [151.119.128.29]) by lxdnp32k.corp.intranet (8.14.8/8.14.8) with ESMTP id x0HK6JPM044066 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <idr@ietf.org>; Thu, 17 Jan 2019 13:06:19 -0700
Received: from PDDCWMBXEX503.ctl.intranet ([fe80::9033:ef22:df02:32a9]) by vddcwhubex502.ctl.intranet ([151.119.128.29]) with mapi id 14.03.0399.000; Thu, 17 Jan 2019 13:06:18 -0700
From: "Smith, Donald" <Donald.Smith@CenturyLink.com>
To: "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] I-D Action: draft-ietf-idr-rfc5575bis-11.txt
Thread-Index: AQHUrjfcBCxC37hL6kO+99NVy1i3bqWz3dse
Date: Thu, 17 Jan 2019 20:06:18 +0000
Message-ID: <68EFACB32CF4464298EA2779B058889D53E6B7B0@PDDCWMBXEX503.ctl.intranet>
References: <154771071144.29438.662134368131147811@ietfa.amsl.com>
In-Reply-To: <154771071144.29438.662134368131147811@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [151.119.128.8]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/al86kE06Zu89feiSEKWvtLX7eho>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-rfc5575bis-11.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: Thu, 17 Jan 2019 20:06:34 -0000
I have an issue with how people describe BHFing and other similar techniques. First the continued use of RTBH (no F?), isn't nearly all BHFing going to be RT? Does it make any difference if it is done manually one router at a time vs via BGP (I think there is a minor difference but the effect is the same.) So when I want to say Destination prefix based Black Hole Filtering, it becomes DBHF. Here are some other filtering definitions and what I think are logical abbrevations. I should probably turn that/this into an informational RFC :) BHF Black Hole Filter (no directionality) DBHF Destination based BHF SBHF Source based BHF CIDBHF Customer Initiated DBHF DSH Destination based Sink Hole SSH Source based Sink Hole DSHSBHF Destination based Sink Hole & SBHF CIDSHSBHF Customer Initiated DSHSBHF In almost no case would you actually do BHF with no directionality but for completeness I have it in there. 9.1 "Several techniques are currently used to control traffic filtering of DoS attacks. Among those, one of the most common is to inject unicast route advertisements corresponding to a destination prefix being attacked (commonly known as remote triggered blackhole RTBH). One variant of this technique marks such route advertisements with a community that gets translated into a discard Next-Hop by the receiving router. Other variants attract traffic to a particular node that serves as a deterministic drop point." DBHF, and if (initial_ttl!=255) then (rfc5082_compliant==0) Donald.Smith@centurylink.com ________________________________________ From: Idr [idr-bounces@ietf.org] on behalf of internet-drafts@ietf.org [internet-drafts@ietf.org] Sent: Thursday, January 17, 2019 12:38 AM To: i-d-announce@ietf.org Cc: idr@ietf.org Subject: [Idr] I-D Action: draft-ietf-idr-rfc5575bis-11.txt 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-11.txt Pages : 34 Date : 2019-01-16 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 and to provide rules for actions which interfere (e.g. redirection of traffic and flow filtering). 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-11 https://datatracker.ietf.org/doc/html/draft-ietf-idr-rfc5575bis-11 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-rfc5575bis-11 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 This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
- [Idr] I-D Action: draft-ietf-idr-rfc5575bis-11.txt internet-drafts
- Re: [Idr] I-D Action: draft-ietf-idr-rfc5575bis-1… Smith, Donald