Hi Micheal, Please see below.
Best, Joanna -----Original Message----- From: Anima [mailto:anima-boun...@ietf.org] On Behalf Of Michael Richardson Sent: 2021年7月8日 2:20 To: Dangjuanna <dangjua...@huawei.com>; anima@ietf.org; duzongp...@foxmail.com Subject: Re: [Anima] New Version Notification for draft-dang-anima-network-service-auto-deployment-00.txt Dangjuanna <dangjua...@huawei.com> wrote: > A new version of I-D, draft-dang-anima-network-service-auto-deployment-00.txt > has been successfully submitted. > Name: draft-dang-anima-network-service-auto-deployment > Revision: 00 > Title: An Auto-deployment Mechanism for Resource-based Network Services > Htmlized: https://datatracker.ietf.org/doc/html/draft-dang-anima-network-service-auto-deployment An interesting read, and a really useful ACP application. Comments/nits: can you expand ASBR, UPE and PE the first time they are used, Move the digram from section 4 to section 3. [JD] I agree with you and it will be updated. section 4 questions: 1) do the ANS message flow over the ACP? I assume so. [JD] Correct. ACP of the autonomic node send or receive the ANS message. I was a little hesitant to use the SPE and UPE names when writing, so the text was a little confusing. I suggest that the SPE and UPE be unified as an SPE in the future because it is a single device on the network. Do you think it is OK? 2) "The specific configuration command lines are not in the scope of this document." section 5: objective-name = EX10 I think you want to do an IANA Action here to define your own? EX10 is just... an example. >[JD]Yes, the new objective-name for network service deployment need to be >defined and added. EX10 is only one example :) service-identification-type --- 3-bits. I don't think you need to be so frugal in your use of bits. That could just be a CBOR Int. path-identification-value, resource-type, same comment. >[JD] Could you help me modify them according to your understanding? 8. Security Considerations It complies with GRASP security consideration. You probably mean to say that it uses the security provided by the ACP. > [JD]Yes, do you think whether it is enough? I think that I'm missing some parts of the flow here. I think that things would start with a NOC device ("SDN Controller") sending out an M_DISCOVERY or M_FLOOD to discover the SPE node. (Maybe it already knows, and if so, then how?) This would have some kind of filter to say, "Answer if you are the resource that is on edge of the AS and has a route to Network-Service-Initiator" (which probably needs a label). well, that might not be exactly the right thing, but the point being is that these node*s* need to be found. There may be more than one! Then the ANS communication would occur with that discovered node. It would, as you say, negotiate the path. > [JD] Correct, this process is necessary in the entire program. But in the > network service auto-deployment scenario, this discovery mechanism has not > been changed, so I did not emphasize it in the text. Where do you think it is > more appropriate to add it? I don't know [I-D.ietf-spring-segment-routing] or [I-D.ietf-mpls] that well, but I didn't think that they included on-path (RSVP-like) discovery of route. Probably, I've missed something. > [JD] The routing protocol can advertise routes and calculate the optimal > route, which I understand should be regarded as a route discovery process. I > also would like to hear more of your thoughts on this point. Or do the P and PE node also need to respond and also be configured? > Abstract: > This document specifies an auto-deployment mechanism that deploys > resource-based network services through the Autonomic Control Plane > (ACP) in an Autonomic Network. This mechanism uses the GRASP in > [RFC8990] to exchange the information among the autonomic nodes so > that the resource among the service path can be coordinated. > Welcome to comment, review or contribute it. > Best wishes, > Joanna > _______________________________________________ > Anima mailing list > Anima@ietf.org > https://www.ietf.org/mailman/listinfo/anima -- Michael Richardson <mcr+i...@sandelman.ca> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide _______________________________________________ Anima mailing list Anima@ietf.org https://www.ietf.org/mailman/listinfo/anima
