Hi Dirk,
Thanks to your useful feeback, making this draft better improve. See inline, please for my response. Regards, Seil Jeon *From:* [email protected] [mailto:[email protected]] *Sent:* Thursday, September 21, 2017 12:58 AM *To:* [email protected]; [email protected] *Cc:* [email protected] *Subject:* RE: [DMM] FW: I-D Action: draft-ietf-dmm-deployment-models-01.txt Dear Seil, Finally I remembered that I promised a review. I am sorry for the delay! Overall I think the draft is well written and useful. Thanks! [SJ] Thanks, I think Sri (as a WT leader before) did a good job, organizing and translating various ideas of the WT members into a draft. Some nits have been detected already by Xuan … in addition: ‘seperated’ should be replaced by ‘separated’ and ‘and where as’ by simply ‘whereas’. [SJ] Many thanks. We’ll do fix it. I would recommend to give the explicit reference where NSH is mentioned and also introduce the acronyms MC and RC for Mobility and Routing Controller, respectively, to improve readability. [SJ] Actually, the reference for NSH was given in Terminology, but we’ll do it again where needed. The extension of MC and RC will be given in a next update. Furthermore I wonder whether MC and RC denoted as DMM functions in the table Figure 1 are not included in the mapping table Figure 2. E.g. I would think in 3GPP they are located at MME-CPA and -CPN … What do you think? [SJ] Looking at the role of mobility management control including the selection of SGW/PGW by MME, MME (MME-CPA) as well as PGW-CPA will be mapped to Home-CPA. I think MME-CPA should be enough. Does it make sense to you? Thanks! Best Regards Dirk *From:* dmm [mailto:[email protected] <[email protected]>] *On Behalf Of *Seil Jeon *Sent:* Mittwoch, 20. September 2017 09:12 *To:* 'Do Truong Xuan' *Cc:* [email protected] *Subject:* Re: [DMM] FW: I-D Action: draft-ietf-dmm-deployment-models-01.txt Hi Xuan, Thanks for your comments. Please see inline. Regards, Seil Jeon *From:* Do Truong Xuan [mailto:[email protected] <[email protected]>] *Sent:* Wednesday, September 20, 2017 12:19 AM *To:* [email protected]; [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 + 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. + 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”. 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,
_______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
