RFC 8625 on Ethernet Traffic Parameters with Availability Information

rfc-editor@rfc-editor.org Sat, 17 August 2019 04:29 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1D331200FB; Fri, 16 Aug 2019 21:29:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 7wnVzIY6Q77N; Fri, 16 Aug 2019 21:29:00 -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 219DF1200D5; Fri, 16 Aug 2019 21:29:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 57E61B80CD8; Fri, 16 Aug 2019 21:28:54 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8625 on Ethernet Traffic Parameters with Availability Information
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, ccamp@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190817042854.57E61B80CD8@rfc-editor.org>
Date: Fri, 16 Aug 2019 21:28:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/O16ifPIJkKLyGwUBogP09fQzeoI>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 17 Aug 2019 04:29:02 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8625

        Title:      Ethernet Traffic Parameters with Availability 
                    Information 
        Author:     H. Long, 
                    M. Ye, Ed.,
                    G. Mirsky, Ed.,
                    A. D'Alessandro,
                    H. Shah
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2019
        Mailbox:    longhao@huawei.com, 
                    amy.yemin@huawei.com, 
                    gregimirsky@gmail.com, 
 alessandro.dalessandro@telecomitalia.it, 
                    hshah@ciena.com
        Pages:      13
        Characters: 26401
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ccamp-rsvp-te-bandwidth-availability-16.txt

        URL:        https://www.rfc-editor.org/info/rfc8625

        DOI:        10.17487/RFC8625

A packet-switching network may contain links with variable bandwidths
(e.g., copper and radio).  The bandwidth of such links is sensitive
to the external environment (e.g., climate).  Availability is
typically used to describe these links when doing network planning.
This document introduces an optional Bandwidth Availability TLV in
RSVP-TE signaling.  This extension can be used to set up a GMPLS
Label Switched Path (LSP) in conjunction with the Ethernet
SENDER_TSPEC object.

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