Re: comments on draft-ietf-dmm-requirements-02

h chan <[email protected]>
Newsgroups gmane.ietf.nemo
Message-ID <6E31144C030982429702B11D6746B98C364A0403__48410.6799857274$1356130045$gmane$org@SZXEML510-MBS.china.huawei.com>
Revised paragraph in Section 3.2:

   Mobility management may be partially or fully distributed.  In the
   former case only the data plane is distributed.  Fully distributed
   mobility management implies that both the data plane and the control
   plane are distributed.  These different approaches are described in
   detail in [I-D.yokota-dmm-scenario].  While mobility management can
   be distributed, it is not necessary for other functions to be
   similarly distributed.  For example, a centralized subscription
   management may co-exist with distributed mobility management.


H Anthony Chan


-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of jouni korhonen
Sent: Monday, November 12, 2012 3:33 PM
To: [email protected]
Subject: [DMM] comments on draft-ietf-dmm-requirements-02

Hi,

<as an individual contributor and not wearing any hats>

In Section 3.2

  "..
   former case only the data plane is distributed.  Fully distributed
   mobility management implies that both the data plane and the control
   plane are distributed.  These different approaches are described in
   .."

 o Would it be OK to mention here that even if full distribution could be achieved
   for the mobility part of the system, some parts are still going to be centralized
   or just geographically replicated at best? Here I mean functions like
   subscriber management, subscription databases and network access authentication.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.