Re: [spring] Updating the SPRING WG Charter

Jeff Tantsura <jefftant.ietf@gmail.com> Fri, 29 June 2018 15:19 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 BC6D7127148 for <spring@ietfa.amsl.com>; Fri, 29 Jun 2018 08:19:49 -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, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 thAng16Z2EbD for <spring@ietfa.amsl.com>; Fri, 29 Jun 2018 08:19:45 -0700 (PDT)
Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d: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 01E2D126CC7 for <spring@ietf.org>; Fri, 29 Jun 2018 08:19:45 -0700 (PDT)
Received: by mail-qk0-x236.google.com with SMTP id b66-v6so5109099qkj.1 for <spring@ietf.org>; Fri, 29 Jun 2018 08:19:44 -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=P4ANbyVxoSbIZZBZsLppUw828wyRN1jnHiH6I/eCbuM=; b=n+V8F84EQPxI140aIlVYqtvKK/RLJ1BcFeI8bj1H2vuXL4+QGoAHFe0pzg4Mxp+ITO Spa9h2o8FWltg/OSRULpS22Y9JK/jTL3U8V+7i3cgY4evB2PqirktDQzp4O8aZ4+Pz8W d53EpVSq5gZTge1w9ljzg/ZM6PdCaei7o9mG6zg0QhnI8nbulC3+FMJ6hZwdtaoLJSYZ LUxiiogcwFXSczDZ9d2txkG44yMl3Psrv27ZFQ+/3QhM4rgp7L/idDILdlggjNLeS03K 2qMbUp7bnlY/rqfKwEYiUxTmwCkEflDy9Ss+YiMSkn2EMpyTUljpandM7Wg41WDcvOro J/Ow==
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=P4ANbyVxoSbIZZBZsLppUw828wyRN1jnHiH6I/eCbuM=; b=J7wpycMtbMEvrX7xXBcw2NGYJo0YWVtyNPv/QcZbNnSeYIpZBIqxUTZsKz4q0ZczTi N2Iqmdzoa9oxW4diz8ZExwFjl8Kg0uEfH8asKMBNVCI9TRmOYniCtTXcPYoWaqRAS0Vg hHChDzQsuPCIaYK+G3rUmEDTWwMxQfZcf6oLklwzelDK2YnovKG695RbL1pg2pJbvalu eAk6lMQMYCerenoDTR54kHJ1goixQG75bIj8bYB/6hJV0RxuKTtZzsyz8yWdJ9OPrmKV 75XSzJP58/inz/2L7l0H0FknUW2dxj7YOzKYuPEtLk7Ng14SmIGzJUjGfB2k964a2lic lNWA==
X-Gm-Message-State: APt69E0ypb3uirwxmBaQTLEgmNV/1AifUxuWxuZZvmO7IqJjK70dnt8Z LIZOINUy755Hu26pp2zW3ZRl8w==
X-Google-Smtp-Source: AAOMgpdFZRQ5Mic63A77f+GrL6yc6m9IDnmq+08Nu5+OIi5Xf7Tg7GeZKIi+C9bPyka4kQFwXYo5ig==
X-Received: by 2002:a37:faa:: with SMTP id 42-v6mr13071178qkp.387.1530285583867; Fri, 29 Jun 2018 08:19:43 -0700 (PDT)
Received: from [172.30.155.140] ([132.205.230.13]) by smtp.gmail.com with ESMTPSA id n17-v6sm118517qtc.34.2018.06.29.08.19.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 Jun 2018 08:19:42 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/10.c.0.180410
Date: Fri, 29 Jun 2018 11:19:41 -0400
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Linda Dunbar <linda.dunbar@huawei.com>, "bruno.decraene@orange.com" <bruno.decraene@orange.com>
CC: SPRING WG List <spring@ietf.org>
Message-ID: <A24831E1-5095-467B-81F8-A0A8F0EF3143@gmail.com>
Thread-Topic: [spring] Updating the SPRING WG Charter
References: <CAHd-QWt+nmQz_R7kE2oeHa2cD88+ndSkpiv56WSFJfHH3PzxRQ@mail.gmail.com> <26600_1530190305_5B34D9E1_26600_224_1_53C29892C857584299CBF5D05346208A47AB824E@OPEXCLILM21.corporate.adroot.infra.ftgroup> <4A95BA014132FF49AE685FAB4B9F17F66B075BA0@sjceml521-mbs.china.huawei.com> <15307_1530280578_5B363A82_15307_33_1_53C29892C857584299CBF5D05346208A47ABA750@OPEXCLILM21.corporate.adroot.infra.ftgroup> <4A95BA014132FF49AE685FAB4B9F17F66B07637A@sjceml521-mbs.china.huawei.com>
In-Reply-To: <4A95BA014132FF49AE685FAB4B9F17F66B07637A@sjceml521-mbs.china.huawei.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3613115982_841129668"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/y_bxOLJWoil1wVqWY6S3E9RRGgc>
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: Fri, 29 Jun 2018 15:19:50 -0000

