Re: [spring] Updating the SPRING WG Charter

Stewart Bryant <stewart.bryant@gmail.com> Tue, 19 June 2018 16:06 UTC

Return-Path: <stewart.bryant@gmail.com>
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 421FE13118A for <spring@ietfa.amsl.com>; Tue, 19 Jun 2018 09:06:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 P8QrsGruOy8d for <spring@ietfa.amsl.com>; Tue, 19 Jun 2018 09:06:10 -0700 (PDT)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 0AE0012777C for <spring@ietf.org>; Tue, 19 Jun 2018 09:06:10 -0700 (PDT)
Received: by mail-wm0-x232.google.com with SMTP id r15-v6so1294211wmc.1 for <spring@ietf.org>; Tue, 19 Jun 2018 09:06:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=GLTGEFFT8ilG/UoLAGBADVNcvG65057vCfbCvH/eTsk=; b=KoYxGA/NT4OAyfiLjZz3fOA7NoyTBMb/kTbEJG+T85SU3jOaj0zYiqT+/yQLMEtGMZ d0fkCxG5eeI9wFK9NVL21ReOA6e7/KY5qy2uVuTjwBfXLDSCzZRo+2O755g7AyzazwEm 4jolkBdAuOKpAF8TiWHbX0gatlp4YZH4sHqENToNCyrbQSq1iUzAlwlmhl9i6H6vqVJ+ 7ZS/O2mE+/sNKrSMFM5rmvCtQwmdjLp/Qos1eV/ldd/QbIQkk0N7TN/ecnzyUeCzlXAS s7ugrdexCZE0tCWQi4py2Dj0JerhCiIKvppSYQdjUHuc7lHa/6joPTaWda6T6sblXGhU bDng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=GLTGEFFT8ilG/UoLAGBADVNcvG65057vCfbCvH/eTsk=; b=oG5xRSHZQRsrLBQuAsQMOniKe2y5h0HvD5AgQ8M5/i7ad6ybC4T46mmdi0nGE477iZ OwjRS1WnSMmm8XkpyNjkiXMft3MXNLnSk9F9yKtUFdU1syanbdggf0lZu6m2xi/gJzBi XSHxdWSs5MNK0RhpRB/OaiCSO2crgcrIqfc75M+xJNz19iTyi/wwhdmaoi3FcJdHM9bF GLtyaLHTJzDS/g/tQo+0p45Bwm30Q4kGfErY3cFJMSnYHVQqLQAfXnmdrFxKhTZSPtWz LEisvc0OilAXxV+seV3xf+8hDYnv07u/6IsbIDNz2IVjikXoAJa9r5cSepxbCltc6ycb 0j2g==
X-Gm-Message-State: APt69E0VNb014hTDYHVNhYmZzGDBROVu3aBgBpZyhoDrpUu8Mn/ItxlT vyFm/JQ6zSMF5sMw0vbztURPgL2h
X-Google-Smtp-Source: ADUXVKIddEVpylrwXo4o6QCXUG2gOAkeaHRq04SmctIB96P1GdtOe4IHOEUVL8HxJ3l1kOKPhDdidA==
X-Received: by 2002:a1c:800e:: with SMTP id b14-v6mr12053540wmd.83.1529424368588; Tue, 19 Jun 2018 09:06:08 -0700 (PDT)
Received: from [192.168.2.105] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id m58-v6sm56527wrf.61.2018.06.19.09.06.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Jun 2018 09:06:08 -0700 (PDT)
To: Robert Raszuk <robert@raszuk.net>
Cc: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, "spring@ietf.org" <spring@ietf.org>, Xiejingrong <xiejingrong@huawei.com>, Michael McBride <michael.mcbride@huawei.com>, Rob Shakir <robjs=40google.com@dmarc.ietf.org>, Paul Mattes <pamattes@microsoft.com>, "Zafar Ali (zali)" <zali@cisco.com>, Eric C Rosen <erosen@juniper.net>, "Voyer, Daniel" <daniel.voyer@bell.ca>
References: <8CCB28152EA2E14A96BBEDC15823481A1CB79F12@sjceml521-mbs.china.huawei.com> <CA+b+ER=UknPNDweStHDXvbsuqkL2+r5=5zzS4ujAredew_F_vQ@mail.gmail.com> <DB5PR0301MB19094268D61209CFB345DE609D7B0@DB5PR0301MB1909.eurprd03.prod.outlook.com> <CA+b+ER=WX6WOxM7BhiysZxY39dNYYAHwT2hemR-tD+PLGi+KiQ@mail.gmail.com> <DM5PR21MB018696A5159598D791C30830CA7B0@DM5PR21MB0186.namprd21.prod.outlook.com> <DB5PR0301MB19091032724ED7EDC11F63659D7B0@DB5PR0301MB1909.eurprd03.prod.outlook.com> <CA+b+ERmzd1SjX4VqONwQGcUuD7rjuzx1zXb1nE3AyHWErBhMRw@mail.gmail.com> <DB5PR0301MB1909DA951760E8B7A6477EF09D7A0@DB5PR0301MB1909.eurprd03.prod.outlook.com> <CA+b+ER=p=qAAp0um4HBtecu23z_csNusViuoeMSadm0s5oyzsQ@mail.gmail.com> <DB5PR0301MB190937574F92F7314291FA129D790@DB5PR0301MB1909.eurprd03.prod.outlook.com> <CA+b+ERkXj4PHmUBAscG7dp-NFFr+iBUz_ya9X85jRdwpZ8kOyw@mail.gmail.com> <c1973e20-5a85-359f-b2ac-5eb7e602a68e@gmail.com> <CA+b+ERmwVHrohaH8BUam4yAraH3_hbE-7zGYxiuSZg_6Ps+OFA@mail.gmail.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <4eaec78d-b270-89a9-566d-779d0761b632@gmail.com>
Date: Tue, 19 Jun 2018 17:06:06 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <CA+b+ERmwVHrohaH8BUam4yAraH3_hbE-7zGYxiuSZg_6Ps+OFA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------43266F5DEE2C533F378A0582"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/R1_LGXsV1lhk7bYgXLSl5NtCQsU>
X-Mailman-Approved-At: Tue, 19 Jun 2018 09:13:20 -0700
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: Tue, 19 Jun 2018 16:06:19 -0000

