[rfc-dist] RFC 8330 on OSPF Traffic Engineering (OSPF-TE) Link Availability Extension for Links with Variable Discrete Bandwidth
rfc-editor@rfc-editor.org Thu, 15 February 2018 01:37 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2D0D12D87B for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 14 Feb 2018 17:37:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 CWReNmceXEGx for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 14 Feb 2018 17:37:30 -0800 (PST)
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 F1A1512D88F for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 14 Feb 2018 17:35:58 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 7BC02B812A5; Wed, 14 Feb 2018 17:35:33 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 1F4C7B812A5; Wed, 14 Feb 2018 17:35:32 -0800 (PST)
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
Message-Id: <20180215013532.1F4C7B812A5@rfc-editor.org>
Date: Wed, 14 Feb 2018 17:35:32 -0800
Subject: [rfc-dist] RFC 8330 on OSPF Traffic Engineering (OSPF-TE) Link Availability Extension for Links with Variable Discrete Bandwidth
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, ccamp@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
RFC 8330
Title: OSPF Traffic Engineering (OSPF-TE) Link
Availability Extension for Links with Variable
Discrete Bandwidth
Author: H. Long,
M. Ye,
G. Mirsky,
A. D'Alessandro,
H. Shah
Status: Standards Track
Stream: IETF
Date: February 2018
Mailbox: longhao@huawei.com,
amy.yemin@huawei.com,
gregimirsky@gmail.com,
alessandro.dalessandro@telecomitalia.it,
hshah@ciena.com
Pages: 10
Characters: 19206
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ccamp-ospf-availability-extension-13.txt
URL: https://www.rfc-editor.org/info/rfc8330
DOI: 10.17487/RFC8330
A network may contain links with variable discrete bandwidth, e.g.,
microwave and copper. The bandwidth of such links may change
discretely in response to a changing external environment. The word
"availability" is typically used to describe such links during network
planning. This document defines a new type of Generalized Switching
Capability-Specific Information (SCSI) TLV to extend the Generalized
Multiprotocol Label Switching (GMPLS) Open Shortest Path First (OSPF)
routing protocol. The extension can be used for route computation in
a network that contains links with variable discrete bandwidth.
Note that this document only covers the mechanisms by which the
availability information is distributed. The mechanisms by which
availability information of a link is determined and the use of the
distributed information for route computation are outside the scope
of this document. It is intended that technology-specific documents
will reference this document to describe specific uses.
This document is a product of the Common Control and Measurement Plane Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. 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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org