PCN Boundary Node Behaviour for the Controlled Load (CL) Mode of Operation
draft-ietf-pcn-cl-edge-behaviour-13

The information below is for an old version of the document
Document Type Active Internet-Draft (pcn WG)
Last updated 2012-03-29 (latest revision 2012-03-22)
Replaces draft-taylor-pcn-cl-edge-behaviour
Stream IETF
Intended RFC status Experimental
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd Steven Blake
IESG IESG state Approved-announcement to be sent::Point Raised - writeup needed
Telechat date
Responsible AD Martin Stiemerling
IESG note Steven Blake (slblake@petri-meat.com> is the document shepherd)
Send notices to pcn-chairs@tools.ietf.org, draft-ietf-pcn-cl-edge-behaviour@tools.ietf.org
Internet Engineering Task Force                                A. Charny
Internet-Draft
Intended status: Experimental                                   F. Huang
Expires: September 22, 2012                          Huawei Technologies
                                                          G. Karagiannis
                                                               U. Twente
                                                                M. Menth
                                                 University of Tuebingen
                                                          T. Taylor, Ed.
                                                     Huawei Technologies
                                                          March 21, 2012

    PCN Boundary Node Behaviour for the Controlled Load (CL) Mode of
                               Operation
                  draft-ietf-pcn-cl-edge-behaviour-13

Abstract

   Pre-congestion notification (PCN) is a means for protecting the
   quality of service for inelastic traffic admitted to a Diffserv
   domain.  The overall PCN architecture is described in RFC 5559.  This
   memo is one of a series describing possible boundary node behaviours
   for a PCN-domain.  The behaviour described here is that for a form of
   measurement-based load control using three PCN marking states, not-
   marked, threshold-marked, and excess-traffic-marked.  This behaviour
   is known informally as the Controlled Load (CL) PCN-boundary-node
   behaviour.

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 September 22, 2012.

Copyright Notice

Charny, et al.         Expires September 22, 2012               [Page 1]
Internet-Draft       PCN CL Boundary Node Behaviour           March 2012

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

Charny, et al.         Expires September 22, 2012               [Page 2]
Internet-Draft       PCN CL Boundary Node Behaviour           March 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5
     1.1.  Terminology  . . . . . . . . . . . . . . . . . . . . . . .  6
   2.  [CL-Specific] Assumed Core Network Behaviour for CL  . . . . .  9
   3.  Node Behaviours  . . . . . . . . . . . . . . . . . . . . . . . 10
     3.1.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . 10
     3.2.  Behaviour of the PCN-Egress-Node . . . . . . . . . . . . . 11
       3.2.1.  Data Collection  . . . . . . . . . . . . . . . . . . . 11
       3.2.2.  Reporting the PCN Data . . . . . . . . . . . . . . . . 12
       3.2.3.  Optional Report Suppression  . . . . . . . . . . . . . 12
     3.3.  Behaviour at the Decision Point  . . . . . . . . . . . . . 13
       3.3.1.  Flow Admission . . . . . . . . . . . . . . . . . . . . 13
       3.3.2.  Flow Termination . . . . . . . . . . . . . . . . . . . 14
       3.3.3.  Decision Point Action For Missing
               PCN-Boundary-Node Reports  . . . . . . . . . . . . . . 15
     3.4.  Behaviour of the Ingress Node  . . . . . . . . . . . . . . 16
     3.5.  Summary of Timers and Associated Configurable Durations  . 17
       3.5.1.  Recommended Values For the Configurable Durations  . . 18
   4.  Specification of Diffserv Per-Domain Behaviour . . . . . . . . 19
     4.1.  Applicability  . . . . . . . . . . . . . . . . . . . . . . 19
     4.2.  Technical Specification  . . . . . . . . . . . . . . . . . 19
       4.2.1.  Classification and Traffic Conditioning  . . . . . . . 19
       4.2.2.  PHB Configuration  . . . . . . . . . . . . . . . . . . 20
Show full document text