Linda,

 

“Legacy Networks” is a derogatory term used by OF bigots to call anything, that’s  distributed ☺

There’s nothing wrong with changing and evolving existing networking to be more programmable and flexible, changes are welcome.

 

I don’t think we should call existing networking – “Legacy”.

 

Cheers,

Jeff

From: spring <spring-bounces@ietf.org> on behalf of Linda Dunbar <linda.dunbar@huawei.com>
Date: Friday, June 29, 2018 at 11:05
To: "bruno.decraene@orange.com" <bruno.decraene@orange.com>
Cc: SPRING WG List <spring@ietf.org>
Subject: Re: [spring] Updating the SPRING WG Charter

 

Bruno, 

 

IMHO, “Interworking between SR and Legacy Networks” is more appropriate than “Interworking between SR and existing routing solutions” because “Interworking SR with existing routing solutions” can imply needing changes to the “existing routing solutions”. 

 

Linda

 

 

From: bruno.decraene@orange.com [mailto:bruno.decraene@orange.com] 
Sent: Friday, June 29, 2018 8:56 AM
To: Linda Dunbar <linda.dunbar@huawei.com>
Cc: SPRING WG List <spring@ietf.org>
Subject: RE: [spring] Updating the SPRING WG Charter

 

Linda,

 

Thanks for the feedback.

Please see inline [Bruno]

 

From: Linda Dunbar [mailto:linda.dunbar@huawei.com] 
Sent: Thursday, June 28, 2018 6:18 PM
To: DECRAENE Bruno IMT/OLN; SPRING WG List
Subject: RE: [spring] Updating the SPRING WG Charter

 

Bruno, 

 

Many thanks for the updated charter. All look good except one minor wording change for the bullet:

 

You have:

o Inter-working between SRv6 and SR-MPLS  and between SR and existing routing solutions to allow for seamless deployment and co-existence.. 

 

We think it should be:

o Inter-working between SRv6 and SR-MPLS/LegacyNetwork  and between SR and existing routing solutions to allow for seamless deployment and co-existence.. 

 

Because it is very likely that flows might traverse some segment of legacy network (like IPv4) before reaching SRv6 domain. After all, it is not like to expect all network to be IPv6 from Day 1. 

 

[Bruno] I though this point would be covered by Inter-working […] between SR and existing routing solutions to allow for seamless deployment and co-existence

Am I missing something? Or would you have something specific in mind?

 

--Bruno

 

Sincerely hope you can add those minor wording to the bullet. 

 

Linda Dunbar

 

 

From: spring [mailto:spring-bounces@ietf.org] On Behalf Of bruno.decraene@orange.com
Sent: Thursday, June 28, 2018 7:52 AM
To: SPRING WG List <spring@ietf.org>
Subject: Re: [spring] Updating the SPRING WG Charter

 

