[alto] Review of draft-lcsr-alto-service-functions

Qin Wu <bill.wu@huawei.com> Wed, 13 July 2022 03:57 UTC

Return-Path: <bill.wu@huawei.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 63272C14F75F; Tue, 12 Jul 2022 20:57:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.906
X-Spam-Level:
X-Spam-Status: No, score=-1.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 ulyL-djnDaNW; Tue, 12 Jul 2022 20:57:09 -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 8197BC14F5E1; Tue, 12 Jul 2022 20:57:09 -0700 (PDT)
Received: from fraeml714-chm.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4LjP0s5r65z67vBH; Wed, 13 Jul 2022 11:55:41 +0800 (CST)
Received: from canpemm100008.china.huawei.com (7.192.104.152) 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.2375.24; Wed, 13 Jul 2022 05:57:05 +0200
Received: from canpemm500005.china.huawei.com (7.192.104.229) by canpemm100008.china.huawei.com (7.192.104.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Wed, 13 Jul 2022 11:57:04 +0800
Received: from canpemm500005.china.huawei.com ([7.192.104.229]) by canpemm500005.china.huawei.com ([7.192.104.229]) with mapi id 15.01.2375.024; Wed, 13 Jul 2022 11:57:04 +0800
From: Qin Wu <bill.wu@huawei.com>
To: LUIS MIGUEL CONTRERAS MURILLO <luismiguel.contrerasmurillo@telefonica.com>
CC: "alto@ietf.org" <alto@ietf.org>, "draft-lcsr-alto-service-functions@ietf.org" <draft-lcsr-alto-service-functions@ietf.org>
Thread-Topic: Review of draft-lcsr-alto-service-functions
Thread-Index: AdiWayn+XbTWOuT4Tt25rZYGNtj7cA==
Date: Wed, 13 Jul 2022 03:57:04 +0000
Message-ID: <369ab83a57844f669661823eb0a7b837@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.100.16]
Content-Type: multipart/alternative; boundary="_000_369ab83a57844f669661823eb0a7b837huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/alto/LUmuMNnZYYDGbbmQ-qu-GM3bFUY>
Subject: [alto] Review of draft-lcsr-alto-service-functions
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: Wed, 13 Jul 2022 03:57:13 -0000

Hi, Luis:
Thank for your proposed new draft on service function handling (https://datatracker.ietf.org/doc/draft-lcsr-alto-service-functions/), I believe it is related to service function invocation use case. Thanks for that.
ALTO Path vector seems a good basis for your requested protocol extension.
One thing I am not very clear is
1.who will be the client to consume ALTO information combining network topo info and service function information?
Should it be cross domain service orchestration system, or ingress node or headend?
2.How does such client consume these information?

-Qin