[spring] Final? design team charge

Joel Halpern <jmh@joelhalpern.com> Tue, 07 July 2020 16:24 UTC

Return-Path: <jmh@joelhalpern.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 D65353A101E for <spring@ietfa.amsl.com>; Tue, 7 Jul 2020 09:24:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 teOhMDrYhqFV for <spring@ietfa.amsl.com>; Tue, 7 Jul 2020 09:24:07 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 721F83A1008 for <spring@ietf.org>; Tue, 7 Jul 2020 09:24:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4B1SS72Wmjz6GDCM for <spring@ietf.org>; Tue, 7 Jul 2020 09:24:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1594139047; bh=PgdA4RPZXck7HIV48Dq3/ZU3VHWmtOScJp9niajDS48=; h=From:Subject:To:Date:From; b=Y2vuwEvZ80ilU7PUunvGcSxW4QLnJ4JKMEVikM64GkU4enniTMmfcIGXW7XhEDc2D VNXKuf5+WV+K/byij10BryRmw62dXpH1fhfhMj0rc1bFt8yQBfGTJzRYer19CAYu3c RfusjI9gaTWO6t1wvxKFpuEDT6ZB9n+mPFdP4WtY=
X-Quarantine-ID: <ovBMnrTX7pxS>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4B1SS66mwZz6GCnp for <spring@ietf.org>; Tue, 7 Jul 2020 09:24:06 -0700 (PDT)
From: Joel Halpern <jmh@joelhalpern.com>
To: "spring@ietf.org" <spring@ietf.org>
Message-ID: <fec37485-0db3-658c-58a6-7ea2294f9def@joelhalpern.com>
Date: Tue, 07 Jul 2020 12:24:06 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/IopJDUcGLo7vU6uZxhQjWQg9Qrs>
Subject: [spring] Final? design team charge
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Jul 2020 16:24:09 -0000

Having gotten various volunteers, and considered what the WG needs, the 
SPRING chairs have selected the design team for clarifying the SR over 
IPv6 compression situation.

The Design team will be
Co-Chaired by:
     Cheng Weiqiang of China Mobile and
     Sanders Steffann of SJM Steffann Consultancy

The other members of the team are:
     Ron Bonica of Juniper
     Darren Dukes of Cisco
     Cheng Li of Huawei
     Peng Shaofu of ZTE
     Wim Henderickx of Nokia
     Chongfeng Xie of China Telecom

(We understand that some members may be on vacation.  We ask the chairs 
to please get the design team up and running as fast as possible, and 
deal with vacations as necessary.)

The design team is to produce (rough) consensus (of the DT) outputs to 
the WG on two related topics:
1) What are the requirements for solutions to compressing segment 
routing information for use over IPv6;
2) A comparison of proposed approaches to compressing segment routing 
information for use over IPv6.

In both cases, assertions / requirements should be explicitly explained 
and motivated.  Please do not assume that everyone has the same 
perspective or assumptions.

We expect these results to take the form of Internet Drafts.  How the 
design team does the development is up to them.  Note that while we are 
asking for I-Ds, we are not assuming that these results will be 
published as RFCs.  When the working group has progressed, we will see 
if there is agreement as to the value of long term publication of this 
material.
Also, as a reminder to both the design team and the working group, the 
design team output is input to the working group.  It is not presumed to 
be a WG document until the WG actually adopts it.

If the design team has insights into the number of solutions (are 
several already standardized?  is there value in picking one / some?) 
this may be included in the requirements readout.  If the design team 
can not agree, or does not think it is helpful to report this aspect, 
that is also acceptable to the chairs.

While the chairs would like to see prompt work, we also want to see a 
thorough job done on this task.  As such, we value quality of result 
over time.  While there is some pressure, we ask that the design team 
focus on reaching clear and useful agreements.  Thus, we are not asking 
for any readout by IETF 108.  As a target, we would like to see a draft 
to the WG by September 15, 2020.

If the design team makes enough progress that they have questions they 
would like the WG to discuss at IETF 108, please let us know.

Yours,
Bruno, Jim, and Joel