Hi SPRING,

 

Following the discussion on the mailing list, please find below the updated text.

The plan is to send it to Martin end of this week.

 

The Source Packet Routing in NetworkinG (SPRING) Working Group is the home of Segment Routing (SR) using MPLS (SR-MPLS) and IPv6 (SRv6). SPRING WG serves as a forum to discuss SPRING networks operations, define new applications, and specify extensions of Segment Routing technologies.

 

The SPRING WG defines procedures that allow a node to steer a packet through an SR Policy instantiated as an ordered list of instructions called segments and without the need for per-path state information to be held at transit nodes. Full explicit control (through loose or strict path specification) can be achieved in a network comprising only SPRING nodes, however SPRING nodes must inter-operate through loose routing in existing networks and may find it advantageous to use loose routing for other network applications.

 

The scope of the SPRING WG work includes both single Autonomous System (AS) and multi-AS environments. Segment Routing operates within a trusted domain; as described in the architecture, a node imposing a segment list is assumed to be allowed to do so. Nonetheless, the SPRING WG must strive to identify and address security considerations brought up by the technologies it defines.

The technologies SPRING WG defines may be applicable to both centralised and distributed path computation.  

 

SPRING WG should avoid modification to existing data planes that would make them incompatible with existing deployments. Where possible, existing control and management plane protocols must be used within existing architectures to implement the SPRING function. Any modification of -or extension to- existing architectures, data planes, or control or management plane protocols should be carried out in the WGs responsible for the architecture, data plane, or control or management plane protocol being modified and in 

coordination with the SPRING WG, but may be done in SPRING WG after agreement with all the relevant WG chairs and responsible Area Directors.

 

 

The SPRING WG will manage its specific work items by milestones agreed with the responsible Area Director.

 

The work-items of the SPRING WG include functional specifications for:

o Segment Routing policies and the associated steering, signalling and traffic engineering mechanisms.

 

o Source-routed stateless service chaining using SR-MPLS and SRv6 dataplanes.

 

o SRv6 network programming for the underlay networks and overlay services, and including data plane behavior and functions associated with SIDs

 

o Operation, Administration and Management (OAM), and traffic accounting in networks with SR-MPLS and SRv6 data planes in the case where SR introduces specificities compared to MPLS or IPv6 technologies.

 

o Performance Management (PM) and monitoring in networks with SR-MPLS and SRv6 data planes in the case where SR introduces specificities compared to MPLS or IPv6 technologies.

 

o Inter-working between SRv6 and SR-MPLS  and between SR and existing routing solutions to allow for seamless deployment and co-existence.. 

 

o new types of segments mapping to forwarding behavior  (e.g. local ingress replication, local forwarding resources, a pre-existing replication structure) if needed for new usages.

 

Any of the above may require architectural extensions.

 

The work-items of SPRING WG also include:

o Specification of management models (YANG) for Segment Routing applications, services and networks with SR-MPLS and SRv6 dataplanes.

 

The SPRING WG will coordinate and collaborate with other WGs as needed. Specific

expected interactions include (but may not be limited to):

    * mpls on the MPLS dataplane and OAM extensions,

    * 6man on the IPv6 dataplane for SR and associated OAM extensions

    * lsr on OSPF and IS-IS extensions to flood SPRING-related information

    * IDR for BGP extensions

    * bess for VPN control plane

    * pce on extensions to communicate with an external entity to compute and program SPRING paths

    * teas on generic traffic engineering architecture

    * sfc on service chaining applications

    * rtgwg on fast-reroute technologies

 

 

 

Thanks,

Rob, Bruno

 

From: spring [mailto:spring-bounces@ietf.org] On Behalf Of Rob Shakir
Sent: Friday, June 01, 2018 6:06 PM
To: SPRING WG List
Subject: [spring] Updating the SPRING WG Charter

 

