Re: [DMM] FW: I-D Action: draft-ietf-dmm-deployment-models-01.txt

Do Truong Xuan <thespring1989@gmail.com> Thu, 21 September 2017 08:38 UTC

Return-Path: <thespring1989@gmail.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBDB5134461 for <dmm@ietfa.amsl.com>; Thu, 21 Sep 2017 01:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.748
X-Spam-Level:
X-Spam-Status: No, score=-0.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 sUYTAzBu96mD for <dmm@ietfa.amsl.com>; Thu, 21 Sep 2017 01:38:28 -0700 (PDT)
Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C607B134460 for <dmm@ietf.org>; Thu, 21 Sep 2017 01:38:26 -0700 (PDT)
Received: by mail-wr0-x233.google.com with SMTP id o42so3956239wrb.3 for <dmm@ietf.org>; Thu, 21 Sep 2017 01:38:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=AY2LM8X43wDWpcHps6HUDokGbOP8xfzC4S9c1UBcjDc=; b=IpKr7jnFLTDryxXNJS7m7CW8Ww92f9xuemZOkIY1F7gr5e8en/gbB6p19H/+luH6g/ RpCd4EYKYDoKUuM/XrZ2egahghxeksIG0Ztdf5bLKsIWUhR2iUYeCHeUqKGjtN1sVa75 ZctX4xFxFVF+t15VzGN0qXnGYvVi8hnguTxXRypn+KJoVY2GmhpjnVmH9Iekry3KlmHd 68i6V8RKrMen9AjyUhOIbtUDu0k2/sM9SWwcfC1rt3Lbi1pgeLwvhuooceJz30zD8aIp KoWPJ3RcJTe7ZC3HYY4HlJof5q5ABrvp75h0ajWUCUZfhu2aaCC3wqK5V4na5xIzeVFs cOqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=AY2LM8X43wDWpcHps6HUDokGbOP8xfzC4S9c1UBcjDc=; b=J99Pg/fVBcoJmM6Gt3BrkXDZnA4TDt27YfEyxpwOKMNUOVOoOST0oF1dK4dJ6mbCV7 NOBjCbGNTcI2eKROytwZWsZXJX78GA5AVbDEmwmW/umMmPH3A7rE078acYE647/3ORcC l89Wtry98yA/Ug0i3WePrFXAlU6QigUH2TE72kjvMSkZxqRx2gFOuRFK4UBOPCA3G2DW 0fMforISt8b/V0Zi71O7v8XxAWmovG6/dUoJtJHJbHbhczOAh7ZwR05Q5WnWfGRc1mj4 QFEusRn5wWrYaBvLkXpP0w6Xp1ARP4/xU/ApWC6Avydiyk5+uQXEoekNy1QD0edjyvNC v1cw==
X-Gm-Message-State: AHPjjUhX1t8bqC2bJaNWkmyM6WykuJ86ngX+nOtsYzUCBz5TFCmJ2nuc sbIoC9Teb3+BLV6k3+b82bo/cigpJnIeE7y4MNM=
X-Google-Smtp-Source: AOwi7QADnhy8rHeW57T02oCEgERWNA8/tX0U/fSEEzeogwEAYFtM5v18T7XhZJppd1uThiZ5BPqLri0rNJZgtl/n+rc=
X-Received: by 10.223.174.150 with SMTP id y22mr1218560wrc.29.1505983105187; Thu, 21 Sep 2017 01:38:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.149.6 with HTTP; Thu, 21 Sep 2017 01:38:24 -0700 (PDT)
In-Reply-To: <00dd01d331df$c4a4a970$4dedfc50$@gmail.com>
References: <CALnYAC6cqmktQOnnNcYSs5YH-n38bNUJ-JibHRqBHkEYo0RfpQ@mail.gmail.com> <00dd01d331df$c4a4a970$4dedfc50$@gmail.com>
From: Do Truong Xuan <thespring1989@gmail.com>
Date: Thu, 21 Sep 2017 17:38:24 +0900
Message-ID: <CALnYAC4K9tjMDTSeXD9-zzkGa038bhgyDc-yX9zUNONg2MEp5w@mail.gmail.com>
To: Seil Jeon <seiljeon@gmail.com>
Cc: dmm@ietf.org
Content-Type: multipart/alternative; boundary="001a1140b18205c3c60559af04dd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/WuhXx0A66HEte2gYrBJRi8ilDkA>
Subject: Re: [DMM] FW: I-D Action: draft-ietf-dmm-deployment-models-01.txt
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Sep 2017 08:38:30 -0000

Please see inline,

On Wed, Sep 20, 2017 at 4:12 PM, Seil Jeon <seiljeon@gmail.com> wrote:

> Hi Xuan,
>
>
>
> Thanks for your comments.
>
> Please see inline.
>
>
>
> Regards,
>
> Seil Jeon
>
>
>
>
>
> *From:* Do Truong Xuan [mailto:thespring1989@gmail.com]
> *Sent:* Wednesday, September 20, 2017 12:19 AM
> *To:* seiljeon@gmail.com; dmm@ietf.org
> *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
>
> + 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
>
> 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

xuan@dcn.ssu.ac.kr