The 'via' keyword in RPSL Policy Specifications
draft-snijders-rpsl-via-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-06-04
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                        J. Snijders
Internet-Draft                                        Atrato IP Networks
Intended status: Informational                               N. Hilliard
Expires: December 4, 2013                                           INEX
                                                            June 4, 2013

            The 'via' keyword in RPSL Policy Specifications
                       draft-snijders-rpsl-via-00

Abstract

   This document defines the 'via' keyword which can be used in RPSL
   policy specifications to publish desired routing policy regarding
   non-adjacent networks.

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 November 30, 2013.

Copyright Notice

   Copyright (c) 2013 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.

Snijders & Hilliard    Expires November 30, 2013                [Page 1]
Internet-Draft         The 'via' keyword in RPSL                May 2013

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Notational Conventions  . . . . . . . . . . . . . . . . . . .   2
   3.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   2
   4.  Import and Export Via Syntax and Semantics  . . . . . . . . .   3
   5.  Example Usage . . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Appendix A.  Grammar Rules  . . . . . . . . . . . . . . . . . . .   6
   Appendix B.  Support and Commitment . . . . . . . . . . . . . . .   6
   Appendix C.  Document Change Log  . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   The Routing Policy Specification Language [RFC4012] allows operators
   to specify routing policies regarding directly adjacent networks
   through various import and export attributes.  These attributes only
   apply to directly adjacent networks.

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

      Provide a way to describe what an adjacent network could use as
      routing policy towards its adjacent networks.

      The extension should be backward compatible with minimal impact on
      existing tools and processes, following Section 10 of [RFC2622].

   The addition of a 'via' keyword in import and export related
   attributes will especially help participants of Multi-Lateral Peering
   services to inform the intermediate autonomous system what routing
   policy should be applied towards other participants.

2.  Notational Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   [RFC2119].

3.  Background

Snijders & Hilliard    Expires November 30, 2013                [Page 2]
Internet-Draft         The 'via' keyword in RPSL                May 2013

   The via keyword specifically benefits operators whom were assigned a
   32 bit AS Number and transit providers when participating in Multi-
   Lateral Peering Agreements facilitated by a Route Server.

   Often Route Server operators overload BGP Communities [RFC1997]) to
   facilitate signalling of desired routing policy between the
Show full document text