Re: [pim] Last Call: <draft-ietf-pim-rfc4601bis-03.txt> (Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)) to Internet Standard
Alia Atlas <akatlas@gmail.com> Mon, 02 March 2015 22:55 UTC
Return-Path: <akatlas@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C8251A1BFA for <pim@ietfa.amsl.com>; Mon, 2 Mar 2015 14:55:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level:
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RVIqpQEUi3np for <pim@ietfa.amsl.com>; Mon, 2 Mar 2015 14:55:34 -0800 (PST)
Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com [IPv6:2607:f8b0:4003:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B93221A8986 for <pim@ietf.org>; Mon, 2 Mar 2015 14:55:33 -0800 (PST)
Received: by mail-oi0-f52.google.com with SMTP id u20so29879641oif.11 for <pim@ietf.org>; Mon, 02 Mar 2015 14:55:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=d5RriVLClqHDiMB8xq2HLiVWn4wG/4OV5MP0H/RnvGk=; b=OWjuALPgpS0dudmvnfYzr3Tke5/gi1KQLmNvGgUVvyCA81JaL9wpRuZ+1irdI7DBTY LPUAOcrzIAIQqJfz7WduXV7dp8Nrb5MUI4GlTxaUJTR92h9U44vz7JdHQAwAZM17MBhf r2MEAUOAXB42dXG7owqQCqr+AsT4LhlmeE6q+yCSDGKQ+3s1iu528EBf9kgj9Cxj9z/H yfnpQggnzDFwxLERksxI8Gf3+cw/wZ0lHQ4kHdIzaAe4OguYNvmIYHH2R8EZXejPvZej QOAC8jtvzqlhN2faZt6PH172LwsLHLrMmqUW4C1F/eFmB+gF+QtLmVfL6UZPH0x9BvHu l1vA==
MIME-Version: 1.0
X-Received: by 10.202.65.8 with SMTP id o8mr19943045oia.113.1425336933062; Mon, 02 Mar 2015 14:55:33 -0800 (PST)
Received: by 10.60.97.135 with HTTP; Mon, 2 Mar 2015 14:55:32 -0800 (PST)
In-Reply-To: <CABjMoXZ787v2zx+Tqb1=J5ByDd5ySvgJex=PmqjAkecmBzR01g@mail.gmail.com>
References: <20150213174210.6909.43630.idtracker@ietfa.amsl.com> <54F0BFB1.4090707@concordia.ca> <CAG4d1reOc4Wzkyqmg3YF_VXhUfWumVuSr3gTU8zAog9NC12sNg@mail.gmail.com> <54F0FF46.7070700@venaas.com> <CAG4d1rcdpB6ANFq_b6vqKuygy-Cy5FBqVDWo_b5zsK6W-qKNDg@mail.gmail.com> <CABjMoXZ787v2zx+Tqb1=J5ByDd5ySvgJex=PmqjAkecmBzR01g@mail.gmail.com>
Date: Mon, 02 Mar 2015 17:55:32 -0500
Message-ID: <CAG4d1rdE2oy2xOJ1NO-rvRzoE2qrO0tZJs4dZjeuZDhNDqxNhg@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
To: Rishabh Parekh <rishabhp@gmail.com>
Content-Type: multipart/alternative; boundary="001a113ddb5e949d2c0510561d0a"
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/g32N0iKOOCo_5JtdTQaNrThlCYE>
Cc: "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] Last Call: <draft-ietf-pim-rfc4601bis-03.txt> (Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)) to Internet Standard
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.15
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, 02 Mar 2015 22:55:37 -0000
Excellent - thanks! On Mon, Mar 2, 2015 at 5:54 PM, Rishabh Parekh <rishabhp@gmail.com> wrote: > Alia, > > Thanks for the guidance. If I understand the A, B, Cs correctly, we > don't need to refer to 5796 in the draft. In that case I believe that > draft version 4 addresses all the comments received so far. > > -Rishabh > > On Mon, Mar 2, 2015 at 2:26 PM, Alia Atlas <akatlas@gmail.com> wrote: > > Hi Stig, > > > > Sorry for the delay in responding. I was getting advice :-) > > > > If A obsoletes B and C updates B, then other than rolling C into A, > there is > > nothing to do for A. That C updates A should be automatic inheritance. > > > > Regards, > > Alia > > > > On Fri, Feb 27, 2015 at 6:35 PM, Stig Venaas <stig@venaas.com> wrote: > >> > >> Hi > >> > >> On 2/27/2015 11:10 AM, Alia Atlas wrote: > >>> > >>> Bill, > >>> > >>> Thanks for the good review and catches! > >>> I'd like to see the draft updated before March 5 so that it can still > >>> make the telechat on March 12. > >> > >> > >> I'm not sure it is appropriate to update the document referencing those > >> more recent standards track document though. We are progressing 4601bis > >> on the standards track here. Should we as part of that have references > >> to less mature documents? Those other documents are updating 4601 I > >> believe which is fine. But that doesn't necessarily mean that 4601bis > >> should reference them. > >> > >> Looking for guidance here Alia. My thinking is that 4601bis shouldn't > >> change anything from 4601, only leave certain things out. > >> > >> Stig > >> > >>> Regards, > >>> Alia > >>> > >>> On Fri, Feb 27, 2015 at 2:04 PM, William Atwood > >>> <william.atwood@concordia.ca <mailto:william.atwood@concordia.ca>> > wrote: > >>> > >>> In the following, I will refer to draft-ietf-pim-4601bis as simply > >>> "4601bis". > >>> > >>> RFC 4601 has been updated by several RFCs: > >>> > >>> RFC 5059 Bootstrap Router (BSR) Mechanism for Protocol > >>> Independent Multicast (PIM) > >>> RFC 5796 Authentication and Confidentiality in Protocol > >>> Independent Multicast Sparse Mode (PIM-SM) > >>> Link-Local Messages > >>> RFC 6226 PIM Group-to-Rendezvous-Point Mapping > >>> > >>> 4601bis refers to RFC 5059 in Section 3.7. The new text is > identical > >>> to > >>> the text in RFC 4601, although the reference in RFC 4601 is to the > >>> Internet Draft that became RFC 5059. > >>> > >>> 4601bis makes no reference to RFC 5796. Given that RFC 5796 alters > >>> the > >>> preferred IPsec solution (AH is "recommended" in RFC 4601, while > RFC > >>> 5796 says that implementations "MUST support ESP and MAY support > >>> AH"), > >>> and given that RFC 5796 provides considerable detail on the use of > >>> IPsec > >>> to protect link-local messages for PIM-SM, RFC 5796 should be > >>> specifically referenced in Section 6.3 of 4601bis. > >>> > >>> 4601bis makes no reference to RFC 6226. Given that RFC 6226 alters > >>> the > >>> algorithm for determining the Rendezvous Point, RFC 6226 should be > >>> specifically mentioned in Section 3.7 of 4601bis. The authors > should > >>> also consider whether to eliminate Section 4.7.1 and replace it > with > >>> a > >>> pointer to RFC 6226, to reduce it and add a pointer to RFC 6226, or > >>> to > >>> leave it unchanged. > >>> > >>> Suggested text for some of these changes has been supplied to the > >>> authors of 4601bis. > >>> > >>> Bill Atwood > >>> > >>> > >>> On 13/02/2015 12:42 PM, The IESG wrote: > >>> > > >>> > The IESG has received a request from the Protocol Independent > >>> Multicast > >>> > WG (pim) to consider the following document: > >>> > - 'Protocol Independent Multicast - Sparse Mode (PIM-SM): > Protocol > >>> > Specification (Revised)' > >>> > <draft-ietf-pim-rfc4601bis-03.txt> as Internet Standard > >>> > > >>> > The IESG plans to make a decision in the next few weeks, and > >>> solicits > >>> > final comments on this action. Please send substantive comments > >>> to the > >>> > ietf@ietf.org <mailto:ietf@ietf.org> mailing lists by > 2015-02-27. > >>> Exceptionally, comments may be > >>> > sent to iesg@ietf.org <mailto:iesg@ietf.org> instead. In either > >>> case, please retain the > >>> > beginning of the Subject line to allow automated sorting. > >>> > > >>> > Abstract > >>> > > >>> > > >>> > 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) feature that lacks sufficient > deployment > >>> > experience. > >>> > > >>> > > >>> > > >>> > > >>> > The file can be obtained via > >>> > http://datatracker.ietf.org/doc/draft-ietf-pim-rfc4601bis/ > >>> > > >>> > IESG discussion can be tracked via > >>> > > http://datatracker.ietf.org/doc/draft-ietf-pim-rfc4601bis/ballot/ > >>> > > >>> > > >>> > No IPR declarations have been submitted directly on this I-D. > >>> > > >>> > > >>> > >>> -- > >>> Dr. J.W. Atwood, Eng. tel: +1 (514) 848-2424 x3046 > >>> <tel:%2B1%20%28514%29%20848-2424%20x3046> > >>> Distinguished Professor Emeritus fax: +1 (514) 848-2830 > >>> <tel:%2B1%20%28514%29%20848-2830> > >>> Department of Computer Science > >>> and Software Engineering > >>> Concordia University EV 3.185 email:william.atwood@concordia.ca > >>> <mailto:email%3Awilliam.atwood@concordia.ca> > >>> 1455 de Maisonneuve Blvd. West > http://users.encs.concordia.ca/~bill > >>> Montreal, Quebec Canada H3G 1M8 > >>> > >>> _______________________________________________ > >>> pim mailing list > >>> pim@ietf.org <mailto:pim@ietf.org> > >>> https://www.ietf.org/mailman/listinfo/pim > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> pim mailing list > >>> pim@ietf.org > >>> https://www.ietf.org/mailman/listinfo/pim > >>> > >> > > > > > > _______________________________________________ > > pim mailing list > > pim@ietf.org > > https://www.ietf.org/mailman/listinfo/pim > > >
- Re: [pim] Last Call: <draft-ietf-pim-rfc4601bis-0… Stig Venaas
- [pim] Last Call: <draft-ietf-pim-rfc4601bis-03.tx… The IESG
- Re: [pim] Last Call: <draft-ietf-pim-rfc4601bis-0… William Atwood
- Re: [pim] Last Call: <draft-ietf-pim-rfc4601bis-0… Alia Atlas
- Re: [pim] Last Call: <draft-ietf-pim-rfc4601bis-0… Stig Venaas
- Re: [pim] Last Call: <draft-ietf-pim-rfc4601bis-0… William Atwood
- Re: [pim] Last Call: <draft-ietf-pim-rfc4601bis-0… Toerless Eckert
- Re: [pim] Last Call: <draft-ietf-pim-rfc4601bis-0… Alia Atlas
- Re: [pim] Last Call: <draft-ietf-pim-rfc4601bis-0… Rishabh Parekh
- Re: [pim] Last Call: <draft-ietf-pim-rfc4601bis-0… Alia Atlas
- Re: [pim] Last Call: <draft-ietf-pim-rfc4601bis-0… William Atwood
- Re: [pim] Last Call: <draft-ietf-pim-rfc4601bis-0… Toerless Eckert
- Re: [pim] Last Call: <draft-ietf-pim-rfc4601bis-0… Alia Atlas
- Re: [pim] Last Call: <draft-ietf-pim-rfc4601bis-0… Toerless Eckert
- Re: [pim] Last Call: <draft-ietf-pim-rfc4601bis-0… Alia Atlas
- Re: [pim] Last Call: <draft-ietf-pim-rfc4601bis-0… Toerless Eckert