datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

BGP Class of Service Interconnection
draft-knoll-idr-cos-interconnect-11

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-11-08
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Inter-Domain Routing Working Group                             Th. Knoll
Internet-Draft                         Chemnitz University of Technology
Intended status: Standards Track                       November 10, 2013
Expires: May 14, 2014

                  BGP Class of Service Interconnection
                  draft-knoll-idr-cos-interconnect-11

Abstract

   This document focuses on Class of Service Interconnection at inter-
   domain interconnection points.  It specifies two new transitive
   attributes, which enable adjacent peers to signal Class of Service
   Capabilities and certain Class of Service admission control
   Parameters.  The new "CoS Capability" is deliberately kept simple and
   denotes the general EF, AF Group BE and LE forwarding support across
   the advertising AS.  The second "CoS Parameter Attribute" is of
   variable length and contains a more detailed description of available
   forwarding behaviours using the PHB id Code encoding.  Each PHB id
   Code is associated with rate and size based traffic parameters, which
   will be applied in the ingress AS Border Router for admission control
   purposes to a given forwarding behaviour.

Requirements Language

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

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 May 14, 2014.

Copyright Notice

Knoll                     Expires May 14, 2014                  [Page 1]
Internet-Draft            BGP CoS Interconnect             November 2013

   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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Definition and Usage of the CoS Capability . . . . . . . . . .  4
     2.1.  Extended Community Type  . . . . . . . . . . . . . . . . .  4
     2.2.  Structure of the CoS Capability Attribute  . . . . . . . .  4
     2.3.  Usage of the CoS Capability Attribute  . . . . . . . . . .  7
   3.  Definition and Usage of the CoS Parameter Attribute  . . . . .  7
     3.1.  Definition of the CoS Parameter Attribute  . . . . . . . .  7
     3.2.  Usage of the CoS Parameter Attribute . . . . . . . . . . .  8
   4.  Confidentiality Considerations . . . . . . . . . . . . . . . .  9
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  9
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 10
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 11
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 11

Knoll                     Expires May 14, 2014                  [Page 2]
Internet-Draft            BGP CoS Interconnect             November 2013

1.  Introduction

   AS interconnection is currently based on best effort interconnection
   only.  BGP-4 [RFC4271] is the de-facto interconnection protocol used
   to exchange reachability information.  There is no standardized set
   of supported traffic classes, no standardized packet marking and no
   standardized forwarding behaviour, which cross-domain traffic could
   rely on.  QoS policy decisions are taken by AS providers

[include full document text]