Re: [spring] Updating the SPRING WG Charter

"Voyer, Daniel" <daniel.voyer@bell.ca> Wed, 06 June 2018 20:20 UTC

Return-Path: <prvs=6881f3bd5=daniel.voyer@bell.ca>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98CB7130F94 for <spring@ietfa.amsl.com>; Wed, 6 Jun 2018 13:20:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
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 DM5SiXM7WV6h for <spring@ietfa.amsl.com>; Wed, 6 Jun 2018 13:20:03 -0700 (PDT)
Received: from CORP-ESA4-Wyn.bell.ca (esa4-wyn.bell.ca [67.69.243.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4ECB81292AD for <spring@ietf.org>; Wed, 6 Jun 2018 13:20:03 -0700 (PDT)
Received: from dm5czo-d01.bellca.int.bell.ca (HELO DG1MBX03-WYN.bell.corp.bce.ca) ([198.235.102.33]) by esa04corp-wyn.bell.corp.bce.ca with ESMTP; 06 Jun 2018 16:20:01 -0400
Received: from DG1MBX04-WYN.bell.corp.bce.ca (2002:8eb6:120e::8eb6:120e) by DG1MBX03-WYN.bell.corp.bce.ca (2002:8eb6:120d::8eb6:120d) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Wed, 6 Jun 2018 16:20:01 -0400
Received: from DG1MBX04-WYN.bell.corp.bce.ca ([fe80::e0f2:82d2:4ec2:f201]) by DG1MBX04-WYN.bell.corp.bce.ca ([fe80::e0f2:82d2:4ec2:f201%22]) with mapi id 15.00.1347.000; Wed, 6 Jun 2018 16:20:01 -0400
From: "Voyer, Daniel" <daniel.voyer@bell.ca>
To: "Zafar Ali (zali)" <zali@cisco.com>, Rob Shakir <robjs=40google.com@dmarc.ietf.org>, Michael McBride <Michael.McBride@huawei.com>
CC: Xiejingrong <xiejingrong@huawei.com>, "spring@ietf.org" <spring@ietf.org>
Thread-Topic: [spring] Updating the SPRING WG Charter
Thread-Index: AdP56p5QOgEqtjT0TPyaFDKrNzAuwABwo3NQACTI6YAAAQilgAAAHQ4AAGFqSQAAAkwAAA==
Date: Wed, 06 Jun 2018 20:20:01 +0000
Message-ID: <CA802BB9-00E2-4DA4-B7F2-B0ECB5DBD8FD@bell.ca>
References: <8CCB28152EA2E14A96BBEDC15823481A1CB79F12@sjceml521-mbs.china.huawei.com> <16253F7987E4F346823E305D08F9115A99A7D4CE@nkgeml514-mbx.china.huawei.com> <CAHd-QWvx-tkP1Asx3PwM3p2=wjuJm7b=A4Hb-BUnCMRzwT1J8w@mail.gmail.com> <8CCB28152EA2E14A96BBEDC15823481A1CB7FBFE@sjceml521-mbs.china.huawei.com> <CAHd-QWu+184A3Nje_Bmki9A3wwpp=4YyyKTTkWBtLcf_gt7Lvg@mail.gmail.com> <75252B5F-6BCB-4166-ACC1-C9E9697B7B68@cisco.com>
In-Reply-To: <75252B5F-6BCB-4166-ACC1-C9E9697B7B68@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.d.1.180523
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.24.25.8]
Content-Type: multipart/alternative; boundary="_000_CA802BB900E24DA4B7F2B0ECB5DBD8FDbellca_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/AV_7jRxokAWpUDybRa0nk_jeU3E>
Subject: Re: [spring] Updating the SPRING WG Charter
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jun 2018 20:20:12 -0000

Hi all,

I support and agree w/ Zafar.

Multicast in SR is much needed and there is lots of development that needs to happen, whether for SRv6 or with SR-MPLS. The core architecture and development need to be included in this working group.

Thanks,
dan


From: "Zafar Ali (zali)" <zali@cisco.com>
Date: Wednesday, June 6, 2018 at 3:14 PM
To: Rob Shakir <robjs=40google.com@dmarc.ietf.org>, Michael McBride <Michael.McBride@huawei.com>
Cc: Xiejingrong <xiejingrong@huawei.com>, "spring@ietf.org" <spring@ietf.org>, "Zafar Ali (zali)" <zali@cisco.com>
Subject: Re: [spring] Updating the SPRING WG Charter

Hi Rob,

The multicast in SR belongs to the same category as I highlighted in my last email. Just to repeat …

At IETF101, you and Bruno presented a slide based on the WG feedback on the mailing list (https://datatracker.ietf.org/meeting/101/materials/slides-101-spring-00-chairs-slides-01). During the Spring meeting, the WG agreed to add milestones to those items. In general, I see some milestones are not included in the proposed chartered text.

Specifically, multicast in SR is included in that list with the "Ingress replication SID (Tree SID /spray)" bullet (and support during the WG meeting) but is missing in the proposed charter text. So, I agree with Xiejingrong and Michael highlighting the same. There is already interest and agreement shown by the WG to include multicast in SR in the charter.

In the light of the above, please add a milestone for the WG to specify architecture, and the required protocol extensions for multicast in SR with MPLS and IPv6 data planes, including specification of the ingress replication SIDs (e.g., Tree SID, Spray). Nonetheless, I wholeheartedly agree that the actual protocol extension work should be done at the WG that owns the protocol.

Thanks

Regards … Zafar

From: spring <spring-bounces@ietf.org> on behalf of Rob Shakir <robjs=40google.com@dmarc.ietf.org>
Date: Monday, June 4, 2018 at 12:45 PM
To: Michael McBride <Michael.McBride@huawei.com>
Cc: Xiejingrong <xiejingrong@huawei.com>, "spring@ietf.org" <spring@ietf.org>
Subject: Re: [spring] Updating the SPRING WG Charter

Michael,

Thanks for the comment.
On Mon, Jun 4, 2018 at 9:42 AM Michael McBride <Michael.McBride@huawei.com<mailto:Michael.McBride@huawei.com>> wrote:
It would be helpful, while updating the charter, to state whether multicast in SR is in/out of scope in order to know which wg to take our future work.

I think this is impractical. If we state everything that is in or out of scope, we'll end up with a laundry list. The aim of the charter is to define clearly the work that the WG should focus on. It does not mean that we can never host discussion of individual drafts if they are relevant. If there are requirements, we can always recharter if something new becomes the highest priority for the industry w.r.t SR.

Kind regards,
r.