Re: [spring] FW: New Version Notification for draft-srcompdt-spring-compression-requirement-00.txt

Andrew Alston <Andrew.Alston@liquidtelecom.com> Thu, 12 November 2020 21:02 UTC

Return-Path: <andrew.alston@liquidtelecom.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 B77113A0880 for <spring@ietfa.amsl.com>; Thu, 12 Nov 2020 13:02:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 JH4238MAGQ-3 for <spring@ietfa.amsl.com>; Thu, 12 Nov 2020 13:02:05 -0800 (PST)
Received: from eu-smtp-delivery-182.mimecast.com (eu-smtp-delivery-182.mimecast.com [185.58.86.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A3C33A0879 for <spring@ietf.org>; Thu, 12 Nov 2020 13:02:04 -0800 (PST)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-db5eur03lp2056.outbound.protection.outlook.com [104.47.10.56]) (Using TLS) by relay.mimecast.com with ESMTP id uk-mta-137-UeXSqTPJMCC9OSPpDoVsNw-1; Thu, 12 Nov 2020 21:01:57 +0000
X-MC-Unique: UeXSqTPJMCC9OSPpDoVsNw-1
Received: from VI1PR03MB5056.eurprd03.prod.outlook.com (2603:10a6:803:bf::31) by VI1PR03MB4143.eurprd03.prod.outlook.com (2603:10a6:803:73::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3541.24; Thu, 12 Nov 2020 21:01:55 +0000
Received: from VI1PR03MB5056.eurprd03.prod.outlook.com ([fe80::fd6d:5942:84f5:3812]) by VI1PR03MB5056.eurprd03.prod.outlook.com ([fe80::fd6d:5942:84f5:3812%3]) with mapi id 15.20.3541.025; Thu, 12 Nov 2020 21:01:54 +0000
From: Andrew Alston <Andrew.Alston@liquidtelecom.com>
To: Weiqiang Cheng <chengweiqiang@chinamobile.com>, "spring@ietf.org" <spring@ietf.org>
CC: 'srcomp' <srcomp@ietf.org>, "spring-chairs@ietf.org" <spring-chairs@ietf.org>
Thread-Topic: [spring] FW: New Version Notification for draft-srcompdt-spring-compression-requirement-00.txt
Thread-Index: Adaw8qWMM8NXBKsVRSCF3jBwduJ55QH3lL/wABjpqnk=
Date: Thu, 12 Nov 2020 21:01:54 +0000
Message-ID: <VI1PR03MB5056546242C4F37B521403BAEEE70@VI1PR03MB5056.eurprd03.prod.outlook.com>
References: <08c001d6b8d3$010d08d0$03271a70$@com>
In-Reply-To: <08c001d6b8d3$010d08d0$03271a70$@com>
Accept-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [152.108.254.20]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 481b3a79-0e9e-477b-b36c-08d8874e2fa6
x-ms-traffictypediagnostic: VI1PR03MB4143:
x-microsoft-antispam-prvs: <VI1PR03MB41438F6907669746D07D8186EEE70@VI1PR03MB4143.eurprd03.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0
x-microsoft-antispam-message-info: fBgDxWs0UZ/squO7lHO0G+YSNqMNdlWAzrxEyR2/Pe4qmGW6YR3lgtlTkeSGnIVmsEr3zxAFrfQEIMJfOw0KFxfVFU5m+BgAa6zvbYzKUGNEOb/kjcbXWDJ9cBApQ/Hded+N83MAOoSHYgFMDVxEVgd2TZC12DAj+kISTAGcdJgAOeNWZcw1LD6ydR+PoaTE/bwW9kvXlSh1kIQvbdMpAWE6G+NYy4QHNiicqWqYVjObyHM/pjKWII2WSAEUdjZUlALIx0kQcGq7TuMy8ewxssVUidtm7UFk7aWCb5Y4ucxtcHnaI5Nyv1s4/xYdb4H7j+wDI0klSk2788sJ9oyYS8qjNiV3NYRwhkPPvo14cLZsC77T80kfymGDmrmDP+Tf1zLywzOWFwIPnC6/vV7X5A==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:VI1PR03MB5056.eurprd03.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(396003)(366004)(39860400002)(346002)(376002)(136003)(8676002)(66574015)(4001150100001)(53546011)(54906003)(6506007)(55016002)(110136005)(2906002)(15650500001)(8936002)(33656002)(9686003)(83380400001)(5660300002)(52536014)(186003)(86362001)(91956017)(316002)(166002)(4326008)(64756008)(71200400001)(66946007)(966005)(478600001)(26005)(7696005)(66446008)(66476007)(66556008)(76116006); DIR:OUT; SFP:1102
x-ms-exchange-antispam-messagedata: vQaQqQj2o5GPbJrz7XVVOlb8Wyuj3dr9RILlAhGb9FRYluqiKzvPnajhSRmV5WpGJIHrIwptFiYfP6iIZoN0GfKPms+H2JPrmJpZ5q7VwJkObKhHcuq0MUlmmOsiW4VzQup9KVOrqVKfG66UO9RhMyjNiyaEUv9C0b7X5UE6c9M8ugpUXvRZ1glQnrUtvZcrcsbgKcBb5G4QM+Oc3GwMnzX4MLnAItXjMQ/SKqmD8YUnSfB0L/cvOYjJEPf82fQGSB//4JeArOEWeedEYvzE/uTKLgK/Nl/WC+siooTtrRI3aPbJuEx/YOWz+JARHR9Va0/iiDVKn18V+MCabVwHwpzQsWBOi5LZpx2omb17luYDRaF2f90KOxlQSh19KReg2kn6+ue9aQhVo3/3dSGu/qoziGmRPwt7wxbVIxV5iCpeS7xoZszDK86WBUkWd9Iy1pb4YHAfdKTPs26Q9F/cZXJFszrsXJUrtqem10qxJs8++HrGOdTkbAqDwCPFTeQjxDqKoXcZ7CWXTR1nYxw5XUSvqbf9wDpvwnePeSHTXhFFnJzczJ1FzzqUkX8KKBOd0ShAVgN4oS46CI43iTvQZWVm58UWxO+7F/u0KycBxiZHhYr+Zbh+a5lOVOesJt5QPz0cRLkIUj7kbyGiX8JD+sQh81iOhdqHuXX9gmAq4vI1LXp3lAE0vhVvQMpoe1IQ+GEsvJoO9q8lyXigdXoSWaxkomTceGsC0Tms8iz8697LogAgQb6dXsoVa6Vilap/D6jgWBrB+3HmCe3TqFlk2D1nbGCJnawoz2DYde6mhmpG6HM5qyWApu0pL5kMUSI0Rijq6SdLgGoelbl3a8rhnnStUuZZOIRgF0ocqoOfV7THJJL5Vy4s2VQz7kGsIPisbDzWZB9tHSTRIoAWoP4SlA==
x-ms-exchange-transport-forked: True
MIME-Version: 1.0
X-OriginatorOrg: liquidtelecom.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: VI1PR03MB5056.eurprd03.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 481b3a79-0e9e-477b-b36c-08d8874e2fa6
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Nov 2020 21:01:54.7179 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 68792612-0f0e-46cb-b16a-fcb82fd80cb1
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ZxPfypfs4pohLppmPkQkOI4drsN0a0x0e3pRlGtYyiiYtGJ7dG1pIYDFfyQGXz32X4N4dEta6+Jlzdq05OC7CrQ9qibD22mJwqqoRPAwDZM=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR03MB4143
Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=C82A168 smtp.mailfrom=andrew.alston@liquidtelecom.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: liquidtelecom.com
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_VI1PR03MB5056546242C4F37B521403BAEEE70VI1PR03MB5056eurp_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/y8eIZhNf701Xi6w3d2ZMDQrQ46w>
Subject: Re: [spring] FW: New Version Notification for draft-srcompdt-spring-compression-requirement-00.txt
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: Thu, 12 Nov 2020 21:02:09 -0000

Erm,

Ok – so – we have waited 6 months for a document – that we will go into SPRING and 6man to discuss – and what we have here in my view – is a document that says precisely nothing.

I’m going to take this section by section – and I would have hoped sending an email like this – that it would be a lot longer than it is going to be – but – since there is so little here – it probably won’t be all that long.

So let’s start at section 3 –

Section 3.1.1 is well, just pretty obvious and goes without stating
Section 3.1.2 again, pretty obvious that forwarding efficiency is important
Section 3.1.3 again, don’t think there is anything much to comment on here – its stating the obvious

Then we get to Section 4.
4.1.1 SRv6 Based – I don’t believe is within the scope of the charter – the charter does not say – design a solution – it says – state the requirements of a solution for compression of segment routing information for use over ipv6.  Nowhere does it say for the design team to decide if that is tied to one protocol or another.
4.1.2 See above comment
4.1.3 No issues
4.1.4 Don’t have a major problem with this
4.1.5 Please explain how you would achieve crossing boundaries using something like a binding SID or something to that effect while being compliant with this section

Section 5
I have a major issue with explicitly stating you need to support the behaviors in network programming – that is entirely outside of the charter.   Again, the charter states – a solution for compression of segment routing information for use over ipv6.  There may well be solutions within this that scope that do conform to the behaviors of network programming – but there may be solutions where such compression is used for purposes entirely different from those described in network programming – and have no relation to network programming at all.

Now lets look at what else the charter says.

The charter states that there would be a comparison of approaches and methods related to compression – that is not in this document at all – it is entirely absent. It states that the design team would look into the current solutions and state if they agreed if there was space for more than one solution or not – and if they were in agreement – that is entirely missing from this document.

The above points form effectively half the charter.

So – with all this said – I can only conclude based on what is here – that the design team has failed to date in its mandate – because this document pretty much states the obvious while ignoring the entire second half of the charter.  And this is what we have waited 6 long months for… based on a commitment that the design team would come with a requirements document at IETF 109.  Well – this – hardly cuts it as a design document.

Disappointed – to say the least

Andrew

From: spring <spring-bounces@ietf.org>
Date: Thursday, 12 November 2020 at 12:06
To: spring@ietf.org <spring@ietf.org>
Cc: 'srcomp' <srcomp@ietf.org>rg>, spring-chairs@ietf.org <spring-chairs@ietf.org>
Subject: [spring] FW: New Version Notification for draft-srcompdt-spring-compression-requirement-00.txt
Hi Group,
As you know, the SPRING Working Group set up an SR compression design team prior to IETF108.
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.

With great effort of design team members, DT have finished the version -00 of the requirements document and have submitted it to datatracker.

Please review it and let's know your comments.

B.R.
Weiqiang Cheng


-----邮件原件-----
发件人: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
发送时间: 2020年11月2日 16:32
收件人: Sander Steffann; SJM Steffann; Weiqiang Cheng
主题: New Version Notification for draft-srcompdt-spring-compression-requirement-00.txt


A new version of I-D, draft-srcompdt-spring-compression-requirement-00.txt
has been successfully submitted by Weiqiang Cheng and posted to the
IETF repository.

Name: draft-srcompdt-spring-compression-requirement
Revision: 00
Title: Compressed SRv6 SID List Requirements
Document date: 2020-10-30
Group: Individual Submission
Pages: 10
URL: https://www.ietf.org/archive/id/draft-srcompdt-spring-compression-requirement-00.txt<https://www.ietf.org/archive/id/draft-srcompdt-spring-compression-requirement-00.txt>
Status: https://datatracker.ietf.org/doc/draft-srcompdt-spring-compression-requirement/<https://datatracker.ietf.org/doc/draft-srcompdt-spring-compression-requirement>
Htmlized: https://datatracker.ietf.org/doc/html/draft-srcompdt-spring-compression-requirement<https://datatracker.ietf.org/doc/html/draft-srcompdt-spring-compression-requirement>
Htmlized: https://tools.ietf.org/html/draft-srcompdt-spring-compression-requirement-00<https://tools.ietf.org/html/draft-srcompdt-spring-compression-requirement-00>


Abstract:
This document specifies requirements for solutions to compress SRv6
SID lists.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat





_______________________________________________
spring mailing list
spring@ietf.org
https://www.ietf.org/mailman/listinfo/spring<https://www.ietf.org/mailman/listinfo/spring>