Hi Robert,

OK, so I understand this a bit more.

Yes, we could introduce a m/c tree in the middle of the network and have 
the leaves terminate in anything. That would include an SR unicast path 
and/or a new m/c tree or any combination thereof. What you have to do is 
to place the correct binding SID at the leaf of the tree which of course 
would be unique to that leaf, and identified by the m/c tree it arrived on.

So by adding in state through a generalised Binding SID mechanism we can 
build a full multicast system strictly within SR.

Sounds like it needs to be in charter.

- Stewart


On 19/06/2018 14:39, Robert Raszuk wrote:
> Hi Stewart,
>
> Nope that would be incorrect assumption.
>
> Replication anchors would be where topologically it makes sense. And 
> there may not be at all any multicast trees those subject flows would 
> need to traverse. It is just about efficiency in content distribution.
>
> Regards,
> R.
>
> On Tue, Jun 19, 2018 at 3:36 PM, Stewart Bryant 
> <stewart.bryant@gmail.com <mailto:stewart.bryant@gmail.com>> wrote:
>
>     For clarification:
>
>     Can I assume that we are talking about replication at ingress to a
>     series of  unicast SR paths each to an installed multicast tree
>     close to egress?
>
>     - Stewart
>
>
>     On 10/06/2018 10:58, Robert Raszuk wrote:
>>     Hey Sasha,
>>
>>     100% agree with your last post. Very glad to see your support for
>>     spray/fan-out or if you will
>>     static MDTs to be in scope of SPRING.
>>
>>     Based on number of WG members input expressed both at the meeting
>>     and on the list  I hope
>>     proposed SPRING charter will be updated soon to reflect that.
>>
>>     Cheers,
>>     R.
>>
>>     ​PS. Btw - I am also ok that ingress replication is not relevant
>>     to SPRING as it essentially happens at the
>>     ingress to the domain. ​
>>
>>
>>
>>     On Sun, Jun 10, 2018 at 7:39 AM, Alexander Vainshtein
>>     <Alexander.Vainshtein@ecitele.com
>>     <mailto:Alexander.Vainshtein@ecitele.com>> wrote:
>>
>>         Robert,
>>
>>         First of all, I did not say that your quote was inaccurate. I
>>         apologize for possible misperception.
>>
>>         Second, I believe that spray or fan-out (meaning support of
>>         externally computed static MDTs) in SR-MPLS is a relevant
>>         focus area for the future WG work. Of course the solution
>>         must be aligned with the SPRING and MPLS architecture, and
>>         this imposes additional restrictions on how such a solution
>>         would look.
>>
>>         Last but not least, I have differentiated (from my first
>>         email on this thread) */ingress replication/* *in SR* from
>>         the more generic *multicast support *in SR:
>>
>>         -The latter is quite acceptable to me
>>
>>         -The former, IMHO, should be left out of scope.
>>
>>         Hope this helps to clarify my position.
>>
>>         Regards, and, again, apologies for possible misinterpretation.
>>
>>         Sasha
>>
>>
>>
>>     _______________________________________________
>>     spring mailing list
>>     spring@ietf.org <mailto:spring@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/spring
>>     <https://www.ietf.org/mailman/listinfo/spring>
>
>