WikiStart: Diff draft-ietf-dmm-best-practices-gap-analysis-03.txt - draft-ietf-dmm-best-practices-gap-analysis-03cep-v2.txt.htm

File Diff draft-ietf-dmm-best-practices-gap-analysis-03.txt - draft-ietf-dmm-best-practices-gap-analysis-03cep-v2.txt.htm, 218.6 KB (added by charliep@…, 8 years ago)

rfcdiff output showing suggested editorial changes for draft-ietf-dmm-best-practices-gap-analysis-03.txt

Line 
1<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
2<!-- saved from url=(0048)http://tools.ietf.org/tools/rfcdiff/rfcdiff.pyht -->
3<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> 
4   
5  <meta http-equiv="Content-Style-Type" content="text/css">
6  <title>Diff: draft-ietf-dmm-best-practices-gap-analysis-03.txt - draft-ietf-dmm-best-practices-gap-analysis-03cep-v2.txt</title>
7  <style type="text/css">
8    body    { margin: 0.4ex; margin-right: auto; }
9    tr      { }
10    td      { white-space: pre; font-family: monospace; vertical-align: top; font-size: 0.86em;}
11    th      { font-size: 0.86em; }
12    .small  { font-size: 0.6em; font-style: italic; font-family: Verdana, Helvetica, sans-serif; }
13    .left   { background-color: #EEE; }
14    .right  { background-color: #FFF; }
15    .diff   { background-color: #CCF; }
16    .lblock { background-color: #BFB; }
17    .rblock { background-color: #FF8; }
18    .insert { background-color: #8FF; }
19    .delete { background-color: #ACF; }
20    .void   { background-color: #FFB; }
21    .cont   { background-color: #EEE; }
22    .linebr { background-color: #AAA; }
23    .lineno { color: red; background-color: #FFF; font-size: 0.7em; text-align: right; padding: 0 2px; }
24    .elipsis{ background-color: #AAA; }
25    .left .cont { background-color: #DDD; }
26    .right .cont { background-color: #EEE; }
27    .lblock .cont { background-color: #9D9; }
28    .rblock .cont { background-color: #DD6; }
29    .insert .cont { background-color: #0DD; }
30    .delete .cont { background-color: #8AD; }
31    .stats, .stats td, .stats th { background-color: #EEE; padding: 2px 0; }
32  </style>
33</head>
34<body> 
35  <table border="0" cellpadding="0" cellspacing="0">
36  <tbody><tr bgcolor="orange"><th></th><th><a href="http://tools.ietf.org/rfcdiff?url2=draft-ietf-dmm-best-practices-gap-analysis-03.txt" style="color:#008; text-decoration:none;">&lt;</a>&nbsp;<a href="http://tools.ietf.org/html/draft-ietf-dmm-best-practices-gap-analysis-03.txt" style="color:#008">draft-ietf-dmm-best-practices-gap-analysis-03.txt</a>&nbsp;</th><th> </th><th>&nbsp;<a href="http://tools.ietf.org/html/draft-ietf-dmm-best-practices-gap-analysis-03cep-v2.txt" style="color:#008">draft-ietf-dmm-best-practices-gap-analysis-03cep-v2.txt</a>&nbsp;<a href="http://tools.ietf.org/rfcdiff?url1=draft-ietf-dmm-best-practices-gap-analysis-03cep-v2.txt" style="color:#008; text-decoration:none;">&gt;</a></th><th></th></tr>
37      <tr><td><a name="diff0001"></a></td></tr>
38      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: Need to avoid the presumption that only 3GPP and 802.11 matter</span></td><td class="lineno" valign="top"></td></tr>
39      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">       = Host route / BGP solutions also should be considered for gaps</span></td><td class="lineno" valign="top"></td></tr>
40      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">       = IoT is coming</span></td><td class="lineno" valign="top"></td></tr>
41      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">       = 802.15 is not out of the running</span></td><td class="lineno" valign="top"></td></tr>
42      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">       = Danger of overlooking a viable alternative solution</span></td><td class="lineno" valign="top"></td></tr>
43      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">       = Should also compare against FMIP.</span></td><td class="lineno" valign="top"></td></tr>
44      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
45      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: Should point out the role of identity management / authentication</span></td><td class="lineno" valign="top"></td></tr>
46      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
47      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: Do existing approaches to DMM properly handle flow management?</span></td><td class="lineno" valign="top"></td></tr>
48      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
49      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: "distributed mobility management environment" ... *not*</span></td><td class="lineno" valign="top"></td></tr>
50      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">       = should use, e.g., "from the standpoint of satisfying DMM requirements"</span></td><td class="lineno" valign="top"></td></tr>
51      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
52      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: "delegate" may be inaccurate; as used here, "advertise" or "assigned"</span></td><td class="lineno" valign="top"></td></tr>
53      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">     seems better</span></td><td class="lineno" valign="top"></td></tr>
54      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
55      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: Does not seem wise to invite arguments about whether configuration and</span></td><td class="lineno" valign="top"></td></tr>
56      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">     advertisement of routing prefixes happens on control plan or management</span></td><td class="lineno" valign="top"></td></tr>
57      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">     plane.</span></td><td class="lineno" valign="top"></td></tr>
58      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
59      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: need to define "flatness", flatten, flat network, etc.</span></td><td class="lineno" valign="top"></td></tr>
60      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
61      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: Probably better to consider "client location management" and</span></td><td class="lineno" valign="top"></td></tr>
62      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">     "server location management" separately.  Even better, this</span></td><td class="lineno" valign="top"></td></tr>
63      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">     concept could be substantially reworked to emphasize the role of</span></td><td class="lineno" valign="top"></td></tr>
64      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">     both parties in managing the "mobility association" or "binding".</span></td><td class="lineno" valign="top"></td></tr>
65      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">     For instance, "LMs" ==&gt; "binding manager" and</span></td><td class="lineno" valign="top"></td></tr>
66      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">       "LMc" ==&gt; "location reporter"</span></td><td class="lineno" valign="top"></td></tr>
67      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
68      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: Why is the concept of "proxy" introduced in this discussion?  Does</span></td><td class="lineno" valign="top"></td></tr>
69      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">     it help with any of the gap analysis?  MAP is not a proxy because it</span></td><td class="lineno" valign="top"></td></tr>
70      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">     is a signaling partner for the mobile node.</span></td><td class="lineno" valign="top"></td></tr>
71      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
72      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: Replace "Routing Management" by "Forwarding Management".</span></td><td class="lineno" valign="top"></td></tr>
73      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
74      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: Should avoid the presumption that all readers are "3GPP-literate"...</span></td><td class="lineno" valign="top"></td></tr>
75      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
76      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: Security Considerations are needed.  Distributed processing quite</span></td><td class="lineno" valign="top"></td></tr>
77      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">     often introduces complicated security problems, which deserve attention</span></td><td class="lineno" valign="top"></td></tr>
78      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">     in this document.  In fact, distributed security should rightfully</span></td><td class="lineno" valign="top"></td></tr>
79      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">     considered a "gap" insofar as current mechanisms are geared towards</span></td><td class="lineno" valign="top"></td></tr>
80      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">     centralized solutions.</span></td><td class="lineno" valign="top"></td></tr>
81      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
82      <tr><td class="lineno" valign="top"></td><td class="left">DMM                                                          D. Liu, Ed.</td><td> </td><td class="right">DMM                                                          D. Liu, Ed.</td><td class="lineno" valign="top"></td></tr>
83      <tr><td class="lineno" valign="top"></td><td class="left">Internet-Draft                                              China Mobile</td><td> </td><td class="right">Internet-Draft                                              China Mobile</td><td class="lineno" valign="top"></td></tr>
84      <tr><td class="lineno" valign="top"></td><td class="left">Intended status: Informational                           JC. Zuniga, Ed.</td><td> </td><td class="right">Intended status: Informational                           JC. Zuniga, Ed.</td><td class="lineno" valign="top"></td></tr>
85      <tr><td class="lineno" valign="top"></td><td class="left">Expires: August 18, 2014                                    InterDigital</td><td> </td><td class="right">Expires: August 18, 2014                                    InterDigital</td><td class="lineno" valign="top"></td></tr>
86      <tr><td class="lineno" valign="top"></td><td class="left">                                                                P. Seite</td><td> </td><td class="right">                                                                P. Seite</td><td class="lineno" valign="top"></td></tr>
87      <tr><td class="lineno" valign="top"></td><td class="left">                                                                  Orange</td><td> </td><td class="right">                                                                  Orange</td><td class="lineno" valign="top"></td></tr>
88      <tr><td class="lineno" valign="top"></td><td class="left">                                                                 H. Chan</td><td> </td><td class="right">                                                                 H. Chan</td><td class="lineno" valign="top"></td></tr>
89      <tr><td class="lineno" valign="top"></td><td class="left">                                                     Huawei Technologies</td><td> </td><td class="right">                                                     Huawei Technologies</td><td class="lineno" valign="top"></td></tr>
90      <tr><td class="lineno" valign="top"></td><td class="left">                                                           CJ. Bernardos</td><td> </td><td class="right">                                                           CJ. Bernardos</td><td class="lineno" valign="top"></td></tr>
91      <tr><td class="lineno" valign="top"></td><td class="left">                                                                    UC3M</td><td> </td><td class="right">                                                                    UC3M</td><td class="lineno" valign="top"></td></tr>
92      <tr><td class="lineno" valign="top"></td><td class="left">                                                       February 14, 2014</td><td> </td><td class="right">                                                       February 14, 2014</td><td class="lineno" valign="top"></td></tr>
93      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
94      <tr><td class="lineno" valign="top"></td><td class="left">  Distributed Mobility Management: Current practices and gap analysis</td><td> </td><td class="right">  Distributed Mobility Management: Current practices and gap analysis</td><td class="lineno" valign="top"></td></tr>
95      <tr><td class="lineno" valign="top"></td><td class="left">             draft-ietf-dmm-best-practices-gap-analysis-03</td><td> </td><td class="right">             draft-ietf-dmm-best-practices-gap-analysis-03</td><td class="lineno" valign="top"></td></tr>
96      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
97      <tr><td class="lineno" valign="top"></td><td class="left">Abstract</td><td> </td><td class="right">Abstract</td><td class="lineno" valign="top"></td></tr>
98      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
99      <tr><td><a name="diff0002"></a></td></tr>
100      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">The present document analyzes deployment</span> practices of existing IP</td><td> </td><td class="rblock">   <span class="insert">Deployment</span> practices of <span class="insert">certain</span> existing IP mobility protocols <span class="insert">are</span></td><td class="lineno" valign="top"></td></tr>
101      <tr><td class="lineno" valign="top"></td><td class="lblock">   mobility protocols <span class="delete">in a</span> distributed mobility management <span class="delete">environment.</span></td><td> </td><td class="rblock"><span class="insert">   analyzed to determine whether or not requirements for</span></td><td class="lineno" valign="top"></td></tr>
102      <tr><td class="lineno" valign="top"></td><td class="lblock">   It <span class="delete">then</span> identifies existing limitations when compared to <span class="delete">the</span></td><td> </td><td class="rblock">   distributed mobility management <span class="insert">solution are satisfied.</span></td><td class="lineno" valign="top"></td></tr>
103      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   requirements defined for a distributed mobility management solution.</span></td><td> </td><td class="rblock">   It identifies existing limitations <span class="insert">(gaps)</span> when compared to <span class="insert">those</span></td><td class="lineno" valign="top"></td></tr>
104      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   requirements.</span></td><td class="lineno" valign="top"></td></tr>
105      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
106      <tr><td class="lineno" valign="top"></td><td class="left">Status of This Memo</td><td> </td><td class="right">Status of This Memo</td><td class="lineno" valign="top"></td></tr>
107      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
108      <tr><td class="lineno" valign="top"></td><td class="left">   This Internet-Draft is submitted in full conformance with the</td><td> </td><td class="right">   This Internet-Draft is submitted in full conformance with the</td><td class="lineno" valign="top"></td></tr>
109      <tr><td class="lineno" valign="top"></td><td class="left">   provisions of BCP 78 and BCP 79.</td><td> </td><td class="right">   provisions of BCP 78 and BCP 79.</td><td class="lineno" valign="top"></td></tr>
110      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
111      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are working documents of the Internet Engineering</td><td> </td><td class="right">   Internet-Drafts are working documents of the Internet Engineering</td><td class="lineno" valign="top"></td></tr>
112      <tr><td class="lineno" valign="top"></td><td class="left">   Task Force (IETF).  Note that other groups may also distribute</td><td> </td><td class="right">   Task Force (IETF).  Note that other groups may also distribute</td><td class="lineno" valign="top"></td></tr>
113      <tr><td class="lineno" valign="top"></td><td class="left">   working documents as Internet-Drafts.  The list of current Internet-</td><td> </td><td class="right">   working documents as Internet-Drafts.  The list of current Internet-</td><td class="lineno" valign="top"></td></tr>
114      <tr><td class="lineno" valign="top"></td><td class="left">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td> </td><td class="right">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td class="lineno" valign="top"></td></tr>
115      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
116      <tr bgcolor="gray"><td></td><th><a name="part-l2"><small>skipping to change at</small><em> page 3, line 15</em></a></th><th> </th><th><a name="part-r2"><small>skipping to change at</small><em> page 3, line 15</em></a></th><td></td></tr>
117      <tr><td class="lineno" valign="top"></td><td class="left">   environment.  Section 4 presents the current practices of IP flat</td><td> </td><td class="right">   environment.  Section 4 presents the current practices of IP flat</td><td class="lineno" valign="top"></td></tr>
118      <tr><td class="lineno" valign="top"></td><td class="left">   wireless networks and 3GPP architectures.  Both network- and host-</td><td> </td><td class="right">   wireless networks and 3GPP architectures.  Both network- and host-</td><td class="lineno" valign="top"></td></tr>
119      <tr><td class="lineno" valign="top"></td><td class="left">   based mobility protocols are considered.  Section 5 presents the gap</td><td> </td><td class="right">   based mobility protocols are considered.  Section 5 presents the gap</td><td class="lineno" valign="top"></td></tr>
120      <tr><td class="lineno" valign="top"></td><td class="left">   analysis with respect to the current practices.</td><td> </td><td class="right">   analysis with respect to the current practices.</td><td class="lineno" valign="top"></td></tr>
121      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
122      <tr><td class="lineno" valign="top"></td><td class="left">2.  Terminology</td><td> </td><td class="right">2.  Terminology</td><td class="lineno" valign="top"></td></tr>
123      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
124      <tr><td class="lineno" valign="top"></td><td class="left">   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td> </td><td class="right">   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td class="lineno" valign="top"></td></tr>
125      <tr><td class="lineno" valign="top"></td><td class="left">   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this</td><td> </td><td class="right">   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this</td><td class="lineno" valign="top"></td></tr>
126      <tr><td class="lineno" valign="top"></td><td class="left">   document are to be interpreted as described in [RFC2119].</td><td> </td><td class="right">   document are to be interpreted as described in [RFC2119].</td><td class="lineno" valign="top"></td></tr>
127      <tr><td><a name="diff0003"></a></td></tr>
128      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: Would prefer not to use this...</span></td><td class="lineno" valign="top"></td></tr>
129      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
130      <tr><td class="lineno" valign="top"></td><td class="left">   All general mobility-related terms and their acronyms used in this</td><td> </td><td class="right">   All general mobility-related terms and their acronyms used in this</td><td class="lineno" valign="top"></td></tr>
131      <tr><td class="lineno" valign="top"></td><td class="left">   document are to be interpreted as defined in the Mobile IPv6 base</td><td> </td><td class="right">   document are to be interpreted as defined in the Mobile IPv6 base</td><td class="lineno" valign="top"></td></tr>
132      <tr><td class="lineno" valign="top"></td><td class="left">   specification [RFC6275] and in the Proxy mobile IPv6 specification</td><td> </td><td class="right">   specification [RFC6275] and in the Proxy mobile IPv6 specification</td><td class="lineno" valign="top"></td></tr>
133      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5213].  These terms include mobile node (MN), correspondent node</td><td> </td><td class="right">   [RFC5213].  These terms include mobile node (MN), correspondent node</td><td class="lineno" valign="top"></td></tr>
134      <tr><td class="lineno" valign="top"></td><td class="left">   (CN), home agent (HA), local mobility anchor (LMA), and mobile access</td><td> </td><td class="right">   (CN), home agent (HA), local mobility anchor (LMA), and mobile access</td><td class="lineno" valign="top"></td></tr>
135      <tr><td class="lineno" valign="top"></td><td class="left">   gateway (MAG).</td><td> </td><td class="right">   gateway (MAG).</td><td class="lineno" valign="top"></td></tr>
136      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
137      <tr><td class="lineno" valign="top"></td><td class="left">   In addition, this document also introduces some definitions of IP</td><td> </td><td class="right">   In addition, this document also introduces some definitions of IP</td><td class="lineno" valign="top"></td></tr>
138      <tr><td class="lineno" valign="top"></td><td class="left">   mobility functions in Section 3.</td><td> </td><td class="right">   mobility functions in Section 3.</td><td class="lineno" valign="top"></td></tr>
139      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
140      <tr><td class="lineno" valign="top"></td><td class="left">   In this document there are also references to a "distributed mobility</td><td> </td><td class="right">   In this document there are also references to a "distributed mobility</td><td class="lineno" valign="top"></td></tr>
141      <tr><td class="lineno" valign="top"></td><td class="left">   management environment".  By this term, we refer to a scenario in</td><td> </td><td class="right">   management environment".  By this term, we refer to a scenario in</td><td class="lineno" valign="top"></td></tr>
142      <tr><td class="lineno" valign="top"></td><td class="left">   which the IP mobility, access network and routing solutions allow for</td><td> </td><td class="right">   which the IP mobility, access network and routing solutions allow for</td><td class="lineno" valign="top"></td></tr>
143      <tr><td class="lineno" valign="top"></td><td class="left">   setting up IP networks so that traffic is distributed in an optimal</td><td> </td><td class="right">   setting up IP networks so that traffic is distributed in an optimal</td><td class="lineno" valign="top"></td></tr>
144      <tr><td><a name="diff0004"></a></td></tr>
145      <tr><td class="lineno" valign="top"></td><td class="lblock">   way, <span class="delete">without relying</span> on centrally deployed anchors to manage IP</td><td> </td><td class="rblock">   way, <span class="insert">reducing the reliance</span> on centrally deployed anchors to manage IP</td><td class="lineno" valign="top"></td></tr>
146      <tr><td class="lineno" valign="top"></td><td class="left">   mobility sessions.</td><td> </td><td class="right">   mobility sessions.</td><td class="lineno" valign="top"></td></tr>
147      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
148      <tr><td class="lineno" valign="top"></td><td class="left">3.  Functions of existing mobility protocols</td><td> </td><td class="right">3.  Functions of existing mobility protocols</td><td class="lineno" valign="top"></td></tr>
149      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
150      <tr><td class="lineno" valign="top"></td><td class="left">   The host-based Mobile IPv6 [RFC6275] and its network-based extension,</td><td> </td><td class="right">   The host-based Mobile IPv6 [RFC6275] and its network-based extension,</td><td class="lineno" valign="top"></td></tr>
151      <tr><td class="lineno" valign="top"></td><td class="left">   PMIPv6 [RFC5213], are both logically centralized mobility management</td><td> </td><td class="right">   PMIPv6 [RFC5213], are both logically centralized mobility management</td><td class="lineno" valign="top"></td></tr>
152      <tr><td class="lineno" valign="top"></td><td class="left">   approaches addressing primarily hierarchical mobile networks.</td><td> </td><td class="right">   approaches addressing primarily hierarchical mobile networks.</td><td class="lineno" valign="top"></td></tr>
153      <tr><td><a name="diff0005"></a></td></tr>
154      <tr><td class="lineno" valign="top"></td><td class="lblock">   Although <span class="delete">they</span> are centralized approaches, they have important</td><td> </td><td class="rblock">   Although <span class="insert">these two</span> are centralized approaches, they have important</td><td class="lineno" valign="top"></td></tr>
155      <tr><td class="lineno" valign="top"></td><td class="lblock">   mobility management <span class="delete">functions resulting from years of extensive work</span></td><td> </td><td class="rblock">   mobility management functions.  It is therefore useful to</td><td class="lineno" valign="top"></td></tr>
156      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   to develop and to extend these</span> functions.  It is therefore useful to</td><td> </td><td class="rblock">   take these existing functions and examine them in</td><td class="lineno" valign="top"></td></tr>
157      <tr><td class="lineno" valign="top"></td><td class="lblock">   take these existing functions and examine them in <span class="delete">a DMM scenario in</span></td><td> </td><td class="rblock">   order to understand how to deploy the existing mobility protocols <span class="insert">to</span></td><td class="lineno" valign="top"></td></tr>
158      <tr><td class="lineno" valign="top"></td><td class="lblock">   order to understand how to deploy the existing mobility protocols <span class="delete">in</span></td><td> </td><td class="rblock"><span class="insert">   provide</span> distributed mobility <span class="insert">management.  We also consider HMIPv6[RFC5380]</span></td><td class="lineno" valign="top"></td></tr>
159      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   a</span> distributed mobility <span class="delete">management environment.</span></td><td> </td><td class="rblock"><span class="insert">   since it enables distributed anchor management.</span></td><td class="lineno" valign="top"></td></tr>
160      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
161      <tr><td class="lineno" valign="top"></td><td class="left">   The main mobility management functions of MIPv6, PMIPv6, and HMIPv6</td><td> </td><td class="right">   The main mobility management functions of MIPv6, PMIPv6, and HMIPv6</td><td class="lineno" valign="top"></td></tr>
162      <tr><td class="lineno" valign="top"></td><td class="left">   are the following:</td><td> </td><td class="right">   are the following:</td><td class="lineno" valign="top"></td></tr>
163      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
164      <tr><td class="lineno" valign="top"></td><td class="left">   1.  Anchoring function (AF): allocation to a mobile node of an IP</td><td> </td><td class="right">   1.  Anchoring function (AF): allocation to a mobile node of an IP</td><td class="lineno" valign="top"></td></tr>
165      <tr><td><a name="diff0006"></a></td></tr>
166      <tr><td class="lineno" valign="top"></td><td class="lblock">       <span class="delete">address/prefix (e.g., a</span> Home Address or Home Network <span class="delete">Prefix)</span></td><td> </td><td class="rblock">       <span class="insert">address (a</span> Home Address <span class="insert">(HoA))/</span> or <span class="insert">prefix (a</span> Home Network <span class="insert">Prefix(HNP))</span></td><td class="lineno" valign="top"></td></tr>
167      <tr><td class="lineno" valign="top"></td><td class="lblock">       topologically anchored by the <span class="delete">delegating</span> node (i.e., the anchor</td><td> </td><td class="rblock">       topologically anchored by the <span class="insert">advertising</span> node (i.e., the anchor</td><td class="lineno" valign="top"></td></tr>
168      <tr><td class="lineno" valign="top"></td><td class="left">       node is able to advertise a connected route into the routing</td><td> </td><td class="right">       node is able to advertise a connected route into the routing</td><td class="lineno" valign="top"></td></tr>
169      <tr><td><a name="diff0007"></a></td></tr>
170      <tr><td class="lineno" valign="top"></td><td class="lblock">       infrastructure for the <span class="delete">delegated</span> IP prefixes).  <span class="delete">It is a control</span></td><td> </td><td class="rblock">       infrastructure for the <span class="insert">allocated</span> IP prefixes).</td><td class="lineno" valign="top"></td></tr>
171      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">       plane function.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
172      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
173      <tr><td class="lineno" valign="top"></td><td class="left">   2.  Internetwork Location Management (LM) function: managing and</td><td> </td><td class="right">   2.  Internetwork Location Management (LM) function: managing and</td><td class="lineno" valign="top"></td></tr>
174      <tr><td class="lineno" valign="top"></td><td class="left">       keeping track of the internetwork location of an MN.  The</td><td> </td><td class="right">       keeping track of the internetwork location of an MN.  The</td><td class="lineno" valign="top"></td></tr>
175      <tr><td><a name="diff0008"></a></td></tr>
176      <tr><td class="lineno" valign="top"></td><td class="lblock">       location information may be a mapping of the IP <span class="delete">delegat</span>ed address</td><td> </td><td class="rblock">       location information may be a mapping of the IP <span class="insert">advertis</span>ed address</td><td class="lineno" valign="top"></td></tr>
177      <tr><td class="lineno" valign="top"></td><td class="left">       /prefix (e.g., HoA or HNP) to the IP routing address of the MN or</td><td> </td><td class="right">       /prefix (e.g., HoA or HNP) to the IP routing address of the MN or</td><td class="lineno" valign="top"></td></tr>
178      <tr><td class="lineno" valign="top"></td><td class="left">       of a node that can forward packets destined to the MN.  It is a</td><td> </td><td class="right">       of a node that can forward packets destined to the MN.  It is a</td><td class="lineno" valign="top"></td></tr>
179      <tr><td class="lineno" valign="top"></td><td class="left">       control plane function.</td><td> </td><td class="right">       control plane function.</td><td class="lineno" valign="top"></td></tr>
180      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
181      <tr><td><a name="diff0009"></a></td></tr>
182      <tr><td class="lineno" valign="top"></td><td class="lblock">       In a client-server <span class="delete">model of the system</span>, location query and update</td><td> </td><td class="rblock">       In a client-server <span class="insert">protocol model</span>, location query and update</td><td class="lineno" valign="top"></td></tr>
183      <tr><td class="lineno" valign="top"></td><td class="left">       messages may be exchanged between the client (LMc) and the server</td><td> </td><td class="right">       messages may be exchanged between the client (LMc) and the server</td><td class="lineno" valign="top"></td></tr>
184      <tr><td class="lineno" valign="top"></td><td class="left">       (LMs).</td><td> </td><td class="right">       (LMs).</td><td class="lineno" valign="top"></td></tr>
185      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
186      <tr><td><a name="diff0010"></a></td></tr>
187      <tr><td class="lineno" valign="top"></td><td class="lblock">       O<span class="delete">ptionally, one (or more) proxy</span> may exist between the LMs and the</td><td> </td><td class="rblock">       O<span class="insert">ne or more proxy agents</span> may exist between the LMs and the</td><td class="lineno" valign="top"></td></tr>
188      <tr><td class="lineno" valign="top"></td><td class="left">       LMc, i.e., LMs-proxy-LMc.  Then, to the LMs, the proxy behaves</td><td> </td><td class="right">       LMc, i.e., LMs-proxy-LMc.  Then, to the LMs, the proxy behaves</td><td class="lineno" valign="top"></td></tr>
189      <tr><td class="lineno" valign="top"></td><td class="left">       like the LMc; to the LMc, the proxy behaves like the LMs.</td><td> </td><td class="right">       like the LMc; to the LMc, the proxy behaves like the LMs.</td><td class="lineno" valign="top"></td></tr>
190      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
191      <tr><td class="lineno" valign="top"></td><td class="left">   3.  Routing management (RM) function: packet interception and</td><td> </td><td class="right">   3.  Routing management (RM) function: packet interception and</td><td class="lineno" valign="top"></td></tr>
192      <tr><td><a name="diff0011"></a></td></tr>
193      <tr><td class="lineno" valign="top"></td><td class="lblock">       forwarding to/from the IP address/prefix <span class="delete">delegat</span>ed to the MN,</td><td> </td><td class="rblock">       forwarding to/from the IP address/prefix <span class="insert">assign</span>ed to the MN,</td><td class="lineno" valign="top"></td></tr>
194      <tr><td class="lineno" valign="top"></td><td class="left">       based on the internetwork location information, either to the</td><td> </td><td class="right">       based on the internetwork location information, either to the</td><td class="lineno" valign="top"></td></tr>
195      <tr><td class="lineno" valign="top"></td><td class="left">       destination or to some other network element that knows how to</td><td> </td><td class="right">       destination or to some other network element that knows how to</td><td class="lineno" valign="top"></td></tr>
196      <tr><td class="lineno" valign="top"></td><td class="left">       forward the packets to their destination.</td><td> </td><td class="right">       forward the packets to their destination.</td><td class="lineno" valign="top"></td></tr>
197      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
198      <tr><td class="lineno" valign="top"></td><td class="left">       RM may optionally be split into the control plane (RM-CP) and</td><td> </td><td class="right">       RM may optionally be split into the control plane (RM-CP) and</td><td class="lineno" valign="top"></td></tr>
199      <tr><td class="lineno" valign="top"></td><td class="left">       data plane (RM-DP).</td><td> </td><td class="right">       data plane (RM-DP).</td><td class="lineno" valign="top"></td></tr>
200      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
201      <tr><td><a name="diff0012"></a></td></tr>
202      <tr><td class="lineno" valign="top"></td><td class="lblock">   In Mobile IPv6<span class="delete"> [RFC6275]</span>, the home agent (HA) typically provides the</td><td> </td><td class="rblock">   In Mobile IPv6, the home agent (HA) typically provides the</td><td class="lineno" valign="top"></td></tr>
203      <tr><td class="lineno" valign="top"></td><td class="left">   anchoring function (AF); the location management server (LMs) is at</td><td> </td><td class="right">   anchoring function (AF); the location management server (LMs) is at</td><td class="lineno" valign="top"></td></tr>
204      <tr><td class="lineno" valign="top"></td><td class="left">   the HA while the location management client (LMc) is at the MN; the</td><td> </td><td class="right">   the HA while the location management client (LMc) is at the MN; the</td><td class="lineno" valign="top"></td></tr>
205      <tr><td class="lineno" valign="top"></td><td class="left">   routing management (RM) function is both ends of tunneling at the HA</td><td> </td><td class="right">   routing management (RM) function is both ends of tunneling at the HA</td><td class="lineno" valign="top"></td></tr>
206      <tr><td class="lineno" valign="top"></td><td class="left">   and the MN.</td><td> </td><td class="right">   and the MN.</td><td class="lineno" valign="top"></td></tr>
207      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
208      <tr><td><a name="diff0013"></a></td></tr>
209      <tr><td class="lineno" valign="top"></td><td class="lblock">   In Proxy Mobile IPv6<span class="delete"> [RFC5213]</span>, the Local Mobility Anchor (LMA)</td><td> </td><td class="rblock">   In Proxy Mobile IPv6, the Local Mobility Anchor (LMA)</td><td class="lineno" valign="top"></td></tr>
210      <tr><td class="lineno" valign="top"></td><td class="left">   provides the anchoring function (AF); the location management server</td><td> </td><td class="right">   provides the anchoring function (AF); the location management server</td><td class="lineno" valign="top"></td></tr>
211      <tr><td class="lineno" valign="top"></td><td class="left">   (LMs) is at the LMA while the location management client (LMc) is at</td><td> </td><td class="right">   (LMs) is at the LMA while the location management client (LMc) is at</td><td class="lineno" valign="top"></td></tr>
212      <tr><td class="lineno" valign="top"></td><td class="left">   the mobile access gateway (MAG); the routing management (RM) function</td><td> </td><td class="right">   the mobile access gateway (MAG); the routing management (RM) function</td><td class="lineno" valign="top"></td></tr>
213      <tr><td class="lineno" valign="top"></td><td class="left">   is both ends of tunneling at the HA and the MAG.</td><td> </td><td class="right">   is both ends of tunneling at the HA and the MAG.</td><td class="lineno" valign="top"></td></tr>
214      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
215      <tr><td><a name="diff0014"></a></td></tr>
216      <tr><td class="lineno" valign="top"></td><td class="lblock">   In Hirarchical <span class="delete">mobile</span> IPv6 <span class="delete">(HMIPv6) [RFC5380], a location management</span></td><td> </td><td class="rblock">   In Hirarchical <span class="insert">Mobile</span> IPv6 <span class="insert">(HMIPv6),</span> the mobility anchor point (MAP)</td><td class="lineno" valign="top"></td></tr>
217      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   proxy is at</span> the mobility anchor point (MAP) <span class="delete">to proxy</span> between the LMs</td><td> </td><td class="rblock">   <span class="insert">serves as a location management aggregator</span> between the LMs</td><td class="lineno" valign="top"></td></tr>
218      <tr><td class="lineno" valign="top"></td><td class="lblock">   at the <span class="delete">LMA</span> and the LMc at the MN.  The MAP also has RM <span class="delete">funtion</span> to</td><td> </td><td class="rblock">   at the <span class="insert">HA</span> and the LMc at the MN.  The MAP also has RM <span class="insert">function</span> to</td><td class="lineno" valign="top"></td></tr>
219      <tr><td class="lineno" valign="top"></td><td class="lblock">   enable tunneling between <span class="delete">LMA</span> and itself as well as tunneling between</td><td> </td><td class="rblock">   enable tunneling between <span class="insert">HA</span> and itself as well as tunneling between</td><td class="lineno" valign="top"></td></tr>
220      <tr><td class="lineno" valign="top"></td><td class="left">   MN and itself.</td><td> </td><td class="right">   MN and itself.</td><td class="lineno" valign="top"></td></tr>
221      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
222      <tr><td class="lineno" valign="top"></td><td class="left">4.  DMM practices</td><td> </td><td class="right">4.  DMM practices</td><td class="lineno" valign="top"></td></tr>
223      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
224      <tr><td class="lineno" valign="top"></td><td class="left">   This section documents deployment practices of existing mobility</td><td> </td><td class="right">   This section documents deployment practices of existing mobility</td><td class="lineno" valign="top"></td></tr>
225      <tr><td class="lineno" valign="top"></td><td class="left">   protocols in a distributed mobility management environment.  This</td><td> </td><td class="right">   protocols in a distributed mobility management environment.  This</td><td class="lineno" valign="top"></td></tr>
226      <tr><td class="lineno" valign="top"></td><td class="left">   description is divided into two main families of network</td><td> </td><td class="right">   description is divided into two main families of network</td><td class="lineno" valign="top"></td></tr>
227      <tr><td class="lineno" valign="top"></td><td class="left">   architectures: i) IP flat wireless networks (e.g., evolved Wi-Fi</td><td> </td><td class="right">   architectures: i) IP flat wireless networks (e.g., evolved Wi-Fi</td><td class="lineno" valign="top"></td></tr>
228      <tr><td class="lineno" valign="top"></td><td class="left">   hotspots) and, ii) 3GPP network flattening approaches.</td><td> </td><td class="right">   hotspots) and, ii) 3GPP network flattening approaches.</td><td class="lineno" valign="top"></td></tr>
229      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
230      <tr><td class="lineno" valign="top"></td><td class="left">   While describing the current DMM practices, references to the generic</td><td> </td><td class="right">   While describing the current DMM practices, references to the generic</td><td class="lineno" valign="top"></td></tr>
231      <tr><td class="lineno" valign="top"></td><td class="left">   mobility management functions described in Section 3 are provided, as</td><td> </td><td class="right">   mobility management functions described in Section 3 are provided, as</td><td class="lineno" valign="top"></td></tr>
232      <tr><td class="lineno" valign="top"></td><td class="left">   well as some initial hints on the identified gaps with respect to the</td><td> </td><td class="right">   well as some initial hints on the identified gaps with respect to the</td><td class="lineno" valign="top"></td></tr>
233      <tr><td class="lineno" valign="top"></td><td class="left">   DMM requirements documented in [I-D.ietf-dmm-requirements].</td><td> </td><td class="right">   DMM requirements documented in [I-D.ietf-dmm-requirements].</td><td class="lineno" valign="top"></td></tr>
234      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
235      <tr><td class="lineno" valign="top"></td><td class="left">4.1.  Assumptions</td><td> </td><td class="right">4.1.  Assumptions</td><td class="lineno" valign="top"></td></tr>
236      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
237      <tr><td class="lineno" valign="top"></td><td class="left">   There are many different approaches that can be considered to</td><td> </td><td class="right">   There are many different approaches that can be considered to</td><td class="lineno" valign="top"></td></tr>
238      <tr><td class="lineno" valign="top"></td><td class="left">   implement and deploy a distributed anchoring and mobility solution.</td><td> </td><td class="right">   implement and deploy a distributed anchoring and mobility solution.</td><td class="lineno" valign="top"></td></tr>
239      <tr><td><a name="diff0015"></a></td></tr>
240      <tr><td class="lineno" valign="top"></td><td class="lblock">   The focus of the gap analysis is on current mobile network</td><td> </td><td class="rblock">   The focus of the gap analysis is on c<span class="insert">ertain c</span>urrent mobile network</td><td class="lineno" valign="top"></td></tr>
241      <tr><td class="lineno" valign="top"></td><td class="left">   architectures and standardized IP mobility solutions, considering any</td><td> </td><td class="right">   architectures and standardized IP mobility solutions, considering any</td><td class="lineno" valign="top"></td></tr>
242      <tr><td class="lineno" valign="top"></td><td class="left">   kind of deployment options which do not violate the original protocol</td><td> </td><td class="right">   kind of deployment options which do not violate the original protocol</td><td class="lineno" valign="top"></td></tr>
243      <tr><td class="lineno" valign="top"></td><td class="left">   specifications.  In order to limit the scope of our analysis of</td><td> </td><td class="right">   specifications.  In order to limit the scope of our analysis of</td><td class="lineno" valign="top"></td></tr>
244      <tr><td><a name="diff0016"></a></td></tr>
245      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">current </span>DMM practices, we consider the following list of technical</td><td> </td><td class="rblock">   DMM practices, we consider the following list of technical</td><td class="lineno" valign="top"></td></tr>
246      <tr><td class="lineno" valign="top"></td><td class="left">   assumptions:</td><td> </td><td class="right">   assumptions:</td><td class="lineno" valign="top"></td></tr>
247      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
248      <tr><td><a name="diff0017"></a></td></tr>
249      <tr><td class="lineno" valign="top"></td><td class="lblock">   1.  Both host- and network-based solutions <span class="delete">SHOULD</span> be considered.</td><td> </td><td class="rblock">   1.  Both host- and network-based solutions <span class="insert">should</span> be considered.</td><td class="lineno" valign="top"></td></tr>
250      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
251      <tr><td><a name="diff0018"></a></td></tr>
252      <tr><td class="lineno" valign="top"></td><td class="lblock">   2.  Solutions <span class="delete">SHOULD</span> allow selecting and using the most appropriate</td><td> </td><td class="rblock">   2.  Solutions <span class="insert">should</span> allow selecting and using the most appropriate</td><td class="lineno" valign="top"></td></tr>
253      <tr><td class="lineno" valign="top"></td><td class="lblock">       IP anchor among a set of available <span class="delete">ones.</span></td><td> </td><td class="rblock">       IP anchor among a set of available <span class="insert">candidates.</span></td><td class="lineno" valign="top"></td></tr>
254      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
255      <tr><td><a name="diff0019"></a></td></tr>
256      <tr><td class="lineno" valign="top"></td><td class="lblock">   3.  Mobility management <span class="delete">SHOULD</span> be realized by the preservation of the</td><td> </td><td class="rblock">   3.  Mobility management <span class="insert">should</span> be realized by the preservation of the</td><td class="lineno" valign="top"></td></tr>
257      <tr><td class="lineno" valign="top"></td><td class="left">       IP address across the different points of attachment (i.e.,</td><td> </td><td class="right">       IP address across the different points of attachment (i.e.,</td><td class="lineno" valign="top"></td></tr>
258      <tr><td><a name="diff0020"></a></td></tr>
259      <tr><td class="lineno" valign="top"></td><td class="lblock">       provision of IP address continuity).</td><td> </td><td class="rblock">       provision of IP address continuity).  <span class="insert">This is in contrast to</span></td><td class="lineno" valign="top"></td></tr>
260      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">       certain transport-layer based approaches such as SCTP or</span></td><td class="lineno" valign="top"></td></tr>
261      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">       application-layer mobility.</span></td><td class="lineno" valign="top"></td></tr>
262      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
263      <tr><td class="lineno" valign="top"></td><td class="left">   Applications which can cope with changes in the MN's IP address do</td><td> </td><td class="right">   Applications which can cope with changes in the MN's IP address do</td><td class="lineno" valign="top"></td></tr>
264      <tr><td class="lineno" valign="top"></td><td class="left">   not depend on IP mobility management protocols such as DMM.</td><td> </td><td class="right">   not depend on IP mobility management protocols such as DMM.</td><td class="lineno" valign="top"></td></tr>
265      <tr><td class="lineno" valign="top"></td><td class="left">   Typically, a connection manager together with the operating system</td><td> </td><td class="right">   Typically, a connection manager together with the operating system</td><td class="lineno" valign="top"></td></tr>
266      <tr><td class="lineno" valign="top"></td><td class="left">   will configure the source address selection mechanism of the IP</td><td> </td><td class="right">   will configure the source address selection mechanism of the IP</td><td class="lineno" valign="top"></td></tr>
267      <tr><td class="lineno" valign="top"></td><td class="left">   stack.  This might involve identifying application capabilities and</td><td> </td><td class="right">   stack.  This might involve identifying application capabilities and</td><td class="lineno" valign="top"></td></tr>
268      <tr><td class="lineno" valign="top"></td><td class="left">   triggering the mobility support accordingly.  Further considerations</td><td> </td><td class="right">   triggering the mobility support accordingly.  Further considerations</td><td class="lineno" valign="top"></td></tr>
269      <tr><td class="lineno" valign="top"></td><td class="left">   on application management and source address selection are out of the</td><td> </td><td class="right">   on application management and source address selection are out of the</td><td class="lineno" valign="top"></td></tr>
270      <tr><td><a name="diff0021"></a></td></tr>
271      <tr><td class="lineno" valign="top"></td><td class="lblock">   scope of this <span class="delete">document.</span></td><td> </td><td class="rblock">   scope of this <span class="insert">document, but the reader might consult</span></td><td class="lineno" valign="top"></td></tr>
272      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   [RFC-SourceAddrSelection].</span></td><td class="lineno" valign="top"></td></tr>
273      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
274      <tr><td class="lineno" valign="top"></td><td class="left">4.2.  IP flat wireless network</td><td> </td><td class="right">4.2.  IP flat wireless network</td><td class="lineno" valign="top"></td></tr>
275      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
276      <tr><td class="lineno" valign="top"></td><td class="left">   This section focuses on common IP wireless network architectures and</td><td> </td><td class="right">   This section focuses on common IP wireless network architectures and</td><td class="lineno" valign="top"></td></tr>
277      <tr><td class="lineno" valign="top"></td><td class="left">   how they can be flattened from an IP mobility and anchoring point of</td><td> </td><td class="right">   how they can be flattened from an IP mobility and anchoring point of</td><td class="lineno" valign="top"></td></tr>
278      <tr><td class="lineno" valign="top"></td><td class="left">   view using common and standardized protocols.  We take Wi-Fi as an</td><td> </td><td class="right">   view using common and standardized protocols.  We take Wi-Fi as an</td><td class="lineno" valign="top"></td></tr>
279      <tr><td><a name="diff0022"></a></td></tr>
280      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">exemplary</span> wireless technology, since it is widely known and deployed</td><td> </td><td class="rblock">   <span class="insert">useful</span> wireless technology, since it is widely known and deployed</td><td class="lineno" valign="top"></td></tr>
281      <tr><td class="lineno" valign="top"></td><td class="left">   nowadays.  Some representative examples of Wi-Fi deployment</td><td> </td><td class="right">   nowadays.  Some representative examples of Wi-Fi deployment</td><td class="lineno" valign="top"></td></tr>
282      <tr><td class="lineno" valign="top"></td><td class="left">   architectures are depicted in Figure 1.</td><td> </td><td class="right">   architectures are depicted in Figure 1.</td><td class="lineno" valign="top"></td></tr>
283      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
284      <tr><td class="lineno" valign="top"></td><td class="left">                    +-------------+             _----_</td><td> </td><td class="right">                    +-------------+             _----_</td><td class="lineno" valign="top"></td></tr>
285      <tr><td class="lineno" valign="top"></td><td class="left">   +---+            |   Access    |           _(      )_</td><td> </td><td class="right">   +---+            |   Access    |           _(      )_</td><td class="lineno" valign="top"></td></tr>
286      <tr><td class="lineno" valign="top"></td><td class="left">   |AAA|. . . . . . | Aggregation |----------( Internet )</td><td> </td><td class="right">   |AAA|. . . . . . | Aggregation |----------( Internet )</td><td class="lineno" valign="top"></td></tr>
287      <tr><td class="lineno" valign="top"></td><td class="left">   +---+            |   Gateway   |           (_      _)</td><td> </td><td class="right">   +---+            |   Gateway   |           (_      _)</td><td class="lineno" valign="top"></td></tr>
288      <tr><td class="lineno" valign="top"></td><td class="left">                    +-------------+             '----'</td><td> </td><td class="right">                    +-------------+             '----'</td><td class="lineno" valign="top"></td></tr>
289      <tr><td class="lineno" valign="top"></td><td class="left">                       |  |   |</td><td> </td><td class="right">                       |  |   |</td><td class="lineno" valign="top"></td></tr>
290      <tr><td class="lineno" valign="top"></td><td class="left">                       |  |   +-------------+</td><td> </td><td class="right">                       |  |   +-------------+</td><td class="lineno" valign="top"></td></tr>
291      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
292      <tr bgcolor="gray"><td></td><th><a name="part-l3"><small>skipping to change at</small><em> page 6, line 40</em></a></th><th> </th><th><a name="part-r3"><small>skipping to change at</small><em> page 6, line 40</em></a></th><td></td></tr>
293      <tr><td class="lineno" valign="top"></td><td class="left">                 Figure 1: IP Wi-Fi network architectures</td><td> </td><td class="right">                 Figure 1: IP Wi-Fi network architectures</td><td class="lineno" valign="top"></td></tr>
294      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
295      <tr><td class="lineno" valign="top"></td><td class="left">   In the figure, three typical deployment options are shown</td><td> </td><td class="right">   In the figure, three typical deployment options are shown</td><td class="lineno" valign="top"></td></tr>
296      <tr><td class="lineno" valign="top"></td><td class="left">   [I-D.gundavelli-v6ops-community-wifi-svcs].  On the left hand side of</td><td> </td><td class="right">   [I-D.gundavelli-v6ops-community-wifi-svcs].  On the left hand side of</td><td class="lineno" valign="top"></td></tr>
297      <tr><td class="lineno" valign="top"></td><td class="left">   the figure, mobile nodes directly connect to a Residential Gateway</td><td> </td><td class="right">   the figure, mobile nodes directly connect to a Residential Gateway</td><td class="lineno" valign="top"></td></tr>
298      <tr><td class="lineno" valign="top"></td><td class="left">   (RG) which is a network device at the customer premises and provides</td><td> </td><td class="right">   (RG) which is a network device at the customer premises and provides</td><td class="lineno" valign="top"></td></tr>
299      <tr><td class="lineno" valign="top"></td><td class="left">   both wireless layer-2 access connectivity (i.e., it hosts the 802.11</td><td> </td><td class="right">   both wireless layer-2 access connectivity (i.e., it hosts the 802.11</td><td class="lineno" valign="top"></td></tr>
300      <tr><td class="lineno" valign="top"></td><td class="left">   Access Point function) and layer-3 routing functions.  In the middle</td><td> </td><td class="right">   Access Point function) and layer-3 routing functions.  In the middle</td><td class="lineno" valign="top"></td></tr>
301      <tr><td class="lineno" valign="top"></td><td class="left">   of the figure, mobile nodes connect to Wi-Fi Access Points (APs) that</td><td> </td><td class="right">   of the figure, mobile nodes connect to Wi-Fi Access Points (APs) that</td><td class="lineno" valign="top"></td></tr>
302      <tr><td class="lineno" valign="top"></td><td class="left">   are managed by a WLAN Controller (WLC), which performs radio resource</td><td> </td><td class="right">   are managed by a WLAN Controller (WLC), which performs radio resource</td><td class="lineno" valign="top"></td></tr>
303      <tr><td><a name="diff0023"></a></td></tr>
304      <tr><td class="lineno" valign="top"></td><td class="lblock">   management on the APs, <span class="delete">system</span>-wide mobility policy enforcement and</td><td> </td><td class="rblock">   management on the APs, <span class="insert">domain</span>-wide mobility policy enforcement and</td><td class="lineno" valign="top"></td></tr>
305      <tr><td class="lineno" valign="top"></td><td class="left">   centralized forwarding function for the user traffic.  The WLC could</td><td> </td><td class="right">   centralized forwarding function for the user traffic.  The WLC could</td><td class="lineno" valign="top"></td></tr>
306      <tr><td class="lineno" valign="top"></td><td class="left">   also implement layer-3 routing functions, or attach to an access</td><td> </td><td class="right">   also implement layer-3 routing functions, or attach to an access</td><td class="lineno" valign="top"></td></tr>
307      <tr><td class="lineno" valign="top"></td><td class="left">   router (AR).  Last, on the right-hand side of the figure, access</td><td> </td><td class="right">   router (AR).  Last, on the right-hand side of the figure, access</td><td class="lineno" valign="top"></td></tr>
308      <tr><td class="lineno" valign="top"></td><td class="left">   points are directly connected to an access router.  This can also be</td><td> </td><td class="right">   points are directly connected to an access router.  This can also be</td><td class="lineno" valign="top"></td></tr>
309      <tr><td class="lineno" valign="top"></td><td class="left">   used as a generic connectivity model.</td><td> </td><td class="right">   used as a generic connectivity model.</td><td class="lineno" valign="top"></td></tr>
310      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
311      <tr><td><a name="diff0024"></a></td></tr>
312      <tr><td class="lineno" valign="top"></td><td class="lblock">   In some network architectures, such as the evolved Wi-Fi hotspot,</td><td> </td><td class="rblock">   In some network architectures, such as the evolved Wi-Fi hotspot<span class="insert">[CITATION!]</span>,</td><td class="lineno" valign="top"></td></tr>
313      <tr><td class="lineno" valign="top"></td><td class="left">   operators might make use of IP mobility protocols to provide mobility</td><td> </td><td class="right">   operators might make use of IP mobility protocols to provide mobility</td><td class="lineno" valign="top"></td></tr>
314      <tr><td class="lineno" valign="top"></td><td class="left">   support to users, for example to allow connecting the IP Wi-Fi</td><td> </td><td class="right">   support to users, for example to allow connecting the IP Wi-Fi</td><td class="lineno" valign="top"></td></tr>
315      <tr><td class="lineno" valign="top"></td><td class="left">   network to a mobile operator core and support roaming between WLAN</td><td> </td><td class="right">   network to a mobile operator core and support roaming between WLAN</td><td class="lineno" valign="top"></td></tr>
316      <tr><td class="lineno" valign="top"></td><td class="left">   and 3GPP accesses.  Two main protocols can be used: Proxy Mobile IPv6</td><td> </td><td class="right">   and 3GPP accesses.  Two main protocols can be used: Proxy Mobile IPv6</td><td class="lineno" valign="top"></td></tr>
317      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
318      <tr><td><a name="diff0025"></a></td></tr>
319      <tr><td class="lineno" valign="top"></td><td class="lblock">   [RFC5213] or Mobile IPv6 [RFC6275], [RFC5555], with the anchor (e.g.,</td><td> </td><td class="rblock">   [RFC5213] or Mobile IPv6 [RFC6275], [RFC5555],</td><td class="lineno" valign="top"></td></tr>
320      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: that's three, not two...</span></td><td class="lineno" valign="top"></td></tr>
321      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                  with the anchor (e.g.,</td><td class="lineno" valign="top"></td></tr>
322      <tr><td class="lineno" valign="top"></td><td class="left">   local mobility anchor or home agent) role typically being played by</td><td> </td><td class="right">   local mobility anchor or home agent) role typically being played by</td><td class="lineno" valign="top"></td></tr>
323      <tr><td class="lineno" valign="top"></td><td class="left">   the Access Aggregation Gateway or even by an entity placed in the</td><td> </td><td class="right">   the Access Aggregation Gateway or even by an entity placed in the</td><td class="lineno" valign="top"></td></tr>
324      <tr><td><a name="diff0026"></a></td></tr>
325      <tr><td class="lineno" valign="top"></td><td class="lblock">   mobile operator's core <span class="delete">network.</span></td><td> </td><td class="rblock"><span class="insert">CEP: *what* entity?</span></td><td class="lineno" valign="top"></td></tr>
326      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   mobile operator's core <span class="insert">network[CITATION!].</span></td><td class="lineno" valign="top"></td></tr>
327      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
328      <tr><td><a name="diff0027"></a></td></tr>
329      <tr><td class="lineno" valign="top"></td><td class="lblock">   Although this section has <span class="delete">adopted</span> the example of Wi-Fi networks,</td><td> </td><td class="rblock">   Although this section has <span class="insert">made use of</span> the example of Wi-Fi networks,</td><td class="lineno" valign="top"></td></tr>
330      <tr><td class="lineno" valign="top"></td><td class="left">   there are other IP flat wireless network architectures specified,</td><td> </td><td class="right">   there are other IP flat wireless network architectures specified,</td><td class="lineno" valign="top"></td></tr>
331      <tr><td class="lineno" valign="top"></td><td class="left">   such as WiMAX [IEEE.802-16.2009], which integrates both host and</td><td> </td><td class="right">   such as WiMAX [IEEE.802-16.2009], which integrates both host and</td><td class="lineno" valign="top"></td></tr>
332      <tr><td class="lineno" valign="top"></td><td class="left">   network-based IP mobility functionality.</td><td> </td><td class="right">   network-based IP mobility functionality.</td><td class="lineno" valign="top"></td></tr>
333      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
334      <tr><td class="lineno" valign="top"></td><td class="left">   Existing IP mobility protocols can also be deployed in a more</td><td> </td><td class="right">   Existing IP mobility protocols can also be deployed in a more</td><td class="lineno" valign="top"></td></tr>
335      <tr><td class="lineno" valign="top"></td><td class="left">   flattened manner, so that the anchoring and access aggregation</td><td> </td><td class="right">   flattened manner, so that the anchoring and access aggregation</td><td class="lineno" valign="top"></td></tr>
336      <tr><td><a name="diff0028"></a></td></tr>
337      <tr><td class="lineno" valign="top"></td><td class="lblock">   functions are distributed.  We next describe several practices for</td><td> </td><td class="rblock">   functions are distributed.</td><td class="lineno" valign="top"></td></tr>
338      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: The claimed consequence does not follow...</span></td><td class="lineno" valign="top"></td></tr>
339      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                               We next describe several practices for</td><td class="lineno" valign="top"></td></tr>
340      <tr><td class="lineno" valign="top"></td><td class="left">   the deployment of existing mobility protocols in a distributed</td><td> </td><td class="right">   the deployment of existing mobility protocols in a distributed</td><td class="lineno" valign="top"></td></tr>
341      <tr><td class="lineno" valign="top"></td><td class="left">   mobility management environment.  The analysis in this section is</td><td> </td><td class="right">   mobility management environment.  The analysis in this section is</td><td class="lineno" valign="top"></td></tr>
342      <tr><td class="lineno" valign="top"></td><td class="left">   limited to protocol solutions based on existing IP mobility</td><td> </td><td class="right">   limited to protocol solutions based on existing IP mobility</td><td class="lineno" valign="top"></td></tr>
343      <tr><td class="lineno" valign="top"></td><td class="left">   protocols, either host- or network-based, such as Mobile IPv6</td><td> </td><td class="right">   protocols, either host- or network-based, such as Mobile IPv6</td><td class="lineno" valign="top"></td></tr>
344      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC6275], [RFC5555], Proxy Mobile IPv6 [RFC5213], [RFC5844] and NEMO</td><td> </td><td class="right">   [RFC6275], [RFC5555], Proxy Mobile IPv6 [RFC5213], [RFC5844] and NEMO</td><td class="lineno" valign="top"></td></tr>
345      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC3963].  Extensions to these base protocol solutions are also</td><td> </td><td class="right">   [RFC3963].  Extensions to these base protocol solutions are also</td><td class="lineno" valign="top"></td></tr>
346      <tr><td class="lineno" valign="top"></td><td class="left">   considered.  We pay special attention to how to efficiently select</td><td> </td><td class="right">   considered.  We pay special attention to how to efficiently select</td><td class="lineno" valign="top"></td></tr>
347      <tr><td class="lineno" valign="top"></td><td class="left">   the source address (care-of-addresses versus home addresses) for</td><td> </td><td class="right">   the source address (care-of-addresses versus home addresses) for</td><td class="lineno" valign="top"></td></tr>
348      <tr><td><a name="diff0029"></a></td></tr>
349      <tr><td class="lineno" valign="top"></td><td class="lblock">   different types of communications.  The analysis is divided into two</td><td> </td><td class="rblock">   different types of communications.</td><td class="lineno" valign="top"></td></tr>
350      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: This contradicts the statement at the end of section 4.1.</span></td><td class="lineno" valign="top"></td></tr>
351      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                       The analysis is divided into two</td><td class="lineno" valign="top"></td></tr>
352      <tr><td class="lineno" valign="top"></td><td class="left">   parts: host- and network-based practices.</td><td> </td><td class="right">   parts: host- and network-based practices.</td><td class="lineno" valign="top"></td></tr>
353      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
354      <tr><td class="lineno" valign="top"></td><td class="left">4.2.1.  Host-based IP DMM practices</td><td> </td><td class="right">4.2.1.  Host-based IP DMM practices</td><td class="lineno" valign="top"></td></tr>
355      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
356      <tr><td class="lineno" valign="top"></td><td class="left">   Mobile IPv6 (MIPv6) [RFC6275] and its extension to support mobile</td><td> </td><td class="right">   Mobile IPv6 (MIPv6) [RFC6275] and its extension to support mobile</td><td class="lineno" valign="top"></td></tr>
357      <tr><td class="lineno" valign="top"></td><td class="left">   networks, the NEMO Basic Support protocol (hereafter, simply referred</td><td> </td><td class="right">   networks, the NEMO Basic Support protocol (hereafter, simply referred</td><td class="lineno" valign="top"></td></tr>
358      <tr><td class="lineno" valign="top"></td><td class="left">   to as NEMO) [RFC3963] are well-known host-based IP mobility</td><td> </td><td class="right">   to as NEMO) [RFC3963] are well-known host-based IP mobility</td><td class="lineno" valign="top"></td></tr>
359      <tr><td><a name="diff0030"></a></td></tr>
360      <tr><td class="lineno" valign="top"></td><td class="lblock">   protocols.  They <span class="delete">heavily rely </span>on the function of the Home Agent (HA),</td><td> </td><td class="rblock">   protocols.  They <span class="insert">depend up</span>on the function of the Home Agent (HA),</td><td class="lineno" valign="top"></td></tr>
361      <tr><td class="lineno" valign="top"></td><td class="left">   a centralized anchor, to provide mobile nodes (hosts and routers)</td><td> </td><td class="right">   a centralized anchor, to provide mobile nodes (hosts and routers)</td><td class="lineno" valign="top"></td></tr>
362      <tr><td class="lineno" valign="top"></td><td class="left">   with mobility support.  In these approaches, the home agent typically</td><td> </td><td class="right">   with mobility support.  In these approaches, the home agent typically</td><td class="lineno" valign="top"></td></tr>
363      <tr><td class="lineno" valign="top"></td><td class="left">   provides the anchoring function (AF), Routing management (RM), and</td><td> </td><td class="right">   provides the anchoring function (AF), Routing management (RM), and</td><td class="lineno" valign="top"></td></tr>
364      <tr><td class="lineno" valign="top"></td><td class="left">   Internetwork Location Management server (LMs) functions.  The mobile</td><td> </td><td class="right">   Internetwork Location Management server (LMs) functions.  The mobile</td><td class="lineno" valign="top"></td></tr>
365      <tr><td class="lineno" valign="top"></td><td class="left">   node possesses the Location management client (LMc) function and the</td><td> </td><td class="right">   node possesses the Location management client (LMc) function and the</td><td class="lineno" valign="top"></td></tr>
366      <tr><td class="lineno" valign="top"></td><td class="left">   RM function to enable tunneling between HA and itself.  We next</td><td> </td><td class="right">   RM function to enable tunneling between HA and itself.  We next</td><td class="lineno" valign="top"></td></tr>
367      <tr><td><a name="diff0031"></a></td></tr>
368      <tr><td class="lineno" valign="top"></td><td class="lblock">   describe some practices <span class="delete">on</span> how MIPv6/NEMO and several <span class="delete">additional</span></td><td> </td><td class="rblock">   describe some practices <span class="insert">that show</span> how MIPv6/NEMO and several <span class="insert">other</span></td><td class="lineno" valign="top"></td></tr>
369      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: Strange to cite NEMO as "host-based" mobility...  perhaps "client-based"?</span></td><td class="lineno" valign="top"></td></tr>
370      <tr><td class="lineno" valign="top"></td><td class="left">   protocol extensions can be deployed in a distributed mobility</td><td> </td><td class="right">   protocol extensions can be deployed in a distributed mobility</td><td class="lineno" valign="top"></td></tr>
371      <tr><td class="lineno" valign="top"></td><td class="left">   management environment.</td><td> </td><td class="right">   management environment.</td><td class="lineno" valign="top"></td></tr>
372      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
373      <tr><td class="lineno" valign="top"></td><td class="left">   One approach to distribute the anchors can be to deploy several HAs</td><td> </td><td class="right">   One approach to distribute the anchors can be to deploy several HAs</td><td class="lineno" valign="top"></td></tr>
374      <tr><td class="lineno" valign="top"></td><td class="left">   (as shown in Figure 2), and assign the topologically closest anchor</td><td> </td><td class="right">   (as shown in Figure 2), and assign the topologically closest anchor</td><td class="lineno" valign="top"></td></tr>
375      <tr><td class="lineno" valign="top"></td><td class="left">   to each MN [RFC4640], [RFC5026], [RFC6611].  In the example shown in</td><td> </td><td class="right">   to each MN [RFC4640], [RFC5026], [RFC6611].  In the example shown in</td><td class="lineno" valign="top"></td></tr>
376      <tr><td class="lineno" valign="top"></td><td class="left">   Figure 2, MN1 is assigned HA1 (and a home address anchored by HA1),</td><td> </td><td class="right">   Figure 2, MN1 is assigned HA1 (and a home address anchored by HA1),</td><td class="lineno" valign="top"></td></tr>
377      <tr><td class="lineno" valign="top"></td><td class="left">   while MN2 is assigned HA2.  Note that MIPv6/NEMO specifications do</td><td> </td><td class="right">   while MN2 is assigned HA2.  Note that MIPv6/NEMO specifications do</td><td class="lineno" valign="top"></td></tr>
378      <tr><td class="lineno" valign="top"></td><td class="left">   not prevent the simultaneous use of multiple home agents by a single</td><td> </td><td class="right">   not prevent the simultaneous use of multiple home agents by a single</td><td class="lineno" valign="top"></td></tr>
379      <tr><td class="lineno" valign="top"></td><td class="left">   mobile node.  This deployment model could be exploited by a mobile</td><td> </td><td class="right">   mobile node.  This deployment model could be exploited by a mobile</td><td class="lineno" valign="top"></td></tr>
380      <tr><td class="lineno" valign="top"></td><td class="left">   node to meet assumption #4 of Section 4.1 and use several anchors at</td><td> </td><td class="right">   node to meet assumption #4 of Section 4.1 and use several anchors at</td><td class="lineno" valign="top"></td></tr>
381      <tr><td class="lineno" valign="top"></td><td class="left">   the same time, each of them anchoring IP flows initiated at a</td><td> </td><td class="right">   the same time, each of them anchoring IP flows initiated at a</td><td class="lineno" valign="top"></td></tr>
382      <tr><td class="lineno" valign="top"></td><td class="left">   different point of attachment.  However there is no mechanism</td><td> </td><td class="right">   different point of attachment.  However there is no mechanism</td><td class="lineno" valign="top"></td></tr>
383      <tr><td class="lineno" valign="top"></td><td class="left">   specified by IETF to enable an efficient dynamic discovery of</td><td> </td><td class="right">   specified by IETF to enable an efficient dynamic discovery of</td><td class="lineno" valign="top"></td></tr>
384      <tr><td><a name="diff0032"></a></td></tr>
385      <tr><td class="lineno" valign="top"></td><td class="lblock">   available anchors and the selection of the most suitable one.  <span class="delete">Note</span></td><td> </td><td class="rblock">   available anchors and the selection of the most suitable one.</td><td class="lineno" valign="top"></td></tr>
386      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   that some</span> of these <span class="delete">mechanisms</span> have been defined outside <span class="delete">IETF (e.g.,</span></td><td> </td><td class="rblock">   <span class="insert">Some</span> of these <span class="insert">mechanisms[cite]</span> have been defined outside <span class="insert">IETF.</span></td><td class="lineno" valign="top"></td></tr>
387      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   3GPP).</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
388      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
389      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;- INTERNET -&gt; &lt;- HOME NETWORK -&gt; &lt;---- ACCESS NETWORK ----&gt;</td><td> </td><td class="right">   &lt;- INTERNET -&gt; &lt;- HOME NETWORK -&gt; &lt;---- ACCESS NETWORK ----&gt;</td><td class="lineno" valign="top"></td></tr>
390      <tr><td class="lineno" valign="top"></td><td class="left">      -------                          -------</td><td> </td><td class="right">      -------                          -------</td><td class="lineno" valign="top"></td></tr>
391      <tr><td class="lineno" valign="top"></td><td class="left">      | CN1 |         -------          | AR1 |-(o) zzzz (o)</td><td> </td><td class="right">      | CN1 |         -------          | AR1 |-(o) zzzz (o)</td><td class="lineno" valign="top"></td></tr>
392      <tr><td class="lineno" valign="top"></td><td class="left">      -------         | HA1 |          -------           |</td><td> </td><td class="right">      -------         | HA1 |          -------           |</td><td class="lineno" valign="top"></td></tr>
393      <tr><td class="lineno" valign="top"></td><td class="left">                      -------   (MN1 anchored at HA1) -------</td><td> </td><td class="right">                      -------   (MN1 anchored at HA1) -------</td><td class="lineno" valign="top"></td></tr>
394      <tr><td class="lineno" valign="top"></td><td class="left">                                       -------        | MN1 |</td><td> </td><td class="right">                                       -------        | MN1 |</td><td class="lineno" valign="top"></td></tr>
395      <tr><td class="lineno" valign="top"></td><td class="left">                                       | AR2 |-(o)    -------</td><td> </td><td class="right">                                       | AR2 |-(o)    -------</td><td class="lineno" valign="top"></td></tr>
396      <tr><td class="lineno" valign="top"></td><td class="left">                                       -------</td><td> </td><td class="right">                                       -------</td><td class="lineno" valign="top"></td></tr>
397      <tr><td class="lineno" valign="top"></td><td class="left">                      -------</td><td> </td><td class="right">                      -------</td><td class="lineno" valign="top"></td></tr>
398      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
399      <tr bgcolor="gray"><td></td><th><a name="part-l4"><small>skipping to change at</small><em> page 9, line 8</em></a></th><th> </th><th><a name="part-r4"><small>skipping to change at</small><em> page 9, line 8</em></a></th><td></td></tr>
400      <tr><td class="lineno" valign="top"></td><td class="left">   the direct path between them.  Using the example shown in Figure 2,</td><td> </td><td class="right">   the direct path between them.  Using the example shown in Figure 2,</td><td class="lineno" valign="top"></td></tr>
401      <tr><td class="lineno" valign="top"></td><td class="left">   MN1 is using BT mode with CN1 and MN2 is in RO mode with CN2.</td><td> </td><td class="right">   MN1 is using BT mode with CN1 and MN2 is in RO mode with CN2.</td><td class="lineno" valign="top"></td></tr>
402      <tr><td class="lineno" valign="top"></td><td class="left">   However, the RO mode has several drawbacks:</td><td> </td><td class="right">   However, the RO mode has several drawbacks:</td><td class="lineno" valign="top"></td></tr>
403      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
404      <tr><td class="lineno" valign="top"></td><td class="left">   o  The RO mode is only supported by Mobile IPv6.  There is no route</td><td> </td><td class="right">   o  The RO mode is only supported by Mobile IPv6.  There is no route</td><td class="lineno" valign="top"></td></tr>
405      <tr><td class="lineno" valign="top"></td><td class="left">      optimization support standardized for the NEMO protocol because of</td><td> </td><td class="right">      optimization support standardized for the NEMO protocol because of</td><td class="lineno" valign="top"></td></tr>
406      <tr><td class="lineno" valign="top"></td><td class="left">      the security problems posed by extending return routability tests</td><td> </td><td class="right">      the security problems posed by extending return routability tests</td><td class="lineno" valign="top"></td></tr>
407      <tr><td class="lineno" valign="top"></td><td class="left">      for prefixes, although many different solutions have been proposed</td><td> </td><td class="right">      for prefixes, although many different solutions have been proposed</td><td class="lineno" valign="top"></td></tr>
408      <tr><td class="lineno" valign="top"></td><td class="left">      [RFC4889].</td><td> </td><td class="right">      [RFC4889].</td><td class="lineno" valign="top"></td></tr>
409      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
410      <tr><td><a name="diff0033"></a></td></tr>
411      <tr><td class="lineno" valign="top"></td><td class="lblock">   o  The RO mode requires <span class="delete">additional signaling, which</span> adds some</td><td> </td><td class="rblock">   o  The RO mode requires <span class="insert">signaling that</span> adds some protocol overhead.</td><td class="lineno" valign="top"></td></tr>
412      <tr><td class="lineno" valign="top"></td><td class="lblock">      protocol overhead.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
413      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
414      <tr><td class="lineno" valign="top"></td><td class="left">   o  The signaling required to enable RO involves the home agent and is</td><td> </td><td class="right">   o  The signaling required to enable RO involves the home agent and is</td><td class="lineno" valign="top"></td></tr>
415      <tr><td class="lineno" valign="top"></td><td class="left">      repeated periodically for security reasons [RFC4225].  This</td><td> </td><td class="right">      repeated periodically for security reasons [RFC4225].  This</td><td class="lineno" valign="top"></td></tr>
416      <tr><td class="lineno" valign="top"></td><td class="left">      basically means that the HA remains a single point of failure,</td><td> </td><td class="right">      basically means that the HA remains a single point of failure,</td><td class="lineno" valign="top"></td></tr>
417      <tr><td class="lineno" valign="top"></td><td class="left">      because the Mobile IPv6 RO mode does not mean HA-less operation.</td><td> </td><td class="right">      because the Mobile IPv6 RO mode does not mean HA-less operation.</td><td class="lineno" valign="top"></td></tr>
418      <tr><td><a name="diff0034"></a></td></tr>
419      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: HA-less operation was intended to be enabled, but disallowed due</span></td><td class="lineno" valign="top"></td></tr>
420      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">       to security considerations.  If DMM wants HA-less operation, the</span></td><td class="lineno" valign="top"></td></tr>
421      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">       same security vulnerabilities will have to be mitigated.</span></td><td class="lineno" valign="top"></td></tr>
422      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
423      <tr><td><a name="diff0035"></a></td></tr>
424      <tr><td class="lineno" valign="top"></td><td class="lblock">   o  The RO mode requires <span class="delete">additional</span> support from the correspondent</td><td> </td><td class="rblock">   o  The RO mode requires support from the correspondent node (CN).</td><td class="lineno" valign="top"></td></tr>
425      <tr><td class="lineno" valign="top"></td><td class="lblock">      node (CN).</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
426      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
427      <tr><td class="lineno" valign="top"></td><td class="left">   Notwithstanding these considerations, the RO mode does offer the</td><td> </td><td class="right">   Notwithstanding these considerations, the RO mode does offer the</td><td class="lineno" valign="top"></td></tr>
428      <tr><td class="lineno" valign="top"></td><td class="left">   possibility of substantially reducing traffic through the Home Agent,</td><td> </td><td class="right">   possibility of substantially reducing traffic through the Home Agent,</td><td class="lineno" valign="top"></td></tr>
429      <tr><td class="lineno" valign="top"></td><td class="left">   in cases when it can be supported by the relevant correspondent</td><td> </td><td class="right">   in cases when it can be supported by the relevant correspondent</td><td class="lineno" valign="top"></td></tr>
430      <tr><td class="lineno" valign="top"></td><td class="left">   nodes.  Note that a mobile node can also use its CoA directly</td><td> </td><td class="right">   nodes.  Note that a mobile node can also use its CoA directly</td><td class="lineno" valign="top"></td></tr>
431      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5014] when communicating with CNs on the same link or anywhere in</td><td> </td><td class="right">   [RFC5014] when communicating with CNs on the same link or anywhere in</td><td class="lineno" valign="top"></td></tr>
432      <tr><td class="lineno" valign="top"></td><td class="left">   the Internet, although no session continuity support would be</td><td> </td><td class="right">   the Internet, although no session continuity support would be</td><td class="lineno" valign="top"></td></tr>
433      <tr><td class="lineno" valign="top"></td><td class="left">   provided by the IP stack in this case.</td><td> </td><td class="right">   provided by the IP stack in this case.</td><td class="lineno" valign="top"></td></tr>
434      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
435      <tr><td class="lineno" valign="top"></td><td class="left">   Hierarchical Mobile IPv6 (HMIPv6) [RFC5380] (as shown in Figure 3),</td><td> </td><td class="right">   Hierarchical Mobile IPv6 (HMIPv6) [RFC5380] (as shown in Figure 3),</td><td class="lineno" valign="top"></td></tr>
436      <tr><td class="lineno" valign="top"></td><td class="left">   is another host-based IP mobility extension which can be considered</td><td> </td><td class="right">   is another host-based IP mobility extension which can be considered</td><td class="lineno" valign="top"></td></tr>
437      <tr><td class="lineno" valign="top"></td><td class="left">   as a complement to provide a less centralized mobility deployment.</td><td> </td><td class="right">   as a complement to provide a less centralized mobility deployment.</td><td class="lineno" valign="top"></td></tr>
438      <tr><td class="lineno" valign="top"></td><td class="left">   It allows reducing the amount of mobility signaling as well as</td><td> </td><td class="right">   It allows reducing the amount of mobility signaling as well as</td><td class="lineno" valign="top"></td></tr>
439      <tr><td class="lineno" valign="top"></td><td class="left">   improving the overall handover performance of Mobile IPv6 by</td><td> </td><td class="right">   improving the overall handover performance of Mobile IPv6 by</td><td class="lineno" valign="top"></td></tr>
440      <tr><td class="lineno" valign="top"></td><td class="left">   introducing a new hierarchy level to handle local mobility.  The</td><td> </td><td class="right">   introducing a new hierarchy level to handle local mobility.  The</td><td class="lineno" valign="top"></td></tr>
441      <tr><td class="lineno" valign="top"></td><td class="left">   Mobility Anchor Point (MAP) entity is introduced as a local mobility</td><td> </td><td class="right">   Mobility Anchor Point (MAP) entity is introduced as a local mobility</td><td class="lineno" valign="top"></td></tr>
442      <tr><td class="lineno" valign="top"></td><td class="left">   handling node deployed closer to the mobile node.  It provides LM</td><td> </td><td class="right">   handling node deployed closer to the mobile node.  It provides LM</td><td class="lineno" valign="top"></td></tr>
443      <tr><td><a name="diff0036"></a></td></tr>
444      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">proxy</span> function between the LM server (LMs) at the HA and the LM</td><td> </td><td class="rblock">   <span class="insert">intermediary</span> function between the LM server (LMs) at the HA and the LM</td><td class="lineno" valign="top"></td></tr>
445      <tr><td class="lineno" valign="top"></td><td class="lblock">   client (LMc) at the MN.  It also <span class="delete">possess</span> RM function <span class="delete">to tunnel</span> with</td><td> </td><td class="rblock">   client (LMc) at the MN.  It also <span class="insert">performs the</span> RM function <span class="insert">using tunneling</span></td><td class="lineno" valign="top"></td></tr>
446      <tr><td class="lineno" valign="top"></td><td class="lblock">   the HA and also <span class="delete">to tunnel</span> with the MN.</td><td> </td><td class="rblock">   with the HA and also with the MN.</td><td class="lineno" valign="top"></td></tr>
447      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
448      <tr><td class="lineno" valign="top"></td><td class="left">     &lt;- INTERNET -&gt; &lt;- HOME NETWORK -&gt; &lt;------- ACCESS NETWORK -------&gt;</td><td> </td><td class="right">     &lt;- INTERNET -&gt; &lt;- HOME NETWORK -&gt; &lt;------- ACCESS NETWORK -------&gt;</td><td class="lineno" valign="top"></td></tr>
449      <tr><td class="lineno" valign="top"></td><td class="left">                                                    -----</td><td> </td><td class="right">                                                    -----</td><td class="lineno" valign="top"></td></tr>
450      <tr><td class="lineno" valign="top"></td><td class="left">                                                   /|AR1|-(o) zz (o)</td><td> </td><td class="right">                                                   /|AR1|-(o) zz (o)</td><td class="lineno" valign="top"></td></tr>
451      <tr><td class="lineno" valign="top"></td><td class="left">                                         -------- / -----         |</td><td> </td><td class="right">                                         -------- / -----         |</td><td class="lineno" valign="top"></td></tr>
452      <tr><td class="lineno" valign="top"></td><td class="left">                                         | MAP1 |&lt;             -------</td><td> </td><td class="right">                                         | MAP1 |&lt;             -------</td><td class="lineno" valign="top"></td></tr>
453      <tr><td class="lineno" valign="top"></td><td class="left">                                         -------- \ -----      | MN1 |</td><td> </td><td class="right">                                         -------- \ -----      | MN1 |</td><td class="lineno" valign="top"></td></tr>
454      <tr><td class="lineno" valign="top"></td><td class="left">        -------                                    \|AR2|      -------</td><td> </td><td class="right">        -------                                    \|AR2|      -------</td><td class="lineno" valign="top"></td></tr>
455      <tr><td class="lineno" valign="top"></td><td class="left">        | CN1 |                                     -----  HoA anchored</td><td> </td><td class="right">        | CN1 |                                     -----  HoA anchored</td><td class="lineno" valign="top"></td></tr>
456      <tr><td class="lineno" valign="top"></td><td class="left">        -------                                     -----     at HA1</td><td> </td><td class="right">        -------                                     -----     at HA1</td><td class="lineno" valign="top"></td></tr>
457      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
458      <tr bgcolor="gray"><td></td><th><a name="part-l5"><small>skipping to change at</small><em> page 10, line 20</em></a></th><th> </th><th><a name="part-r5"><small>skipping to change at</small><em> page 10, line 20</em></a></th><td></td></tr>
459      <tr><td class="lineno" valign="top"></td><td class="left">                                         -------- \ -----</td><td> </td><td class="right">                                         -------- \ -----</td><td class="lineno" valign="top"></td></tr>
460      <tr><td class="lineno" valign="top"></td><td class="left">                                                   \|AR6|</td><td> </td><td class="right">                                                   \|AR6|</td><td class="lineno" valign="top"></td></tr>
461      <tr><td class="lineno" valign="top"></td><td class="left">                                                    -----</td><td> </td><td class="right">                                                    -----</td><td class="lineno" valign="top"></td></tr>
462      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
463      <tr><td class="lineno" valign="top"></td><td class="left">     CN1      CN2         HA1              MAP1      AR1         MN1</td><td> </td><td class="right">     CN1      CN2         HA1              MAP1      AR1         MN1</td><td class="lineno" valign="top"></td></tr>
464      <tr><td class="lineno" valign="top"></td><td class="left">      |        |           |                | ________|__________ |</td><td> </td><td class="right">      |        |           |                | ________|__________ |</td><td class="lineno" valign="top"></td></tr>
465      <tr><td class="lineno" valign="top"></td><td class="left">      |&lt;------------------&gt;|&lt;==============&gt;|&lt;________+__________&gt;| HoA</td><td> </td><td class="right">      |&lt;------------------&gt;|&lt;==============&gt;|&lt;________+__________&gt;| HoA</td><td class="lineno" valign="top"></td></tr>
466      <tr><td class="lineno" valign="top"></td><td class="left">      |        |           |                |         |           |</td><td> </td><td class="right">      |        |           |                |         |           |</td><td class="lineno" valign="top"></td></tr>
467      <tr><td class="lineno" valign="top"></td><td class="left">      |        |&lt;--------------------------&gt;|&lt;===================&gt;| RCoA</td><td> </td><td class="right">      |        |&lt;--------------------------&gt;|&lt;===================&gt;| RCoA</td><td class="lineno" valign="top"></td></tr>
468      <tr><td class="lineno" valign="top"></td><td class="left">      |        |           |                |         |           |</td><td> </td><td class="right">      |        |           |                |         |           |</td><td class="lineno" valign="top"></td></tr>
469      <tr><td><a name="diff0037"></a></td></tr>
470      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: Is this intended to show a secondary encapsulation between MAP and MN?</span></td><td class="lineno" valign="top"></td></tr>
471      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
472      <tr><td class="lineno" valign="top"></td><td class="left">                    Figure 3: Hierarchical Mobile IPv6</td><td> </td><td class="right">                    Figure 3: Hierarchical Mobile IPv6</td><td class="lineno" valign="top"></td></tr>
473      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
474      <tr><td><a name="diff0038"></a></td></tr>
475      <tr><td class="lineno" valign="top"></td><td class="lblock">   When HMIPv6 is used, the MN has two different tempora<span class="delete">l</span> addresses: the</td><td> </td><td class="rblock">   When HMIPv6 is used, the MN has two different tempora<span class="insert">ry</span> addresses: the</td><td class="lineno" valign="top"></td></tr>
476      <tr><td class="lineno" valign="top"></td><td class="left">   Regional Care-of Address (RCoA) and the Local Care-of Address (LCoA).</td><td> </td><td class="right">   Regional Care-of Address (RCoA) and the Local Care-of Address (LCoA).</td><td class="lineno" valign="top"></td></tr>
477      <tr><td class="lineno" valign="top"></td><td class="left">   The RCoA is anchored at one MAP, that plays the role of local home</td><td> </td><td class="right">   The RCoA is anchored at one MAP, that plays the role of local home</td><td class="lineno" valign="top"></td></tr>
478      <tr><td class="lineno" valign="top"></td><td class="left">   agent, while the LCoA is anchored at the access router level.  The</td><td> </td><td class="right">   agent, while the LCoA is anchored at the access router level.  The</td><td class="lineno" valign="top"></td></tr>
479      <tr><td class="lineno" valign="top"></td><td class="left">   mobile node uses the RCoA as the CoA signaled to its home agent.</td><td> </td><td class="right">   mobile node uses the RCoA as the CoA signaled to its home agent.</td><td class="lineno" valign="top"></td></tr>
480      <tr><td class="lineno" valign="top"></td><td class="left">   Therefore, while roaming within a local domain handled by the same</td><td> </td><td class="right">   Therefore, while roaming within a local domain handled by the same</td><td class="lineno" valign="top"></td></tr>
481      <tr><td class="lineno" valign="top"></td><td class="left">   MAP, the mobile node does not need to update its home agent (i.e.,</td><td> </td><td class="right">   MAP, the mobile node does not need to update its home agent (i.e.,</td><td class="lineno" valign="top"></td></tr>
482      <tr><td class="lineno" valign="top"></td><td class="left">   the mobile node does not change its RCoA).</td><td> </td><td class="right">   the mobile node does not change its RCoA).</td><td class="lineno" valign="top"></td></tr>
483      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
484      <tr><td><a name="diff0039"></a></td></tr>
485      <tr><td class="lineno" valign="top"></td><td class="lblock">   The use of HMIPv6 <span class="delete">allows achieving</span> some form of route optimization,</td><td> </td><td class="rblock">   The use of HMIPv6 <span class="insert">enables</span> some form of route optimization,</td><td class="lineno" valign="top"></td></tr>
486      <tr><td class="lineno" valign="top"></td><td class="left">   since a mobile node may decide to directly use the RCoA as source</td><td> </td><td class="right">   since a mobile node may decide to directly use the RCoA as source</td><td class="lineno" valign="top"></td></tr>
487      <tr><td><a name="diff0040"></a></td></tr>
488      <tr><td class="lineno" valign="top"></td><td class="lblock">   address for a communication with a given correspondent node, <span class="delete">notab</span>ly</td><td> </td><td class="rblock">   address for a communication with a given correspondent node, <span class="insert">particular</span>ly</td><td class="lineno" valign="top"></td></tr>
489      <tr><td class="lineno" valign="top"></td><td class="left">   if the MN does not expect to move outside the local domain during the</td><td> </td><td class="right">   if the MN does not expect to move outside the local domain during the</td><td class="lineno" valign="top"></td></tr>
490      <tr><td class="lineno" valign="top"></td><td class="left">   lifetime of the communication.  This can be seen as a potential DMM</td><td> </td><td class="right">   lifetime of the communication.  This can be seen as a potential DMM</td><td class="lineno" valign="top"></td></tr>
491      <tr><td class="lineno" valign="top"></td><td class="left">   mode of operation.  In the example shown in Figure 3, MN1 is using</td><td> </td><td class="right">   mode of operation.  In the example shown in Figure 3, MN1 is using</td><td class="lineno" valign="top"></td></tr>
492      <tr><td class="lineno" valign="top"></td><td class="left">   its global HoA to communicate with CN1, while it is using its RCoA to</td><td> </td><td class="right">   its global HoA to communicate with CN1, while it is using its RCoA to</td><td class="lineno" valign="top"></td></tr>
493      <tr><td class="lineno" valign="top"></td><td class="left">   communicate with CN2.</td><td> </td><td class="right">   communicate with CN2.</td><td class="lineno" valign="top"></td></tr>
494      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
495      <tr><td><a name="diff0041"></a></td></tr>
496      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">Additionally</span>, a local domain might have several MAPs deployed,</td><td> </td><td class="rblock">   <span class="insert">Furthermore</span>, a local domain might have several MAPs deployed,</td><td class="lineno" valign="top"></td></tr>
497      <tr><td class="lineno" valign="top"></td><td class="left">   enabling therefore a different kind of HMIPv6 deployments (e.g., flat</td><td> </td><td class="right">   enabling therefore a different kind of HMIPv6 deployments (e.g., flat</td><td class="lineno" valign="top"></td></tr>
498      <tr><td class="lineno" valign="top"></td><td class="left">   and distributed).  The HMIPv6 specification supports a flexible</td><td> </td><td class="right">   and distributed).  The HMIPv6 specification supports a flexible</td><td class="lineno" valign="top"></td></tr>
499      <tr><td class="lineno" valign="top"></td><td class="left">   selection of the MAP (e.g., based on the distance between the MN and</td><td> </td><td class="right">   selection of the MAP (e.g., based on the distance between the MN and</td><td class="lineno" valign="top"></td></tr>
500      <tr><td class="lineno" valign="top"></td><td class="left">   the MAP, taking into consideration the expected mobility pattern of</td><td> </td><td class="right">   the MAP, taking into consideration the expected mobility pattern of</td><td class="lineno" valign="top"></td></tr>
501      <tr><td class="lineno" valign="top"></td><td class="left">   the MN, etc.).</td><td> </td><td class="right">   the MN, etc.).</td><td class="lineno" valign="top"></td></tr>
502      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
503      <tr><td><a name="diff0042"></a></td></tr>
504      <tr><td class="lineno" valign="top"></td><td class="lblock">   An<span class="delete"> additional</span> extension that can be used to help deploying a mobility</td><td> </td><td class="rblock">   An<span class="insert">other</span> extension that can be used to help deploying a mobility</td><td class="lineno" valign="top"></td></tr>
505      <tr><td class="lineno" valign="top"></td><td class="left">   protocol in a distributed mobility management environment is the Home</td><td> </td><td class="right">   protocol in a distributed mobility management environment is the Home</td><td class="lineno" valign="top"></td></tr>
506      <tr><td class="lineno" valign="top"></td><td class="left">   Agent switch specification [RFC5142], which defines a new mobility</td><td> </td><td class="right">   Agent switch specification [RFC5142], which defines a new mobility</td><td class="lineno" valign="top"></td></tr>
507      <tr><td class="lineno" valign="top"></td><td class="left">   header for signaling a mobile node that it should acquire a new home</td><td> </td><td class="right">   header for signaling a mobile node that it should acquire a new home</td><td class="lineno" valign="top"></td></tr>
508      <tr><td><a name="diff0043"></a></td></tr>
509      <tr><td class="lineno" valign="top"></td><td class="lblock">   agent.  <span class="delete">Even though the purposes of this specification do not include</span></td><td> </td><td class="rblock">   agent.  <span class="insert">RFC 5142 does not specify</span></td><td class="lineno" valign="top"></td></tr>
510      <tr><td class="lineno" valign="top"></td><td class="left">   the case of changing the mobile node's home address, as that might</td><td> </td><td class="right">   the case of changing the mobile node's home address, as that might</td><td class="lineno" valign="top"></td></tr>
511      <tr><td><a name="diff0044"></a></td></tr>
512      <tr><td class="lineno" valign="top"></td><td class="lblock">   imply loss of connectivity for ongoing persistent <span class="delete">connections, it</span></td><td> </td><td class="rblock">   imply loss of connectivity for ongoing persistent <span class="insert">connections.</span></td><td class="lineno" valign="top"></td></tr>
513      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">   Nevertheless, that specification</span></td><td class="lineno" valign="top"></td></tr>
514      <tr><td class="lineno" valign="top"></td><td class="left">   could be used to force the change of home agent in those situations</td><td> </td><td class="right">   could be used to force the change of home agent in those situations</td><td class="lineno" valign="top"></td></tr>
515      <tr><td class="lineno" valign="top"></td><td class="left">   where there are no active persistent data sessions that cannot cope</td><td> </td><td class="right">   where there are no active persistent data sessions that cannot cope</td><td class="lineno" valign="top"></td></tr>
516      <tr><td class="lineno" valign="top"></td><td class="left">   with a change of home address.</td><td> </td><td class="right">   with a change of home address.</td><td class="lineno" valign="top"></td></tr>
517      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
518      <tr><td class="lineno" valign="top"></td><td class="left">   There are other host-based approaches standardized within IETF that</td><td> </td><td class="right">   There are other host-based approaches standardized within IETF that</td><td class="lineno" valign="top"></td></tr>
519      <tr><td class="lineno" valign="top"></td><td class="left">   can be used to provide mobility support.  For example MOBIKE</td><td> </td><td class="right">   can be used to provide mobility support.  For example MOBIKE</td><td class="lineno" valign="top"></td></tr>
520      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC4555] allows a mobile node encrypting traffic through IKEv2</td><td> </td><td class="right">   [RFC4555] allows a mobile node encrypting traffic through IKEv2</td><td class="lineno" valign="top"></td></tr>
521      <tr><td class="lineno" valign="top"></td><td class="left">   [RFC5996] to change its point of attachment while maintaining a</td><td> </td><td class="right">   [RFC5996] to change its point of attachment while maintaining a</td><td class="lineno" valign="top"></td></tr>
522      <tr><td class="lineno" valign="top"></td><td class="left">   Virtual Private Network (VPN) session.  The MOBIKE protocol allows</td><td> </td><td class="right">   Virtual Private Network (VPN) session.  The MOBIKE protocol allows</td><td class="lineno" valign="top"></td></tr>
523      <tr><td class="lineno" valign="top"></td><td class="left">   updating the VPN Security Associations (SAs) in cases where the base</td><td> </td><td class="right">   updating the VPN Security Associations (SAs) in cases where the base</td><td class="lineno" valign="top"></td></tr>
524      <tr><td class="lineno" valign="top"></td><td class="left">   connection initially used is lost and needs to be re-established.</td><td> </td><td class="right">   connection initially used is lost and needs to be re-established.</td><td class="lineno" valign="top"></td></tr>
525      <tr><td class="lineno" valign="top"></td><td class="left">   The use of the MOBIKE protocol avoids having to perform an IKEv2 re-</td><td> </td><td class="right">   The use of the MOBIKE protocol avoids having to perform an IKEv2 re-</td><td class="lineno" valign="top"></td></tr>
526      <tr><td class="lineno" valign="top"></td><td class="left">   negotiation.  Similar considerations to those made for Mobile IPv6</td><td> </td><td class="right">   negotiation.  Similar considerations to those made for Mobile IPv6</td><td class="lineno" valign="top"></td></tr>
527      <tr><td class="lineno" valign="top"></td><td class="left">   can be applied to MOBIKE; though MOBIKE is best suited for situations</td><td> </td><td class="right">   can be applied to MOBIKE; though MOBIKE is best suited for situations</td><td class="lineno" valign="top"></td></tr>
528      <tr><td class="lineno" valign="top"></td><td class="left">   where the address of at least one endpoint is relatively stable and</td><td> </td><td class="right">   where the address of at least one endpoint is relatively stable and</td><td class="lineno" valign="top"></td></tr>
529      <tr><td class="lineno" valign="top"></td><td class="left">   can be discovered using existing mechanisms such as DNS.</td><td> </td><td class="right">   can be discovered using existing mechanisms such as DNS.</td><td class="lineno" valign="top"></td></tr>
530      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
531      <tr><td class="lineno" valign="top"></td><td class="left">4.2.2.  Network-based IP DMM practices</td><td> </td><td class="right">4.2.2.  Network-based IP DMM practices</td><td class="lineno" valign="top"></td></tr>
532      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
533      <tr><td class="lineno" valign="top"></td><td class="left">   Proxy Mobile IPv6 (PMIPv6) [RFC5213] is the main network-based IP</td><td> </td><td class="right">   Proxy Mobile IPv6 (PMIPv6) [RFC5213] is the main network-based IP</td><td class="lineno" valign="top"></td></tr>
534      <tr><td><a name="diff0045"></a></td></tr>
535      <tr><td class="lineno" valign="top"></td><td class="lblock">   mobility protocol specified for <span class="delete">IPv6 ([RFC5844]</span> defines some IPv4</td><td> </td><td class="rblock">   mobility protocol specified for <span class="insert">IPv6; Proxy Mobile IPv4 [RFC5844]</span> defines</td><td class="lineno" valign="top"></td></tr>
536      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">extensions).</span>  With network-based IP mobility protocols, the local</td><td> </td><td class="rblock">   some IPv4 <span class="insert">extensions.</span>  With network-based IP mobility protocols, the local</td><td class="lineno" valign="top"></td></tr>
537      <tr><td class="lineno" valign="top"></td><td class="left">   mobility anchor (LMA) typically provides the anchoring function (AF),</td><td> </td><td class="right">   mobility anchor (LMA) typically provides the anchoring function (AF),</td><td class="lineno" valign="top"></td></tr>
538      <tr><td class="lineno" valign="top"></td><td class="left">   Routing management (RM) function, Internetwork Location Management</td><td> </td><td class="right">   Routing management (RM) function, Internetwork Location Management</td><td class="lineno" valign="top"></td></tr>
539      <tr><td class="lineno" valign="top"></td><td class="left">   server (LMs) function and RM function.  The mobile access gateway</td><td> </td><td class="right">   server (LMs) function and RM function.  The mobile access gateway</td><td class="lineno" valign="top"></td></tr>
540      <tr><td class="lineno" valign="top"></td><td class="left">   (MAG) provides the Location Management client (LMc) function and</td><td> </td><td class="right">   (MAG) provides the Location Management client (LMc) function and</td><td class="lineno" valign="top"></td></tr>
541      <tr><td class="lineno" valign="top"></td><td class="left">   Routing management (RM) function to tunnel with LMA.  PMIPv6 is</td><td> </td><td class="right">   Routing management (RM) function to tunnel with LMA.  PMIPv6 is</td><td class="lineno" valign="top"></td></tr>
542      <tr><td><a name="diff0046"></a></td></tr>
543      <tr><td class="lineno" valign="top"></td><td class="lblock">   architecturally <span class="delete">similar</span> to MIPv6, as the mobility signaling and</td><td> </td><td class="rblock">   architecturally <span class="insert">almost identical</span> to MIPv6, as the mobility signaling and</td><td class="lineno" valign="top"></td></tr>
544      <tr><td class="lineno" valign="top"></td><td class="left">   routing between LMA and MAG in PMIPv6 is similar to those between HA</td><td> </td><td class="right">   routing between LMA and MAG in PMIPv6 is similar to those between HA</td><td class="lineno" valign="top"></td></tr>
545      <tr><td class="lineno" valign="top"></td><td class="left">   and MN in MIPv6.  The required mobility functionality at the MN is</td><td> </td><td class="right">   and MN in MIPv6.  The required mobility functionality at the MN is</td><td class="lineno" valign="top"></td></tr>
546      <tr><td class="lineno" valign="top"></td><td class="left">   provided by the MAG so that the involvement in mobility support by</td><td> </td><td class="right">   provided by the MAG so that the involvement in mobility support by</td><td class="lineno" valign="top"></td></tr>
547      <tr><td class="lineno" valign="top"></td><td class="left">   the MN is not required.</td><td> </td><td class="right">   the MN is not required.</td><td class="lineno" valign="top"></td></tr>
548      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
549      <tr><td><a name="diff0047"></a></td></tr>
550      <tr><td class="lineno" valign="top"></td><td class="lblock">   We next describe some practices <span class="delete">on</span> how network-based mobility</td><td> </td><td class="rblock">   We next describe some practices <span class="insert">that show</span> how network-based mobility</td><td class="lineno" valign="top"></td></tr>
551      <tr><td class="lineno" valign="top"></td><td class="lblock">   protocols and several <span class="delete">additional</span> protocol extensions can be deployed</td><td> </td><td class="rblock">   protocols and several <span class="insert">other</span> protocol extensions can be deployed</td><td class="lineno" valign="top"></td></tr>
552      <tr><td class="lineno" valign="top"></td><td class="left">   in a distributed mobility management environment.</td><td> </td><td class="right">   in a distributed mobility management environment.</td><td class="lineno" valign="top"></td></tr>
553      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
554      <tr><td><a name="diff0048"></a></td></tr>
555      <tr><td class="lineno" valign="top"></td><td class="lblock">   One <span class="delete">simple but still suboptimal approach</span> to decentralize Proxy Mobile</td><td> </td><td class="rblock">   One <span class="insert">way</span> to decentralize Proxy Mobile</td><td class="lineno" valign="top"></td></tr>
556      <tr><td class="lineno" valign="top"></td><td class="left">   IPv6 operation can be to deploy several local mobility anchors and</td><td> </td><td class="right">   IPv6 operation can be to deploy several local mobility anchors and</td><td class="lineno" valign="top"></td></tr>
557      <tr><td class="lineno" valign="top"></td><td class="left">   use some selection criteria to assign LMAs to attaching mobile nodes</td><td> </td><td class="right">   use some selection criteria to assign LMAs to attaching mobile nodes</td><td class="lineno" valign="top"></td></tr>
558      <tr><td><a name="diff0049"></a></td></tr>
559      <tr><td class="lineno" valign="top"></td><td class="lblock">   (an example of this type of assignment is shown in Figure 4).  As <span class="delete">per</span></td><td> </td><td class="rblock">   (an example of this type of assignment is shown in Figure 4).  As <span class="insert">with</span></td><td class="lineno" valign="top"></td></tr>
560      <tr><td class="lineno" valign="top"></td><td class="left">   the client based approach, a mobile node may use several anchors at</td><td> </td><td class="right">   the client based approach, a mobile node may use several anchors at</td><td class="lineno" valign="top"></td></tr>
561      <tr><td class="lineno" valign="top"></td><td class="left">   the same time, each of them anchoring IP flows initiated at a</td><td> </td><td class="right">   the same time, each of them anchoring IP flows initiated at a</td><td class="lineno" valign="top"></td></tr>
562      <tr><td class="lineno" valign="top"></td><td class="left">   different point of attachment.  This assignment can be static or</td><td> </td><td class="right">   different point of attachment.  This assignment can be static or</td><td class="lineno" valign="top"></td></tr>
563      <tr><td class="lineno" valign="top"></td><td class="left">   dynamic (as described later in this document).  The main advantage of</td><td> </td><td class="right">   dynamic (as described later in this document).  The main advantage of</td><td class="lineno" valign="top"></td></tr>
564      <tr><td><a name="diff0050"></a></td></tr>
565      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: xref would be nice.</span></td><td class="lineno" valign="top"></td></tr>
566      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
567      <tr><td class="lineno" valign="top"></td><td class="left">   this simple approach is that the IP address anchor (i.e., the LMA)</td><td> </td><td class="right">   this simple approach is that the IP address anchor (i.e., the LMA)</td><td class="lineno" valign="top"></td></tr>
568      <tr><td class="lineno" valign="top"></td><td class="left">   could be placed closer to the mobile node.  Therefore the resulting</td><td> </td><td class="right">   could be placed closer to the mobile node.  Therefore the resulting</td><td class="lineno" valign="top"></td></tr>
569      <tr><td class="lineno" valign="top"></td><td class="left">   paths are close-to-optimal.  On the other hand, as soon as the mobile</td><td> </td><td class="right">   paths are close-to-optimal.  On the other hand, as soon as the mobile</td><td class="lineno" valign="top"></td></tr>
570      <tr><td class="lineno" valign="top"></td><td class="left">   node moves, the resulting path will start deviating from the optimal</td><td> </td><td class="right">   node moves, the resulting path will start deviating from the optimal</td><td class="lineno" valign="top"></td></tr>
571      <tr><td class="lineno" valign="top"></td><td class="left">   one.</td><td> </td><td class="right">   one.</td><td class="lineno" valign="top"></td></tr>
572      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
573      <tr><td class="lineno" valign="top"></td><td class="left">   &lt;- INTERNET -&gt;&lt;- HOME NET -&gt;&lt;----------- ACCESS NETWORK ------------&gt;</td><td> </td><td class="right">   &lt;- INTERNET -&gt;&lt;- HOME NET -&gt;&lt;----------- ACCESS NETWORK ------------&gt;</td><td class="lineno" valign="top"></td></tr>
574      <tr><td class="lineno" valign="top"></td><td class="left">       -------</td><td> </td><td class="right">       -------</td><td class="lineno" valign="top"></td></tr>
575      <tr><td class="lineno" valign="top"></td><td class="left">       | CN1 |                      --------      --------      --------</td><td> </td><td class="right">       | CN1 |                      --------      --------      --------</td><td class="lineno" valign="top"></td></tr>
576      <tr><td class="lineno" valign="top"></td><td class="left">       -------      --------        | MAG1 |      | MAG2 |      | MAG3 |</td><td> </td><td class="right">       -------      --------        | MAG1 |      | MAG2 |      | MAG3 |</td><td class="lineno" valign="top"></td></tr>
577      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
578      <tr bgcolor="gray"><td></td><th><a name="part-l6"><small>skipping to change at</small><em> page 13, line 23</em></a></th><th> </th><th><a name="part-r6"><small>skipping to change at</small><em> page 13, line 23</em></a></th><td></td></tr>
579      <tr><td class="lineno" valign="top"></td><td class="left">   sessions can survive an IP address change.  Note that several</td><td> </td><td class="right">   sessions can survive an IP address change.  Note that several</td><td class="lineno" valign="top"></td></tr>
580      <tr><td class="lineno" valign="top"></td><td class="left">   possible dynamic local mobility anchor discovery solutions can be</td><td> </td><td class="right">   possible dynamic local mobility anchor discovery solutions can be</td><td class="lineno" valign="top"></td></tr>
581      <tr><td class="lineno" valign="top"></td><td class="left">   used, as described in [RFC6097].</td><td> </td><td class="right">   used, as described in [RFC6097].</td><td class="lineno" valign="top"></td></tr>
582      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
583      <tr><td class="lineno" valign="top"></td><td class="left">4.3.  3GPP network flattening approaches</td><td> </td><td class="right">4.3.  3GPP network flattening approaches</td><td class="lineno" valign="top"></td></tr>
584      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
585      <tr><td class="lineno" valign="top"></td><td class="left">   The 3rd Generation Partnership Project (3GPP) is the standards</td><td> </td><td class="right">   The 3rd Generation Partnership Project (3GPP) is the standards</td><td class="lineno" valign="top"></td></tr>
586      <tr><td class="lineno" valign="top"></td><td class="left">   development organization that specifies the 3rd generation mobile</td><td> </td><td class="right">   development organization that specifies the 3rd generation mobile</td><td class="lineno" valign="top"></td></tr>
587      <tr><td class="lineno" valign="top"></td><td class="left">   network and the Evolved Packet System (EPS), which mainly comprises</td><td> </td><td class="right">   network and the Evolved Packet System (EPS), which mainly comprises</td><td class="lineno" valign="top"></td></tr>
588      <tr><td class="lineno" valign="top"></td><td class="left">   the Evolved Packet Core (EPC) and a new radio access network,</td><td> </td><td class="right">   the Evolved Packet Core (EPC) and a new radio access network,</td><td class="lineno" valign="top"></td></tr>
589      <tr><td><a name="diff0051"></a></td></tr>
590      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">sometimes</span> referred to as LTE (Long Term Evolution).</td><td> </td><td class="rblock">   <span class="insert">usually</span> referred to as LTE (Long Term Evolution).</td><td class="lineno" valign="top"></td></tr>
591      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
592      <tr><td class="lineno" valign="top"></td><td class="left">   Architecturally, the 3GPP Evolved Packet Core (EPC) network is</td><td> </td><td class="right">   Architecturally, the 3GPP Evolved Packet Core (EPC) network is</td><td class="lineno" valign="top"></td></tr>
593      <tr><td class="lineno" valign="top"></td><td class="left">   similar to an IP wireless network running PMIPv6 or MIPv6, as it</td><td> </td><td class="right">   similar to an IP wireless network running PMIPv6 or MIPv6, as it</td><td class="lineno" valign="top"></td></tr>
594      <tr><td class="lineno" valign="top"></td><td class="left">   relies on the Packet Data Gateway (PGW) anchoring services to provide</td><td> </td><td class="right">   relies on the Packet Data Gateway (PGW) anchoring services to provide</td><td class="lineno" valign="top"></td></tr>
595      <tr><td class="lineno" valign="top"></td><td class="left">   mobile nodes with mobility support (see Figure 5).  There are client-</td><td> </td><td class="right">   mobile nodes with mobility support (see Figure 5).  There are client-</td><td class="lineno" valign="top"></td></tr>
596      <tr><td class="lineno" valign="top"></td><td class="left">   based and network-based mobility solutions in 3GPP, which for</td><td> </td><td class="right">   based and network-based mobility solutions in 3GPP, which for</td><td class="lineno" valign="top"></td></tr>
597      <tr><td class="lineno" valign="top"></td><td class="left">   simplicity will be analyzed together.  We next describe how 3GPP</td><td> </td><td class="right">   simplicity will be analyzed together.  We next describe how 3GPP</td><td class="lineno" valign="top"></td></tr>
598      <tr><td><a name="diff0052"></a></td></tr>
599      <tr><td class="lineno" valign="top"></td><td class="lblock">   mobility protocols and several <span class="delete">additional</span> completed or ongoing</td><td> </td><td class="rblock">   mobility protocols and several <span class="insert">other</span> completed or ongoing</td><td class="lineno" valign="top"></td></tr>
600      <tr><td class="lineno" valign="top"></td><td class="left">   extensions can be deployed to meet some of the DMM requirements</td><td> </td><td class="right">   extensions can be deployed to meet some of the DMM requirements</td><td class="lineno" valign="top"></td></tr>
601      <tr><td class="lineno" valign="top"></td><td class="left">   [I-D.ietf-dmm-requirements].</td><td> </td><td class="right">   [I-D.ietf-dmm-requirements].</td><td class="lineno" valign="top"></td></tr>
602      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
603      <tr><td class="lineno" valign="top"></td><td class="left">            +---------------------------------------------------------+</td><td> </td><td class="right">            +---------------------------------------------------------+</td><td class="lineno" valign="top"></td></tr>
604      <tr><td class="lineno" valign="top"></td><td class="left">            |                           PCRF                          |</td><td> </td><td class="right">            |                           PCRF                          |</td><td class="lineno" valign="top"></td></tr>
605      <tr><td class="lineno" valign="top"></td><td class="left">            +-----------+--------------------------+----------------+-+</td><td> </td><td class="right">            +-----------+--------------------------+----------------+-+</td><td class="lineno" valign="top"></td></tr>
606      <tr><td class="lineno" valign="top"></td><td class="left">                        |                          |                |</td><td> </td><td class="right">                        |                          |                |</td><td class="lineno" valign="top"></td></tr>
607      <tr><td class="lineno" valign="top"></td><td class="left">   +----+   +-----------+------------+    +--------+-----------+  +-+-+</td><td> </td><td class="right">   +----+   +-----------+------------+    +--------+-----------+  +-+-+</td><td class="lineno" valign="top"></td></tr>
608      <tr><td class="lineno" valign="top"></td><td class="left">   |    |   |          +-+           |    |  Core Network      |  |   |</td><td> </td><td class="right">   |    |   |          +-+           |    |  Core Network      |  |   |</td><td class="lineno" valign="top"></td></tr>
609      <tr><td class="lineno" valign="top"></td><td class="left">   |    |   | +------+ |S|__         |    | +--------+  +---+  |  |   |</td><td> </td><td class="right">   |    |   | +------+ |S|__         |    | +--------+  +---+  |  |   |</td><td class="lineno" valign="top"></td></tr>
610      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
611      <tr bgcolor="gray"><td></td><th><a name="part-l7"><small>skipping to change at</small><em> page 14, line 29</em></a></th><th> </th><th><a name="part-r7"><small>skipping to change at</small><em> page 14, line 29</em></a></th><td></td></tr>
612      <tr><td class="lineno" valign="top"></td><td class="left">   +----+                                 +--------------------+  +---+</td><td> </td><td class="right">   +----+                                 +--------------------+  +---+</td><td class="lineno" valign="top"></td></tr>
613      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
614      <tr><td class="lineno" valign="top"></td><td class="left">             Figure 5: EPS (non-roaming) architecture overview</td><td> </td><td class="right">             Figure 5: EPS (non-roaming) architecture overview</td><td class="lineno" valign="top"></td></tr>
615      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
616      <tr><td class="lineno" valign="top"></td><td class="left">   The GPRS Tunnelling Protocol (GTP) [SDO-3GPP.29.060]</td><td> </td><td class="right">   The GPRS Tunnelling Protocol (GTP) [SDO-3GPP.29.060]</td><td class="lineno" valign="top"></td></tr>
617      <tr><td class="lineno" valign="top"></td><td class="left">   [SDO-3GPP.29.281] [SDO-3GPP.29.274] is a network-based mobility</td><td> </td><td class="right">   [SDO-3GPP.29.281] [SDO-3GPP.29.274] is a network-based mobility</td><td class="lineno" valign="top"></td></tr>
618      <tr><td class="lineno" valign="top"></td><td class="left">   protocol specified for 3GPP networks (S2a, S2b, S5 and S8</td><td> </td><td class="right">   protocol specified for 3GPP networks (S2a, S2b, S5 and S8</td><td class="lineno" valign="top"></td></tr>
619      <tr><td class="lineno" valign="top"></td><td class="left">   interfaces).  Similar to PMIPv6, it can handle mobility without</td><td> </td><td class="right">   interfaces).  Similar to PMIPv6, it can handle mobility without</td><td class="lineno" valign="top"></td></tr>
620      <tr><td class="lineno" valign="top"></td><td class="left">   requiring the involvement of the mobile nodes.  In this case, the</td><td> </td><td class="right">   requiring the involvement of the mobile nodes.  In this case, the</td><td class="lineno" valign="top"></td></tr>
621      <tr><td class="lineno" valign="top"></td><td class="left">   mobile node functionality is provided in a proxy manner by the</td><td> </td><td class="right">   mobile node functionality is provided in a proxy manner by the</td><td class="lineno" valign="top"></td></tr>
622      <tr><td><a name="diff0053"></a></td></tr>
623      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: "binding update functionality"??</span></td><td class="lineno" valign="top"></td></tr>
624      <tr><td class="lineno" valign="top"></td><td class="left">   Serving Data Gateway (SGW), Evolved Packet Data Gateway (ePDG), or</td><td> </td><td class="right">   Serving Data Gateway (SGW), Evolved Packet Data Gateway (ePDG), or</td><td class="lineno" valign="top"></td></tr>
625      <tr><td class="lineno" valign="top"></td><td class="left">   Trusted Wireless Access Gateway (TWAG).</td><td> </td><td class="right">   Trusted Wireless Access Gateway (TWAG).</td><td class="lineno" valign="top"></td></tr>
626      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
627      <tr><td class="lineno" valign="top"></td><td class="left">   3GPP specifications also include client-based mobility support, based</td><td> </td><td class="right">   3GPP specifications also include client-based mobility support, based</td><td class="lineno" valign="top"></td></tr>
628      <tr><td class="lineno" valign="top"></td><td class="left">   on adopting the use of Dual-Stack Mobile IPv6 (DSMIPv6) [RFC5555] for</td><td> </td><td class="right">   on adopting the use of Dual-Stack Mobile IPv6 (DSMIPv6) [RFC5555] for</td><td class="lineno" valign="top"></td></tr>
629      <tr><td class="lineno" valign="top"></td><td class="left">   the S2c interface.  In this case, the User Equipment (UE) implements</td><td> </td><td class="right">   the S2c interface.  In this case, the User Equipment (UE) implements</td><td class="lineno" valign="top"></td></tr>
630      <tr><td class="lineno" valign="top"></td><td class="left">   the mobile node functionality, while the home agent role is played by</td><td> </td><td class="right">   the mobile node functionality, while the home agent role is played by</td><td class="lineno" valign="top"></td></tr>
631      <tr><td class="lineno" valign="top"></td><td class="left">   the PGW.</td><td> </td><td class="right">   the PGW.</td><td class="lineno" valign="top"></td></tr>
632      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
633      <tr><td class="lineno" valign="top"></td><td class="left">   A Local IP Access (LIPA) and Selected IP Traffic Offload (SIPTO)</td><td> </td><td class="right">   A Local IP Access (LIPA) and Selected IP Traffic Offload (SIPTO)</td><td class="lineno" valign="top"></td></tr>
634      <tr><td class="lineno" valign="top"></td><td class="left">   enabled network [SDO-3GPP.23.401] allows offloading some IP services</td><td> </td><td class="right">   enabled network [SDO-3GPP.23.401] allows offloading some IP services</td><td class="lineno" valign="top"></td></tr>
635      <tr><td class="lineno" valign="top"></td><td class="left">   at the local access network, above the Radio Access Network (RAN) or</td><td> </td><td class="right">   at the local access network, above the Radio Access Network (RAN) or</td><td class="lineno" valign="top"></td></tr>
636      <tr><td><a name="diff0054"></a></td></tr>
637      <tr><td class="lineno" valign="top"></td><td class="lblock">   at the macro, without the need to <span class="delete">traverse</span> back to the PGW (see</td><td> </td><td class="rblock">   at the macro, without the need to <span class="insert">travel</span> back to the PGW (see</td><td class="lineno" valign="top"></td></tr>
638      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: "macro" meaning is unclear</span></td><td class="lineno" valign="top"></td></tr>
639      <tr><td class="lineno" valign="top"></td><td class="left">   Figure 6).</td><td> </td><td class="right">   Figure 6).</td><td class="lineno" valign="top"></td></tr>
640      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
641      <tr><td class="lineno" valign="top"></td><td class="left">   +---------+ IP traffic to mobile operator's CN</td><td> </td><td class="right">   +---------+ IP traffic to mobile operator's CN</td><td class="lineno" valign="top"></td></tr>
642      <tr><td class="lineno" valign="top"></td><td class="left">   |  User   |....................................(Operator's CN)</td><td> </td><td class="right">   |  User   |....................................(Operator's CN)</td><td class="lineno" valign="top"></td></tr>
643      <tr><td class="lineno" valign="top"></td><td class="left">   | Equipm. |..................</td><td> </td><td class="right">   | Equipm. |..................</td><td class="lineno" valign="top"></td></tr>
644      <tr><td class="lineno" valign="top"></td><td class="left">   +---------+                 . Local IP traffic</td><td> </td><td class="right">   +---------+                 . Local IP traffic</td><td class="lineno" valign="top"></td></tr>
645      <tr><td class="lineno" valign="top"></td><td class="left">                               .</td><td> </td><td class="right">                               .</td><td class="lineno" valign="top"></td></tr>
646      <tr><td class="lineno" valign="top"></td><td class="left">                         +-----------+</td><td> </td><td class="right">                         +-----------+</td><td class="lineno" valign="top"></td></tr>
647      <tr><td class="lineno" valign="top"></td><td class="left">                         |Residential|</td><td> </td><td class="right">                         |Residential|</td><td class="lineno" valign="top"></td></tr>
648      <tr><td class="lineno" valign="top"></td><td class="left">                         |enterprise |</td><td> </td><td class="right">                         |enterprise |</td><td class="lineno" valign="top"></td></tr>
649      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
650      <tr bgcolor="gray"><td></td><th><a name="part-l8"><small>skipping to change at</small><em> page 15, line 28</em></a></th><th> </th><th><a name="part-r8"><small>skipping to change at</small><em> page 15, line 28</em></a></th><td></td></tr>
651      <tr><td class="lineno" valign="top"></td><td class="left">                             +------+        +------+</td><td> </td><td class="right">                             +------+        +------+</td><td class="lineno" valign="top"></td></tr>
652      <tr><td class="lineno" valign="top"></td><td class="left">                             |L-PGW |   ---- | MME  |</td><td> </td><td class="right">                             |L-PGW |   ---- | MME  |</td><td class="lineno" valign="top"></td></tr>
653      <tr><td class="lineno" valign="top"></td><td class="left">                             +------+  /     +------+</td><td> </td><td class="right">                             +------+  /     +------+</td><td class="lineno" valign="top"></td></tr>
654      <tr><td class="lineno" valign="top"></td><td class="left">                                 |    /</td><td> </td><td class="right">                                 |    /</td><td class="lineno" valign="top"></td></tr>
655      <tr><td class="lineno" valign="top"></td><td class="left">   +-------+     +------+    +------+/       +------+</td><td> </td><td class="right">   +-------+     +------+    +------+/       +------+</td><td class="lineno" valign="top"></td></tr>
656      <tr><td class="lineno" valign="top"></td><td class="left">   |  UE   |.....|eNB   |....| S-GW |........| P-GW |...&gt; CN Traffic</td><td> </td><td class="right">   |  UE   |.....|eNB   |....| S-GW |........| P-GW |...&gt; CN Traffic</td><td class="lineno" valign="top"></td></tr>
657      <tr><td class="lineno" valign="top"></td><td class="left">   +-------+     +------+    +------+        +------+</td><td> </td><td class="right">   +-------+     +------+    +------+        +------+</td><td class="lineno" valign="top"></td></tr>
658      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
659      <tr><td class="lineno" valign="top"></td><td class="left">                       Figure 7: SIPTO architecture</td><td> </td><td class="right">                       Figure 7: SIPTO architecture</td><td class="lineno" valign="top"></td></tr>
660      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
661      <tr><td><a name="diff0055"></a></td></tr>
662      <tr><td class="lineno" valign="top"></td><td class="lblock">   LIPA, on the other hand, enables an IP <span class="delete">capable</span> UE connected via a</td><td> </td><td class="rblock">   LIPA, on the other hand, enables an IP <span class="insert">addressable</span> UE connected via a</td><td class="lineno" valign="top"></td></tr>
663      <tr><td class="lineno" valign="top"></td><td class="lblock">   Home eNB (HeNB) to access other IP <span class="delete">capable</span> entities in the same</td><td> </td><td class="rblock">   Home eNB (HeNB) to access other IP <span class="insert">addressable</span> entities in the same</td><td class="lineno" valign="top"></td></tr>
664      <tr><td class="lineno" valign="top"></td><td class="left">   residential/enterprise IP network without traversing the mobile</td><td> </td><td class="right">   residential/enterprise IP network without traversing the mobile</td><td class="lineno" valign="top"></td></tr>
665      <tr><td class="lineno" valign="top"></td><td class="left">   operator's network core in the user plane.  In order to achieve this,</td><td> </td><td class="right">   operator's network core in the user plane.  In order to achieve this,</td><td class="lineno" valign="top"></td></tr>
666      <tr><td class="lineno" valign="top"></td><td class="left">   a Local GW (L-GW) collocated with the HeNB is used.  LIPA is</td><td> </td><td class="right">   a Local GW (L-GW) collocated with the HeNB is used.  LIPA is</td><td class="lineno" valign="top"></td></tr>
667      <tr><td class="lineno" valign="top"></td><td class="left">   established by the UE requesting a new PDN connection to an access</td><td> </td><td class="right">   established by the UE requesting a new PDN connection to an access</td><td class="lineno" valign="top"></td></tr>
668      <tr><td><a name="diff0056"></a></td></tr>
669      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: PDN connection undefined (and irrelevant?)</span></td><td class="lineno" valign="top"></td></tr>
670      <tr><td class="lineno" valign="top"></td><td class="left">   point name for which LIPA is permitted, and the network selecting the</td><td> </td><td class="right">   point name for which LIPA is permitted, and the network selecting the</td><td class="lineno" valign="top"></td></tr>
671      <tr><td><a name="diff0057"></a></td></tr>
672      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: Is it really important for the gap analysis to discuss LIPA policy?</span></td><td class="lineno" valign="top"></td></tr>
673      <tr><td class="lineno" valign="top"></td><td class="left">   Local GW associated with the HeNB and enabling a direct user plane</td><td> </td><td class="right">   Local GW associated with the HeNB and enabling a direct user plane</td><td class="lineno" valign="top"></td></tr>
674      <tr><td class="lineno" valign="top"></td><td class="left">   path between the Local GW and the HeNB.</td><td> </td><td class="right">   path between the Local GW and the HeNB.</td><td class="lineno" valign="top"></td></tr>
675      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
676      <tr><td class="lineno" valign="top"></td><td class="left">   +---------------+-------+  +----------+  +-------------+    =====</td><td> </td><td class="right">   +---------------+-------+  +----------+  +-------------+    =====</td><td class="lineno" valign="top"></td></tr>
677      <tr><td class="lineno" valign="top"></td><td class="left">   |Residential |  |H(e)NB |  | Backhaul |  |Mobile       |   ( IP  )</td><td> </td><td class="right">   |Residential |  |H(e)NB |  | Backhaul |  |Mobile       |   ( IP  )</td><td class="lineno" valign="top"></td></tr>
678      <tr><td class="lineno" valign="top"></td><td class="left">   |Enterprise  |..|-------|..|          |..|Operator     |..(Network)</td><td> </td><td class="right">   |Enterprise  |..|-------|..|          |..|Operator     |..(Network)</td><td class="lineno" valign="top"></td></tr>
679      <tr><td class="lineno" valign="top"></td><td class="left">   |Network     |  |L-GW   |  |          |  |Core network |   =======</td><td> </td><td class="right">   |Network     |  |L-GW   |  |          |  |Core network |   =======</td><td class="lineno" valign="top"></td></tr>
680      <tr><td class="lineno" valign="top"></td><td class="left">   +---------------+-------+  +----------+  +-------------+</td><td> </td><td class="right">   +---------------+-------+  +----------+  +-------------+</td><td class="lineno" valign="top"></td></tr>
681      <tr><td class="lineno" valign="top"></td><td class="left">                       /</td><td> </td><td class="right">                       /</td><td class="lineno" valign="top"></td></tr>
682      <tr><td class="lineno" valign="top"></td><td class="left">                       |</td><td> </td><td class="right">                       |</td><td class="lineno" valign="top"></td></tr>
683      <tr><td class="lineno" valign="top"></td><td class="left">                       /</td><td> </td><td class="right">                       /</td><td class="lineno" valign="top"></td></tr>
684      <tr><td class="lineno" valign="top"></td><td class="left">                    +-----+</td><td> </td><td class="right">                    +-----+</td><td class="lineno" valign="top"></td></tr>
685      <tr><td class="lineno" valign="top"></td><td class="left">                    | UE  |</td><td> </td><td class="right">                    | UE  |</td><td class="lineno" valign="top"></td></tr>
686      <tr><td class="lineno" valign="top"></td><td class="left">                    +-----+</td><td> </td><td class="right">                    +-----+</td><td class="lineno" valign="top"></td></tr>
687      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
688      <tr><td class="lineno" valign="top"></td><td class="left">                        Figure 8: LIPA architecture</td><td> </td><td class="right">                        Figure 8: LIPA architecture</td><td class="lineno" valign="top"></td></tr>
689      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
690      <tr><td class="lineno" valign="top"></td><td class="left">   The 3GPP architecture specifications also provide mechanisms to allow</td><td> </td><td class="right">   The 3GPP architecture specifications also provide mechanisms to allow</td><td class="lineno" valign="top"></td></tr>
691      <tr><td class="lineno" valign="top"></td><td class="left">   discovery and selection of gateways [SDO-3GPP.29.303].  These</td><td> </td><td class="right">   discovery and selection of gateways [SDO-3GPP.29.303].  These</td><td class="lineno" valign="top"></td></tr>
692      <tr><td class="lineno" valign="top"></td><td class="left">   mechanisms enable decisions taking into consideration topological</td><td> </td><td class="right">   mechanisms enable decisions taking into consideration topological</td><td class="lineno" valign="top"></td></tr>
693      <tr><td><a name="diff0058"></a></td></tr>
694      <tr><td class="lineno" valign="top"></td><td class="lblock">   location and gateway collocation aspects, <span class="delete">using heavily</span> the DNS as a</td><td> </td><td class="rblock">   location and gateway collocation aspects, <span class="insert">relying upon</span> the DNS as a</td><td class="lineno" valign="top"></td></tr>
695      <tr><td class="lineno" valign="top"></td><td class="left">   "location database".</td><td> </td><td class="right">   "location database".</td><td class="lineno" valign="top"></td></tr>
696      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
697      <tr><td class="lineno" valign="top"></td><td class="left">   Both SIPTO and LIPA have a very limited mobility support, specially</td><td> </td><td class="right">   Both SIPTO and LIPA have a very limited mobility support, specially</td><td class="lineno" valign="top"></td></tr>
698      <tr><td><a name="diff0059"></a></td></tr>
699      <tr><td class="lineno" valign="top"></td><td class="lblock">   in 3GPP specifications up to Rel-12<span class="delete">.  In a glimpse</span>, LIPA mobility</td><td> </td><td class="rblock">   in 3GPP specifications up to Rel-12<span class="insert">[CITATION!].  Briefly</span>, LIPA mobility</td><td class="lineno" valign="top"></td></tr>
700      <tr><td class="lineno" valign="top"></td><td class="left">   support is limited to handovers between HeNBs that are managed by the</td><td> </td><td class="right">   support is limited to handovers between HeNBs that are managed by the</td><td class="lineno" valign="top"></td></tr>
701      <tr><td class="lineno" valign="top"></td><td class="left">   same L-GW (i.e., mobility within the local domain), while seamless</td><td> </td><td class="right">   same L-GW (i.e., mobility within the local domain), while seamless</td><td class="lineno" valign="top"></td></tr>
702      <tr><td class="lineno" valign="top"></td><td class="left">   SIPTO mobility is still limited to the case where the SGW/PGW is at</td><td> </td><td class="right">   SIPTO mobility is still limited to the case where the SGW/PGW is at</td><td class="lineno" valign="top"></td></tr>
703      <tr><td class="lineno" valign="top"></td><td class="left">   or above Radio Access Network (RAN) level.</td><td> </td><td class="right">   or above Radio Access Network (RAN) level.</td><td class="lineno" valign="top"></td></tr>
704      <tr><td><a name="diff0060"></a></td></tr>
705      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: But, SGW/PGW is *always* above the RAN!</span></td><td class="lineno" valign="top"></td></tr>
706      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
707      <tr><td class="lineno" valign="top"></td><td class="left">5.  Gap analysis</td><td> </td><td class="right">5.  Gap analysis</td><td class="lineno" valign="top"></td></tr>
708      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
709      <tr><td class="lineno" valign="top"></td><td class="left">   The goal of this section is to identify the limitations in the</td><td> </td><td class="right">   The goal of this section is to identify the limitations in the</td><td class="lineno" valign="top"></td></tr>
710      <tr><td class="lineno" valign="top"></td><td class="left">   current practices, described in Section 4, with respect to the DMM</td><td> </td><td class="right">   current practices, described in Section 4, with respect to the DMM</td><td class="lineno" valign="top"></td></tr>
711      <tr><td class="lineno" valign="top"></td><td class="left">   requirements listed in [I-D.ietf-dmm-requirements].</td><td> </td><td class="right">   requirements listed in [I-D.ietf-dmm-requirements].</td><td class="lineno" valign="top"></td></tr>
712      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
713      <tr><td class="lineno" valign="top"></td><td class="left">5.1.  Distributed processing - REQ1</td><td> </td><td class="right">5.1.  Distributed processing - REQ1</td><td class="lineno" valign="top"></td></tr>
714      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
715      <tr><td class="lineno" valign="top"></td><td class="left">   According to requirement #1 stated in [I-D.ietf-dmm-requirements], IP</td><td> </td><td class="right">   According to requirement #1 stated in [I-D.ietf-dmm-requirements], IP</td><td class="lineno" valign="top"></td></tr>
716      <tr><td><a name="diff0061"></a></td></tr>
717      <tr><td class="lineno" valign="top"></td><td class="lblock">   mobility, network access and routing solutions provided by DMM <span class="delete">MUST</span></td><td> </td><td class="rblock">   mobility, network access and routing solutions provided by DMM <span class="insert">must</span></td><td class="lineno" valign="top"></td></tr>
718      <tr><td class="lineno" valign="top"></td><td class="left">   enable distributed processing for mobility management so that traffic</td><td> </td><td class="right">   enable distributed processing for mobility management so that traffic</td><td class="lineno" valign="top"></td></tr>
719      <tr><td class="lineno" valign="top"></td><td class="left">   can avoid traversing single mobility anchor far from the optimal</td><td> </td><td class="right">   can avoid traversing single mobility anchor far from the optimal</td><td class="lineno" valign="top"></td></tr>
720      <tr><td class="lineno" valign="top"></td><td class="left">   route.</td><td> </td><td class="right">   route.</td><td class="lineno" valign="top"></td></tr>
721      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
722      <tr><td class="lineno" valign="top"></td><td class="left">   From the analysis performed in Section 4, a DMM deployment can meet</td><td> </td><td class="right">   From the analysis performed in Section 4, a DMM deployment can meet</td><td class="lineno" valign="top"></td></tr>
723      <tr><td class="lineno" valign="top"></td><td class="left">   the requirement "REQ#1 Distributed processing" usually relying on the</td><td> </td><td class="right">   the requirement "REQ#1 Distributed processing" usually relying on the</td><td class="lineno" valign="top"></td></tr>
724      <tr><td class="lineno" valign="top"></td><td class="left">   following functions:</td><td> </td><td class="right">   following functions:</td><td class="lineno" valign="top"></td></tr>
725      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
726      <tr><td class="lineno" valign="top"></td><td class="left">   o  Multiple (distributed) anchoring: ability to anchor different</td><td> </td><td class="right">   o  Multiple (distributed) anchoring: ability to anchor different</td><td class="lineno" valign="top"></td></tr>
727      <tr><td class="lineno" valign="top"></td><td class="left">      sessions of a single mobile node at different anchors.  In order</td><td> </td><td class="right">      sessions of a single mobile node at different anchors.  In order</td><td class="lineno" valign="top"></td></tr>
728      <tr><td><a name="diff0062"></a></td></tr>
729      <tr><td class="lineno" valign="top"></td><td class="lblock">      to <span class="delete">make this feature "DMM-friendly"</span>, some anchors might need to be</td><td> </td><td class="rblock">      to <span class="insert">provide improved routing</span>, some anchors might need to be</td><td class="lineno" valign="top"></td></tr>
730      <tr><td class="lineno" valign="top"></td><td class="left">      placed closer to the mobile node.</td><td> </td><td class="right">      placed closer to the mobile node.</td><td class="lineno" valign="top"></td></tr>
731      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
732      <tr><td><a name="diff0063"></a></td></tr>
733      <tr><td class="lineno" valign="top"></td><td class="lblock">   o  Dynamic anchor assignment/re-location: ability to i) <span class="delete">optimally</span></td><td> </td><td class="rblock">   o  Dynamic anchor assignment/re-location: ability to i) assign <span class="insert">the</span></td><td class="lineno" valign="top"></td></tr>
734      <tr><td class="lineno" valign="top"></td><td class="lblock">      assign initial anchor, and ii) dynamically change the initially</td><td> </td><td class="rblock">      initial anchor, and ii) dynamically change the initially</td><td class="lineno" valign="top"></td></tr>
735      <tr><td class="lineno" valign="top"></td><td class="left">      assigned anchor and/or assign a new one (this may also require to</td><td> </td><td class="right">      assigned anchor and/or assign a new one (this may also require to</td><td class="lineno" valign="top"></td></tr>
736      <tr><td class="lineno" valign="top"></td><td class="left">      transfer mobility context between anchors).  This can be achieved</td><td> </td><td class="right">      transfer mobility context between anchors).  This can be achieved</td><td class="lineno" valign="top"></td></tr>
737      <tr><td class="lineno" valign="top"></td><td class="left">      either by changing anchor for all ongoing sessions, or by</td><td> </td><td class="right">      either by changing anchor for all ongoing sessions, or by</td><td class="lineno" valign="top"></td></tr>
738      <tr><td class="lineno" valign="top"></td><td class="left">      assigning new anchors just for new sessions.</td><td> </td><td class="right">      assigning new anchors just for new sessions.</td><td class="lineno" valign="top"></td></tr>
739      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
740      <tr><td class="lineno" valign="top"></td><td class="left">   Both the main client- and network-based IP mobility protocols, namely</td><td> </td><td class="right">   Both the main client- and network-based IP mobility protocols, namely</td><td class="lineno" valign="top"></td></tr>
741      <tr><td class="lineno" valign="top"></td><td class="left">   (DS)MIPv6 and PMIPv6 allow deploying multiple anchors (i.e., home</td><td> </td><td class="right">   (DS)MIPv6 and PMIPv6 allow deploying multiple anchors (i.e., home</td><td class="lineno" valign="top"></td></tr>
742      <tr><td class="lineno" valign="top"></td><td class="left">   agents and localized mobility anchors), therefore providing the</td><td> </td><td class="right">   agents and localized mobility anchors), therefore providing the</td><td class="lineno" valign="top"></td></tr>
743      <tr><td class="lineno" valign="top"></td><td class="left">   multiple anchoring function.  However, existing solutions only</td><td> </td><td class="right">   multiple anchoring function.  However, existing solutions only</td><td class="lineno" valign="top"></td></tr>
744      <tr><td><a name="diff0064"></a></td></tr>
745      <tr><td class="lineno" valign="top"></td><td class="lblock">   provide a<span class="delete">n optimal</span> initial anchor assignment, thus the lack of</td><td> </td><td class="rblock">   provide a initial anchor assignment, thus the lack of</td><td class="lineno" valign="top"></td></tr>
746      <tr><td class="lineno" valign="top"></td><td class="left">   dynamic anchor change/new anchor assignment is a gap.  Neither the HA</td><td> </td><td class="right">   dynamic anchor change/new anchor assignment is a gap.  Neither the HA</td><td class="lineno" valign="top"></td></tr>
747      <tr><td class="lineno" valign="top"></td><td class="left">   switch nor the LMA runtime assignment allow changing the anchor</td><td> </td><td class="right">   switch nor the LMA runtime assignment allow changing the anchor</td><td class="lineno" valign="top"></td></tr>
748      <tr><td class="lineno" valign="top"></td><td class="left">   during an ongoing session.  This actually comprises several gaps:</td><td> </td><td class="right">   during an ongoing session.  This actually comprises several gaps:</td><td class="lineno" valign="top"></td></tr>
749      <tr><td class="lineno" valign="top"></td><td class="left">   ability to perform anchor assignment at any time (not only at the</td><td> </td><td class="right">   ability to perform anchor assignment at any time (not only at the</td><td class="lineno" valign="top"></td></tr>
750      <tr><td class="lineno" valign="top"></td><td class="left">   initial MN's attachment), ability of the current anchor to initiate/</td><td> </td><td class="right">   initial MN's attachment), ability of the current anchor to initiate/</td><td class="lineno" valign="top"></td></tr>
751      <tr><td class="lineno" valign="top"></td><td class="left">   trigger the relocation, and ability to transfer registration context</td><td> </td><td class="right">   trigger the relocation, and ability to transfer registration context</td><td class="lineno" valign="top"></td></tr>
752      <tr><td class="lineno" valign="top"></td><td class="left">   between anchors.</td><td> </td><td class="right">   between anchors.</td><td class="lineno" valign="top"></td></tr>
753      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
754      <tr><td class="lineno" valign="top"></td><td class="left">   Dynamic anchor assignment may lead the MN to manage different</td><td> </td><td class="right">   Dynamic anchor assignment may lead the MN to manage different</td><td class="lineno" valign="top"></td></tr>
755      <tr><td class="lineno" valign="top"></td><td class="left">   mobility sessions served by different mobility anchors.  This is not</td><td> </td><td class="right">   mobility sessions served by different mobility anchors.  This is not</td><td class="lineno" valign="top"></td></tr>
756      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
757      <tr bgcolor="gray"><td></td><th><a name="part-l9"><small>skipping to change at</small><em> page 18, line 11</em></a></th><th> </th><th><a name="part-r9"><small>skipping to change at</small><em> page 18, line 11</em></a></th><td></td></tr>
758      <tr><td class="lineno" valign="top"></td><td class="left">   processing therefore should not contradict with centralized control</td><td> </td><td class="right">   processing therefore should not contradict with centralized control</td><td class="lineno" valign="top"></td></tr>
759      <tr><td class="lineno" valign="top"></td><td class="left">   plane.  Other control plane solutions such as charging, lawful</td><td> </td><td class="right">   plane.  Other control plane solutions such as charging, lawful</td><td class="lineno" valign="top"></td></tr>
760      <tr><td class="lineno" valign="top"></td><td class="left">   interception, etc.  should not be limited.  Yet combining the control</td><td> </td><td class="right">   interception, etc.  should not be limited.  Yet combining the control</td><td class="lineno" valign="top"></td></tr>
761      <tr><td class="lineno" valign="top"></td><td class="left">   plane and data plane routing management (RM) function may limit the</td><td> </td><td class="right">   plane and data plane routing management (RM) function may limit the</td><td class="lineno" valign="top"></td></tr>
762      <tr><td class="lineno" valign="top"></td><td class="left">   choice to distributing boht data plane and control plane together.</td><td> </td><td class="right">   choice to distributing boht data plane and control plane together.</td><td class="lineno" valign="top"></td></tr>
763      <tr><td class="lineno" valign="top"></td><td class="left">   In order to enable distributing only the data plane without</td><td> </td><td class="right">   In order to enable distributing only the data plane without</td><td class="lineno" valign="top"></td></tr>
764      <tr><td class="lineno" valign="top"></td><td class="left">   distributing the control plane, a gap is to split the routing</td><td> </td><td class="right">   distributing the control plane, a gap is to split the routing</td><td class="lineno" valign="top"></td></tr>
765      <tr><td class="lineno" valign="top"></td><td class="left">   management function into the control plane (RM-CP) and data plane</td><td> </td><td class="right">   management function into the control plane (RM-CP) and data plane</td><td class="lineno" valign="top"></td></tr>
766      <tr><td class="lineno" valign="top"></td><td class="left">   (RM-DP).</td><td> </td><td class="right">   (RM-DP).</td><td class="lineno" valign="top"></td></tr>
767      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
768      <tr><td><a name="diff0065"></a></td></tr>
769      <tr><td class="lineno" valign="top"></td><td class="lblock">5.2.  <span class="delete">Bypassable network-layer mobility support - REQ2</span></td><td> </td><td class="rblock">5.2.  <span class="insert">REQ2: On-demand network-layer mobility support</span></td><td class="lineno" valign="top"></td></tr>
770      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
771      <tr><td><a name="diff0066"></a></td></tr>
772      <tr><td class="lineno" valign="top"></td><td class="lblock">   The need for "<span class="delete">bypassable</span> network-layer mobility support" introduced</td><td> </td><td class="rblock">   The need for "<span class="insert">on-demand</span> network-layer mobility support" introduced</td><td class="lineno" valign="top"></td></tr>
773      <tr><td class="lineno" valign="top"></td><td class="left">   in [I-D.ietf-dmm-requirements] will enable dynamic mobility</td><td> </td><td class="right">   in [I-D.ietf-dmm-requirements] will enable dynamic mobility</td><td class="lineno" valign="top"></td></tr>
774      <tr><td><a name="diff0067"></a></td></tr>
775      <tr><td class="lineno" valign="top"></td><td class="lblock">   management.  <span class="delete">Note that this requirement is not on dynamic mobilitly</span></td><td> </td><td class="rblock">   management.  <span class="insert">Flexibility</span> on the</td><td class="lineno" valign="top"></td></tr>
776      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   itself but only enables it.  It therefore leaves flexibility</span> on the</td><td> </td><td class="rblock">   determination of whether network-layer mobility support is <span class="insert">needed.</span></td><td class="lineno" valign="top"></td></tr>
777      <tr><td class="lineno" valign="top"></td><td class="lblock">   determination of whether network-layer mobility support is <span class="delete">needed and</span></td><td> </td><td class="rblock">   The</td><td class="lineno" valign="top"></td></tr>
778      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   the role to use of not use network-layer mobility support.</span>  The</td><td> </td><td class="rblock">   requirement enables one to <span class="insert">choose whether</span> or not use network-layer</td><td class="lineno" valign="top"></td></tr>
779      <tr><td class="lineno" valign="top"></td><td class="lblock">   requirement <span class="delete">only</span> enables one to <span class="delete">use</span> or not use network-layer mobility</td><td> </td><td class="rblock">   mobility support.  It only enables the two following functions:</td><td class="lineno" valign="top"></td></tr>
780      <tr><td class="lineno" valign="top"></td><td class="lblock">   support.  It only enables <span class="delete">the which basically leverages</span> the two</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
781      <tr><td class="lineno" valign="top"></td><td class="lblock">   following functions:</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
782      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
783      <tr><td class="lineno" valign="top"></td><td class="left">   o  Dynamically assign/relocate anchor: a mobility anchor is assigned</td><td> </td><td class="right">   o  Dynamically assign/relocate anchor: a mobility anchor is assigned</td><td class="lineno" valign="top"></td></tr>
784      <tr><td class="lineno" valign="top"></td><td class="left">      only to sessions which uses the network-layer mobility support.</td><td> </td><td class="right">      only to sessions which uses the network-layer mobility support.</td><td class="lineno" valign="top"></td></tr>
785      <tr><td class="lineno" valign="top"></td><td class="left">      The MN may thus manage more than one session; some of them may be</td><td> </td><td class="right">      The MN may thus manage more than one session; some of them may be</td><td class="lineno" valign="top"></td></tr>
786      <tr><td class="lineno" valign="top"></td><td class="left">      associated with anchored IP address(es), while the others may be</td><td> </td><td class="right">      associated with anchored IP address(es), while the others may be</td><td class="lineno" valign="top"></td></tr>
787      <tr><td class="lineno" valign="top"></td><td class="left">      associated with local IP address(es).</td><td> </td><td class="right">      associated with local IP address(es).</td><td class="lineno" valign="top"></td></tr>
788      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
789      <tr><td class="lineno" valign="top"></td><td class="left">   o  Multiple IP address management: this function is related to the</td><td> </td><td class="right">   o  Multiple IP address management: this function is related to the</td><td class="lineno" valign="top"></td></tr>
790      <tr><td class="lineno" valign="top"></td><td class="left">      preceding and is about the ability of the mobile node to</td><td> </td><td class="right">      preceding and is about the ability of the mobile node to</td><td class="lineno" valign="top"></td></tr>
791      <tr><td class="lineno" valign="top"></td><td class="left">      simultaneously use multiple IP addresses and select the best one</td><td> </td><td class="right">      simultaneously use multiple IP addresses and select the best one</td><td class="lineno" valign="top"></td></tr>
792      <tr><td class="lineno" valign="top"></td><td class="left">      (from an anchoring point of view) to use on a per-session/</td><td> </td><td class="right">      (from an anchoring point of view) to use on a per-session/</td><td class="lineno" valign="top"></td></tr>
793      <tr><td class="lineno" valign="top"></td><td class="left">      application/service basis.</td><td> </td><td class="right">      application/service basis.</td><td class="lineno" valign="top"></td></tr>
794      <tr><td><a name="diff0068"></a></td></tr>
795      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: Problem: this requires MN to acquire network topology information</span></td><td class="lineno" valign="top"></td></tr>
796      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
797      <tr><td class="lineno" valign="top"></td><td class="left">   The dynamic anchor assignment/relocation needs to ensure that IP</td><td> </td><td class="right">   The dynamic anchor assignment/relocation needs to ensure that IP</td><td class="lineno" valign="top"></td></tr>
798      <tr><td class="lineno" valign="top"></td><td class="left">   address continuity is guaranteed for sessions that uses such mobility</td><td> </td><td class="right">   address continuity is guaranteed for sessions that uses such mobility</td><td class="lineno" valign="top"></td></tr>
799      <tr><td class="lineno" valign="top"></td><td class="left">   support (e.g., in some scenarios, the provision of mobility locally</td><td> </td><td class="right">   support (e.g., in some scenarios, the provision of mobility locally</td><td class="lineno" valign="top"></td></tr>
800      <tr><td class="lineno" valign="top"></td><td class="left">   within a limited area might be enough from the mobile node or the</td><td> </td><td class="right">   within a limited area might be enough from the mobile node or the</td><td class="lineno" valign="top"></td></tr>
801      <tr><td class="lineno" valign="top"></td><td class="left">   application point of view) at the relocated anchor.  Implicitly, when</td><td> </td><td class="right">   application point of view) at the relocated anchor.  Implicitly, when</td><td class="lineno" valign="top"></td></tr>
802      <tr><td class="lineno" valign="top"></td><td class="left">   no applications are using the network-layer mobility support, DMM may</td><td> </td><td class="right">   no applications are using the network-layer mobility support, DMM may</td><td class="lineno" valign="top"></td></tr>
803      <tr><td><a name="diff0069"></a></td></tr>
804      <tr><td class="lineno" valign="top"></td><td class="lblock">   relea<span class="delete">v</span>e the needed resources.  This may imply having the knowledge of</td><td> </td><td class="rblock">   relea<span class="insert">s</span>e the needed resources.  This may imply having the knowledge of</td><td class="lineno" valign="top"></td></tr>
805      <tr><td class="lineno" valign="top"></td><td class="left">   which sessions at the mobile node are active and are using the</td><td> </td><td class="right">   which sessions at the mobile node are active and are using the</td><td class="lineno" valign="top"></td></tr>
806      <tr><td class="lineno" valign="top"></td><td class="left">   mobility support.  This is something typically known only by the MN</td><td> </td><td class="right">   mobility support.  This is something typically known only by the MN</td><td class="lineno" valign="top"></td></tr>
807      <tr><td class="lineno" valign="top"></td><td class="left">   (e.g., by its connection manager).  Therefore, (part of) this</td><td> </td><td class="right">   (e.g., by its connection manager).  Therefore, (part of) this</td><td class="lineno" valign="top"></td></tr>
808      <tr><td class="lineno" valign="top"></td><td class="left">   knowledge might need to be transferred to/shared with the network.</td><td> </td><td class="right">   knowledge might need to be transferred to/shared with the network.</td><td class="lineno" valign="top"></td></tr>
809      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
810      <tr><td class="lineno" valign="top"></td><td class="left">   Multiple IP address management provides the MN with the choice to</td><td> </td><td class="right">   Multiple IP address management provides the MN with the choice to</td><td class="lineno" valign="top"></td></tr>
811      <tr><td class="lineno" valign="top"></td><td class="left">   pick-up the correct address (provided with mobility support or not)</td><td> </td><td class="right">   pick-up the correct address (provided with mobility support or not)</td><td class="lineno" valign="top"></td></tr>
812      <tr><td class="lineno" valign="top"></td><td class="left">   depending on the application requirements.  When using client based</td><td> </td><td class="right">   depending on the application requirements.  When using client based</td><td class="lineno" valign="top"></td></tr>
813      <tr><td><a name="diff0070"></a></td></tr>
814      <tr><td class="lineno" valign="top"></td><td class="lblock">   mobility management, the mobile node is <span class="delete">natively</span> aware <span class="delete">about</span> the</td><td> </td><td class="rblock">   mobility management, the mobile node is <span class="insert">itself</span> aware <span class="insert">of</span> the anchoring</td><td class="lineno" valign="top"></td></tr>
815      <tr><td class="lineno" valign="top"></td><td class="lblock">   anchoring capabilities of its assigned IP addresses.  This is not the</td><td> </td><td class="rblock">   capabilities of its assigned IP addresses.  This is not <span class="insert">necessarily</span> the</td><td class="lineno" valign="top"></td></tr>
816      <tr><td class="lineno" valign="top"></td><td class="lblock">   case with network based IP mobility <span class="delete">management and</span> current mechanisms</td><td> </td><td class="rblock">   case with network based IP mobility <span class="insert">management;</span> current mechanisms</td><td class="lineno" valign="top"></td></tr>
817      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">does</span> not allow the MN to be aware of the IP addresses <span class="delete">properties</span></td><td> </td><td class="rblock">   <span class="insert">do</span> not allow the MN to be aware of the <span class="insert">properties of its</span> IP addresses</td><td class="lineno" valign="top"></td></tr>
818      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   (i.e.,</span> the MN does not know whether the allocated IP addresses are</td><td> </td><td class="rblock">   <span class="insert">(e.g.,</span> the MN does not know whether the allocated IP addresses are</td><td class="lineno" valign="top"></td></tr>
819      <tr><td class="lineno" valign="top"></td><td class="lblock">   anchored).  However, there are <span class="delete">ongoing IETF works that are proposing</span></td><td> </td><td class="rblock">   anchored).  However, there are <span class="insert">proposals</span></td><td class="lineno" valign="top"></td></tr>
820      <tr><td class="lineno" valign="top"></td><td class="lblock">   that the network could indicate <span class="delete">the different</span> IP <span class="delete">addresses</span> properties</td><td> </td><td class="rblock">   that the network could indicate <span class="insert">such</span> IP <span class="insert">address</span> properties</td><td class="lineno" valign="top"></td></tr>
821      <tr><td class="lineno" valign="top"></td><td class="left">   during assignment procedures, such as</td><td> </td><td class="right">   during assignment procedures, such as</td><td class="lineno" valign="top"></td></tr>
822      <tr><td class="lineno" valign="top"></td><td class="left">   [I-D.bhandari-dhc-class-based-prefix],</td><td> </td><td class="right">   [I-D.bhandari-dhc-class-based-prefix],</td><td class="lineno" valign="top"></td></tr>
823      <tr><td class="lineno" valign="top"></td><td class="left">   [I-D.korhonen-6man-prefix-properties] and [I-D.anipko-mif-mpvd-arch].</td><td> </td><td class="right">   [I-D.korhonen-6man-prefix-properties] and [I-D.anipko-mif-mpvd-arch].</td><td class="lineno" valign="top"></td></tr>
824      <tr><td><a name="diff0071"></a></td></tr>
825      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">However, although</span> there exist these individual efforts that could be</td><td> </td><td class="rblock">   <span class="insert">Although</span> there exist these individual efforts that could be</td><td class="lineno" valign="top"></td></tr>
826      <tr><td class="lineno" valign="top"></td><td class="lblock">   be considered as attempts to fix the gap, there is no solution <span class="delete">close</span></td><td> </td><td class="rblock">   be considered as attempts to fix the gap, there is no solution adopted</td><td class="lineno" valign="top"></td></tr>
827      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   to be</span> adopted <span class="delete">and standardized in IETF.</span></td><td> </td><td class="rblock">   <span class="insert">as a work item within any IETF working group.</span></td><td class="lineno" valign="top"></td></tr>
828      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
829      <tr><td class="lineno" valign="top"></td><td class="left">5.3.  IPv6 deployment - REQ3</td><td> </td><td class="right">5.3.  IPv6 deployment - REQ3</td><td class="lineno" valign="top"></td></tr>
830      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
831      <tr><td><a name="diff0072"></a></td></tr>
832      <tr><td class="lineno" valign="top"></td><td class="lblock">   This requirement states that DMM solutions <span class="delete">SHOULD</span> primarily target</td><td> </td><td class="rblock">   This requirement states that DMM solutions <span class="insert">should</span> primarily target</td><td class="lineno" valign="top"></td></tr>
833      <tr><td class="lineno" valign="top"></td><td class="left">   IPv6 as the primary deployment environment.  IPv4 support is not</td><td> </td><td class="right">   IPv6 as the primary deployment environment.  IPv4 support is not</td><td class="lineno" valign="top"></td></tr>
834      <tr><td><a name="diff0073"></a></td></tr>
835      <tr><td class="lineno" valign="top"></td><td class="lblock">   considered mandatory and solutions <span class="delete">SHOULD NOT</span> be tailored</td><td> </td><td class="rblock">   considered mandatory and solutions <span class="insert">should not</span> be tailored</td><td class="lineno" valign="top"></td></tr>
836      <tr><td class="lineno" valign="top"></td><td class="lblock">   specifically to support <span class="delete">IPv4, in</span> particular in situations where</td><td> </td><td class="rblock">   specifically to support <span class="insert">IPv4.</span></td><td class="lineno" valign="top"></td></tr>
837      <tr><td class="lineno" valign="top"></td><td class="lblock">   private IPv4 addresses and/or NATs are <span class="delete">used.</span></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
838      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP:  "in</span> particular in situations where private IPv4 addresses</td><td class="lineno" valign="top"></td></tr>
839      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">       and/or NATs are <span class="insert">used." -- why is this needed??</span></td><td class="lineno" valign="top"></td></tr>
840      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
841      <tr><td class="lineno" valign="top"></td><td class="left">   All analyzed DMM practices support IPv6.  Some of them, such as MIPv6</td><td> </td><td class="right">   All analyzed DMM practices support IPv6.  Some of them, such as MIPv6</td><td class="lineno" valign="top"></td></tr>
842      <tr><td class="lineno" valign="top"></td><td class="left">   /NEMO (including the support of dynamic HA selection), MOBIKE, SIPTO</td><td> </td><td class="right">   /NEMO (including the support of dynamic HA selection), MOBIKE, SIPTO</td><td class="lineno" valign="top"></td></tr>
843      <tr><td><a name="diff0074"></a></td></tr>
844      <tr><td class="lineno" valign="top"></td><td class="lblock">   have also IPv4 support.  <span class="delete">Additionally, there</span> are also some solutions</td><td> </td><td class="rblock">   have also IPv4 support.</td><td class="lineno" valign="top"></td></tr>
845      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: Does this mean that MOBIKE, SIPTO, and NEMO are "analyzed DMM practices"?</span></td><td class="lineno" valign="top"></td></tr>
846      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">                            There</span> are also some solutions</td><td class="lineno" valign="top"></td></tr>
847      <tr><td class="lineno" valign="top"></td><td class="left">   that have some limited IPv4 support (e.g., PMIPv6).  In conclusion,</td><td> </td><td class="right">   that have some limited IPv4 support (e.g., PMIPv6).  In conclusion,</td><td class="lineno" valign="top"></td></tr>
848      <tr><td class="lineno" valign="top"></td><td class="left">   this requirement is met by existing DMM practices.</td><td> </td><td class="right">   this requirement is met by existing DMM practices.</td><td class="lineno" valign="top"></td></tr>
849      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
850      <tr><td class="lineno" valign="top"></td><td class="left">5.4.  Existing mobility protocols - REQ4</td><td> </td><td class="right">5.4.  Existing mobility protocols - REQ4</td><td class="lineno" valign="top"></td></tr>
851      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
852      <tr><td><a name="diff0075"></a></td></tr>
853      <tr><td class="lineno" valign="top"></td><td class="lblock">   A DMM solution <span class="delete">MUST</span> first consider reusing and extending IETF-</td><td> </td><td class="rblock">   A DMM solution <span class="insert">must</span> first consider reusing and extending IETF-</td><td class="lineno" valign="top"></td></tr>
854      <tr><td class="lineno" valign="top"></td><td class="left">   standardized protocols before specifying new protocols.</td><td> </td><td class="right">   standardized protocols before specifying new protocols.</td><td class="lineno" valign="top"></td></tr>
855      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
856      <tr><td class="lineno" valign="top"></td><td class="left">   As stated in [I-D.ietf-dmm-requirements], a DMM solution could reuse</td><td> </td><td class="right">   As stated in [I-D.ietf-dmm-requirements], a DMM solution could reuse</td><td class="lineno" valign="top"></td></tr>
857      <tr><td class="lineno" valign="top"></td><td class="left">   existing IETF and standardized protocols before specifying new</td><td> </td><td class="right">   existing IETF and standardized protocols before specifying new</td><td class="lineno" valign="top"></td></tr>
858      <tr><td class="lineno" valign="top"></td><td class="left">   protocols.  Besides, Section 4 of this document discusses various</td><td> </td><td class="right">   protocols.  Besides, Section 4 of this document discusses various</td><td class="lineno" valign="top"></td></tr>
859      <tr><td class="lineno" valign="top"></td><td class="left">   ways to flatten and distribute current mobility solutions.  Actually,</td><td> </td><td class="right">   ways to flatten and distribute current mobility solutions.  Actually,</td><td class="lineno" valign="top"></td></tr>
860      <tr><td class="lineno" valign="top"></td><td class="left">   nothing prevent the distribution of mobility functions with vanilla</td><td> </td><td class="right">   nothing prevent the distribution of mobility functions with vanilla</td><td class="lineno" valign="top"></td></tr>
861      <tr><td><a name="diff0076"></a></td></tr>
862      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: "vanilla"??</span></td><td class="lineno" valign="top"></td></tr>
863      <tr><td class="lineno" valign="top"></td><td class="left">   IP mobility protocols.  However, as discussed in Section 5.1 and</td><td> </td><td class="right">   IP mobility protocols.  However, as discussed in Section 5.1 and</td><td class="lineno" valign="top"></td></tr>
864      <tr><td class="lineno" valign="top"></td><td class="left">   Section 5.2, limitations exist.  The 3GPP data plane anchoring</td><td> </td><td class="right">   Section 5.2, limitations exist.  The 3GPP data plane anchoring</td><td class="lineno" valign="top"></td></tr>
865      <tr><td class="lineno" valign="top"></td><td class="left">   function, i.e., the PGW, can be also be distributed, but with</td><td> </td><td class="right">   function, i.e., the PGW, can be also be distributed, but with</td><td class="lineno" valign="top"></td></tr>
866      <tr><td class="lineno" valign="top"></td><td class="left">   limitations; e.g., no anchoring relocation, no context transfer</td><td> </td><td class="right">   limitations; e.g., no anchoring relocation, no context transfer</td><td class="lineno" valign="top"></td></tr>
867      <tr><td class="lineno" valign="top"></td><td class="left">   between anchors, centralized control plane.  The 3GPP architecture is</td><td> </td><td class="right">   between anchors, centralized control plane.  The 3GPP architecture is</td><td class="lineno" valign="top"></td></tr>
868      <tr><td class="lineno" valign="top"></td><td class="left">   also going into the direction of flattening with SIPTO and LIPA,</td><td> </td><td class="right">   also going into the direction of flattening with SIPTO and LIPA,</td><td class="lineno" valign="top"></td></tr>
869      <tr><td class="lineno" valign="top"></td><td class="left">   though they do not provide mobility support.</td><td> </td><td class="right">   though they do not provide mobility support.</td><td class="lineno" valign="top"></td></tr>
870      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
871      <tr><td class="lineno" valign="top"></td><td class="left">5.5.  Co-existence - REQ5</td><td> </td><td class="right">5.5.  Co-existence - REQ5</td><td class="lineno" valign="top"></td></tr>
872      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
873      <tr><td><a name="diff0077"></a></td></tr>
874      <tr><td class="lineno" valign="top"></td><td class="lblock">   According to [I-D.ietf-dmm-requirements], DMM solution <span class="delete">MUST</span> be able</td><td> </td><td class="rblock">   According to [I-D.ietf-dmm-requirements], DMM solution <span class="insert">must</span> be able</td><td class="lineno" valign="top"></td></tr>
875      <tr><td class="lineno" valign="top"></td><td class="left">   to co-exist with existing network deployments, end hosts and routers.</td><td> </td><td class="right">   to co-exist with existing network deployments, end hosts and routers.</td><td class="lineno" valign="top"></td></tr>
876      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
877      <tr><td class="lineno" valign="top"></td><td class="left">   All current mobility protocols can co-exist with existing network</td><td> </td><td class="right">   All current mobility protocols can co-exist with existing network</td><td class="lineno" valign="top"></td></tr>
878      <tr><td class="lineno" valign="top"></td><td class="left">   deployments and end hosts.  There is no gap between existing mobility</td><td> </td><td class="right">   deployments and end hosts.  There is no gap between existing mobility</td><td class="lineno" valign="top"></td></tr>
879      <tr><td class="lineno" valign="top"></td><td class="left">   protocols and this requirement.</td><td> </td><td class="right">   protocols and this requirement.</td><td class="lineno" valign="top"></td></tr>
880      <tr><td><a name="diff0078"></a></td></tr>
881      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: "can co-exist with" means "do not interfere with"?</span></td><td class="lineno" valign="top"></td></tr>
882      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
883      <tr><td class="lineno" valign="top"></td><td class="left">5.6.  Security considerations - REQ6</td><td> </td><td class="right">5.6.  Security considerations - REQ6</td><td class="lineno" valign="top"></td></tr>
884      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
885      <tr><td><a name="diff0079"></a></td></tr>
886      <tr><td class="lineno" valign="top"></td><td class="lblock">   As stated in [I-D.ietf-dmm-requirements], a DMM solution <span class="delete">MUST NOT</span> NOT</td><td> </td><td class="rblock">   As stated in [I-D.ietf-dmm-requirements], a DMM solution <span class="insert">must</span> NOT</td><td class="lineno" valign="top"></td></tr>
887      <tr><td class="lineno" valign="top"></td><td class="left">   introduce new security risks, or amplify existing security risks,</td><td> </td><td class="right">   introduce new security risks, or amplify existing security risks,</td><td class="lineno" valign="top"></td></tr>
888      <tr><td class="lineno" valign="top"></td><td class="left">   that cannot be mitigated by existing security mechanisms or</td><td> </td><td class="right">   that cannot be mitigated by existing security mechanisms or</td><td class="lineno" valign="top"></td></tr>
889      <tr><td class="lineno" valign="top"></td><td class="left">   protocols.  Current mobility protocols have all security mechanisms</td><td> </td><td class="right">   protocols.  Current mobility protocols have all security mechanisms</td><td class="lineno" valign="top"></td></tr>
890      <tr><td class="lineno" valign="top"></td><td class="left">   in place.  For example, Mobile IPv6 defines security features to</td><td> </td><td class="right">   in place.  For example, Mobile IPv6 defines security features to</td><td class="lineno" valign="top"></td></tr>
891      <tr><td class="lineno" valign="top"></td><td class="left">   protect binding updates both to home agents and correspondent nodes.</td><td> </td><td class="right">   protect binding updates both to home agents and correspondent nodes.</td><td class="lineno" valign="top"></td></tr>
892      <tr><td class="lineno" valign="top"></td><td class="left">   It also defines mechanisms to protect the data packets transmission</td><td> </td><td class="right">   It also defines mechanisms to protect the data packets transmission</td><td class="lineno" valign="top"></td></tr>
893      <tr><td><a name="diff0080"></a></td></tr>
894      <tr><td class="lineno" valign="top"></td><td class="lblock">   for Mobile IPv6 users.  Proxy Mobile IPv6 and other variation of</td><td> </td><td class="rblock">   for Mobile IPv6 users.  Proxy Mobile IPv6 and other variation<span class="insert">s</span> of</td><td class="lineno" valign="top"></td></tr>
895      <tr><td class="lineno" valign="top"></td><td class="left">   mobile IP also have similar security considerations.</td><td> </td><td class="right">   mobile IP also have similar security considerations.</td><td class="lineno" valign="top"></td></tr>
896      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
897      <tr><td class="lineno" valign="top"></td><td class="left">5.7.  Multicast - REQ7</td><td> </td><td class="right">5.7.  Multicast - REQ7</td><td class="lineno" valign="top"></td></tr>
898      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
899      <tr><td><a name="diff0081"></a></td></tr>
900      <tr><td class="lineno" valign="top"></td><td class="lblock">   It is stated in [I-D.ietf-dmm-requirements] that DMM solutions <span class="delete">SHOULD</span></td><td> </td><td class="rblock">   It is stated in [I-D.ietf-dmm-requirements] that DMM solutions <span class="insert">should</span></td><td class="lineno" valign="top"></td></tr>
901      <tr><td class="lineno" valign="top"></td><td class="left">   enable multicast solutions to be developed to avoid network</td><td> </td><td class="right">   enable multicast solutions to be developed to avoid network</td><td class="lineno" valign="top"></td></tr>
902      <tr><td class="lineno" valign="top"></td><td class="left">   inefficiency in multicast traffic delivery.</td><td> </td><td class="right">   inefficiency in multicast traffic delivery.</td><td class="lineno" valign="top"></td></tr>
903      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
904      <tr><td class="lineno" valign="top"></td><td class="left">   Current IP mobility solutions address mainly the mobility problem for</td><td> </td><td class="right">   Current IP mobility solutions address mainly the mobility problem for</td><td class="lineno" valign="top"></td></tr>
905      <tr><td class="lineno" valign="top"></td><td class="left">   unicast traffic.  Solutions relying on the use of an anchor point for</td><td> </td><td class="right">   unicast traffic.  Solutions relying on the use of an anchor point for</td><td class="lineno" valign="top"></td></tr>
906      <tr><td class="lineno" valign="top"></td><td class="left">   tunneling multicast traffic down to the access router, or to the</td><td> </td><td class="right">   tunneling multicast traffic down to the access router, or to the</td><td class="lineno" valign="top"></td></tr>
907      <tr><td class="lineno" valign="top"></td><td class="left">   mobile node, introduce the so-called "tunnel convergence problem".</td><td> </td><td class="right">   mobile node, introduce the so-called "tunnel convergence problem".</td><td class="lineno" valign="top"></td></tr>
908      <tr><td class="lineno" valign="top"></td><td class="left">   This means that multiple instances of the same multicast traffic can</td><td> </td><td class="right">   This means that multiple instances of the same multicast traffic can</td><td class="lineno" valign="top"></td></tr>
909      <tr><td><a name="diff0082"></a></td></tr>
910      <tr><td class="lineno" valign="top"></td><td class="lblock">   converge to the same node, d<span class="delete">efeating hence</span> the advantage of using</td><td> </td><td class="rblock">   converge to the same node, d<span class="insert">iminishing</span> the advantage of using</td><td class="lineno" valign="top"></td></tr>
911      <tr><td class="lineno" valign="top"></td><td class="left">   multicast protocols.</td><td> </td><td class="right">   multicast protocols.</td><td class="lineno" valign="top"></td></tr>
912      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
913      <tr><td class="lineno" valign="top"></td><td class="left">   The MULTIMOB WG in IETF has studied this issue, for the specific case</td><td> </td><td class="right">   The MULTIMOB WG in IETF has studied this issue, for the specific case</td><td class="lineno" valign="top"></td></tr>
914      <tr><td class="lineno" valign="top"></td><td class="left">   of PMIPv6, and has produced a baseline solution [RFC6224] as well as</td><td> </td><td class="right">   of PMIPv6, and has produced a baseline solution [RFC6224] as well as</td><td class="lineno" valign="top"></td></tr>
915      <tr><td class="lineno" valign="top"></td><td class="left">   a routing optimization solution [RFC7028] to address the problem.</td><td> </td><td class="right">   a routing optimization solution [RFC7028] to address the problem.</td><td class="lineno" valign="top"></td></tr>
916      <tr><td class="lineno" valign="top"></td><td class="left">   The baseline solution suggests deploying an MLD proxy function at the</td><td> </td><td class="right">   The baseline solution suggests deploying an MLD proxy function at the</td><td class="lineno" valign="top"></td></tr>
917      <tr><td class="lineno" valign="top"></td><td class="left">   MAG, and either a multicast router or another MLD proxy function at</td><td> </td><td class="right">   MAG, and either a multicast router or another MLD proxy function at</td><td class="lineno" valign="top"></td></tr>
918      <tr><td class="lineno" valign="top"></td><td class="left">   the LMA.  The routing optimization solution describes an architecture</td><td> </td><td class="right">   the LMA.  The routing optimization solution describes an architecture</td><td class="lineno" valign="top"></td></tr>
919      <tr><td class="lineno" valign="top"></td><td class="left">   where a dedicated multicast tree mobility anchor (MTMA) or a direct</td><td> </td><td class="right">   where a dedicated multicast tree mobility anchor (MTMA) or a direct</td><td class="lineno" valign="top"></td></tr>
920      <tr><td class="lineno" valign="top"></td><td class="left">   routing option can be used to avoid the tunnel convergence problem.</td><td> </td><td class="right">   routing option can be used to avoid the tunnel convergence problem.</td><td class="lineno" valign="top"></td></tr>
921      <tr><td><a name="diff0083"></a></td></tr>
922      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: What is "a direct routing option"?</span></td><td class="lineno" valign="top"></td></tr>
923      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
924      <tr><td><a name="diff0084"></a></td></tr>
925      <tr><td class="lineno" valign="top"></td><td class="lblock">   Besides the solutions proposed in MULTIMOB for PMIPv6, there are no</td><td> </td><td class="rblock">   Besides the solutions proposed in MULTIMOB for PMIPv6, <span class="insert">within the IETF</span></td><td class="lineno" valign="top"></td></tr>
926      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">   there are no <span class="insert">other</span></td><td class="lineno" valign="top"></td></tr>
927      <tr><td class="lineno" valign="top"></td><td class="left">   solutions for other mobility protocols to address the multicast</td><td> </td><td class="right">   solutions for other mobility protocols to address the multicast</td><td class="lineno" valign="top"></td></tr>
928      <tr><td class="lineno" valign="top"></td><td class="left">   tunnel convergence problem.</td><td> </td><td class="right">   tunnel convergence problem.</td><td class="lineno" valign="top"></td></tr>
929      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
930      <tr><td class="lineno" valign="top"></td><td class="left">5.8.  Summary</td><td> </td><td class="right">5.8.  Summary</td><td class="lineno" valign="top"></td></tr>
931      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
932      <tr><td class="lineno" valign="top"></td><td class="left">   We next list the main gaps identified from the analysis performed</td><td> </td><td class="right">   We next list the main gaps identified from the analysis performed</td><td class="lineno" valign="top"></td></tr>
933      <tr><td class="lineno" valign="top"></td><td class="left">   above:</td><td> </td><td class="right">   above:</td><td class="lineno" valign="top"></td></tr>
934      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
935      <tr><td><a name="diff0085"></a></td></tr>
936      <tr><td class="lineno" valign="top"></td><td class="lblock">   o  Existing solutions <span class="delete">do </span>only provide an optimal initial anchor</td><td> </td><td class="rblock">   o  Existing solutions only provide an optimal initial anchor</td><td class="lineno" valign="top"></td></tr>
937      <tr><td class="lineno" valign="top"></td><td class="left">      assignment, a gap being the lack of dynamic anchor change/new</td><td> </td><td class="right">      assignment, a gap being the lack of dynamic anchor change/new</td><td class="lineno" valign="top"></td></tr>
938      <tr><td class="lineno" valign="top"></td><td class="left">      anchor assignment.  Neither the HA switch nor the LMA runtime</td><td> </td><td class="right">      anchor assignment.  Neither the HA switch nor the LMA runtime</td><td class="lineno" valign="top"></td></tr>
939      <tr><td class="lineno" valign="top"></td><td class="left">      assignment allow changing the anchor during an ongoing session.</td><td> </td><td class="right">      assignment allow changing the anchor during an ongoing session.</td><td class="lineno" valign="top"></td></tr>
940      <tr><td class="lineno" valign="top"></td><td class="left">      While MOBIKE could be used to switch from a gateway to another in</td><td> </td><td class="right">      While MOBIKE could be used to switch from a gateway to another in</td><td class="lineno" valign="top"></td></tr>
941      <tr><td class="lineno" valign="top"></td><td class="left">      the middle of a session from MN side, there is no protocol support</td><td> </td><td class="right">      the middle of a session from MN side, there is no protocol support</td><td class="lineno" valign="top"></td></tr>
942      <tr><td class="lineno" valign="top"></td><td class="left">      for the network side.</td><td> </td><td class="right">      for the network side.</td><td class="lineno" valign="top"></td></tr>
943      <tr><td><a name="diff0086"></a></td></tr>
944      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: What about HAHA?</span></td><td class="lineno" valign="top"></td></tr>
945      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
946      <tr><td class="lineno" valign="top"></td><td class="left">   o  The mobile node needs to simultaneously use multiple IP addresses,</td><td> </td><td class="right">   o  The mobile node needs to simultaneously use multiple IP addresses,</td><td class="lineno" valign="top"></td></tr>
947      <tr><td><a name="diff0087"></a></td></tr>
948      <tr><td class="lineno" valign="top"></td><td class="lblock">      which requires <span class="delete">additional </span>support which might not be available on</td><td> </td><td class="rblock">      which requires support which might not be available on</td><td class="lineno" valign="top"></td></tr>
949      <tr><td class="lineno" valign="top"></td><td class="left">      the mobile node's stack, especially for the case of network-based</td><td> </td><td class="right">      the mobile node's stack, especially for the case of network-based</td><td class="lineno" valign="top"></td></tr>
950      <tr><td class="lineno" valign="top"></td><td class="left">      solutions.</td><td> </td><td class="right">      solutions.</td><td class="lineno" valign="top"></td></tr>
951      <tr><td><a name="diff0088"></a></td></tr>
952      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: All IPv6 nodes can use multiple IP addresses.  Something here is</span></td><td class="lineno" valign="top"></td></tr>
953      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">       not stated correctly.</span></td><td class="lineno" valign="top"></td></tr>
954      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
955      <tr><td class="lineno" valign="top"></td><td class="left">   o  Currently, there is no efficient mechanism specified by the IETF</td><td> </td><td class="right">   o  Currently, there is no efficient mechanism specified by the IETF</td><td class="lineno" valign="top"></td></tr>
956      <tr><td class="lineno" valign="top"></td><td class="left">      that allows to dynamically discover the presence of nodes that can</td><td> </td><td class="right">      that allows to dynamically discover the presence of nodes that can</td><td class="lineno" valign="top"></td></tr>
957      <tr><td class="lineno" valign="top"></td><td class="left">      play the role of anchor, discover their capabilities and allow the</td><td> </td><td class="right">      play the role of anchor, discover their capabilities and allow the</td><td class="lineno" valign="top"></td></tr>
958      <tr><td><a name="diff0089"></a></td></tr>
959      <tr><td class="lineno" valign="top"></td><td class="lblock">      selection of the most suitable one.  <span class="delete">There are though some</span></td><td> </td><td class="rblock">      selection of the most suitable one.  <span class="insert">However, the following</span></td><td class="lineno" valign="top"></td></tr>
960      <tr><td class="lineno" valign="top"></td><td class="lblock">      mechanisms that could help discovering <span class="delete">anchors, such as the</span></td><td> </td><td class="rblock">      mechanisms that could help discovering <span class="insert">anchors:</span></td><td class="lineno" valign="top"></td></tr>
961      <tr><td class="lineno" valign="top"></td><td class="lblock">      Dynamic Home Agent Address Discovery <span class="delete">(DHAAD),</span> the use of the Home</td><td> </td><td class="rblock"><span class="insert">      o</span> Dynamic Home Agent Address Discovery <span class="insert">(DHAAD)</span></td><td class="lineno" valign="top"></td></tr>
962      <tr><td class="lineno" valign="top"></td><td class="lblock">      Agent (H) flag in Router Advertisements (which indicates that the</td><td> </td><td class="rblock"><span class="insert">      o</span> the use of the Home Agent (H) flag in Router Advertisements</td><td class="lineno" valign="top"></td></tr>
963      <tr><td class="lineno" valign="top"></td><td class="lblock">      router sending the Router Advertisement is also functioning as a</td><td> </td><td class="rblock">        (which indicates that the router sending the Router Advertisement</td><td class="lineno" valign="top"></td></tr>
964      <tr><td class="lineno" valign="top"></td><td class="lblock">      Mobile IPv6 home agent on the <span class="delete">link) or</span> the MAP option in Router</td><td> </td><td class="rblock">         is also functioning as a Mobile IPv6 home agent on the <span class="insert">link), and</span></td><td class="lineno" valign="top"></td></tr>
965      <tr><td class="lineno" valign="top"></td><td class="lblock">      Advertisements defined by HMIPv6.</td><td> </td><td class="rblock"><span class="insert">      o</span> the MAP option in Router Advertisements defined by HMIPv6.</td><td class="lineno" valign="top"></td></tr>
966      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
967      <tr><td class="lineno" valign="top"></td><td class="left">   o  While existing network-based DMM practices may allow to deploy</td><td> </td><td class="right">   o  While existing network-based DMM practices may allow to deploy</td><td class="lineno" valign="top"></td></tr>
968      <tr><td class="lineno" valign="top"></td><td class="left">      multiple LMAs and dynamically select the best one, this requires</td><td> </td><td class="right">      multiple LMAs and dynamically select the best one, this requires</td><td class="lineno" valign="top"></td></tr>
969      <tr><td class="lineno" valign="top"></td><td class="left">      to still keep some centralization in the control plane, to access</td><td> </td><td class="right">      to still keep some centralization in the control plane, to access</td><td class="lineno" valign="top"></td></tr>
970      <tr><td><a name="diff0090"></a></td></tr>
971      <tr><td class="lineno" valign="top"></td><td class="lblock">      <span class="delete">on the policy stor</span>e (as defined in RFC5213).  Currently, there is</td><td> </td><td class="rblock">      <span class="insert">the policy databas</span>e (as defined in RFC5213).  Currently, there is</td><td class="lineno" valign="top"></td></tr>
972      <tr><td class="lineno" valign="top"></td><td class="left">      a lack of solutions/extensions that support a clear control and</td><td> </td><td class="right">      a lack of solutions/extensions that support a clear control and</td><td class="lineno" valign="top"></td></tr>
973      <tr><td class="lineno" valign="top"></td><td class="left">      data plane separation for IETF IP mobility protocols.</td><td> </td><td class="right">      data plane separation for IETF IP mobility protocols.</td><td class="lineno" valign="top"></td></tr>
974      <tr><td><a name="diff0091"></a></td></tr>
975      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">CEP: There is the CP-UP separation document adopted within [netext]</span></td><td class="lineno" valign="top"></td></tr>
976      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
977      <tr><td class="lineno" valign="top"></td><td class="left">6.  Security Considerations</td><td> </td><td class="right">6.  Security Considerations</td><td class="lineno" valign="top"></td></tr>
978      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
979      <tr><td class="lineno" valign="top"></td><td class="left">   This document does not define any protocol, so it does not introduce</td><td> </td><td class="right">   This document does not define any protocol, so it does not introduce</td><td class="lineno" valign="top"></td></tr>
980      <tr><td class="lineno" valign="top"></td><td class="left">   any new security concern.</td><td> </td><td class="right">   any new security concern.</td><td class="lineno" valign="top"></td></tr>
981      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
982      <tr><td class="lineno" valign="top"></td><td class="left">7.  IANA Considerations</td><td> </td><td class="right">7.  IANA Considerations</td><td class="lineno" valign="top"></td></tr>
983      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
984      <tr><td class="lineno" valign="top"></td><td class="left">   None.</td><td> </td><td class="right">   None.</td><td class="lineno" valign="top"></td></tr>
985      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
986
987     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
988     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 91 change blocks.&nbsp;</a></th></tr>
989     <tr class="stats"><td></td><th><i>121 lines changed or deleted</i></th><th><i> </i></th><th><i>196 lines changed or added</i></th><td></td></tr>
990     <tr><td colspan="5" align="center" class="small"><br>This html diff was produced by rfcdiff 1.41. The latest version is available from <a href="http://www.tools.ietf.org/tools/rfcdiff/">http://tools.ietf.org/tools/rfcdiff/</a> </td></tr>
991   </tbody></table>
992   
993   
994</body></html>