[pim] RFC 6166 on A Registry for PIM Message Types
rfc-editor@rfc-editor.org Mon, 25 April 2011 16:54 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pim@ietfc.amsl.com
Delivered-To: pim@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 8D5C6E076B; Mon, 25 Apr 2011 09:54:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.027
X-Spam-Level:
X-Spam-Status: No, score=-102.027 tagged_above=-999 required=5 tests=[AWL=-0.027, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P0RZm0sEYUr6; Mon, 25 Apr 2011 09:54:16 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfc.amsl.com (Postfix) with ESMTP id EE2FEE076A; Mon, 25 Apr 2011 09:54:15 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 79A4BE0773; Mon, 25 Apr 2011 09:54:15 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110425165415.79A4BE0773@rfc-editor.org>
Date: Mon, 25 Apr 2011 09:54:15 -0700
Cc: pim@ietf.org, rfc-editor@rfc-editor.org
Subject: [pim] RFC 6166 on A Registry for PIM Message Types
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pim>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Apr 2011 16:54:16 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6166
Title: A Registry for PIM Message Types
Author: S. Venaas
Status: Standards Track
Stream: IETF
Date: April 2011
Mailbox: stig@cisco.com
Pages: 4
Characters: 7441
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pim-registry-04.txt
URL: http://www.rfc-editor.org/rfc/rfc6166.txt
This document provides instructions to IANA for the creation of a
registry for PIM message types. It specifies the initial content of
the registry, based on existing RFCs specifying PIM message types.
It also specifies a procedure for registering new types.
In addition to this, one message type is reserved, and may be used
for a future extension of the message type space. [STANDARDS-TRACK]
This document is a product of the Protocol Independent Multicast Working Group of the IETF.
This is now a Proposed Standard Protocol.
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 Internet
Official Protocol Standards (STD 1) 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
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://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