Analysis of Existing work for I2NSF
draft-ietf-idr-aspath-orf-12

The information below is for an old version of the document
Document Type Active Internet-Draft (idr WG)
Last updated 2016-12-08
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
IDR                                                             S. Hares
Internet-Draft                                                    Huawei
Intended status: Standards Track                                K. Patel
Expires: June 11, 2017                                             Cisco
                                                        December 8, 2016

                  Analysis of Existing work for I2NSF
                    draft-ietf-idr-aspath-orf-12.txt

Abstract

   This document defines a new Outbound Router Filter type for BGP,
   termed "Aspath Outbound Route Filter", that can be used to perform
   aspath based route filtering.  This ORF-type supports aspath based
   route filtering as well as regular expression based matching, for
   address groups.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   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 http://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 June 11, 2017.

Copyright Notice

   Copyright (c) 2016 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
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Hares & Patel             Expires June 11, 2017                 [Page 1]
Internet-Draft             I2NSF Gap analysis              December 2016

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  ASpath ORF-Type . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  ASpath ORF encoding . . . . . . . . . . . . . . . . . . . . .   3
   4.  Capability Specification for Cooperative route filtering with
       ASpath  . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  ASpath ORF Matching . . . . . . . . . . . . . . . . . . . . .   6
   6.  Error handling  . . . . . . . . . . . . . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   6
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   10. Security Considerations . . . . . . . . . . . . . . . . . . .   7
   11. Normative References  . . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   The Cooperative Outbound Route Filtering Capability defined in
   [RFC5292] provides a mechanism for a BGP speaker to send to its BGP
   peer a set of Outbound Route Filters (ORFs) that can be used by its
   peer to filter its outbound routing updates to the speaker.

   This documents defines a new ORF-type for BGP, termed "ASpath
   Outbound Route Filter (ASpath ORF)", that can be used to perform AS
   Path based route filtering.  The ASpath ORF supports AS path route
   filtering as well as the regular expression based matching for
   address groups.

2.  ASpath ORF-Type

   The ASpath ORF-Type allows one to express ORFs in terms of regular
   expression and AS path numbers.  That is, it provides AS path based
   route filtering, including regular expression based matching.

   Conceptually an ASpath ORF entry consists of the fields <Sequence,
   Match, Length, Aspath>.

      The "Sequence" field is a number that specifies the relative
      ordering of the entry.

      The "Match" field specifies whether this entry is "PERMIT" (value
      0), or "DENY" (value 1).

Hares & Patel             Expires June 11, 2017                 [Page 2]
Internet-Draft             I2NSF Gap analysis              December 2016

      The "Length" field indicates the length of AS path regular
      expression string.

      The "aspath" field contains an AS path regular expression of an
      address group.

      The field "Sequence" is an unsigned 32 bit value.  The field
      "Length" is an unsigned 16 bit value.  The field "aspath" is a
      variable length hexadecimal string.  The field "aspath" will be
      followed by enough trailing bits to make end of field fall on an
Show full document text