Re: [alto] Murray Kucherawy's Discuss on draft-ietf-alto-cost-mode-04: (with DISCUSS and COMMENT)

mohamed.boucadair@orange.com Thu, 02 June 2022 06:54 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D481FC157B47; Wed, 1 Jun 2022 23:54:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 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_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
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 Ny08qXe-11PW; Wed, 1 Jun 2022 23:54:32 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF26EC157B45; Wed, 1 Jun 2022 23:54:31 -0700 (PDT)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr20.francetelecom.fr (ESMTP service) with ESMTPS id 4LDGw54mTXz2058; Thu, 2 Jun 2022 08:54:29 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1654152869; bh=CshaBRp/y/WzqJzqU8pyaaXzG6FLFs+B2LNRSkaCeVs=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=nrnxbwN2H9E4j/MGFzBjuThGsusirdZXmShJYUTYaPqZJUcsf61yEhnUV1yCT816M DTSdb2d4lJUA6/ZB5LGG9FDm+CSfZqWKN3K+wYbih+wkmnhWbyn4pDs9HTVqphwN4z k307EuSJJQ9FYnoyTHD7O01giXjBZeZQF/jEpEkvG7WsO60HWwbKafAb90lGJ60wLv 62iJxAiJTRPJhB8661nySnks0gPIrJNvf6lSLwqFn0DT53bNJ3p74IzzumxGdEPLdd MUWzClk6Y4c+VMsRITQ3UVXBFq6FO71L0lF7hAXHRcli7kuikSKWuE8LKTMS2Nqb0M zpBf/ydYx81Ug==
From: mohamed.boucadair@orange.com
To: Murray Kucherawy <superuser@gmail.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-alto-cost-mode@ietf.org" <draft-ietf-alto-cost-mode@ietf.org>, "alto-chairs@ietf.org" <alto-chairs@ietf.org>, "alto@ietf.org" <alto@ietf.org>, "kaigao@scu.edu.cn" <kaigao@scu.edu.cn>
Thread-Topic: Murray Kucherawy's Discuss on draft-ietf-alto-cost-mode-04: (with DISCUSS and COMMENT)
Thread-Index: AQHYdkhJM67K67S0aUOJz2sLRp7qXa07qZqA
Content-Class:
Date: Thu, 02 Jun 2022 06:54:29 +0000
Message-ID: <19400_1654152869_62985EA5_19400_327_1_bf1383808a624411817048e0c99fd119@orange.com>
References: <165415058321.30949.13923667541698209796@ietfa.amsl.com>
In-Reply-To: <165415058321.30949.13923667541698209796@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-06-02T06:37:03Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=ebddadb1-85d3-45e0-a322-11aea142edfa; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.115.27.53]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/3LRL3ahx8T4rFHCjufLVTGxOMMg>
Subject: Re: [alto] Murray Kucherawy's Discuss on draft-ietf-alto-cost-mode-04: (with DISCUSS and COMMENT)
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Application-Layer Traffic Optimization \(alto\) WG mailing list" <alto.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/alto>, <mailto:alto-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/alto/>
List-Post: <mailto:alto@ietf.org>
List-Help: <mailto:alto-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/alto>, <mailto:alto-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jun 2022 06:54:35 -0000

Hi Murray, 

Thanks for the review. 

Please see inline. 

Cheers,
Med

> -----Message d'origine-----
> De : Murray Kucherawy via Datatracker <noreply@ietf.org>
> Envoyé : jeudi 2 juin 2022 08:16
> À : The IESG <iesg@ietf.org>
> Cc : draft-ietf-alto-cost-mode@ietf.org; alto-chairs@ietf.org;
> alto@ietf.org; kaigao@scu.edu.cn
> Objet : Murray Kucherawy's Discuss on draft-ietf-alto-cost-mode-
> 04: (with DISCUSS and COMMENT)
> 
> Murray Kucherawy has entered the following ballot position for
> draft-ietf-alto-cost-mode-04: 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-alto-cost-mode/
> 
> 
> 
> ------------------------------------------------------------------
> ----
> DISCUSS:
> ------------------------------------------------------------------
> ----
> 
> Paul said:
> 
> > I think that SHOULD can be a MUST. Although one could question
> the 2119 usage
> as it seems to be a directive to a document author and not a
> protocol action.
> So I would also be okay with lowercasing this.
> 
> I'm ambivalent about the first sentence, but I concur strongly
> with the second;
> use of BCP 14 language to establish a requirement against some
> future document
> seems quite unconventional to me.  Can we talk about why this is
> necessary
> and/or appropriate?

[Med] That wording was on purpose. We could easily turn that text into the following:

NEW:
 If the definition of a cost mode does not indicate whether it
 applies to a subset of cost metrics, ALTO implementations
 MUST be prepared to accept that cost mode for any cost metric.

... but there is a high risk that this behavior will overlooked and thus the default mode will be the rule. This would have interoperability implications as it is likely that some modes can't be associated with all cost metrics. 

The SHOULD is some sort of authors guideline to assess the applicability and record it.  


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.