RFC 7892 on IANA Allocation Procedures for the GMPLS OTN Signal Type Registry
rfc-editor@rfc-editor.org Sat, 28 May 2016 01:30 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 8754212D1D0; Fri, 27 May 2016 18:30:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.328
X-Spam-Level:
X-Spam-Status: No, score=-108.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426, 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 PK1miCnJ7FCP; Fri, 27 May 2016 18:30:52 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E268512D139; Fri, 27 May 2016 18:30:52 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B1226180006; Fri, 27 May 2016 18:30:10 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7892 on IANA Allocation Procedures for the GMPLS OTN Signal Type Registry
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160528013010.B1226180006@rfc-editor.org>
Date: Fri, 27 May 2016 18:30:10 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/_RQWOf9D03I2hHrI6fB7iuY4aK0>
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
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, 28 May 2016 01:30:54 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7892
Title: IANA Allocation Procedures for the
GMPLS OTN Signal Type Registry
Author: Z. Ali,
A. Bonfanti,
M. Hartley,
F. Zhang
Status: Standards Track
Stream: IETF
Date: May 2016
Mailbox: zali@cisco.com,
abonfant@cisco.com,
mhartley@cisco.com,
zhangfatai@huawei.com
Pages: 4
Characters: 7019
Updates: RFC 7139
I-D Tag: draft-ietf-ccamp-otn-signal-type-subregistry-05.txt
URL: https://www.rfc-editor.org/info/rfc7892
DOI: http://dx.doi.org/10.17487/RFC7892
IANA defined the "OTN Signal Type" subregistry of the "Generalized
Multi-Protocol Label Switching (GMPLS) Signaling Parameters" registry
in RFC 7139. This document updates the "OTN Signal Type" subregistry
to allow registration via Specification Required.
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