[Anima] Review comments on draft-ietf-anima-grasp-api

"Liguangpeng (Roc, Network Technology Laboratory)" <liguangpeng@huawei.com> Wed, 18 September 2019 06:22 UTC

Return-Path: <liguangpeng@huawei.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5653A1201AA for <anima@ietfa.amsl.com>; Tue, 17 Sep 2019 23:22:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 llLhMc1b_A4F for <anima@ietfa.amsl.com>; Tue, 17 Sep 2019 23:22:34 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41D821200A4 for <anima@ietf.org>; Tue, 17 Sep 2019 23:22:34 -0700 (PDT)
Received: from lhreml707-cah.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id 7E9BDEBDCBCCDA9FDC90; Wed, 18 Sep 2019 07:22:31 +0100 (IST)
Received: from DGGEMM401-HUB.china.huawei.com ( by lhreml707-cah.china.huawei.com ( with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 18 Sep 2019 07:22:30 +0100
Received: from DGGEMM533-MBX.china.huawei.com ([]) by DGGEMM401-HUB.china.huawei.com ([]) with mapi id 14.03.0439.000; Wed, 18 Sep 2019 14:22:23 +0800
From: "Liguangpeng (Roc, Network Technology Laboratory)" <liguangpeng@huawei.com>
To: "anima@ietf.org" <anima@ietf.org>
Thread-Topic: Review comments on draft-ietf-anima-grasp-api
Thread-Index: AdVt6NO1Oc6IzgggSm+u71yVAMuX/w==
Date: Wed, 18 Sep 2019 06:22:23 +0000
Message-ID: <6F4E6B0C717D4641A2B79BC1740D8CF4A7E22578@DGGEMM533-MBX.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_6F4E6B0C717D4641A2B79BC1740D8CF4A7E22578DGGEMM533MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/XT4oALm-QJoI2wNHc9lxtvAMZKk>
Subject: [Anima] Review comments on draft-ietf-anima-grasp-api
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 06:22:36 -0000

Hi authors,

I read the draft. I think the API list for grasp is complete and good. But I have some comments on section 2.2.

2.2. Asynchronous Operations

'... there are two main techniques for such parallel operations: multi-threading, or a polling or 'event loop' structure.'

According to my knowledge, 'multi-threading' is a different thing with asynchronous programming mechanism. So I prefer to 'asynchronous programming mechanisms with multi-threading' here. The main techniques for asynchronous programming discussed in draft should be 'polling', however, polling is not so efficient. The more efficient one is 'call back' mechanism.

'session_nonce' parameter may be useful for polling, but 'call back function pointer( or reference in some programming language)' is normally used as parameter of invoked functions. All logics should be executed in call back functions which will be called when some events occur, for example receiving response message for the request, or message timeout.

Best regards,
Guangpeng Li