RFC 8245 on Rules for Designing Protocols Using the Generalized Packet/Message Format from RFC 5444

rfc-editor@rfc-editor.org Sat, 21 October 2017 05:12 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 []) by ietfa.amsl.com (Postfix) with ESMTP id D8D551321D8; Fri, 20 Oct 2017 22:12:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id p162lmdLak77; Fri, 20 Oct 2017 22:12:33 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 569F213208E; Fri, 20 Oct 2017 22:12:33 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 587E9B81A9D; Fri, 20 Oct 2017 22:12:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8245 on Rules for Designing Protocols Using the Generalized Packet/Message Format from RFC 5444
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, manet@ietf.org
Message-Id: <20171021051208.587E9B81A9D@rfc-editor.org>
Date: Fri, 20 Oct 2017 22:12:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/tlGHiECsRMJKHPaJN_-h3PV2f8Q>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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, 21 Oct 2017 05:12:35 -0000

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

        RFC 8245

        Title:      Rules for Designing Protocols Using 
                    the Generalized Packet/Message Format 
                    from RFC 5444 
        Author:     T. Clausen, 
                    C. Dearlove,
                    U. Herberg, 
                    H. Rogge
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2017
        Mailbox:    T.Clausen@computer.org, 
        Pages:      29
        Characters: 66723
        Updates:    RFC 5444

        I-D Tag:    draft-ietf-manet-rfc5444-usage-07.txt

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

        DOI:        10.17487/RFC8245

RFC 5444 specifies a generalized Mobile Ad Hoc Network (MANET)
packet/message format and describes an intended use for multiplexed
MANET routing protocol messages; this use is mandated by RFC 5498 when
using the MANET port or protocol number that it specifies.  This
document updates RFC 5444 by providing rules and recommendations for
how the multiplexer operates and how protocols can use the
packet/message format.  In particular, the mandatory rules prohibit a
number of uses that have been suggested in various proposals and that
would have led to interoperability problems, to the impediment of
protocol extension development, and/or to an inability to use optional
generic parsers.

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

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