Routing Policy Specification Language next generation (RPSLng)
RFC 4012

Document Type RFC - Proposed Standard (March 2005; No errata)
Was draft-blunk-rpslng (individual in ops area)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 4012 (Proposed Standard)
Telechat date
Responsible AD Bert Wijnen
Send notices to <joao@psg.com>,<ljb@merit.edu>,<andrei@ripe.net>,<Florent.Parent@viagenie.qc.ca>
Network Working Group                                           L. Blunk
Request for Comments: 4012                                 Merit Network
Updates: 2725, 2622                                             J. Damas
Category: Standards Track                    Internet Systems Consortium
                                                               F. Parent
                                                                  Hexago
                                                          A. Robachevsky
                                                                RIPE NCC
                                                              March 2005

     Routing Policy Specification Language next generation (RPSLng)

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2005).

Abstract

   This memo introduces a new set of simple extensions to the Routing
   Policy Specification Language (RPSL), enabling the language to
   document routing policies for the IPv6 and multicast address families
   currently used in the Internet.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Specifying routing policy for different address families . . .  2
       2.1.  Ambiguity Resolution . . . . . . . . . . . . . . . . . .  3
       2.2.  The afi dictionary attribute . . . . . . . . . . . . . .  3
       2.3.  RPSL dictionary extensions . . . . . . . . . . . . . . .  4
       2.4.  IPv6 RPSL types  . . . . . . . . . . . . . . . . . . . .  4
       2.5.  mp-import, mp-export, and mp-default . . . . . . . . . .  4
             2.5.1.  <mp-peering> . . . . . . . . . . . . . . . . . .  6
             2.5.2.  <mp-filter>  . . . . . . . . . . . . . . . . . .  6
             2.5.3.  Policy examples  . . . . . . . . . . . . . . . .  7
   3.  route6 Class . . . . . . . . . . . . . . . . . . . . . . . . .  7
   4.  Updates to existing Classes to support the extensions  . . . .  8
       4.1.  as-set Class . . . . . . . . . . . . . . . . . . . . . .  8
       4.2.  route-set Class  . . . . . . . . . . . . . . . . . . . .  9

Blunk, et al.               Standards Track                     [Page 1]
RFC 4012                         RPSLng                       March 2005

       4.3.  filter-set Class . . . . . . . . . . . . . . . . . . . .  9
       4.4.  peering-set Class  . . . . . . . . . . . . . . . . . . .  9
       4.5.  inet-rtr Class . . . . . . . . . . . . . . . . . . . . . 10
       4.6.  rtr-set Class  . . . . . . . . . . . . . . . . . . . . . 11
   5.  RFC 2725 Extensions  . . . . . . . . . . . . . . . . . . . . . 11
       5.1.  Authorization model for route6 Objects . . . . . . . . . 13
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 13
   7.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 14
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
       8.1.  Normative References . . . . . . . . . . . . . . . . . . 14
       8.2.  Informative References . . . . . . . . . . . . . . . . . 14
       Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 15
       Full Copyright Statement . . . . . . . . . . . . . . . . . . . 16

1.  Introduction

   RFC 2622 [1] defines the RPSL language for the IPv4 unicast routing
   protocols and provides a series of guidelines for extending the RPSL
   language itself.  Additionally, security extensions to the RPSL
   language are specified in RFC 2725 [2].

   This document proposes to extend RPSL according to the following
   goals and requirements:

   o  Provide RPSL extensibility in the dimension of address families,
      specifically, to allow users to document routing policy for IPv6
      and multicast.
   o  Extensions should be backward compatible with minimal impact on
      existing tools and processes, following Section 10 of RFC 2622 [1]
      for guidelines on extending RPSL.
   o  Maintain clarity and non-ambiguity: RPSL information is used by
      humans in addition to software tools.
   o  Minimize duplication of information, particularly when routing
      policies for different address families are the same.

   The addition of IPv6 and multicast support to RPSL leads to four
   distinct routing policies that need to be distinguished in this
   specification, namely, (IPv4 {unicast|multicast}, IPv6
   {unicast|multicast}).

2.  Specifying Routing Policy for Different Address Families
Show full document text