Re: [spring] Updating the SPRING WG Charter

Rob Shakir <robjs@google.com> Mon, 04 June 2018 16:12 UTC

Return-Path: <robjs@google.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 D0B3E120052 for <spring@ietfa.amsl.com>; Mon, 4 Jun 2018 09:12:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.51
X-Spam-Level:
X-Spam-Status: No, score=-17.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 Wym8H6ZOh2Ns for <spring@ietfa.amsl.com>; Mon, 4 Jun 2018 09:12:21 -0700 (PDT)
Received: from mail-yb0-x236.google.com (mail-yb0-x236.google.com [IPv6:2607:f8b0:4002:c09::236]) (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 EC4601228E2 for <spring@ietf.org>; Mon, 4 Jun 2018 09:12:20 -0700 (PDT)
Received: by mail-yb0-x236.google.com with SMTP id w3-v6so8629975ybq.10 for <spring@ietf.org>; Mon, 04 Jun 2018 09:12:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=vPzjvfvJesc9InySmMBVnl/VKDDePNz5mGqVBf3lVag=; b=J/HxoLMCu80/kx49PxFEeDNDYQoODL5HQ8fWddKYL8vmfWjqzY0xC756GFkV1fvmV9 6V6VF7BjQdxnYl/9iV4u+MTdivwSv8OC2HrVEDlHSM9jdvZZcIXnX/ESAaEPI2066+Kf TR7Zksmwb6D1Y2QGKXq1gfXp5ea6lKQW8wyzuKXwbglqQthNNK5QHHYw20E7l40KcRxf 70wNRcVROkreAtY//niPcB4V1hUvCQf3TzUaGPr0yeCw/MORnUD+TaXLTdKxILyn3NEe Ll7D1XGlnGrVmlmVy96j6ddpspV+Sb611pR2i+clqX78wGdV+bT4q2yVV8MlyhDg9Ypo 2+ng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=vPzjvfvJesc9InySmMBVnl/VKDDePNz5mGqVBf3lVag=; b=A0ytoDBjOXNqStSHAvjsBzsLt/5qd5t9Jgv5PO1G8isKsSRcbftpWMQQTTIwvY1pkm qOWh+op4Ez9cDfwLD+UyAiePaI0jLMkJeeFH7fmDZdeAw+bwKFbChLE0S5XDB6BpolSf 43kbmdfRQbRCTB+ReWHVI8pK9Qk+sV6LQKEPxz33Z5Iipufaa1S1+t02P8ZwQxPzIbxS skuTJD7IK//Bs4FtE6V307W6GUx/BuKL4YmSf7hiChBEHVOi1rGTCQSrCkvXdjE/HJuQ 8A2JoKfreSf3qKIFHdhHDEVnHjxTnCWeYDbvcf3M3P3poNq/qalLYtAXHFUgTVwPFYMG rC5A==
X-Gm-Message-State: APt69E2GlTvBxBHS9GyhfMm84k44AreFm3sS0wvPgQplAc+hLj8dhHpo kyWJDY8iGSIh04BPcrZX8DstJGRhYsKeiw82mS+iWg==
X-Google-Smtp-Source: ADUXVKKnjoswo5h5oRu4odp3qD1Gug8dLYDX+qX7Xv2Z9gP4nZL3zihjuS43WJFLOJosVP4DpiuvPb8z/6wzlp3FHY0=
X-Received: by 2002:a25:ac06:: with SMTP id w6-v6mr7912834ybi.153.1528128739490; Mon, 04 Jun 2018 09:12:19 -0700 (PDT)
MIME-Version: 1.0
References: <8CCB28152EA2E14A96BBEDC15823481A1CB79F12@sjceml521-mbs.china.huawei.com> <16253F7987E4F346823E305D08F9115A99A7D4CE@nkgeml514-mbx.china.huawei.com>
In-Reply-To: <16253F7987E4F346823E305D08F9115A99A7D4CE@nkgeml514-mbx.china.huawei.com>
From: Rob Shakir <robjs@google.com>
Date: Mon, 04 Jun 2018 09:12:07 -0700
Message-ID: <CAHd-QWvx-tkP1Asx3PwM3p2=wjuJm7b=A4Hb-BUnCMRzwT1J8w@mail.gmail.com>
To: Xiejingrong <xiejingrong@huawei.com>
Cc: "spring@ietf.org" <spring@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b0d915056dd332ed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/2Mikvi2yOFl3rMN0RuRmHBebwvs>
Subject: Re: [spring] Updating the SPRING WG Charter
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 04 Jun 2018 16:12:23 -0000

Hi Jingrong,

On Sun, Jun 3, 2018 at 7:44 PM Xiejingrong <xiejingrong@huawei.com> wrote:

> Will SPRING consider multicast/BIER being included ? These are some
> reasons I am thinking about:
>
> (1) multicast/multipoint-transfer is always a requirement for internet
> service, and is always requiring some unicast technology as a precursor.
>
> (2) there is already a similar WG BIER to considering the similar
> stateless solution for multicast for long-term.
>
> (3) there is already some consideration about multipoint SR in
> segment-routing-policy draft for a long time.
>
> (4) there is already some consideration about combining BIER and SR in
> bier-6man-encapsulation draft.
>
> (5) it had been mentioned in ietf101 London to consider cooperating with
> BIER for some purpose.
>

robjs> IMHO, if BIER leverages SR work this should be in liaison with
SPRING, but I do not expect there to be any BIER related work in SPRING
itself. If this needs changes to dataplanes, then the relevnat working
group (mpls, or 6man) should be involved too.

robjs> It is my personal opinion that the SR-TE policy draft needs to be a
constrained set of problems. It had become a collect-your-use-case
document. Part of the ask of breaking the document down is so that we can
produce a clear, succinct set of documents. Until such time as there are
concrete proposals on multicast in SR that SPRING needs to consider (i.e.,
require a new functional specification, ratheror architectural extension)
then I would aim to err on the side of keeping the charter clear, rather
than collecting all possible use cases in it.

robjs> Please disagree with me if there is a benefit to having this in the
charter that I'm missing.

Thanks,
r.