RFC 7631 on TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format
rfc-editor@rfc-editor.org Tue, 08 September 2015 18:31 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5B2A1B2AA6; Tue, 8 Sep 2015 11:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 prvFAz22Wyjr; Tue, 8 Sep 2015 11:31:50 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD411A9050; Tue, 8 Sep 2015 11:31:50 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 33D73187A98; Tue, 8 Sep 2015 11:31:43 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7631 on TLV Naming in the Mobile Ad Hoc Network (MANET) Generalized Packet/Message Format
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150908183143.33D73187A98@rfc-editor.org>
Date: Tue, 08 Sep 2015 11:31:43 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/9TB7k1l0nQBkwF0US7GXZo3Mc8M>
Cc: drafts-update-ref@iana.org, manet@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 08 Sep 2015 18:31:52 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7631
Title: TLV Naming in the Mobile Ad Hoc Network (MANET)
Generalized Packet/Message Format
Author: C. Dearlove, T. Clausen
Status: Standards Track
Stream: IETF
Date: September 2015
Mailbox: chris.dearlove@baesystems.com,
T.Clausen@computer.org
Pages: 15
Characters: 34376
Updates: RFC 5444
I-D Tag: draft-ietf-manet-tlv-naming-05.txt
URL: https://www.rfc-editor.org/info/rfc7631
DOI: http://dx.doi.org/10.17487/RFC7631
This document reorganizes the naming of already-allocated TLV (type-
length-value) types and type extensions in the "Mobile Ad hoc NETwork
(MANET) Parameters" registries defined by RFC 5444 to use names
appropriately. It has no consequences in terms of any protocol
implementation.
This document also updates the Expert Review guidelines in RFC 5444,
so as to establish a policy for consistent naming of future TLV type
and type extension allocations. It makes no other changes to
RFC 5444.
This document is a product of the Mobile Ad-hoc Networks 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/rfc.html
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