Re: [spring] Updating the SPRING WG Charter

Jeff Tantsura <jefftant.ietf@gmail.com> Tue, 12 June 2018 18:16 UTC

Return-Path: <jefftant.ietf@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 D0B27130FA2 for <spring@ietfa.amsl.com>; Tue, 12 Jun 2018 11:16:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, MIME_QP_LONG_LINE=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 Dg6RC4Lwyzcg for <spring@ietfa.amsl.com>; Tue, 12 Jun 2018 11:16:18 -0700 (PDT)
Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::231]) (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 61F8B130E7B for <spring@ietf.org>; Tue, 12 Jun 2018 11:16:18 -0700 (PDT)
Received: by mail-pf0-x231.google.com with SMTP id c22-v6so12113014pfi.2 for <spring@ietf.org>; Tue, 12 Jun 2018 11:16:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version; bh=vn+bX1BVsBTgZf4QQZoWnSwuukIFaQwiObyrzx13yu8=; b=hzWqFGhH0a3eEc82aVSWEqRA1Qg+Knt4rgrHEBRaZT4reRvmurlSMXj4MUPggOE5X/ 7Wgm/f8WVS0Zw38ltwN8VlkSo2cua7guSLJ6Krz1TiU2u3uZJElmxqe1rfpYsTexpbi0 y1vvW0K646scANeOp9G+a96f7PGy2HQMPjQwUrZgZFe8ow/YGSttrDU6DLaAMB8SBc+6 58ISR3JQtsnEsTZI/p1CqzFdetoDKftBn5tWVVR8Gr/K1PSpT4uN/niZqU27T6hC3y3o upnboDjrZiDz6vm2N5kr3QOd8vbsLzKRNnH82OAWLejdukGmt+2Zr2YXcjwZwH2K0uSU cQbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version; bh=vn+bX1BVsBTgZf4QQZoWnSwuukIFaQwiObyrzx13yu8=; b=X9Zt1TODh9apeieCzme1P3pm+M6oa/pU0SvCGhfsG05hMT+YRU4+U9P6HN0TV/WKrD MNjCqj9dGpkJImCvgaA0IpDCjy4dB0Rt7SXNfUbyP1eb0zjMNlxjPOf/oO96Hf9KeGlr cB7QUW0iBbLI8+GF61n9BHtGO1cgreF+pHl9ThZwaxyBnpF2NNjpdV/y7xqByq8ZrIJE h1c9aEryqPdoKGnCUQ2d7EevJu8cli4WU26IP+duUYhuUDfy/j1IxkRPnu6oYYIEye3n Iba9A33mhO3A8g30B47Z43O9LbP+XhwTymmKtHXsr9HLVn1dd37tcJCWx+w9jaegaieS lJ5A==
X-Gm-Message-State: APt69E0ldfo6Z4G3YB0UinTJwo+FgLKOE3hZX4aZAsQYUTiuIo2TsyGs VSC0ZPG5r8iA9OHbUn3N4ZT7kQ==
X-Google-Smtp-Source: ADUXVKKEVesDsX7FHRtElxqsTXtiWvYtHpHZSPt4IPZuDHMNTh5WkQfM9o2pNdFmYV0Te3/INVZy9A==
X-Received: by 2002:a62:f551:: with SMTP id n78-v6mr1542746pfh.200.1528827378000; Tue, 12 Jun 2018 11:16:18 -0700 (PDT)
Received: from [10.11.13.172] ([66.201.62.254]) by smtp.gmail.com with ESMTPSA id t134-v6sm727676pgb.93.2018.06.12.11.16.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Jun 2018 11:16:17 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/10.c.0.180410
Date: Tue, 12 Jun 2018 11:16:13 -0700
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Rob Shakir <robjs@google.com>
CC: SPRING WG List <spring@ietf.org>
Message-ID: <FCA644E1-D68B-439F-BB85-3A758254B0B1@gmail.com>
Thread-Topic: [spring] Updating the SPRING WG Charter
References: <CAHd-QWt+nmQz_R7kE2oeHa2cD88+ndSkpiv56WSFJfHH3PzxRQ@mail.gmail.com> <6395E535-C5D7-4F95-8FD8-B99B258165C9@gmail.com> <CAHd-QWv0jBgt6PtvyHcdf0P_sLfq+hvU-iCx01Q6AfunSMFV=A@mail.gmail.com>
In-Reply-To: <CAHd-QWv0jBgt6PtvyHcdf0P_sLfq+hvU-iCx01Q6AfunSMFV=A@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3611646977_196411075"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/pRxpbTHKn0NzkclGUFXdqWK5AtE>
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, 12 Jun 2018 18:16:22 -0000

Rob,

 

Sorry for the delay, please see inline.

Thanks!

 

Cheers,

Jeff

From: Rob Shakir <robjs@google.com>
Date: Sunday, June 3, 2018 at 14:36
To: Jeff Tantsura <jefftant.ietf@gmail.com>
Cc: SPRING WG List <spring@ietf.org>
Subject: Re: [spring] Updating the SPRING WG Charter

 

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?

[jeff] I absolutely agree with you that the work should have all abovementioned planes, it is more to how the sentence reads, I meant not to limit the works to dataplane only but a common convention, when we say SR-MPLS we really mean SR with MPLS data plane, same for SRv6

 

*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.

[jeff] we’d disagree on this one, I would not consider setting the context (ie where to lookup) as a forwarding instruction  

 

*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.

[jeff] Ack

 

*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.

[jeff] thanks!

 

Thanks,

r.