RFC 8736 on PIM Message Type Space Extension and Reserved Bits
rfc-editor@rfc-editor.org Sat, 29 February 2020 03:42 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 65B453A0AA9; Fri, 28 Feb 2020 19:42:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 Fyx4y8FHwRUL; Fri, 28 Feb 2020 19:42:06 -0800 (PST)
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 DC8CA3A0A9F; Fri, 28 Feb 2020 19:42:06 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 04B19F40714; Fri, 28 Feb 2020 19:41:50 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8736 on PIM Message Type Space Extension and Reserved Bits
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, pim@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200229034150.04B19F40714@rfc-editor.org>
Date: Fri, 28 Feb 2020 19:41:50 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/yYjCeZFUVg31boDympOhQ6ctL7E>
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, 29 Feb 2020 03:42:09 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8736
Title: PIM Message Type Space Extension
and Reserved Bits
Author: S. Venaas,
A. Retana
Status: Standards Track
Stream: IETF
Date: February 2020
Mailbox: stig@cisco.com,
alvaro.retana@futurewei.com
Pages: 8
Obsoletes: RFC 6166
Updates: RFC 3973, RFC 5015, RFC 5059, RFC 6754,
RFC 7761, RFC 8364
I-D Tag: draft-ietf-pim-reserved-bits-04.txt
URL: https://www.rfc-editor.org/info/rfc8736
DOI: 10.17487/RFC8736
The PIM version 2 messages share a common message header format. The
common header definition contains eight reserved bits. This document
specifies how these bits may be used by individual message types and
creates a registry containing the per-message-type usage. This
document also extends the PIM type space by defining three new
message types. For each of the new types, four of the previously
reserved bits are used to form an extended type range.
This document updates RFCs 7761 and 3973 by defining the use of the
currently Reserved field in the PIM common header. This document
further updates RFCs 7761 and 3973, along with RFCs 5015, 5059, 6754,
and 8364, by specifying the use of the currently reserved bits for
each PIM message.
This document obsoletes RFC 6166.
This document is a product of the Protocols for IP Multicast 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