Re: I-D Action: draft-ietf-dmm-requirements-07.txt

Thanks for the comments. We are replying under different sections in separate emails. More emails will follow.
-----------------------------------------------
We accept your comment to Section 2 and added the explanation of a few terms there in version 08. Please check.

2.1.  Terminology

   All the general mobility-related terms and their acronyms used in
   this document are to be interpreted as defined in the Mobile IPv6
   base specification [RFC6275], in the Proxy mobile IPv6 specification
   [RFC5213], and in Mobility Related Terminology [RFC3753].  These
   terms include the following: mobile node (MN), correspondent node
   (CN), and home agent (HA) as per [RFC6275]; local mobility anchor
   (LMA) and mobile access gateway (MAG) as per [RFC5213], and context
   as per [RFC3753].

   In addition, this draft introduces the following terms.

   Centrally deployed mobility anchors
      refer to the mobility management deployments in which there are
      very few mobility anchors and the traffic of millions of mobile
      nodes in an operator network are managed by the same anchor.

   Centralized mobility management
      makes use of centrally deployed mobility anchors.

   Distributed mobility management
      is not centralized so that traffic does not need to traverse
      centrally deployed mobility anchors.

   Flat mobile network
      has few levels of routing hierarchy introduced into the data path
      by the mobility management system.

   Mobility context
      is the collection of information required to provide mobility
      management support for a given mobile node.

The following have contributed to the revisions in draft 08: Pierrick, Dapeng, and Jouni


From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Sri Gundavelli (sgundave)
Sent: Sunday, August 25, 2013 10:04 PM
To: [email protected]<mailto:[email protected]>
Subject: Re: [DMM] I-D Action: draft-ietf-dmm-requirements-07.txt

Please see inline for some comments.

Regards
Sri


2.  Conventions used in this document



2.1.  Terminology



   All the general mobility-related terms and their acronyms used in

   this document are to be interpreted as defined in the Mobile IPv6

   base specification [RFC6275], in the Proxy mobile IPv6 specification

   [RFC5213], and in Mobility Related Terminology [RFC3753].  These

   terms include the following: mobile node (MN), correspondent node

   (CN), and home agent (HA) as per [RFC6275]; local mobility anchor

   (LMA) and mobile access gateway (MAG) as per [RFC5213], and context

   as per [RFC3753].



   In addition, this draft introduces the following term.



   Mobility context



      is the collection of information required to provide mobility

      management support for a given mobile node.





[Sri] There needs to be some definition of "centrally deployed mobility anchor". This term is used through-out the document. What is central, what is local ? Even in the so called, "centralized anchor models", a gateway can be enabled locally. Ex: LMA/MAG, PGW/SGW functions can exist on the same node.


Accept and added explanation of this term. Also added the explanation of a few other terms.

_______________________________________________
dmm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmm