draft-ietf-pim-proposed-req-00.txt   draft-ietf-pim-proposed-req-01.txt 
Network Working Group Tom Pusateri Network Working Group Tom Pusateri
Internet-Draft Juniper Networks Internet-Draft Juniper Networks
Expires: July 11, 2005 January 2005 Expires: August 21, 2005 February 2005
PIM IETF Proposed Standard Requirements Analysis PIM Sparse-Mode IETF Proposed Standard Requirements Analysis
draft-ietf-pim-proposed-req-00.txt draft-ietf-pim-proposed-req-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of RFC 3668. aware will be disclosed, in accordance with Section 6 of RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 36 skipping to change at page 1, line 36
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
1. Introduction 1. Introduction
This analysis provides supporting documentation to advance the This analysis provides supporting documentation to advance the
Protocol Independent Multicast (PIM) routing protocol from the IETF Protocol Independent Multicast (PIM) Sparse-Mode routing protocol
Experimental status to Proposed Standard. PIM was first published as from the IETF Experimental status to Proposed Standard. PIM Sparse-
RFC 2117 in 1997 and then again as RFC 2362 in 1998. The protocol was Mode was first published as RFC 2117 in 1997 and then again as RFC
classified as Experimental in both of these documents. The PIM 2362 in 1998. The protocol was classified as Experimental in both of
protocol specification was then rewritten in whole in order to more these documents. The PIM Sparse-Mode protocol specification was then
fully specify the protocol. It is this new specification that is to rewritten in whole in order to more fully specify the protocol. It
be advanced to Proposed Standard. is this new specification that is to be advanced to Proposed
Standard.
2. RFC 1264 Requirements 2. RFC 1264 Requirements
Section 4.0 of RFC 1264 [ROUTESTD] describes the requirements for Section 4.0 of RFC 1264 [ROUTESTD] describes the requirements for
routing protocols to advance to Proposed Standard. Each requirement routing protocols to advance to Proposed Standard. Each requirement
is listed below along with an explanation of how the requirement has is listed below along with an explanation of how the requirement has
been satisfied. been satisfied.
2.1. Documents specifying the Protocol and its Usage 2.1. Documents specifying the Protocol and its Usage
The authors of the new PIM specification have taken considerable care The authors of the new PIM Sparse-Mode specification have taken
to fully specify the protocol operation. It removes all known considerable care to fully specify the protocol operation. It removes
ambiguities and tries to normalize corner cases that existed in the all known ambiguities and tries to normalize corner cases that
previous specification. It has been used to provide several existed in the previous specification. It has been used to provide
interoperable implementations by developers that were not authors of several interoperable implementations by developers that were not
the specification. These implementations will be described below. authors of the specification. These implementations will be
described below.
2.2. Management Information Base 2.2. Management Information Base
A Management Information Base for PIM is currently specified in RFC A Management Information Base for PIM is currently specified in RFC
2934 [PIMMIB]. This MIB has many implementations and has been used 2934 [PIMMIB]. This MIB has many implementations and has been used
by network management applications for several years. Updates to this by network management applications for several years. Updates to this
MIB to support IPv6 and other improvements based on operation MIB to support IPv6 and other improvements based on operation
experience are in progress in the PIM Working Group of the IETF. experience are in progress in the PIM Working Group of the IETF.
2.3. Explicit Security Architecture 2.3. Explicit Security Architecture
The new PIM protocol specification contains an extensive security The new PIM Sparse-Mode protocol specification contains an extensive
section explaining its security features and limitations. Data security section explaining its security features and limitations.
integrity protection and groupwise data origin authentication is Data integrity protection and groupwise data origin authentication is
provided for PIM protocol messages. provided for PIM protocol messages.
2.4. Implementation Existence 2.4. Implementation Existence
There are at least 4 known independent implementations of the new There are at least 4 known independent implementations of the new
protocol specification and there are over 6 independent protocol specification and there are over 6 independent
implementations of a previous version (RFC 2362) of the implementations of a previous version (RFC 2362) of the
specification. The new specification was carefully written to be specification. The new specification was carefully written to be
backward compatible with the old specification allowing backward compatible with the old specification allowing
implementations compliant with RFC 2362 to also be compliant with the implementations compliant with RFC 2362 to also be compliant with the
skipping to change at page 3, line 24 skipping to change at page 3, line 24
Cisco Systems, Inc. has written an implementation of the new Cisco Systems, Inc. has written an implementation of the new
protocol specification which has been deployed in production protocol specification which has been deployed in production
routers. There exists an IOS implementation for IPv6 only. There routers. There exists an IOS implementation for IPv6 only. There
exists an IOX implementation for both IPv4 and IPv6. This code was exists an IOX implementation for both IPv4 and IPv6. This code was
initially written by Isidor Kouvelas <kouvelas@cisco.com>. It does initially written by Isidor Kouvelas <kouvelas@cisco.com>. It does
not depend on any existing code base. Isidor is a co-author of not depend on any existing code base. Isidor is a co-author of
the protocol specification. the protocol specification.
Infosys Technologies, Ltd. Infosys Technologies, Ltd.
Infosys Technologies, Ltd. (www.infosys.com) have developed a Infosys Technologies, Ltd. (www.infosys.com) have developed a
limited shared tree implementation of the new specification limited shared tree implementation of the new Sparse-Mode
including PIM Hello messages, DR election, PIM join/prune specification including PIM Hello messages, DR election, PIM
messages, join suppression, and prune override. It was written by join/prune messages, join suppression, and prune override. It was
Bharat Joshi <<bharat_joshi@infosys.com> and is used in commercial written by Bharat Joshi <<bharat_joshi@infosys.com> and is used in
products. Bharat is not an author of the protocol specification. commercial products. Bharat is not an author of the protocol
specification.
Procket Networks Procket Networks
An implementation was written from scratch at Procket Networks by An implementation was written from scratch at Procket Networks by
Dino Farinacci <dino@cisco.com>. This implementation is now owned Dino Farinacci <dino@cisco.com>. This implementation is now owned
by Cisco Systems, Inc. Dino is not an author of the new protocol by Cisco Systems, Inc. Dino is not an author of the new protocol
speicfication. speicfication.
2.5. Evidence of Testing 2.5. Evidence of Testing
Cisco Cisco
The Cisco implementation has undergone extensive laboratory The Cisco implementation has undergone extensive laboratory
testing as well as testing in production deployments. It is found testing as well as testing in production deployments. It is found
to interoperate with implementations of earlier versions of the to interoperate with implementations of earlier versions of the
PIM protocol specification. PIM Sparse-Mode protocol specification.
XORP XORP
The XORP PIM-SM implementation has been thoughtfully tested The XORP PIM-SM implementation has been thoughtfully tested
internally by the XORP project. The emphasis during testing has internally by the XORP project. The emphasis during testing has
been on correctness. In a typical setup, a PIM-SM router's been on correctness. In a typical setup, a PIM-SM router's
behavior is tested by connecting it to external packet generators behavior is tested by connecting it to external packet generators
and observers. The packet generators are used to generate messages and observers. The packet generators are used to generate messages
such as IGMP and PIM-SM control packets, and multicast data such as IGMP and PIM-SM control packets, and multicast data
packets. The packet observers are used to observe the PIM-SM packets. The packet observers are used to observe the PIM-SM
control packets generated by the PIM-SM router under test, and to control packets generated by the PIM-SM router under test, and to
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/