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

"lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com> Fri, 03 March 2017 09:43 UTC

Return-Path: <lizhenqiang@chinamobile.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 E7BED12941E for <idr@ietfa.amsl.com>; Fri, 3 Mar 2017 01:43:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-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 R0bZ9Xf2aDiW for <idr@ietfa.amsl.com>; Fri, 3 Mar 2017 01:43:34 -0800 (PST)
Received: from cmccmta2.chinamobile.com (cmccmta2.chinamobile.com [221.176.66.80]) by ietfa.amsl.com (Postfix) with ESMTP id BC7521293F4 for <idr@ietf.org>; Fri, 3 Mar 2017 01:43:32 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.19]) by rmmx-syy-dmz-app05-12005 (RichMail) with SMTP id 2ee558b93abd652-e6cb7; Fri, 03 Mar 2017 17:43:25 +0800 (CST)
X-RM-TRANSID: 2ee558b93abd652-e6cb7
X-RM-SPAM-FLAG: 00000000
Received: from cmcc-PC (unknown[223.69.29.1]) by rmsmtp-syy-appsvr10-12010 (RichMail) with SMTP id 2eea58b93abcdfc-16f4a; Fri, 03 Mar 2017 17:43:25 +0800 (CST)
X-RM-TRANSID: 2eea58b93abcdfc-16f4a
Date: Fri, 3 Mar 2017 17:43:50 +0800
From: "lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com>
To: idr <idr@ietf.org>
References: <148784903318.20350.3977002902067988959.idtracker@ietfa.amsl.com>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7, 2, 7, 164[cn]
Mime-Version: 1.0
Message-ID: <2017030317434995427747@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart515324677571_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Kk8BrXihF2auFcr1Ht3yANWSEtk>
Subject: Re: [Idr] I-D Action: draft-ietf-idr-rfc5575bis-00.txt
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
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, 03 Mar 2017 09:43:38 -0000

Hi,

I am reading this draft. I noticed that there are 7 actions listed in table 2. But Only 5 of them are illustrated in section 7. Actions for type 0x8108 and 0x8208 are not explained in this section. No references are given here. May I know the reason? Thanks.

Best Regards,


lizhenqiang@chinamobile.com
 
From: internet-drafts@ietf.org
Date: 2017-02-23 19:23
To: i-d-announce@ietf.org
CC: idr@ietf.org
Subject: [Idr] I-D Action: draft-ietf-idr-rfc5575bis-00.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 of the IETF.
 
        Title           : Dissemination of Flow Specification Rules
        Authors         : Susan Hares
                          Robert Raszuk
                          Danny McPherson
                          Christoph Loibl
                          Martin Bacher
Filename        : draft-ietf-idr-rfc5575bis-00.txt
Pages           : 30
Date            : 2017-02-22
 
Abstract:
   This document updates RFC5575 which 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.  This draft 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 updates RFC5575 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 of inter-domain coordination of traffic filtering,
   such as what is required in order to mitigate (distributed) denial-
   of-service attacks; 2) application 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 of
   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's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-idr-rfc5575bis-00
 
 
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