Network Working Group S. Venaas
Internet-Draft cisco Systems
Intended status: Informational November 18, 2009
Expires: May 22, 2010
A Registry for PIM Message Types
draft-venaas-pim-registry-00.txt
Abstract
This document provides instructions to IANA for the creation of a
registry for PIM message types. It specifies initial content of the
registry based on existing RFCs specifying PIM message types. It
also specifies a procedure for registering new types.
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on May 22, 2010.
Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
Venaas Expires May 22, 2010 [Page 1]
Internet-Draft A Registry for PIM Message Types November 2009
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Security Considerations . . . . . . . . . . . . . . . . . . . . 4
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Initial registry . . . . . . . . . . . . . . . . . . . . . 5
3.2. Assignment of new message types . . . . . . . . . . . . . . 5
4. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1. Normative References . . . . . . . . . . . . . . . . . . . 6
4.2. Informative References . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7
Venaas Expires May 22, 2010 [Page 2]
Internet-Draft A Registry for PIM Message Types November 2009
1. Introduction
Apart from this document, there is no existing document specifying a
registry for PIM message types. PIM version 1 made use of IGMP
[RFC1112] and there is an IGMP registry [IGMPREG] listing the message
types used by PIM version 1. PIM version 2 however is not based on
IGMP, and a separate PIM message type registry is needed. There are
currently several RFCs specifying new PIM version 2 message types
that should be in this new registry. They are the RFCs for PIM Dense
Mode [RFC3973], PIM Sparse Mode [RFC4601] and Bidirectional PIM
[RFC5015].
This document specifies the initial content of the new PIM message
type registry based on those existing RFCs. This document also
specifies a procedure for registering new PIM message types.
Venaas Expires May 22, 2010 [Page 3]
Internet-Draft A Registry for PIM Message Types November 2009
2. Security Considerations
This document only creates an IANA registry. There may be a security
benefit in a well-known place for finding information on which PIM
message types are valid and what they mean. Apart from that there
are no security considerations.
Venaas Expires May 22, 2010 [Page 4]
Internet-Draft A Registry for PIM Message Types November 2009
3. IANA Considerations
This document requests IANA to create a PIM message type registry.
This should be placed in the "Protocol Independent Multicast (PIM)"
branch of the tree. Each entry in the registry consists of message
type, message name and references to the documents defining the type.
3.1. Initial registry
The initial content of the registry should be as follows.
Type Name Reference
---- ---------------------------- ---------------------
0 Hello [RFC3973] [RFC4601]
1 Register [RFC4601]
2 Register Stop [RFC4601]
3 Join/Prune [RFC3973] [RFC4601]
4 Bootstrap [RFC4601]
5 Assert [RFC3973] [RFC4601]
6 Graft [RFC3973]
7 Graft-Ack [RFC3973]
8 Candidate RP Advertisement [RFC4601]
9 State Refresh [RFC3973]
10 DF election [RFC5015]
3.2. Assignment of new message types
Assignment of new message types is done according to the "IETF
Review" model, see [RFC5226].
Venaas Expires May 22, 2010 [Page 5]
Internet-Draft A Registry for PIM Message Types November 2009
4. References
4.1. Normative References
[RFC3973] Adams, A., Nicholas, J., and W. Siadak, "Protocol
Independent Multicast - Dense Mode (PIM-DM): Protocol
Specification (Revised)", RFC 3973, January 2005.
[RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas,
"Protocol Independent Multicast - Sparse Mode (PIM-SM):
Protocol Specification (Revised)", RFC 4601, August 2006.
[RFC5015] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano,
"Bidirectional Protocol Independent Multicast (BIDIR-
PIM)", RFC 5015, October 2007.
4.2. Informative References
[IGMPREG] IANA, "IGMP Type Numbers", IGMP TYPE NUMBERS - per
RFC3228,
BCP57 http://www.iana.org/assignments/igmp-type-numbers,
June 2005.
[RFC1112] Deering, S., "Host extensions for IP multicasting", STD 5,
RFC 1112, August 1989.
Venaas Expires May 22, 2010 [Page 6]
Internet-Draft A Registry for PIM Message Types November 2009
Author's Address
Stig Venaas
cisco Systems
Tasman Drive
San Jose, CA 95134
USA
Email: stig@cisco.com
Venaas Expires May 22, 2010 [Page 7]