Re: [ippm] Roman Danyliw's Discuss on draft-ietf-ippm-rfc8889bis-02: (with DISCUSS and COMMENT)
Giuseppe Fioccola <giuseppe.fioccola@huawei.com> Tue, 12 July 2022 13:26 UTC
Return-Path: <giuseppe.fioccola@huawei.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15D39C14F73F; Tue, 12 Jul 2022 06:26:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9MWgTG3N3xf8; Tue, 12 Jul 2022 06:26:36 -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 6C48FC14F73E; Tue, 12 Jul 2022 06:26:36 -0700 (PDT)
Received: from fraeml713-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Lj1hR098Wz689sp; Tue, 12 Jul 2022 21:25:11 +0800 (CST)
Received: from fraeml714-chm.china.huawei.com (10.206.15.33) by fraeml713-chm.china.huawei.com (10.206.15.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Tue, 12 Jul 2022 15:26:33 +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.2375.024; Tue, 12 Jul 2022 15:26:33 +0200
From: Giuseppe Fioccola <giuseppe.fioccola@huawei.com>
To: Roman Danyliw <rdd@cert.org>, The IESG <iesg@ietf.org>
CC: "draft-ietf-ippm-rfc8889bis@ietf.org" <draft-ietf-ippm-rfc8889bis@ietf.org>, "ippm-chairs@ietf.org" <ippm-chairs@ietf.org>, "ippm@ietf.org" <ippm@ietf.org>, "tpauly@apple.com" <tpauly@apple.com>
Thread-Topic: Roman Danyliw's Discuss on draft-ietf-ippm-rfc8889bis-02: (with DISCUSS and COMMENT)
Thread-Index: AQHYlVLxAWEB1MQRRE6+7VgPpjiclq16tbBA
Date: Tue, 12 Jul 2022 13:26:33 +0000
Message-ID: <63bcd8a3e70d47119cb412e8ea4722bf@huawei.com>
References: <165756360104.6318.5137554143289792383@ietfa.amsl.com>
In-Reply-To: <165756360104.6318.5137554143289792383@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.81.220.147]
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/ippm/a9vffCo_WJ2MX2IFKwKgnoZVfv4>
Subject: Re: [ippm] Roman Danyliw's Discuss on draft-ietf-ippm-rfc8889bis-02: (with DISCUSS and COMMENT)
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jul 2022 13:26:41 -0000
Hi Roman, Thank you for the review. Please find my replies inline tagged as [GF]. I will work on a new revision to address your comments. Best Regards, Giuseppe -----Original Message----- From: Roman Danyliw via Datatracker <noreply@ietf.org> Sent: Monday, July 11, 2022 8:20 PM To: The IESG <iesg@ietf.org> Cc: draft-ietf-ippm-rfc8889bis@ietf.org; ippm-chairs@ietf.org; ippm@ietf.org; tpauly@apple.com; tpauly@apple.com Subject: Roman Danyliw's Discuss on draft-ietf-ippm-rfc8889bis-02: (with DISCUSS and COMMENT) Roman Danyliw has entered the following ballot position for draft-ietf-ippm-rfc8889bis-02: Discuss 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/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-ippm-rfc8889bis/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- Please clarify the expected deployment model of this approach. (a) Section 9. The Multipoint Alternate Marking Method is RECOMMENDED only for controlled domains, as per [I-D.ietf-ippm-rfc8321bis]. (b) Section 10 This document specifies a method of performing measurements that does not directly affect Internet security or applications that run on the Internet. The text in (a) suggests that deployment can occur on the Internet (although it isn’t recommended). However, (b) suggests that OAM meta-data would not be used on the Internet. [GF] Similarly to RFC8321bis, I will revise the text in (a) and replace it with: "The Multipoint Alternate Marking Method MUST only be applied to controlled domains." ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- ** Section 7.2.2. Is [I-D.mizrahi-ippm-marking] the expected mechanism to combine hashing with Alternative Marking? If so, it should be a normative reference. [GF]: I can omit the reference to [I-D.mizrahi-ippm-marking] also because it is currently expired. I can probably refer to [IEEE-Network-PNPM] given that it introduces the same mechanism. ** Section 9. Is there a citation that can be provided for the experiments that informed this design? [GF]: The original RFC8889 reported deployment examples (in particular it was experimented for Mobile Backhaul and VPN). Also, [IEEE-Network-PNPM] includes some information about the operational experience.
- [ippm] Roman Danyliw's Discuss on draft-ietf-ippm… Roman Danyliw via Datatracker
- Re: [ippm] Roman Danyliw's Discuss on draft-ietf-… Giuseppe Fioccola