Re: [pim] Protocol Action: 'Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)' to Internet Standard (draft-ietf-pim-rfc4601bis-06.txt)

Stig Venaas <stig@venaas.com> Thu, 13 August 2015 18:32 UTC

MIME-Version: 1.0
In-Reply-To: <20150813170151.13355.38707.idtracker@ietfa.amsl.com>
References: <20150813170151.13355.38707.idtracker@ietfa.amsl.com>
Date: Thu, 13 Aug 2015 11:32:13 -0700
Message-ID: <CAHANBtKRAdu-9FsRFYrt0S9zbv=R3XUiSa+2YUM0QmML02=3Fw@mail.gmail.com>
From: Stig Venaas <stig@venaas.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/cIZ2bwv_fcoAzZXm9RF93I8ELSY>
Cc: "draft-ietf-pim-rfc4601bis@ietf.org" <draft-ietf-pim-rfc4601bis@ietf.org>, pim mailing list <pim@ietf.org>
Subject: Re: [pim] Protocol Action: 'Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)' to Internet Standard (draft-ietf-pim-rfc4601bis-06.txt)
Precedence: list

We finally got the rfc4601bis draft approved!

Congrats to the authors for all the work that went into this, and to
those that contributed answering surveys and discussions in the
working group.

The RFC editor might still want some minor changes, but the rest is
now just a formality. Sparse-Mode will now be an Internet Standard.

Stig


On Thu, Aug 13, 2015 at 10:01 AM, The IESG <iesg-secretary@ietf.org> wrote:
> The IESG has approved the following document:
> - 'Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol
>    Specification (Revised)'
>   (draft-ietf-pim-rfc4601bis-06.txt) as Internet Standard
>
> This document is the product of the Protocols for IP Multicast Working
> Group.
>
> The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah
> Brungard.
>
> A URL of this Internet Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-pim-rfc4601bis/
>
>
>
>
> Technical Summary
>
> This document specifies Protocol Independent Multicast - Sparse Mode
> (PIM-SM).  PIM-SM is a multicast routing protocol that can use the
> underlying unicast routing information base or a separate multicast-
> capable routing information base.  It builds unidirectional shared
> trees rooted at a Rendezvous Point (RP) per group, and optionally
> creates shortest-path trees per source.This document addresses errata
> filed against RFC 4601, and removes the optional (*,*,RP) and PIM
> Multicast Border Router features that lacks sufficient deployment
> experience.
>
> Working Group Summary
>
> There was very good feedback on the list over the last year,
> particularly during the last WGLCs.
> All comments were addressed to the satisfaction of those commenting.
>
>
> Document Quality
>
> There are several existing implementations of the protocol over the span
> of many years. Bharat Joshi, most particularly, had many recent comments
> that were all addressed in final fine tuning of the document.
> RFC7063 documents the features implemented in a survey report.
> The document shepherds verified that all the errata had been handled.
>
> Personnel
>
> Mike McBride & Bill Atwood are the document shepherd and Alvaro Retana
> is the responsible AD.
>

[pim] Protocol Action: 'Protocol Independent Mult… The IESG
Re: [pim] Protocol Action: 'Protocol Independent … Stig Venaas