Hi Xuan,
Thanks. Please have a look inline. Regards, Seil Jeon From: Do Truong Xuan [mailto:[email protected]] Sent: Thursday, September 21, 2017 5:38 PM To: Seil Jeon Cc: [email protected] Subject: Re: [DMM] FW: I-D Action: draft-ietf-dmm-deployment-models-01.txt Please see inline, On Wed, Sep 20, 2017 at 4:12 PM, Seil Jeon <[email protected] <mailto:[email protected]> > wrote: Hi Xuan, Thanks for your comments. Please see inline. Regards, Seil Jeon From: Do Truong Xuan [mailto:[email protected] <mailto:[email protected]> ] Sent: Wednesday, September 20, 2017 12:19 AM To: [email protected] <mailto:[email protected]> ; [email protected] <mailto:[email protected]> Subject: Re: [DMM] FW: I-D Action: draft-ietf-dmm-deployment-models-01.txt Dear Seil ! I have some comments on deployment architecture document as follows: + In the Figure 1, the authors mentioned about primitive function "NSH classifier" supported by H-DPA or A-DPN, could you elaborate more how this service could support DMM. NSH classifiers (for SFC) will at data-plane entities, i.e., DPA and/or DPN, which will be deployed in a distributed manner. For the functionality of DPA and DPN in terms of SFC, you can find what context data is maintained by the FPC Agent at 4.3.2.1. and 4.3.2.2. in https://tools.ietf.org/html/draft-ietf-dmm-fpc-cpdp-08 ==> IMO, I don't see any relations between NSH classifiers and mobility management [SJ] It was given to describe the functionality of DPA and DPN. But I see your concern. We’ll address it in a next update. + Other service primitive such as IP management, IP anchoring, mobility controller deserve more explanation to better understand the DMM functions IP management means IP address assignment and management. The mobility controller itself is given to call a control entity which can be different depending on the model introduced. In Model-3, we call the combined home-CPA and access-CPN a mobility controller. In the on-demand control plane orchestration mode, it is called an orchestrator of all the mobility-related control-plane and data-plane anchors/nodes. ==> OK + In Section 4.3, model 3, IMO this is centralized architecture for signaling and distributed for data plane functions similar to SDN architecture. However, in description text, authors wrote "this is a flat architecture" --> need more elaboration You need to look at the relationship between the access node and home-DPA for the meaning of “flat architecture”. ==> maybe H-DPA and A-DPN are distributed but how about control plane, you mean flat arch is only for dataplane [SJ] Doesn’t necessarily “only”. But enough to call it. Some other spelling errors: + in Section 3.2.1, homd-dpa --> home-dpa Wow! Will be fixed in a next update. + Section 3.2.5, DMM function --> DMM functions O.K BRs, -- Truong-Xuan, Do PHD Candidate DCN Lab, Soongsil University (+82) 10 4473 6869 [email protected] <mailto:[email protected]>
_______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
