RFC 7963 on RSVP-TE Extension for Additional Signal Types in G.709 Optical Transport Networks (OTNs)
rfc-editor@rfc-editor.org Fri, 26 August 2016 23:47 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 B3EEA12D625; Fri, 26 Aug 2016 16:47:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.17
X-Spam-Level:
X-Spam-Status: No, score=-103.17 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 rHQbo22xeopK; Fri, 26 Aug 2016 16:47:11 -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 5C50112D5BE; Fri, 26 Aug 2016 16:47:11 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4AF04B809DD; Fri, 26 Aug 2016 16:47:11 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7963 on RSVP-TE Extension for Additional Signal Types in G.709 Optical Transport Networks (OTNs)
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160826234711.4AF04B809DD@rfc-editor.org>
Date: Fri, 26 Aug 2016 16:47:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/Fr1zS5fArkwcrG-d_Q1I88xwKcE>
Cc: drafts-update-ref@iana.org, ccamp@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: Fri, 26 Aug 2016 23:47:13 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7963
Title: RSVP-TE Extension for Additional Signal Types
in G.709 Optical Transport Networks (OTNs)
Author: Z. Ali,
A. Bonfanti,
M. Hartley,
F. Zhang
Status: Informational
Stream: IETF
Date: August 2016
Mailbox: zali@cisco.com,
abonfant@cisco.com,
mhartley@cisco.com,
zhangfatai@huawei.com
Pages: 5
Characters: 8665
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-ccamp-additional-signal-type-g709v3-04.txt
URL: https://www.rfc-editor.org/info/rfc7963
DOI: http://dx.doi.org/10.17487/RFC7963
RFCs 4328 and 7139 provide signaling extensions in Resource ReserVation
Protocol - Traffic Engineering (RSVP-TE) to control the full set
of Optical Transport Network (OTN) features. However, these
specifications do not cover the additional Optical channel Data
Unit (ODU) containers defined in G.Sup43 (ODU1e, ODU3e1, and
ODU3e2). This document defines new Signal Types for these
additional containers.
This document is a product of the Common Control and Measurement Plane 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