Re: [alto] Call for Adoption: draft-bw-alto-cost-mode-01

mohamed.boucadair@orange.com Tue, 08 March 2022 09:16 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 C4FDC3A0D30; Tue, 8 Mar 2022 01:16:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gJOPN4UIKBKm; Tue, 8 Mar 2022 01:16:10 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 985073A0D1F; Tue, 8 Mar 2022 01:16:09 -0800 (PST)
Received: from opfedar01.francetelecom.fr (unknown [xx.xx.xx.2]) (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 opfedar23.francetelecom.fr (ESMTP service) with ESMTPS id 4KCV7C5kmrzBrXj; Tue, 8 Mar 2022 10:16:07 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1646730967; bh=bz4HjvAs8enT9+uDs3JNuYB1yE9+i2lc782FgTXqXXc=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=Ciov5wWz3isjkv6TDjKO0b3TKJCrR/UIsr9pRPiHKrd1wxoq6zwVnTFgWkCADyFrn Ts+8d43K+tI9kzQi0P4AeGfcMu34Ox2fVUOJHTbl4hXV6o38UjxJn/qvrU99Qi4aZj MPFzN5PsSa/0xPR/jg5vhP62ESwQLfTejAsoVY0/m6GfIA1Egbe7e4uHqvmtpkBt6O 1J7+VU/PVvw0o8A7DQAag4bXDQKKdHqB6K2AqowigVYYlxhad5X3m6bvn3shoFPkuB QnNClf4b6Ukj0txmjKAA7l2Nent9fripTATn7ad1r78IzzOLj9RD4wxObFyi1SM1jH AdJZ16OvB4g9A==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfedar01.francetelecom.fr (ESMTP service) with ESMTPS id 4KCV7C4FhQzBrLT; Tue, 8 Mar 2022 10:16:07 +0100 (CET)
From: mohamed.boucadair@orange.com
To: LUIS MIGUEL CONTRERAS MURILLO <luismiguel.contrerasmurillo@telefonica.com>, Dhruv Dhody <dhruv.ietf@gmail.com>
CC: "alto-chairs@ietf.org" <alto-chairs@ietf.org>, Kai Gao <kaigao@scu.edu.cn>, alto <alto@ietf.org>
Thread-Topic: [alto] Call for Adoption: draft-bw-alto-cost-mode-01
Thread-Index: AQHYMhZ0DCYdfhpVLUqjpxaFchlWjqy0/PSAgAAI/4CAAAypAIAAF0rQgAAJQ7A=
Content-Class:
Date: Tue, 08 Mar 2022 09:16:06 +0000
Message-ID: <9556_1646730967_62271ED7_9556_262_3_787AE7BB302AE849A7480A190F8B9330354ACC26@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <6651b813.199bc.17f6422ddf3.Coremail.kaigao@scu.edu.cn> <CAB75xn6L_Lsni4LTVXfu3wkqgGhX9PCVMAhfJhHwgHc7zzQjAg@mail.gmail.com> <5363_1646720626_6226F672_5363_288_1_787AE7BB302AE849A7480A190F8B9330354AC885@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <CAB75xn6SFtmJxHOt+mC_vyQtP_n+NnEG3aQHQH3wVy_MGrQ4Rg@mail.gmail.com> <DB9PR06MB791560278F1E623491C1BA2C9E099@DB9PR06MB7915.eurprd06.prod.outlook.com>
In-Reply-To: <DB9PR06MB791560278F1E623491C1BA2C9E099@DB9PR06MB7915.eurprd06.prod.outlook.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-03-08T09:06:01Z; 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=cc6f90e7-ce3c-435f-a884-8c6285004daf; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.114.13.245]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B9330354ACC26OPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/N4zExfRywuS-irgrjWjfDJavcbY>
Subject: Re: [alto] Call for Adoption: draft-bw-alto-cost-mode-01
X-BeenThere: alto@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 08 Mar 2022 09:16:15 -0000

Hi Luis,
Re-, Dhruv,

Thank you for sharing your thoughts. I wasn’t against “enabling private use”, but was not sure that having a dedicated prefix will stop from using other values that match local templates (e.g., prefix with a PEN) and which would achieve the same objective.

I hear the consistency argument made bye Dhruv. That’s what I went with the changes that you can track at: https://tinyurl.com/alto-cost-mode-latest

Cheers,
Med

De : LUIS MIGUEL CONTRERAS MURILLO <luismiguel.contrerasmurillo@telefonica.com>
Envoyé : mardi 8 mars 2022 09:37
À : Dhruv Dhody <dhruv.ietf@gmail.com>; BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>
Cc : alto-chairs@ietf.org; Kai Gao <kaigao@scu.edu.cn>; alto <alto@ietf.org>
Objet : RE: [alto] Call for Adoption: draft-bw-alto-cost-mode-01

Hi all,

I agree with Dhruv on the fact that enabling private use could be useful. I’m thinking on the fact of positioning ALTO as IETF Network Exposure Function (as described in draft-contreras-alto-ietf-nef-00) where some private (non-standard or experimental) information could be exposed among parties for specific purposes.

Best regards

Luis

De: alto <alto-bounces@ietf.org<mailto:alto-bounces@ietf.org>> En nombre de Dhruv Dhody
Enviado el: martes, 8 de marzo de 2022 8:09
Para: mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>
CC: alto-chairs@ietf.org<mailto:alto-chairs@ietf.org>; Kai Gao <kaigao@scu.edu.cn<mailto:kaigao@scu.edu.cn>>; alto <alto@ietf.org<mailto:alto@ietf.org>>
Asunto: Re: [alto] Call for Adoption: draft-bw-alto-cost-mode-01

Hi Med,

On Tue, Mar 8, 2022 at 11:53 AM <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> wrote:
Hi Dhruv,

Thank you for the comments.

We will be adding a “description” in the next iteration, however the details about the structure/etc should not be echoed in the table but be available in the pointer provided under “Specification”.


Dhruv: Maybe I was not clear. I meant to say the IANA sections in RFC 7285 included a lot more text than what is there in this I-D. See https://datatracker.ietf.org/doc/html/rfc7285#section-14.2 and https://datatracker.ietf.org/doc/html/rfc7285#section-14.3. I was suggesting using a similar format and adding more text about this new registry as well.


I’m not sure a specific prefix for private use is needed, but I may be mistaken. When running experiments, the owners can just pick any value which does not conflict with a value in the registry + provide the semantic/behavior to ALTO nodes that are involved in the experiment.


Dhruv: Experiments sometimes leak into the wild and thus we discourage simply picking any value and opting for private use and experimental use values in the IANA registry. Further, consistency in the protocol extensions is a good thing to have, and thus using priv: makes sense to me! I was not in the room when RFC 7285 was being developed. Maybe some of the OG participants from the WG could through some light on this as well :)

Thanks!
Dhruv


Cheers,
Med

De : Dhruv Dhody <dhruv.ietf@gmail.com<mailto:dhruv.ietf@gmail.com>>
Envoyé : mardi 8 mars 2022 06:52
À : Kai Gao <kaigao@scu.edu.cn<mailto:kaigao@scu.edu.cn>>
Cc : alto <alto@ietf.org<mailto:alto@ietf.org>>; alto-chairs@ietf.org<mailto:alto-chairs@ietf.org>
Objet : Re: [alto] Call for Adoption: draft-bw-alto-cost-mode-01

Hi Kai,

Support adoption!

Should the IANA consideration section follow the format followed by RFC 7285 which includes lot more details on the rationale, requested information, string format etc.

That also made me wonder if there is some benefit to also mark priv: for private use as done for some of the other ALTO registries.

Thanks!
Dhruv

On Mon, Mar 7, 2022 at 4:58 PM <kaigao@scu.edu.cn<mailto:kaigao@scu.edu.cn>> wrote:
Dear all,

I have been appointed to run the Call for Adoption of draft-bw-alto-cost-mode-01.

Following up with what has been proposed and agreed during the IESG review on draft-ietf-alto-path-vector [1], we are starting a call for adoption of the ALTO cost mode [2] document as a charter deliverable. It both helps push forward existing WG document and fits in the protocol maintenance item in the current charter.

The Call for Adoption will close on March 21 (2 weeks after the IETF submission deadline). Please post to the mailing list if you support or appose the adoption, or have any comments or suggestions.

[1] https://mailarchive.ietf.org/arch/msg/alto/WWoyJyM0PioBWM_rADYT-Z_I8t4/
[2] https://datatracker.ietf.org/doc/html/draft-bw-alto-cost-mode-01

Thanks!

Best,
Kai
_______________________________________________
alto mailing list
alto@ietf.org<mailto:alto@ietf.org>
https://www.ietf.org/mailman/listinfo/alto

_________________________________________________________________________________________________________________________



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.

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is confidential and privileged information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição

_________________________________________________________________________________________________________________________

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.