Architecture for Stateless RSVP
draft-qin-teas-sl-rsvp-00

Document Type Active Internet-Draft (individual)
Last updated 2016-12-27
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. Qin
Internet-Draft                                                    D. Sun
Intended status: Informational                                   J. Dong
Expires: July 1, 2017                                             X. Wei
                                                                 M. Chen
                                                     Huawei Technologies
                                                       December 28, 2016

                    Architecture for Stateless RSVP
                       draft-qin-teas-sl-rsvp-00

Abstract

   RSVP takes a "soft state" scheme to manage the reservation states in
   routers and hosts, the soft states are created and periodically
   refreshed by Path and Resv messages.  Soft state scheme gives a
   simple way to maintain the state synchonization between neighbors,
   but also introduces scalability issue.  This document provides a
   framework that describes and discusses the architecture for stateless
   RSVP (SL-RSVP), which disabled the soft-state scheme to improve the
   protocol scalability and the other processes of RSVP are kept.  This
   document does not describe specific protocols or protocol extensions
   needed to realize this architecture.

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 July 1, 2017.

Qin, et al.               Expires July 1, 2017                  [Page 1]
Internet-Draft                   SL-RSVP                   December 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
   2.  Definition of SL-RSVP . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Motivation  . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Basic Idea of SL-RSVP . . . . . . . . . . . . . . . . . .   4
     2.3.  Responsbility of the Controller . . . . . . . . . . . . .   4
   3.  Architecture  . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Generic Architecture  . . . . . . . . . . . . . . . . . .   5
     3.2.  Deployment Considerations . . . . . . . . . . . . . . . .   6
   4.  Operation Overview  . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  LSP States Collection . . . . . . . . . . . . . . . . . .   6
     4.2.  Procedures of LSP States Deletion . . . . . . . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   7.  Informative References  . . . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   RSVP (TE) protocol[RFC2205] [RFC3209] is designed to establish
   constraint-based LSP or QoS supported LSP that guarantee subscriber's
   quality requriements or apply network operator's policy.  The soft
   state scheme in the protocol gives a simple way to maintain the state
   synchronization between neighbors, but introduces scalability issue.
   It is found that with the increase of the number of LSPs the
   processing overhead becomes considerable.  In extreme cases it is
Show full document text