Re: [Anima] New Version Notification for draft-dang-anima-network-service-auto-deployment-00.txt

Dangjuanna <dangjuanna@huawei.com> Tue, 27 July 2021 09:20 UTC

Return-Path: <dangjuanna@huawei.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D99453A1C66 for <anima@ietfa.amsl.com>; Tue, 27 Jul 2021 02:20:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 unIB2QBbRASK for <anima@ietfa.amsl.com>; Tue, 27 Jul 2021 02:20:00 -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 BF7743A1C62 for <anima@ietf.org>; Tue, 27 Jul 2021 02:19:59 -0700 (PDT)
Received: from fraeml704-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4GYrcQ4t0Wz6H7jd; Tue, 27 Jul 2021 17:10:46 +0800 (CST)
Received: from kwepeml500002.china.huawei.com (7.221.188.128) by fraeml704-chm.china.huawei.com (10.206.15.53) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2176.2; Tue, 27 Jul 2021 11:19:56 +0200
Received: from kwepeml500003.china.huawei.com (7.221.188.182) by kwepeml500002.china.huawei.com (7.221.188.128) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Tue, 27 Jul 2021 17:19:54 +0800
Received: from kwepeml500003.china.huawei.com ([7.221.188.182]) by kwepeml500003.china.huawei.com ([7.221.188.182]) with mapi id 15.01.2176.012; Tue, 27 Jul 2021 17:19:54 +0800
From: Dangjuanna <dangjuanna@huawei.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "duzongpeng@foxmail.com" <duzongpeng@foxmail.com>, "anima@ietf.org" <anima@ietf.org>
Thread-Topic: [Anima] New Version Notification for draft-dang-anima-network-service-auto-deployment-00.txt
Thread-Index: AQHXctoZIF/USi7E6UeulUA0rRagTKs3phFw//+neICAAPTBAIAAgLCAgAaub4CAEJB4sIAAE8kAgAZ0LeA=
Date: Tue, 27 Jul 2021 09:19:54 +0000
Message-ID: <7c1b67e9ecef441f89639efc855b9f89@huawei.com>
References: <162562590439.897.10503138190698470295@ietfa.amsl.com> <70a863c394e64b9aa8f924be5d870d80@huawei.com> <10648.1625681991@localhost> <b0e0a049f74240799a0874778de0fb17@huawei.com> <12818.1625762187@localhost> <383d3aa0276544929b5082a7d1e4d2ae@huawei.com> <630243de50824cb39d66ecf09db6a35d@huawei.com> <594538.1627044382@dooku>
In-Reply-To: <594538.1627044382@dooku>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.235.250]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/IH-MyVrTV5Ea8j72IHNr2k5-sDw>
Subject: Re: [Anima] New Version Notification for draft-dang-anima-network-service-auto-deployment-00.txt
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: Tue, 27 Jul 2021 09:20:05 -0000

Hi,

Thanks for your kind reminder and suggestion. 

I have studied GRASP Objective allocations in RFC8994 which is very helpful for me.

The GRASP objective between Network Initiator and SPE is an example as follows.

The formal definition of the objective in CDDL (see "Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures" [RFC8610]) is as follows:
discovery-message = [M_DISCOVERY, session-id, initiator, objective]
response-message = [M_RESPONSE, session-id, initiator, ttl,
                         (+locator-option // divert-option), ?objective]
request-negotiation-message = [M_REQ_NEG, session-id, initiator, objective]
negotiation-message = [M_NEGOTIATE, session-id, objective]

objective = ["xxxx-s", objective-flags, loop-count, objective-value]
objective-name = "xxxx-s"           ; Assigned by IANA registration
objective-flags = (F_DISC and F_NEG)  ; As in [RFC8990].
loop-count = ?                    ; TBD
objective-value = [s-identification, s-deployment-type, s-resource-information]
s-identification       ; Distinguish different network services
s-deployment-type    ; Indicating that it is new, or updated, or deleted
s-resource-information ; Assured resources of the network service.

s-resource-information = [[resource-type, resource-value], [resource-type, resource-value], ...] ; One message may include one or multiple resource information
resource-type        ; Indicating bandwidth type, or latency type, etc.
resource-value       ; Indicating the value

About IANA Considerations, I will try to apply it.

Best wishes,
Joanna

-----Original Message-----
From: Michael Richardson [mailto:mcr+ietf@sandelman.ca] 
Sent: 2021年7月23日 20:46
To: Dangjuanna <dangjuanna@huawei.com>; duzongpeng@foxmail.com; anima@ietf.org
Subject: Re: [Anima] New Version Notification for draft-dang-anima-network-service-auto-deployment-00.txt


Dangjuanna <dangjuanna@huawei.com> wrote:
    > A New GRASP Objective Option as an example is defined as follows,

...
    > Do you think it is available?

You just need to put this kind of thing (with answers) into your IANA Considerations section, and when your document advances it will be allocated.
You can also ask for early allocation if you are trying to do interop.

RFC8994 and RFC8994 do GRASP Objective allocations, you could use that as your template.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works  -= IPv6 IoT consulting =-