[Teas] RFC 8413 on Framework for Scheduled Use of Resources
rfc-editor@rfc-editor.org Tue, 10 July 2018 05:14 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 072C2130DCB; Mon, 9 Jul 2018 22:14:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZD44GjRKYTSj; Mon, 9 Jul 2018 22:14:36 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0367A130DCC; Mon, 9 Jul 2018 22:14:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6C404B81557; Mon, 9 Jul 2018 22:14:35 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, teas@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180710051435.6C404B81557@rfc-editor.org>
Date: Mon, 09 Jul 2018 22:14:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/r0sGcBFqRhpU9nWP2iZKI0cBRJo>
Subject: [Teas] RFC 8413 on Framework for Scheduled Use of Resources
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2018 05:14:38 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8413
Title: Framework for Scheduled Use of Resources
Author: Y. Zhuang,
Q. Wu,
H. Chen,
A. Farrel
Status: Informational
Stream: IETF
Date: July 2018
Mailbox: zhuangyan.zhuang@huawei.com,
bill.wu@huawei.com,
huaimo.chen@huawei.com,
afarrel@juniper.net
Pages: 22
Characters: 53135
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-teas-scheduled-resources-07.txt
URL: https://www.rfc-editor.org/info/rfc8413
DOI: 10.17487/RFC8413
Time-Scheduled (TS) 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 at any moment in time, including
network usage that is planned for the future. This document provides
a framework that describes and discusses the architecture for
supporting scheduled reservation of TE resources. This document does
not describe specific protocols or protocol extensions needed to
realize this service.
This document is a product of the Traffic Engineering Architecture and Signaling Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC