Hi Yujing,

Thanks, it is clear now what you intend. Do you have the 'cddl' tool installed? 
It is quite simple, but it allows you to validate CDDL syntax and generate 
random examples. See Appendix F of RFC8610.

I did find a few nits.

1) CDDL does not accept tab characters. So all the tabs must be changed to 
spaces.
2) If you define an element as xxx : uint, a second definition such as xxx = 
0..7 is ignored.
3) service-tag-info = str should be service-tag-info = text
4) Did you mean resource-requirement-pair to be a group with () or an array 
with []? I think probably you meant an array. (See section 3.4 of RFC8610.)

So my version that works with the CDDL tool is:

autonomic-network-service-value =
    [
     [
      service-type,
      service-id,
      service-lifetime,
      service-tag
      ],[
      *resource-requirement-pair
     ]
    ]

service-type = 0..7
service-id = uint
service-lifetime = 0..4294967295 ; in milliseconds
service-tag = [ *service-tag-info]
service-tag-info = text

resource-requirement-pair =
    [
     resource-type,
     resource-value
    ]

resource-type = 0..7
resource-value = uint

Is that OK?

Regards
   Brian Carpenter

On 27-Oct-22 15:56, zhouyujing (A) wrote:
Hi Brian,
        
        Thanks for your reply, allowing me to modify the draft better.
        Because of my lack of understanding of the CDDL format, some 
definitions are misunderstood. I update Figure 2 according to RFC8610, and hope 
this version is clearer. If there are lack of standardization, please let me 
know.

        -----------------------------------------------------------
        UPDATE : Format of autonomic-network-service-value-value

        autonomic-network-service-value = [
        [
                service-type : uint,
                service-id : uint,
                service-lifetime : uint,
                service-tag
        ],[
                *resource-requirement-pair
                ]
        ]

        service-type = 0..7
        service-id = uint
        service-lifetime = 0..4294967295 ; in milliseconds
        service-tag = [ *service-tag-info]
        service-tag-info = str

        resource-requirement-pair = (
                resource-type: uint,
                resource-value: uint
        )

        resource-type = 0..7
        resource-value = uint
        -----------------------------------------------------------

Best Regards

Yujing Zhou

-----Original Message-----
From: Brian E Carpenter <brian.e.carpen...@gmail.com>
Sent: 2022年10月25日 8:46
To: anima@ietf.org
Subject: Re: [Anima] I-D Action: 
draft-ietf-anima-network-service-auto-deployment-03.txt

Hi,

I'm still not fully understanding the notation used in Figure 2 at:
https://www.ietf.org/archive/id/draft-ietf-anima-network-service-auto-deployment-03.html#section-5-8

There is an expansion of service-information in CDDL just below the figure, but 
if you want conforming implementations, I think you need to fully expand 
autonomic-network-service-value in CDDL, or define carefully how Figure 2 is to 
be understood.

Regards
     Brian

On 25-Oct-22 03:37, internet-dra...@ietf.org wrote:

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Autonomic Networking Integrated Model and 
Approach WG of the IETF.

          Title           : A Generic Autonomic Deployment and Management 
Mechanism for Resource-based Network Services
          Authors         : Yujing Zhou
                            Joanna Dang
                            Sheng Jiang
                            Zongpeng Du
    Filename        : draft-ietf-anima-network-service-auto-deployment-03.txt
    Pages           : 16
    Date            : 2022-10-24

Abstract:
     This document specifies an autonomic mechanism for resource-based
     network services deployment and management, using the GeneRic
     Autonomic Signaling Protocol (GRASP) defined in [RFC8990] to
     dynamically exchange the information among the autonomic nodes.  It
     supports the coordination and consistently operations within an
     autonomic network domain.  This mechanism is generic for most, if not
     all, of kinds of network resources, although this document only
     defines the process of quality transmission service deployment and
     management.  It can be easily extended to support network services
     deployment and management that is based on other types ofnetwork
     resources.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-anima-network-service-auto
-deployment/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-anima-network-service
-auto-deployment-03

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-anima-network-service-aut
o-deployment-03


Internet-Drafts are also available by rsync at
rsync.ietf.org::internet-drafts


_______________________________________________
I-D-Announce mailing list
i-d-annou...@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html or
ftp://ftp.ietf.org/ietf/1shadow-sites.txt


_______________________________________________
Anima mailing list
Anima@ietf.org
https://www.ietf.org/mailman/listinfo/anima

Reply via email to