draft.raw.txt

Network Working Group                                         M. Stucchi
Internet-Draft                                                  RIPE NCC
Obsoletes: 2622,4012 (if approved)                        S. Kostantaras
Intended status: Standards Track                              NLnet Labs
Expires: August 4, 2016                                    February 2016


                      The third generation of RPSL
                         draft-stucchi-rpsl3-00

Abstract

   This memo presents some modifications to the Routing Policy
   Specification Language (RPSL) discussed in [RFC2622] and subsequently
   updated in [RFC4012], creating the third generation of the language.
   It fixes some issues left from the previous standards, and enhances
   the language.  Enhancements include the addition of recommendations
   for using RPSL to describe routing policies in Internet Exchange
   environments running route servers and other minor corrections.

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 August 4, 2016.

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
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction
   2.  Basic objects
     2.1.  aut-num objects
     2.2.  as-set objects
     2.3.  route objects
     2.4.  IXP objects
       2.4.1.  Defining IXP members
       2.4.2.  Members using the route server
   3.  Basic syntax
     3.1.  Keywords
     3.2.  Using brackets
     3.3.  Defining a peer
   4.  Defining a peer's routing policy
     4.1.  IPv4
       4.1.1.  IPv4 Prefix lists
     4.2.  IPv6
       4.2.1.  IPv6 Prefix lists
     4.3.  Local Preference
     4.4.  Prepending
     4.5.  MED
     4.6.  Communities
   5.  Security Considerations
   6.  RPKI
   7.  Generating RPSL from router configuration
   8.  Generating router configuration from RPSL
   9.  Normative References
   Appendix A.  Example Policy
   Authors' Addresses

1.  Introduction

   This is the introductory section.

2.  Basic objects

   This section contains information about the objects involved in
   defining a policy

2.1.  aut-num objects

   This section contains information about the aut-num objects, and
   their relationship with RPSL3

2.2.  as-set objects

   This section contains information about the as-set objects, and their
   relationship with RPSL3

2.3.  route objects

   This section contains information about the route objects, and their
   relationship with RPSL3

2.4.  IXP objects

   This section contains information about the IXP objects, and their
   relationship with RPSL3

2.4.1.  Defining IXP members

   Listing members of an internet exchange

2.4.2.  Members using the route server

   The route-server attribute in the object

3.  Basic syntax

   This section describes the basic syntax of the language.

3.1.  Keywords

   Keywords used in the language

3.2.  Using brackets

   Brackets used in the language

3.3.  Defining a peer

   How a peer is defined, with all its attributes

4.  Defining a peer's routing policy

   A peer and all its attributes

4.1.  IPv4

   IPv4

4.1.1.  IPv4 Prefix lists

   IPv4 Prefix lists

4.2.  IPv6

   IPv6

4.2.1.  IPv6 Prefix lists

   IPv6 Prefix lists

4.3.  Local Preference

   Local preference

4.4.  Prepending

   Prepending

4.5.  MED

   Multiple Exit Discriminator

4.6.  Communities

   Communities in action

5.  Security Considerations

   This memo raises no security issues;

6.  RPKI

   Here, we discuss RPKI in relationship with RPSL

7.  Generating RPSL from router configuration

   How to generate RPSL from routers

8.  Generating router configuration from RPSL

   How to generate router configs from RPSL

9.  Normative References

   [RFC2622]  Alaettinoglu, C., Villamizar, C., Gerich, E., Kessens, D.,
              Meyer, D., Bates, T., Karrenberg, D., and M. Terpstra,
              "Routing Policy Specification Language (RPSL)", RFC 2622,
              DOI 10.17487/RFC2622, June 1999,
              <http://www.rfc-editor.org/info/rfc2622>.

   [RFC4012]  Blunk, L., Damas, J., Parent, F., and A. Robachevsky,
              "Routing Policy Specification Language next generation
              (RPSLng)", RFC 4012, DOI 10.17487/RFC4012, March 2005,
              <http://www.rfc-editor.org/info/rfc4012>.

Appendix A.  Example Policy

   This section contains an example policy for an Internet Service
   Provider.  This should serve as the basis for an operator to start
   drafting their own set of rules.

   aut-num: AS1
   remarks: ------
   peer: AS2
   community: in {add, remove, set} AS1:3240
   filter: out AS1 0-24
   filter: in 4 Any [192.168.0.0]0-24 {}
   policy: in * ANY {%AS3333$%}
   policy: prepend 3
   community: null-routing {}
   policy: out 4 med 1000 @10.20.30.40
   policy: out 6 med 900 @2001:db8:999::fff
   policy: in 6 localpref 200 [AS1:3240]
   policy: in 4 prepend 3
   peer: AS3
   filter: {in, out} Any 0-48
   filter: out -AS28929 0-128 {} 6

   # Example Internet Exchange

   IXP: AMS-IX
   member: AS1
   route-Server: Yes
   filter:
   policy:

   aut-num: AS1
   remarks: ------

   peer: AS2
   community: in {add, remove, set} AS1:3240

   filters: out AS1 0-24 {} 4
   filters: in Any [192.168.0.0]0-24 {} 4

   policy: prepend 3
   community: null-routing {}

   policy: out med 1000 {10.20.30.40}4
   policy: out med 900 {2001:db8:999::fff} 6
   policy: in localpref 200 {} 6 [AS1:3240]
   policy: in prepend 3 {} 4

   peer: AS3
   filter: {in, out} Any 0-48
   filter: out -AS28929 0-128 {} 6



Authors' Addresses

   Massimiliano Stucchi
   RIPE NCC

   Email: mstucchi@ripe.net


   Stavros Kostantaras
   NLnet Labs

   Email: stavros@nlnetlabs.nl