Re: [spring] Updating the SPRING WG Charter
<Ruediger.Geib@telekom.de> Fri, 29 June 2018 06:11 UTC
Return-Path: <Ruediger.Geib@telekom.de>
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 55755130E65 for <spring@ietfa.amsl.com>; Thu, 28 Jun 2018 23:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.309
X-Spam-Level:
X-Spam-Status: No, score=-4.309 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_MED=-2.3, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=telekom.de header.b=XClpA8LP; dkim=pass (1024-bit key) header.d=telekom.onmicrosoft.de header.b=D8KOn12r
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 zPmnipiliSCd for <spring@ietfa.amsl.com>; Thu, 28 Jun 2018 23:11:14 -0700 (PDT)
Received: from mailout34.telekom.de (MAILOUT34.telekom.de [194.25.225.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39A26130DC4 for <spring@ietf.org>; Thu, 28 Jun 2018 23:11:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1530252673; x=1561788673; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=KdOiuC4nmbILu8xayFAEPUwVhx0fb+oifArfa4ehGzU=; b=XClpA8LPaYylK2z+bNEIZzvYoblSDlT6PVWkpwUQBoujX6s9qCxZuJmW AExiTjqwCJ9p7PMtj84R5o1k5rx6htFv20WcEQpfpo65C6vKMDxkqkWDJ Sy5tC4ayUxmiXg7vOLyhe1aqXTPIp1GYVf/PD9ChUFPOMPvXu8jr1bBfO 7ScavdcAlEzGynSxSedfuI8q4g4lY+GuMJCgCvMldtuDFOsb+LLLRtg33 GTZeV7UQtrMv3M5J5T2VwaDQ+ZsFAuXn5d0Q/NE42anfGNlZGDxuoUaa5 tF9bTF3g3Kpvx0oAoAQ3/EnXU3qVV2cP4bs3t3nrJm2wsSHUMyeHDpJlS w==;
Received: from qdec94.de.t-internal.com ([10.171.255.41]) by MAILOUT31.dmznet.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jun 2018 08:02:08 +0200
X-IronPort-AV: E=Sophos;i="5.48,405,1517871600"; d="scan'208,217";a="202395492"
Received: from he105824.emea1.cds.t-internal.com ([10.169.118.46]) by QDEC97.de.t-internal.com with ESMTP/TLS/AES256-SHA; 29 Jun 2018 08:02:08 +0200
Received: from HE105761.EMEA1.cds.t-internal.com (10.169.118.57) by HE105824.emea1.cds.t-internal.com (10.169.118.46) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Fri, 29 Jun 2018 08:02:08 +0200
Received: from HE106564.emea1.cds.t-internal.com (10.171.40.16) by HE105761.EMEA1.cds.t-internal.com (10.169.118.57) with Microsoft SMTP Server (TLS) id 15.0.1367.3 via Frontend Transport; Fri, 29 Jun 2018 08:02:08 +0200
Received: from GER01-LEJ-obe.outbound.protection.outlook.de (51.5.80.23) by O365mail01.telekom.de (172.30.0.234) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Fri, 29 Jun 2018 08:01:27 +0200
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.onmicrosoft.de; s=selector1-telekom-onmicrosoft-de; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=KdOiuC4nmbILu8xayFAEPUwVhx0fb+oifArfa4ehGzU=; b=D8KOn12rXPC/sT9trqHaRUWC4+pZjZYDr1l40Rrd3ZDsadjdqegPCmZuA4Ng7kVr86yPlkZ7/Qfu9J5LEZw25g1wgQI0H9Upmz8jfS3kwO5Rx53pQOsMBIRrAyH41URYiRY6sNRHR2KtYWUCd3QzAWpLcGnw9G/Hs4razz+nEpM=
Received: from FRAPR01MB0113.DEUPRD01.PROD.OUTLOOK.DE (10.158.130.143) by FRAPR01MB0114.DEUPRD01.PROD.OUTLOOK.DE (10.158.130.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.906.20; Fri, 29 Jun 2018 06:02:07 +0000
Received: from FRAPR01MB0113.DEUPRD01.PROD.OUTLOOK.DE ([fe80::7870:2709:87ee:7789]) by FRAPR01MB0113.DEUPRD01.PROD.OUTLOOK.DE ([fe80::7870:2709:87ee:7789%2]) with mapi id 15.20.0906.025; Fri, 29 Jun 2018 06:02:07 +0000
From: Ruediger.Geib@telekom.de
To: bruno.decraene@orange.com
CC: spring@ietf.org
Thread-Topic: [spring] Updating the SPRING WG Charter
Thread-Index: AQHUDt7Db2WE4BtuQ0iRzbs6VN00gqR2v4hg
Date: Fri, 29 Jun 2018 06:02:07 +0000
Message-ID: <FRAPR01MB0113556559F7315B96BC832E9C4E0@FRAPR01MB0113.DEUPRD01.PROD.OUTLOOK.DE>
References: <CAHd-QWt+nmQz_R7kE2oeHa2cD88+ndSkpiv56WSFJfHH3PzxRQ@mail.gmail.com> <26600_1530190305_5B34D9E1_26600_224_1_53C29892C857584299CBF5D05346208A47AB824E@OPEXCLILM21.corporate.adroot.infra.ftgroup>
In-Reply-To: <26600_1530190305_5B34D9E1_26600_224_1_53C29892C857584299CBF5D05346208A47AB824E@OPEXCLILM21.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Ruediger.Geib@telekom.de;
x-originating-ip: [164.19.3.224]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; FRAPR01MB0114; 7:iUur9eYqp3MaPJOGLNarz598ZIFdnQAZjei3ekxs+QBa/aZnVa2kTS96cSh/dCi4rZBnda+nbeb4DsUXwObRWDTMPRIK0H09UgnuSPcq3t4oUHY1hsZayluadlrrGCcrGmmGd9s2Uk32i5/w8wLctBtyefECnh6liKucorTQLu7UFBP0M5PN6na1q4BKIXsDlvVBovdxl+5CtXBFMfOSTL09ZKRfCBhawJcmqBCXuovs02q59CubbnYYB8tmn8gM
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: bbdda3b1-b98a-4312-1640-08d5dd85d864
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600026)(711020)(2017052603328)(7153060)(7193020); SRVR:FRAPR01MB0114;
x-ms-traffictypediagnostic: FRAPR01MB0114:
x-microsoft-antispam-prvs: <FRAPR01MB01144E6CB9B951E446D7AD169C4E0@FRAPR01MB0114.DEUPRD01.PROD.OUTLOOK.DE>
x-exchange-antispam-report-test: UriScan:(28532068793085)(278428928389397)(72170088055959)(192374486261705)(18271650672692)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3231254)(944501410)(52105095)(93006095)(93001095)(10201501046)(3002001)(149027)(150027)(6041310)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123558120)(20161123562045)(6072148)(201708071742011)(7699016); SRVR:FRAPR01MB0114; BCL:0; PCL:0; RULEID:; SRVR:FRAPR01MB0114;
x-forefront-prvs: 0718908305
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(346002)(366004)(39860400002)(376002)(396003)(199004)(189003)(11346002)(446003)(186003)(5250100002)(790700001)(476003)(2501003)(53546011)(6916009)(486006)(26005)(14454004)(72206003)(53946003)(53936002)(4326008)(97736004)(5640700003)(3846002)(5660300001)(478600001)(55016002)(54896002)(6306002)(236005)(9686003)(102836004)(81156014)(8936002)(76176011)(8676002)(81166006)(7696005)(7736002)(52396003)(2906002)(6116002)(85182001)(5630700001)(66066001)(316002)(75402003)(106356001)(86362001)(256004)(14444005)(5024004)(74482002)(33656002)(105586002)(85202003)(2351001)(68736007)(2900100001)(777600001)(19627235001); DIR:OUT; SFP:1101; SCL:1; SRVR:FRAPR01MB0114; H:FRAPR01MB0113.DEUPRD01.PROD.OUTLOOK.DE; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: telekom.de does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 3968le6InSOAlnS4g3vq9Icn0T2eNYf2GAYl4euwYsDc0p0tzz7OGvLzoZHQZxrf9wcp+uuQKyXeoyP0IIkQyRju/AP3740aQoJ5As3pfYvYRSArsJyoCntBVZTqYt9fFsNarM6tjTaigB0ETycvHOdE+IjPawOLFpQm+Xy5xnxxF0Sc7AcGJoETfxt/XQ5Pb7TOAMvtrZUOUTgSJNqs1gbHE5rcImu4tKmJ+vcAWeLa3nWGSCr8/a3GyD2qaMtXioqDu0UnjFtZt5XjVBXbDdjMaQAifvV02raBbuB/XAuNDGZ5j8pd8qBl6+MsJRUFMoCf5vZbVolN32/cVROKQQqmyx2ES/wAF435t+gZUBo=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_FRAPR01MB0113556559F7315B96BC832E9C4E0FRAPR01MB0113DEUP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: bbdda3b1-b98a-4312-1640-08d5dd85d864
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jun 2018 06:02:07.3269 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: FRAPR01MB0114
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/ZE7u41O6_uVHl0ifY2fC5NI1Fhk>
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 06:11:19 -0000
Hi Bruno, thanks, looks good to me. Regards, Ruediger Von: spring [mailto:spring-bounces@ietf.org] Im Auftrag von bruno.decraene@orange.com Gesendet: Donnerstag, 28. Juni 2018 14:52 An: SPRING WG List <spring@ietf.org> Betreff: 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.
- [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