Skip to main content

Telechat Review of draft-ietf-dmm-distributed-mobility-anchoring-14

Request Review of draft-ietf-dmm-distributed-mobility-anchoring
Requested revision No specific revision (document currently at 15)
Type Telechat Review
Team Internet Area Directorate (intdir)
Deadline 2020-03-03
Requested 2020-02-19
Requested by Éric Vyncke
Authors Anthony Chan , Xinpeng Wei , Jong-Hyouk Lee , Seil Jeon , Carlos J. Bernardos
I-D last updated 2020-02-28
Completed reviews Tsvart Last Call review of -13 by Yoshifumi Nishida (diff)
Opsdir Last Call review of -13 by Qin Wu (diff)
Secdir Last Call review of -13 by Joseph A. Salowey (diff)
Genart Last Call review of -13 by Paul Kyzivat (diff)
Intdir Telechat review of -14 by Carlos Pignataro (diff)
Secdir Telechat review of -14 by Joseph A. Salowey (diff)
Assignment Reviewer Carlos Pignataro
State Completed
Request Telechat review on draft-ietf-dmm-distributed-mobility-anchoring by Internet Area Directorate Assigned
Posted at
Reviewed revision 14 (document currently at 15)
Result Ready w/nits
Completed 2020-02-28
I am an assigned INT directorate reviewer for this Internet-Draft.  These
comments were written primarily for the benefit of the Internet Area Directors.
Document editors and shepherd(s) should treat these comments just like they
would treat comments from any other IETF contributors and resolve them along
with any other Last Call comments that have been received. For more details on
the INT Directorate, see

I hope these comments are clear and useful.

As requested, from the Internet area Directorate review, these two DMM
documents are being reviewed together:
* draft-ietf-dmm-distributed-mobility-anchoring-14
* draft-ietf-dmm-pmipv6-dlif-05

This document defines distributed mobility anchoring, in terms of the
different configurations and functions to provide IP mobility support,
including network-based or host-based mobility support.

The intended status is Informational. It is a very well written and
comprehensive document. It is technically sound.

No major or minor issues.


A set of small nits for your consideration.

1.  Introduction

   As a Mobile Node (MN) attaches to an access router and establishes a
   link between them, a /64 IPv6 prefix anchored to the router may be
   assigned to the link for exclusive use by the MN [RFC6459].  The MN
   may then configure a global IPv6 address from this prefix and use it
   as the source IP address in a flow to communicate with its
   correspondent node (CN).

s/correspondent node/Correspondent Node/

2.  Conventions and Terminology

   These include terms such as mobile node (MN), correspondent node
   (CN), home agent (HA), home address (HoA), care-of-address (CoA),
   local mobility anchor (LMA), and mobile access gateway (MAG).

Capitalize “Mobile Node” (as per § 1), “Corespondent Node”, etc.

Similar within this same § 2, “mobile router”, etc.
Same throughout the document (e.g., “router advertisement (RA)”)

4.3.  Mobility case, anchor relocation

   The IP prefix/address anchoring may move without changing the IP
   prefix/address of the flow.  Here the LM and FM functions in Figure 1
   in Section 3.1 are implemented as shown in Figure 7.

“Figure 1 in Section 3.1.1 are implemented”

                         Figure 7: Anchor mobility

Should this figure’s label be “Anchor Relocation” instead of ‘Anchor mobility”?

5.  Security Considerations

   As stated in [RFC7333], "a DMM solution MUST supportany security

s/supportany/support any/

8.2. Informative References

The relationship of this document and draft-ietf-dmm-deployment-models is
mostly clear, thank you for that.

I hope you fid these comments useful.

Carlos Pignataro.