[alto] Unified properties terminology clarification

Qin Wu <bill.wu@huawei.com> Thu, 19 November 2020 12:32 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: alto@ietfa.amsl.com
Delivered-To: alto@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 15E103A0D1E for <alto@ietfa.amsl.com>; Thu, 19 Nov 2020 04:32:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id JLAiC8Rdl64x for <alto@ietfa.amsl.com>; Thu, 19 Nov 2020 04:32:57 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D1153A0CE0 for <alto@ietf.org>; Thu, 19 Nov 2020 04:32:57 -0800 (PST)
Received: from fraeml708-chm.china.huawei.com (unknown []) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4CcJtt1Wxfz67FKR for <alto@ietf.org>; Thu, 19 Nov 2020 20:31:02 +0800 (CST)
Received: from fraeml708-chm.china.huawei.com ( by fraeml708-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Thu, 19 Nov 2020 13:32:55 +0100
Received: from DGGEML406-HUB.china.huawei.com ( by fraeml708-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Thu, 19 Nov 2020 13:32:54 +0100
Received: from DGGEML511-MBS.china.huawei.com ([]) by dggeml406-hub.china.huawei.com ([]) with mapi id 14.03.0487.000; Thu, 19 Nov 2020 20:32:50 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "alto@ietf.org" <alto@ietf.org>
Thread-Topic: Unified properties terminology clarification
Thread-Index: Ada+byxh5DtG5Vj7TTmS+sVk1cbO0Q==
Date: Thu, 19 Nov 2020 12:32:49 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABAADB8CC75@dggeml511-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABAADB8CC75dggeml511mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/Yuq6y2JWBm4Vaa0vN0FaooBPqfA>
Subject: [alto] Unified properties terminology clarification
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: Thu, 19 Nov 2020 12:32:59 -0000

Hi, Sabine:
Follow up our discussion in today's ALTO session, one issue I raised is about the terminology we used in the unified properties draft. I feel the term "unified properties" lacks clarity and causes a little bit confusion to people who are familiar with this draft, that is on is unified property break existing protocol or component such as
Endpoint property, I am wondering if we can change the term into property Map, so the title will be changed into "ALTO extension: Property Map" , which is also align with the title of Path vector draft, Does this make sense?
As you mentioned, this was discussed in the past, can you remind me the history discussion why the current name is picked. Thanks in advance, hope we can resolve this as soon as possible.