RE: Alvaro Retana's No Objection on draft-ietf-6man-ipv6-alt-mark-08: (with COMMENT)

Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Wed, 11 August 2021 07:43 UTC

Return-Path: <giuseppe.fioccola@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6634D3A083F; Wed, 11 Aug 2021 00:43:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 JihRXPLEHuF4; Wed, 11 Aug 2021 00:43:10 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02FD83A083D; Wed, 11 Aug 2021 00:43:10 -0700 (PDT)
Received: from fraeml714-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Gl1xj5SyMz6BDBh; Wed, 11 Aug 2021 15:42:33 +0800 (CST)
Received: from fraeml714-chm.china.huawei.com (10.206.15.33) by fraeml714-chm.china.huawei.com (10.206.15.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Wed, 11 Aug 2021 09:43:05 +0200
Received: from fraeml714-chm.china.huawei.com ([10.206.15.33]) by fraeml714-chm.china.huawei.com ([10.206.15.33]) with mapi id 15.01.2308.008; Wed, 11 Aug 2021 09:43:05 +0200
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
To: Alvaro Retana <aretana.ietf@gmail.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-6man-ipv6-alt-mark@ietf.org" <draft-ietf-6man-ipv6-alt-mark@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "bob.hinden@gmail.com" <bob.hinden@gmail.com>, "otroan@employees.org" <otroan@employees.org>
Subject: RE: Alvaro Retana's No Objection on draft-ietf-6man-ipv6-alt-mark-08: (with COMMENT)
Thread-Topic: Alvaro Retana's No Objection on draft-ietf-6man-ipv6-alt-mark-08: (with COMMENT)
Thread-Index: AQHXjgJ8NwY5UmpFW06X4AwRyFjbaatt4idQ
Date: Wed, 11 Aug 2021 07:43:05 +0000
Message-ID: <79a7dc3b36b14de3884d00e064851211@huawei.com>
References: <162861192237.16565.13751715030393499177@ietfa.amsl.com>
In-Reply-To: <162861192237.16565.13751715030393499177@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.95.62]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/phtMe3gKdbL2WXr9tNfIzVsWuEc>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Aug 2021 07:43:16 -0000

Dear Alvaro,
Thank you for your review. 
Please find my answers inline tagged as [GF].

Regards,

Giuseppe

-----Original Message-----
From: Alvaro Retana via Datatracker <noreply@ietf.org> 
Sent: Tuesday, August 10, 2021 6:12 PM
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-6man-ipv6-alt-mark@ietf.org; 6man-chairs@ietf.org; ipv6@ietf.org; bob.hinden@gmail.com; otroan@employees.org
Subject: Alvaro Retana's No Objection on draft-ietf-6man-ipv6-alt-mark-08: (with COMMENT)

Alvaro Retana has entered the following ballot position for
draft-ietf-6man-ipv6-alt-mark-08: No Objection

When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-6man-ipv6-alt-mark/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

(1) I support the DISCUSS positions from Lars, Roman, and Martin.

(1a) Of special concern to me is Martin's point about the relationship between this document and rfc8321/8889, and the potential ability to reference this work without proper review by the ippm WG.  Note that neither RFC is explicit about the criteria to complete the respective experiments; the Shepherd writeup for rfc8321 [a] states that "the measurement utility of this extension still is to be demonstrated at a variety of scales in a plurality of network conditions." Furthermore, I am not aware of discussions about the maturity of
rfc8321 in the ippm WG.

[GF]: We already had an offline discussion last year with 6MAN chairs, IPPM chairs and ADs (in particular with Magnus Westerlund). RFC 8321 was originally labeled as Experimental because it came from an experimental deployment. Indeed the initial application of the method was done by using marking fields that are not intended for performance measurements (in case of IPv4, we used two bits from the DSCP fields or the unused bit of the IPv4 header). For this reason, we could not follow the Standards Track in IPPM and the document was considered Experimental, even if the description of the methodology is protocol agnostic and can be applicable to different protocols. Regarding the maturity, I think the experiment, started in 2010, is done (https://datatracker.ietf.org/doc/html/rfc8321#section-5.1) and now the methodology is mature to make it applicable and standard for IPv6. We discussed last year the relationship between this document and RFC 8321 / RFC 8889 with the IPPM chairs (Tommy Pauly and Ian Swett), and they suggested to have RFC 8321 as informative reference. We also asked Mirja Kühlewind, that did the AD review for RFC 8889, and she gave a similar advice. It was also highlighted that, in the case of RFC 8321, Experimental and Informational can be considered at the same maturity level. For this reason, the detailed description of the methodology in RFC8321 has been included in this document to enable the informative reference.

[a] https://datatracker.ietf.org/doc/draft-ietf-ippm-alt-mark/shepherdwriteup/

(2) There are several references to I-D.fioccola-v6ops-ipv6-alt-mark, which was replaced by draft-fz-6man-ipv6-alt-mark and ultimately by this document.  IOW, it looks like this document refers to an old version of itself.  Since the references are mostly about analysis made in the early drafts, it may be better to include some of that in an appendix instead.

[GF]: I see. I can remove this reference and report the relevant considerations in the document.