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

"Seil Jeon" <seiljeon@gmail.com> Wed, 20 September 2017 07:12 UTC

Return-Path: <seiljeon@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 B2E0F133044 for <dmm@ietfa.amsl.com>; Wed, 20 Sep 2017 00:12:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level:
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 kTeFlryyCIpp for <dmm@ietfa.amsl.com>; Wed, 20 Sep 2017 00:12:10 -0700 (PDT)
Received: from mail-pg0-x235.google.com (mail-pg0-x235.google.com [IPv6:2607:f8b0:400e:c05::235]) (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 61A1813301E for <dmm@ietf.org>; Wed, 20 Sep 2017 00:12:10 -0700 (PDT)
Received: by mail-pg0-x235.google.com with SMTP id v23so1229258pgc.5 for <dmm@ietf.org>; Wed, 20 Sep 2017 00:12:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:thread-index:content-language; bh=O86o8E7QkMl7Z3t+VTnDvU3wo+mtw5K0YGN1ZOCm358=; b=LnpuObWh2zf6lKBdbwKiYO/iEmi2VuW+yYtmCEGjdBObGajJnMf5494LVcMvLwZaEm wKisG68P74sFxj8vX7iH/h0yPH9KSUXR5U/inUkIYtogKYr4TmEkaujwb83d8O4zHGMn bBXDGmGIFbhkTuRMxFgfHF8igm5DdURK6t31A1s87R3XcJ9FpTeRYKhca5NdLFzUqpi7 ifQ9VOxD7XJnwqPiZ42bqQ4osuFFUTxBGPrNUnbg8BFPBKLv2+brhqK1elAoS7/qXa1x m9MS7RVBbu0GdnhA+lYD2O4Q/i8vfy+SW7ZGfVWehvEaJoA+bKTZ5CjmbmJPf8sVFWzc iJAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:thread-index:content-language; bh=O86o8E7QkMl7Z3t+VTnDvU3wo+mtw5K0YGN1ZOCm358=; b=c2+Ig3xvNXYiDyKwoLpjb3jIx29Cwr4TWcLeitXICWYWdUApWByU0cD5KC2MS3oWRz ZWVeqKzaHnntIbIMopGzXGx32jqOYWi4mhqJaMEO9y5clYrMsbbrdTiC3ZG+Zx2rOlXw QZuKBAB2Ix54OMDnftz0UuCKL9r6Q6moLCvPD5JjPXsM+ZNaFmniolL1goxcrYqbh2Fn yNbxeRd6IapUybzd2m1Cc2tfMr9ZeiKcP4IfpTRBf5Fb+LwhTvB6+Q6qB2rVLgx6YRfq r72l78IaNeLYhKTpnqBiFTvX54rYwYh1fHaVkHlG7vgwOaYSjQvOO3Se6mF/CHUeho35 i36Q==
X-Gm-Message-State: AHPjjUhQcIxxvB4HkIjq9iSkFpOjanl+FQuLwXeD/OweKaOmuasBoC7f k7qrpahgS6kvc7PVpbuFq9XhpQ==
X-Google-Smtp-Source: AOwi7QAHgaItCbkh/c+iB8ByegxuaoqDluF909ds6tuzBu4Ir8DzDD2vtnT87epZHzY60846L9sbdw==
X-Received: by 10.99.191.6 with SMTP id v6mr1256418pgf.284.1505891529765; Wed, 20 Sep 2017 00:12:09 -0700 (PDT)
Received: from LAPTOPFOEU10F0 ([115.145.171.163]) by smtp.gmail.com with ESMTPSA id c85sm6147939pfj.118.2017.09.20.00.12.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Sep 2017 00:12:09 -0700 (PDT)
From: Seil Jeon <seiljeon@gmail.com>
To: 'Do Truong Xuan' <thespring1989@gmail.com>
Cc: dmm@ietf.org
References: <CALnYAC6cqmktQOnnNcYSs5YH-n38bNUJ-JibHRqBHkEYo0RfpQ@mail.gmail.com>
In-Reply-To: <CALnYAC6cqmktQOnnNcYSs5YH-n38bNUJ-JibHRqBHkEYo0RfpQ@mail.gmail.com>
Date: Wed, 20 Sep 2017 16:12:04 +0900
Message-ID: <00dd01d331df$c4a4a970$4dedfc50$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00DE_01D3322B.348E4D40"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQH34Zvqq2cwPBeDrziEVV+ap/7iAqJz+Fwg
Content-Language: en-us
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmm/CfiNuWARkA3xG3ifJ1O32Kn_vUo>
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: Wed, 20 Sep 2017 07:12:12 -0000

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 

 

+ 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,