Re: [spring] Updating the SPRING WG Charter

Rob Shakir <robjs@google.com> Sun, 03 June 2018 21:36 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 F3925126B6D for <spring@ietfa.amsl.com>; Sun, 3 Jun 2018 14:36:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.21
X-Spam-Level:
X-Spam-Status: No, score=-18.21 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_LOW=-0.7, 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 V3fBCYydiDUD for <spring@ietfa.amsl.com>; Sun, 3 Jun 2018 14:36:38 -0700 (PDT)
Received: from mail-yw0-x233.google.com (mail-yw0-x233.google.com [IPv6:2607:f8b0:4002:c05::233]) (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 24ADC124234 for <spring@ietf.org>; Sun, 3 Jun 2018 14:36:38 -0700 (PDT)
Received: by mail-yw0-x233.google.com with SMTP id j190-v6so9780511ywe.4 for <spring@ietf.org>; Sun, 03 Jun 2018 14:36:38 -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=ySbOTjkIh8vhM8pvsjBUDiz+lRw/0pRNiC1mD1AjmSQ=; b=MhhSLXST8ZW12WSiPfw5nmQhzG1KfMH6v9j+OWhQbbwOalhUF/dRotqCCWxBnPTB+2 C8Zwe8Di94E2eIGbTDLySw/r/hfwrjAP3VaXhMIrMj9bejpATeKiZixealwqpIlZnfHF keVCftvyFGW74LK0AWCAeKoDnMBDpfLUwTgRUSObuoWSWWBOh67Flzx2idDNJIleGHOy fAYn5PHhD72bId1RTSQ+9kKBU5vcmJZsaZMu9L7gllem78cfbXzrExfbtNW2LkMhKsNp PRJgAFQMfWxPRdZKBEX7ZacxgSajc31hHttreyM19PnRkQZqEEkU3YAAkGGAYBTgMiS7 LM/A==
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=ySbOTjkIh8vhM8pvsjBUDiz+lRw/0pRNiC1mD1AjmSQ=; b=L8MElFWfMLbr6lMhHkkHXDxqfWv9nWKCwN/cPs5UxOre3I3VDjxuxH+BqDPtqU3qKO 63oAqNyv+1lzZFiODiwWYcFamjfH8kTnnp4QmnrTf7N7m4uk8NGbhkbpj7Z5fXY/7xbu CL3ku+MHC+GSSQcOJTvLDj4qF7HxTOA1isiohP6Vw0z+10HB2ldx3mLZnG12KWm25Rc0 62YqmrnSpWhL9mI4Kuc5ZQSKPEWPCE37a29FbhYSEQSO0wLfPTwlKxrSwTnx4TSE7Uzd CVeJEUwj34mFgOUKs/wdTR7y4Cd1uNDb24BRbTmU2nHqmiVw+PDemD2QNNgorRhxwXk8 bFCg==
X-Gm-Message-State: APt69E2dicwpzFMnGn4meMHC+zSn/o/Fd4Y50Sqp07Wbaf1bn7nE7c51 VVEX8+E1YXRMmeA3jo/MkdYI6NuJBprRLTcf78U3DA==
X-Google-Smtp-Source: ADUXVKIopWbweI3fZjcwTU83WCu4p9yChHYgirno0qs6BT3hSsbyL1N/dYHTUxdZiR1BpJQ67h3mfrOvu6HWeqkSh0g=
X-Received: by 2002:a81:3e1c:: with SMTP id l28-v6mr4845516ywa.34.1528061796912; Sun, 03 Jun 2018 14:36:36 -0700 (PDT)
MIME-Version: 1.0
References: <CAHd-QWt+nmQz_R7kE2oeHa2cD88+ndSkpiv56WSFJfHH3PzxRQ@mail.gmail.com> <6395E535-C5D7-4F95-8FD8-B99B258165C9@gmail.com>
In-Reply-To: <6395E535-C5D7-4F95-8FD8-B99B258165C9@gmail.com>
From: Rob Shakir <robjs@google.com>
Date: Sun, 03 Jun 2018 14:36:24 -0700
Message-ID: <CAHd-QWv0jBgt6PtvyHcdf0P_sLfq+hvU-iCx01Q6AfunSMFV=A@mail.gmail.com>
To: Jeff Tantsura <jefftant.ietf@gmail.com>
Cc: SPRING WG List <spring@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009a73c8056dc39ce6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/vxmkujNiPjUEIanzEboWhKyqIZM>
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: Sun, 03 Jun 2018 21:36:40 -0000

Hi Jeff,

Thanks for the comments.

On Fri, Jun 1, 2018 at 9:44 AM Jeff Tantsura <jefftant.ietf@gmail.com>
wrote:

>
> The Source Packet Routing in NetworkinG (SPRING) Working Group is the home
> of
>
> Segment Routing (SR) using MPLS (SR-MPLS) and IPv6 (SRv6).
>
> [jeff] I’d add “dataplanes”
>

robjs> I don't think that SPRING should limit itself to having to just work
on dataplane technologies. The functional specifications or architectures
that are proposed are likely to span both data, control, and management
planes (e.g., YANG models, counter specifications). I'd be interested if
you disagree?

*snip*
>
>
>
> o Using SR
>
> [jeff] SR conveyed metadata perhaps? Think of BSID x-connect into another
> layer
>

robjs> I'd argue that this is more than metadata, it's really a forwarding
instruction that says to send to some other layer, or that is interpreted
in another domain. Metadata to me would mean information that we're
carrying on the packet that *isn't* used for forwarding.


> *snip*
>
>      * lsr on OSPF and IS-IS extensions to flood SPRING-related information
>
> [jeff] in RIFT we plan to support SR as well
>

robjs> This is probably RIFT co-ordinating with SPRING. I'd rather avoid
listing another protocol here without there being SPRING work that affects
it. Of course, please do involve SPRING in discussions of SR support in
RIFT.


> *snip*
>
>      * teas on generic traffic engineering architecture
>
> [jeff] rtgwg for fast convergence related topics
>

robjs> Thanks -- yes, given all the work in rtgwg on this topic, this
should definitely be added.

Thanks,
r.