Hi SPRING,

 

After the discussions on the list and in London relating to the charter, Bruno and I have been working to propose a new charter for the WG with Martin, and the other routing ADs. The text for this suggested charter is below. We would like to solicit WG feedback on the charter text prior to Martin taking to the IESG. We'd like to try and get the charter agreed prior to IETF 102 in Montréal.

 

The Source Packet Routing in NetworkinG (SPRING) Working Group is the home of

Segment Routing (SR) using MPLS (SR-MPLS) and IPv6 (SRv6). SPRING WG serves as

a forum to discuss SPRING networks operations, define new applications, and

specify extensions of Segment Routing technologies.

 

The SPRING WG defines procedures that allow a node to steer a packet through an

SR Policy instantiated as an ordered list of instructions called segments and

without the need for per-path state information to be held at transit nodes.

Full explicit control (through loose or strict path specification) can be

achieved in a network comprising only SPRING nodes, however SPRING nodes must

inter-operate through loose routing in existing networks and may find it

advantageous to use loose routing for other network applications.

 

The scope of the SPRING WG work includes both single Autonomous System (AS) and

multi-AS environments. Segment Routing operates within a trusted domain; as

described in the architecture, a node imposing a segment list is assumed to be

allowed to do so. Nonetheless, the SPRING WG must strive to identify and

address security considerations brought up by the technologies it defines.  The

technologies SPRING WG defines may be applicable to both centralised and

distributed path computation.

 

SPRING WG should avoid modification to existing data planes that would make

them incompatible with existing deployments. Where possible, existing control

and management plane protocols must be used within existing architectures to

implement the SPRING function. Any modification of - or extension to - existing

architectures, data planes, or control or management plane protocols should be

carried out in the WGs responsible for the architecture, data plane, or control

or management plane protocol being modified and in coordination with the SPRING

WG, but may be done in SPRING WG after agreement with all the relevant WG

chairs and responsible Area Directors.

 

 

The SPRING WG will manage its specific work items by milestones agreed with the

responsible Area Director.

 

The work-items of the SPRING WG include functional specifications for:

 

o Segment Routing policies and the associated steering and traffic engineering

  mechanisms.

 

o Source-routed stateless service chaining using SR-MPLS and SRv6 dataplanes.

 

o SRv6 network programming for the underlay networks and overlay services, and

  including data plane behavior and functions associated with SIDs

 

o Operation, Administration and Management (OAM), and traffic accounting in

  networks with SR-MPLS and SRv6 data planes in the case where SR introduces

  specificities compared to MPLS or IPv6 technologies.

 

o Performance Management (PM) and monitoring in networks with SR-MPLS and SRv6

  data planes in the case where SR introduces specificities compared to MPLS or

  IPv6 technologies.

 

o The inter-working between SRv6 and SR-MPLS.

 

o Using SR as the mechanism to identify sets of resources in networks with

  SR-MPLS and SRv6 dataplanes.

 

Any of the above may require architectural extensions.

 

The work-items of SPRING WG also include:

 

o Specification of management models (YANG) for Segment Routing applications,

  services and networks with SR-MPLS and SRv6 dataplanes.

 

The SPRING WG will coordinate and collaborate with other WGs as needed. Specific

expected interactions include (but may not be limited to):

 

    * mpls on the MPLS dataplane and OAM extensions,

    * 6man on the IPv6 dataplane for SR and associated OAM extensions

    * lsr on OSPF and IS-IS extensions to flood SPRING-related information

        * idr for BGP extensions

    * bess for VPN control plane

    * pce on extensions to communicate with an external entity to compute and program SPRING paths

    * teas on generic traffic engineering architecture

 

Please comment on the contents of the charter text on the list.

 

Thanks,

Bruno & Rob
_________________________________________________________________________________________________________________________
 
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
 
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_________________________________________________________________________________________________________________________
 
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
 
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
_______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring