Architecture for Scheduled Use of Resources
draft-ietf-teas-scheduled-resources-03

Document Type Active Internet-Draft (teas WG)
Last updated 2017-06-26
Replaces draft-zhuang-teas-scheduled-resources
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
TEAS Working Group                                             Y. Zhuang
Internet-Draft                                                     Q. Wu
Intended status: Standards Track                                 H. Chen
Expires: December 28, 2017                                        Huawei
                                                               A. Farrel
                                                        Juniper Networks
                                                           June 26, 2017

              Architecture for Scheduled Use of Resources
                 draft-ietf-teas-scheduled-resources-03

Abstract

   Time-scheduled reservation of traffic engineering (TE) resources can
   be used to provide resource booking for TE Label Switched Paths so as
   to better guarantee services for customers and to improve the
   efficiency of network resource usage into the future.  This document
   provides a framework that describes and discusses the architecture
   for the scheduled reservation of TE resources.  This document does
   not describe specific protocols or protocol extensions needed to
   realize this service.

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 December 28, 2017.

Copyright Notice

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

Zhuang, et al.          Expires December 28, 2017               [Page 1]
Internet-Draft         Scheduled Use of Resources              June 2017

   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.  Problem Statement . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Provisioning TE-LSPs and TE Resources . . . . . . . . . .   3
     2.2.  Selecting the Path of an LSP  . . . . . . . . . . . . . .   4
     2.3.  Planning Future LSPs  . . . . . . . . . . . . . . . . . .   4
     2.4.  Looking at Future Demands on TE Resources . . . . . . . .   5
     2.5.  Requisite State Information . . . . . . . . . . . . . . .   5
   3.  Architectural Concepts  . . . . . . . . . . . . . . . . . . .   6
     3.1.  Where is Scheduling State Held? . . . . . . . . . . . . .   6
     3.2.  What State is Held? . . . . . . . . . . . . . . . . . . .   8
   4.  Architecture Overview . . . . . . . . . . . . . . . . . . . .  10
     4.1.  Service Request . . . . . . . . . . . . . . . . . . . . .  10
     4.2.  Initialization and Recovery . . . . . . . . . . . . . . .  11
     4.3.  Synchronization Between PCEs  . . . . . . . . . . . . . .  12
   5.  Multi-Domain Considerations . . . . . . . . . . . . . . . . .  13
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  15
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  16
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  16
   9.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  16
   10. Informative References  . . . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Introduction

   Traffic Engineering Label Switched Paths (TE-LSPs) are connection
   oriented tunnels in packet and non-packet networks [RFC3209],
   [RFC3945].  TE-LSPs may reserve network resources for use by the
   traffic they carry, thus providing some guarantees of service
   delivery and allowing a network operator to plan the use of the
   resources across the whole network.

   In some technologies (such as wavelength switched optical networks)
   the resource is synonymous with the label that is switched on the
   path of the LSP so that it is not possible to establish an LSP that
Show full document text