Re: [pim] PIM recharter

Lucy yong <lucy.yong@huawei.com> Fri, 27 February 2015 15:42 UTC

Return-Path: <lucy.yong@huawei.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 492A81ACD4E for <pim@ietfa.amsl.com>; Fri, 27 Feb 2015 07:42:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level:
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 xG-esTJDNddm for <pim@ietfa.amsl.com>; Fri, 27 Feb 2015 07:42:11 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D8C01ACD4A for <pim@ietf.org>; Fri, 27 Feb 2015 07:42:10 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BTB36422; Fri, 27 Feb 2015 15:42:08 +0000 (GMT)
Received: from DFWEML704-CHM.china.huawei.com (10.193.5.141) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 27 Feb 2015 15:42:08 +0000
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml704-chm ([10.193.5.141]) with mapi id 14.03.0158.001; Fri, 27 Feb 2015 07:41:55 -0800
From: Lucy yong <lucy.yong@huawei.com>
To: Alia Atlas <akatlas@gmail.com>
Thread-Topic: [pim] PIM recharter
Thread-Index: AQHQUExBQrt8D850R0uJG2ggc2osOp0AEB7wgACe1oCAAMrEgIAACVPAgALJsgCAAFgOAA==
Date: Fri, 27 Feb 2015 15:41:55 +0000
Message-ID: <2691CE0099834E4A9C5044EEC662BB9D45457FBB@dfweml701-chm>
References: <CAG4d1rf+FVaPO41kbTGn=avpwJEgdH8rJU0j6mtQSp3cf_TV4w@mail.gmail.com> <2691CE0099834E4A9C5044EEC662BB9D45455B90@dfweml701-chm> <CAG4d1rfbE265Q3Js_G3YupR5C61LWVN1v_rqQGQpNsU6mSY_JQ@mail.gmail.com> <2691CE0099834E4A9C5044EEC662BB9D45455C89@dfweml701-chm> <CAG4d1rcau9WtY+FcE9WWBKUyNyHi-pd9NLqOqRRiaSkyDSPuQA@mail.gmail.com> <2691CE0099834E4A9C5044EEC662BB9D454561AC@dfweml701-chm> <CAG4d1rewRqP5jsXBWdYBkWWkj+AKpScD2zeT8F==PjuQ4DQesQ@mail.gmail.com>
In-Reply-To: <CAG4d1rewRqP5jsXBWdYBkWWkj+AKpScD2zeT8F==PjuQ4DQesQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.146.134]
Content-Type: multipart/alternative; boundary="_000_2691CE0099834E4A9C5044EEC662BB9D45457FBBdfweml701chm_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/pim/Cb8ZkQnQdMesZj9oK3o8mcnKrN8>
Cc: joel jaeggli <joelja@bogus.com>, Brian Haberman <brian@innovationslab.net>, "Deborah Brungard (dbrungard@att.com)" <dbrungard@att.com>, "pim@ietf.org" <pim@ietf.org>
Subject: Re: [pim] PIM recharter
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: Fri, 27 Feb 2015 15:42:18 -0000

Alia,

Please see inline below.

From: Alia Atlas [mailto:akatlas@gmail.com]
Sent: Thursday, February 26, 2015 8:18 PM
To: Lucy yong
Cc: pim@ietf.org; joel jaeggli; Brian Haberman; Deborah Brungard (dbrungard@att.com)
Subject: Re: [pim] PIM recharter

Lucy,

Just to clarify and finish up this conversation.  In the proposed charter, I have:

"The WG should discuss and develop new ideas related to multicast
protocols and distributing of multicast-related information.  The WG must
be explicitly rechartered to adopt any."

and the multicast work that I was specifically thinking of is the IGP-based multicast work that you've
been working on.  I can certainly see and understand its potential usefulness in data-center scenarios
as well as the trade-offs implied.

I am sorry if the previously floated charter raised expectations.  I was busy at NANOG and didn't
have time to rapidly revise the preliminary draft version of the charter.

This really isn't about trying to have you jump through hoops.  It's trying to make sure that
there's enough interest in the work that others will collaborate, that others will review, and that it will
become a useful standard.

