[v6ops] Comments on draft-ietf-v6ops-ipv6-ehs-packet-drops-01

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Tue, 01 December 2020 16:31 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 448093A1440 for <v6ops@ietfa.amsl.com>; Tue, 1 Dec 2020 08:31:02 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 u7G_EDWWQCnM for <v6ops@ietfa.amsl.com>; Tue, 1 Dec 2020 08:30:56 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id 7A5723A1479 for <v6ops@ietf.org>; Tue, 1 Dec 2020 08:30:50 -0800 (PST)
Received: from GF-MacBook-Pro.lan (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 81CA51B00062; Tue, 1 Dec 2020 16:30:44 +0000 (GMT)
References: <d97ca0fd-776a-1525-50d1-3a62fd7edf5f@erg.abdn.ac.uk>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
To: v6ops@ietf.org
Cc: fernando@gont.com.ar, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, fredbaker.ietf@gmail.com
X-Forwarded-Message-Id: <d97ca0fd-776a-1525-50d1-3a62fd7edf5f@erg.abdn.ac.uk>
Message-ID: <0c121812-44cf-119e-fd09-bb138ff789de@erg.abdn.ac.uk>
Date: Tue, 01 Dec 2020 16:30:43 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
MIME-Version: 1.0
In-Reply-To: <d97ca0fd-776a-1525-50d1-3a62fd7edf5f@erg.abdn.ac.uk>
Content-Type: multipart/mixed; boundary="------------D972FB92435BE6F001DD5AC6"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/c1GmfyOQ9Le7ZzGK2J7OPuxySVw>
Subject: [v6ops] Comments on draft-ietf-v6ops-ipv6-ehs-packet-drops-01
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Dec 2020 16:31:10 -0000

I promised a  careful read of this ID at the last v6OPS meeting, and 
this is it.

* First, I think this is a useful document to help understand what is 
happening in operational networks and reasons for this. It's also a 
ueseful input for planning standards actions in 6man, etc. Thanks for 
doing this.

* I have some concerns that some of the choices of words could 
(unintentionally) be taken as endorsing a best practice, which I don't 
think the IETF would generally promote. This is more about ensuring 
specific parts can not be quoted out of context. I did a careful read 
and hope I identified most of these and propose something that might be 
helpful (please see attached PDF - RTF is identical). I think it would 
be good to clarify in a few places this is the RFC8200 spec, since I 
have heard there could be new work to update that.

* On the measurement evidence: I have  a slight concern that the results 
might not cover the wide variety of use cases and you may like to be 
more careful in the words you use to generalise these for the 
"internet".  I think we should be aware that in some scenarios an EH 
might still be effectively used, where path can safely support this. In 
some other uses, the fact that packets with these options might be 
expected to be dropped by many paths - for good reasons, does not mean 
that the option is useless to set in general - it might merely be that 
for these paths it is not possible to use the option and then care is 
needed in deciding which packets set the EH and how this is used.

Hope this helps, Fernando. If you need any clarification or other help, 
just let me know,

Gorry

---