Survey Report on PIM-SM Implementations and Deployments
draft-ietf-pim-rfc4601-update-survey-report-01

The information below is for an old version of the document
Document Type Active Internet-Draft (pim WG)
Last updated 2013-05-23
Replaces draft-zzp-pim-rfc4601-update-survey-report
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           L. Zheng
Internet-Draft                                       Huawei Technologies
Intended status: Informational                                  Z. Zhang
Expires: November 23, 2013                              Juniper Networks
                                                               R. Parekh
                                                           Cisco Systems
                                                            May 23, 2013

        Survey Report on PIM-SM Implementations and Deployments
           draft-ietf-pim-rfc4601-update-survey-report-01.txt

Abstract

   This document provides supporting documentation to advance the
   Protocol Independent Multicast - Sparse Mode (PIM-SM)
   protocol from IETF Proposed Standard to Internet Standard.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on November 23, 2013.

Copyright Notice

   Copyright (c) 2012 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
   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

Zheng, et al.        Expires November 23, 2013                 [Page 1]
Internet-Draft           Survey Report on PIM-SM                May 2013

   described in the Simplified BSD License.

Table of Contents

   1.  Motivation . . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Overview of PIM-SM . . . . . . . . . . . . . . . . . . . .  3
     1.2.  RFC2026 and RFC6410 Requirements . . . . . . . . . . . . .  3

   2.  Survey on Implementations and Deployments  . . . . . . . . . .  4
     2.1.  Methodology  . . . . . . . . . . . . . . . . . . . . . . .  4
     2.2.  Operator Responses . . . . . . . . . . . . . . . . . . . .  4
       2.2.1.  Description of PIM Sparse-Mode deployments . . . . . .  4
       2.2.2.  PIM Sparse-Mode deployment with other multicast
               technologies . . . . . . . . . . . . . . . . . . . . .  4
       2.2.3.  PIM Sparse-Mode RPs and RP Discovery mechanisms  . . .  4
     2.3.  Vendor Responses . . . . . . . . . . . . . . . . . . . . .  5
       2.3.1.  RFC4601 and RFC2362 implementations  . . . . . . . . .  5
       2.3.2.  Lack of (*,*,RP) and PMBR implementations  . . . . . .  5
       2.3.3.  Implementations of other features of RFC4601 . . . . .  5
     2.4.  Key Findings . . . . . . . . . . . . . . . . . . . . . . .  6

   3.  Security Considerations  . . . . . . . . . . . . . . . . . . .  7

   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  8

   5.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  9

   6.  Appendix A. Questionnaire  . . . . . . . . . . . . . . . . . . 10
     6.1.  Appendix A.1 PIM Survey for Operators  . . . . . . . . . . 10
     6.2.  Appendix A.2 PIM Survey for Implementors . . . . . . . . . 11

   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 14
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 14

   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 15

Zheng, et al.        Expires November 23, 2013                 [Page 2]
Internet-Draft           Survey Report on PIM-SM                May 2013

1.  Motivation

1.1.  Overview of PIM-SM

   PIM-SM was first published as [RFC2117] in 1997 and then again as
   [RFC2362] in 1998.  The protocol was classified as Experimental in
   both of these documents.  The PIM-SM protocol specification was then
   rewritten in whole and advanced to Proposed Standard as [RFC4601] in
   2006.  Considering its multiple independent implementations developed
   and sufficient successful operational experience gained, the IETF has
   decided to advance the PIM-SM protocol to Internet Standard.

1.2.  RFC2026 and RFC6410 Requirements

   [RFC2026] defines the stages in the standardization process, the
Show full document text