I would appreciate hearing from others on the mailing list about interest in pursuing this work.

At this point, I am not expecting to have a final rechartering until after Dallas and there should be time
in the meeting to discuss thoughts on the charter too.
Lucy: OK, we will submit the arch draft, solicit comments/feedbacks, and present/discuss it in PIM in Dallas. Hope we reach a consistent consensus then.

Which WG should the draft be entitled for now?

Thanks,
Lucy

Regards,
Alia

On Wed, Feb 25, 2015 at 10:45 AM, Lucy yong <lucy.yong@huawei.com<mailto:lucy.yong@huawei.com>> wrote:
[resend without too BIG message body]

Alia,
[snip]
I am disappointed this charter text. It is very different from the proposed and discussed charter text on the mailing list. The following charter text only allows working on PIM/IGMP/MLD protocol. Any other item is in “may” category and requires WG rechartering to work on it.

 Yes, I do not think that having a broadly open charter to come work on anything is healthy for the WG.  We are working on what should be clearly in charter and what areas the WG may explore but cannot work on unless the recharter occurs.

You know that IGP multicast proposal and homenet were discussed in PIM in Honolulu.  There were interests to work on these technologies and you suggested that PIM WG is the right place to work on IGP multicast (was discussed in IS-IS WG several times).  But the new charter text does not accept it as a work item and make it as “may or may not”.  This does not reflect the outcome from Honolulu meeting. Why do you want make this gate for IGP multicast and homenet?

Because there has been NO DISCUSSION or WORK done on the IGP multicast proposal since Honolulu.  The WG said that it was interesting - but has not yet demonstrated active consensus and willingness to work on it.  I see a message from Nov 10 on the mailing list ( http://www.ietf.org/mail-archive/web/pim/current/msg03055.html ) that was never responded to.  This does not indicate to me that there is currently active interest in developing the work in the WG.
Lucy:  I did not response that email because that was in IETF meeting week and before the PIM meeting. Some questions and comments are addressed in our presentation and Ice were there. I did not know that you are waiting on some discussion on mailing list while We are waiting on the next charter text. In fact, we are working it offline.

[Alia] You know that conversations and decisions happen on the list.  One of the critical aspects of IETF is that we have an open consensus process.  That means open discussion on the mailing list.
[Lucy] This is my thought too. The charter text was openly discussed on the mailing list based on the WG consensus in Honolulu. ADs do not express any concern but change it now.
 There is no reason to "wait on the next charter text".  If you do the work and have the active consensus and enthusiasm, that is key to the WG getting the work done.  Of course, off-line and individual conversations happen and are also useful - but doing them solely doesn't forward the standardization process.  This particular email raised a concern about looping that I haven't seen addressed.
[Lucy] Yes, we need do our job and also need AD help. If you could ping us early on this concern, we would do that to avoid it.  I have replied Ice’s comments about looping concern.
 Similarly, the homenet work has not been discussed on the mailing list.  It has been raised by one other in this thread as something of potential interest.  Sure - but I need more information on what that work should entail and whom would actually do it.

That's why both of these items are not explicitly in the charter.   There is the possibility to add them later - but I must see active consensus to work on them and some actual work.  The IGP multicast proposal is interesting - but it is also clearly another way of doing multicast.
Lucy: The proposal is supported by many vendors as of draft co-authors. Huawei has some implementation. I am not sure what kind of active consensus you look for at this point. We already clearly pointed out the use case for this in DC and why PIM can’t fit for the use case.

[Alia] I'm sure that you don't need me to explain that draft authors should be writing the draft.  Support can be expressed in many ways - including discussions.  I am happy to hear that Huawei has an implementation; that's a good sign of serious interest and that the basic ideas can work.  I just read through the draft again; it could be improved significantly to be clearer.

[Alia] As I've said, the reception at the last IETF in the room was good but nothing has confirmed that on the list.  I look forward to hearing more discussion and opinions on the list and in Dallas.
[Lucy] This is my misunderstand. The charter text discussed on the mailing list was the confirmation in my mind.  Hope you /chairs can give some warning ahead. We will submit the architecture draft and present it in Dallas meeting.

Regards,
Lucy