Re: [spring] Updating the SPRING WG Charter
"Zafar Ali (zali)" <zali@cisco.com> Tue, 12 June 2018 13:45 UTC
Return-Path: <zali@cisco.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 584C9130F0E for <spring@ietfa.amsl.com>; Tue, 12 Jun 2018 06:45:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.509
X-Spam-Level:
X-Spam-Status: No, score=-14.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 qrDFkIhPbmGR for <spring@ietfa.amsl.com>; Tue, 12 Jun 2018 06:45:20 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21152130E27 for <spring@ietf.org>; Tue, 12 Jun 2018 06:45:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=44364; q=dns/txt; s=iport; t=1528811120; x=1530020720; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=RQ/79q4yeNvnNl27aoeoicofGG4UuehTj9BgxpFVO8c=; b=T9eKo9m6eUhCfNpYxK3wNZMoPaM+VLPkykTXU+IXHoNh/dGO9zuBha2r aEgIk5IKXjENVOgj3CMVreKv3QnpwlemECvlnEpXW/Tnmp9Sd4yTz2olM N2D440DF0GQiQuvSAf4z6Lidk5ZM6CACE/EvEWY1HeYxeMkDGc4VT7DcD A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DSAADqzR9b/4oNJK1SChkBAQEBAQEBAQEBAQEHAQEBAQGCTkcuYn8oCoNtiASMaIF/lFsUgWQLhGwCF4IaITQYAQIBAQEBAQECbSiFKAEBAQQjRBIQAgEIEQECAQIhAQkCAgIwFwYIAgQBDQWDIgKBG2SqVoIchFqDa4FoiEiBVD+BDgEkgmiDEQSBJg0EBEMGgloxgiQChy2BDIhdIIdQCQKOd4E/g36HdZERAhETAYEkHTiBUnAVOyoBghgJgh0SjhdvAY1hgS6BGgEB
X-IronPort-AV: E=Sophos;i="5.51,214,1526342400"; d="scan'208,217";a="409285099"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Jun 2018 13:45:18 +0000
Received: from XCH-RTP-019.cisco.com (xch-rtp-019.cisco.com [64.101.220.159]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id w5CDjItl020943 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 12 Jun 2018 13:45:18 GMT
Received: from xch-rtp-018.cisco.com (64.101.220.158) by XCH-RTP-019.cisco.com (64.101.220.159) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 12 Jun 2018 09:45:17 -0400
Received: from xch-rtp-018.cisco.com ([64.101.220.158]) by XCH-RTP-018.cisco.com ([64.101.220.158]) with mapi id 15.00.1320.000; Tue, 12 Jun 2018 09:45:17 -0400
From: "Zafar Ali (zali)" <zali@cisco.com>
To: Rob Shakir <robjs=40google.com@dmarc.ietf.org>, SPRING WG List <spring@ietf.org>
CC: "Zafar Ali (zali)" <zali@cisco.com>
Thread-Topic: [spring] Updating the SPRING WG Charter
Thread-Index: AQHT+cKki+AMif91OkKrakOGxBk/KqRcs6yA
Date: Tue, 12 Jun 2018 13:45:17 +0000
Message-ID: <9309CB81-A1E6-48E0-B6E0-D5F72966DC39@cisco.com>
References: <CAHd-QWt+nmQz_R7kE2oeHa2cD88+ndSkpiv56WSFJfHH3PzxRQ@mail.gmail.com>
In-Reply-To: <CAHd-QWt+nmQz_R7kE2oeHa2cD88+ndSkpiv56WSFJfHH3PzxRQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.9.0.180116
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.216.193]
Content-Type: multipart/alternative; boundary="_000_9309CB81A1E648E0B6E0D5F72966DC39ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/j8Ml-2RtJgIrzQXuDBV5Nb9GiZg>
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 13:45:26 -0000
Dear Rob, Bruno, I have a question on the specifics of the following milestone: * Using SR as the mechanism to identify sets of resources in networks with SR-MPLS and SRv6 dataplanes. I do not know of any specific use-case, requirement or an individual draft associated with this milestone beyond what is already covered by other milestones (e.g., by “Segment Routing policies and the associated steering and traffic engineering mechanisms”). What specific deliverable you have in mind? Is there an individual(s) draft against this milestone? Please advise. Thanks Regards … Zafar From: spring <spring-bounces@ietf.org> on behalf of Rob Shakir <robjs=40google.com@dmarc.ietf.org> Date: Friday, June 1, 2018 at 12:07 PM To: SPRING WG List <spring@ietf.org> 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
- [spring] 答复: Updating the SPRING WG Charter Dongjie (Jimmy)
- Re: [spring] Updating the SPRING WG Charter Stewart Bryant
- Re: [spring] Updating the SPRING WG Charter Stewart Bryant
- Re: [spring] Updating the SPRING WG Charter David Allan I
- Re: [spring] Updating the SPRING WG Charter Stewart Bryant
- Re: [spring] Updating the SPRING WG Charter Robert Raszuk
- Re: [spring] Updating the SPRING WG Charter Stewart Bryant
- Re: [spring] Updating the SPRING WG Charter Alexander Vainshtein
- Re: [spring] Updating the SPRING WG Charter bruno.decraene
- Re: [spring] Updating the SPRING WG Charter Alexander Vainshtein
- Re: [spring] Updating the SPRING WG Charter Ruediger.Geib
- Re: [spring] Updating the SPRING WG Charter Stewart Bryant
- Re: [spring] 答复: Updating the SPRING WG Charter Zafar Ali (zali)
- Re: [spring] Updating the SPRING WG Charter Voyer, Daniel
- Re: [spring] Updating the SPRING WG Charter bruno.decraene
- Re: [spring] 答复: Updating the SPRING WG Charter Rob Shakir
- Re: [spring] 答复: Updating the SPRING WG Charter Zafar Ali (zali)
- Re: [spring] Updating the SPRING WG Charter Loa Andersson
- [spring] 答复: Updating the SPRING WG Charter Dongjie (Jimmy)
- Re: [spring] Updating the SPRING WG Charter Zafar Ali (zali)
- Re: [spring] Updating the SPRING WG Charter Dongjie (Jimmy)
- Re: [spring] Updating the SPRING WG Charter Zafar Ali (zali)
- Re: [spring] Updating the SPRING WG Charter Ruediger.Geib
- Re: [spring] Updating the SPRING WG Charter Dongjie (Jimmy)
- Re: [spring] Updating the SPRING WG Charter Jeff Tantsura
- Re: [spring] Updating the SPRING WG Charter bruno.decraene
- Re: [spring] Updating the SPRING WG Charter Alexander Vainshtein
- Re: [spring] Updating the SPRING WG Charter Zafar Ali (zali)
- Re: [spring] Updating the SPRING WG Charter Zafar Ali (zali)
- Re: [spring] Updating the SPRING WG Charter Zafar Ali (zali)
- Re: [spring] Updating the SPRING WG Charter Voyer, Daniel
- Re: [spring] Updating the SPRING WG Charter Robert Raszuk
- Re: [spring] Updating the SPRING WG Charter Alexander Vainshtein
- Re: [spring] Updating the SPRING WG Charter Rob Shakir
- Re: [spring] Updating the SPRING WG Charter David Allan I
- Re: [spring] Updating the SPRING WG Charter Rob Shakir
- Re: [spring] Updating the SPRING WG Charter Robert Raszuk
- Re: [spring] Updating the SPRING WG Charter Eric C Rosen
- Re: [spring] Updating the SPRING WG Charter Alexander Vainshtein
- Re: [spring] Updating the SPRING WG Charter Robert Raszuk
- Re: [spring] Updating the SPRING WG Charter Alexander Vainshtein
- Re: [spring] Updating the SPRING WG Charter Robert Raszuk
- Re: [spring] Updating the SPRING WG Charter Voyer, Daniel
- Re: [spring] Updating the SPRING WG Charter Alexander Vainshtein
- Re: [spring] Updating the SPRING WG Charter Robert Raszuk
- Re: [spring] Updating the SPRING WG Charter Paul Mattes
- Re: [spring] Updating the SPRING WG Charter Alexander Vainshtein
- Re: [spring] Updating the SPRING WG Charter Robert Raszuk
- Re: [spring] Updating the SPRING WG Charter Alexander Vainshtein
- Re: [spring] Updating the SPRING WG Charter Robert Raszuk
- Re: [spring] Updating the SPRING WG Charter Bernier, Daniel
- Re: [spring] Updating the SPRING WG Charter Alexander Vainshtein
- Re: [spring] Updating the SPRING WG Charter bruno.decraene
- Re: [spring] Updating the SPRING WG Charter Linda Dunbar
- Re: [spring] Updating the SPRING WG Charter Ruediger.Geib
- Re: [spring] Updating the SPRING WG Charter Dongjie (Jimmy)
- Re: [spring] Updating the SPRING WG Charter bruno.decraene
- Re: [spring] Updating the SPRING WG Charter Linda Dunbar
- Re: [spring] Updating the SPRING WG Charter Jeff Tantsura
- Re: [spring] Updating the SPRING WG Charter Linda Dunbar
- Re: [spring] Updating the SPRING WG Charter bruno.decraene
- Re: [spring] Updating the SPRING WG Charter Jeff Tantsura
- Re: [spring] Updating the SPRING WG Charter bruno.decraene
- [spring] Updating the SPRING WG Charter Rob Shakir
- Re: [spring] Updating the SPRING WG Charter Jeff Tantsura
- Re: [spring] Updating the SPRING WG Charter Linda Dunbar
- Re: [spring] Updating the SPRING WG Charter James N Guichard
- Re: [spring] Updating the SPRING WG Charter Rob Shakir
- Re: [spring] Updating the SPRING WG Charter Rob Shakir
- Re: [spring] Updating the SPRING WG Charter Xiejingrong
- Re: [spring] Updating the SPRING WG Charter Rob Shakir
- Re: [spring] Updating the SPRING WG Charter Michael McBride
- Re: [spring] Updating the SPRING WG Charter Rob Shakir