draft-ietf-lisp-mn-07.txt   draft-ietf-lisp-mn-08.txt 
Network Working Group D. Farinacci Network Working Group D. Farinacci
Internet-Draft lispers.net Internet-Draft lispers.net
Intended status: Experimental D. Lewis Intended status: Experimental D. Lewis
Expires: September 2, 2020 cisco Systems Expires: February 25, 2021 cisco Systems
D. Meyer D. Meyer
1-4-5.net 1-4-5.net
C. White C. White
Logical Elegance, LLC. Logical Elegance, LLC.
March 1, 2020 August 24, 2020
LISP Mobile Node LISP Mobile Node
draft-ietf-lisp-mn-07 draft-ietf-lisp-mn-08
Abstract Abstract
This document describes how a lightweight version of LISP's ITR/ETR This document describes how a lightweight version of LISP's ITR/ETR
functionality can be used to provide seamless mobility to a mobile functionality can be used to provide seamless mobility to a mobile
node. The LISP Mobile Node design described in this document uses node. The LISP Mobile Node design described in this document uses
standard LISP functionality to provide scalable mobility for LISP standard LISP functionality to provide scalable mobility for LISP
mobile nodes. mobile nodes.
Status of This Memo Status of This Memo
skipping to change at page 1, line 39 skipping to change at page 1, line 39
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 2, 2020. This Internet-Draft will expire on February 25, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 28 skipping to change at page 2, line 28
5. LISP Mobile Node Operation . . . . . . . . . . . . . . . . . 7 5. LISP Mobile Node Operation . . . . . . . . . . . . . . . . . 7
5.1. Addressing Architecture . . . . . . . . . . . . . . . . . 8 5.1. Addressing Architecture . . . . . . . . . . . . . . . . . 8
5.2. Control Plane Operation . . . . . . . . . . . . . . . . . 9 5.2. Control Plane Operation . . . . . . . . . . . . . . . . . 9
5.3. Data Plane Operation . . . . . . . . . . . . . . . . . . 9 5.3. Data Plane Operation . . . . . . . . . . . . . . . . . . 9
6. Updating Remote Caches . . . . . . . . . . . . . . . . . . . 10 6. Updating Remote Caches . . . . . . . . . . . . . . . . . . . 10
7. Protocol Operation . . . . . . . . . . . . . . . . . . . . . 11 7. Protocol Operation . . . . . . . . . . . . . . . . . . . . . 11
7.1. LISP Mobile Node to a Stationary Node in a LISP Site . . 11 7.1. LISP Mobile Node to a Stationary Node in a LISP Site . . 11
7.1.1. Handling Unidirectional Traffic . . . . . . . . . . . 11 7.1.1. Handling Unidirectional Traffic . . . . . . . . . . . 11
7.2. LISP Mobile Node to a Non-LISP Stationary Node . . . . . 12 7.2. LISP Mobile Node to a Non-LISP Stationary Node . . . . . 12
7.3. LISP Mobile Node to LISP Mobile Node . . . . . . . . . . 12 7.3. LISP Mobile Node to LISP Mobile Node . . . . . . . . . . 12
7.3.1. One Mobile Node is Roaming . . . . . . . . . . . . . 12 7.3.1. One Mobile Node is Roaming . . . . . . . . . . . . . 13
7.4. Non-LISP Site to a LISP Mobile Node . . . . . . . . . . . 13 7.4. Non-LISP Site to a LISP Mobile Node . . . . . . . . . . . 13
7.5. LISP Site to LISP Mobile Node . . . . . . . . . . . . . . 13 7.5. LISP Site to LISP Mobile Node . . . . . . . . . . . . . . 13
8. Multicast and Mobility . . . . . . . . . . . . . . . . . . . 14 8. Multicast and Mobility . . . . . . . . . . . . . . . . . . . 14
9. RLOC Considerations . . . . . . . . . . . . . . . . . . . . . 15 9. RLOC Considerations . . . . . . . . . . . . . . . . . . . . . 15
9.1. Mobile Node's RLOC is an EID . . . . . . . . . . . . . . 15 9.1. Mobile Node's RLOC is an EID . . . . . . . . . . . . . . 15
10. LISP Mobile Nodes behind NAT Devices . . . . . . . . . . . . 17 10. LISP Mobile Nodes behind NAT Devices . . . . . . . . . . . . 17
11. Mobility Example . . . . . . . . . . . . . . . . . . . . . . 17 11. Mobility Example . . . . . . . . . . . . . . . . . . . . . . 17
11.1. Provisioning . . . . . . . . . . . . . . . . . . . . . . 17 11.1. Provisioning . . . . . . . . . . . . . . . . . . . . . . 17
11.2. Registration . . . . . . . . . . . . . . . . . . . . . . 18 11.2. Registration . . . . . . . . . . . . . . . . . . . . . . 18
12. LISP Implementation in a Mobile Node . . . . . . . . . . . . 18 12. LISP Implementation in a Mobile Node . . . . . . . . . . . . 18
13. Security Considerations . . . . . . . . . . . . . . . . . . . 19 13. Security Considerations . . . . . . . . . . . . . . . . . . . 19
13.1. Proxy ETR Hijacking . . . . . . . . . . . . . . . . . . 20 13.1. Proxy ETR Hijacking . . . . . . . . . . . . . . . . . . 20
13.2. LISP Mobile Node using an EID as its RLOC . . . . . . . 20 13.2. LISP Mobile Node using an EID as its RLOC . . . . . . . 20
14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20 14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 20
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 21 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 21
15.1. Normative References . . . . . . . . . . . . . . . . . . 21 15.1. Normative References . . . . . . . . . . . . . . . . . . 21
15.2. Informative References . . . . . . . . . . . . . . . . . 22 15.2. Informative References . . . . . . . . . . . . . . . . . 22
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 22 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 22
Appendix B. Document Change Log . . . . . . . . . . . . . . . . 22 Appendix B. Document Change Log . . . . . . . . . . . . . . . . 23
B.1. Changes to draft-ietf-lisp-mn-07 . . . . . . . . . . . . 23 B.1. Changes to draft-ietf-lisp-mn-08 . . . . . . . . . . . . 23
B.2. Changes to draft-ietf-lisp-mn-06 . . . . . . . . . . . . 23 B.2. Changes to draft-ietf-lisp-mn-07 . . . . . . . . . . . . 23
B.3. Changes to draft-ietf-lisp-mn-05 . . . . . . . . . . . . 23 B.3. Changes to draft-ietf-lisp-mn-06 . . . . . . . . . . . . 23
B.4. Changes to draft-ietf-lisp-mn-04 . . . . . . . . . . . . 23 B.4. Changes to draft-ietf-lisp-mn-05 . . . . . . . . . . . . 23
B.5. Changes to draft-ietf-lisp-mn-03 . . . . . . . . . . . . 23 B.5. Changes to draft-ietf-lisp-mn-04 . . . . . . . . . . . . 23
B.6. Changes to draft-ietf-lisp-mn-02 . . . . . . . . . . . . 23 B.6. Changes to draft-ietf-lisp-mn-03 . . . . . . . . . . . . 23
B.7. Changes to draft-ietf-lisp-mn-01 . . . . . . . . . . . . 23 B.7. Changes to draft-ietf-lisp-mn-02 . . . . . . . . . . . . 23
B.8. Changes to draft-ietf-lisp-mn-00 . . . . . . . . . . . . 24 B.8. Changes to draft-ietf-lisp-mn-01 . . . . . . . . . . . . 24
B.9. Changes to draft-ietf-lisp-mn-00 . . . . . . . . . . . . 24
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 24
1. Introduction 1. Introduction
The Locator/ID Separation Protocol (LISP) [I-D.ietf-lisp-rfc6830bis] The Locator/ID Separation Protocol (LISP) [I-D.ietf-lisp-rfc6830bis]
specifies a design and mechanism for replacing the addresses specifies a design and mechanism for replacing the addresses
currently used in the Internet with two separate name spaces: currently used in the Internet with two separate name spaces:
Endpoint Identifiers (EIDs), used within sites, and Routing Locators Endpoint Identifiers (EIDs), used within sites, and Routing Locators
(RLOCs), used by the transit networks that make up the Internet (RLOCs), used by the transit networks that make up the Internet
infrastructure. To achieve this separation, LISP defines protocol infrastructure. To achieve this separation, LISP defines protocol
skipping to change at page 17, line 36 skipping to change at page 17, line 36
device will translate the source address and source UDP port in the device will translate the source address and source UDP port in the
LISP encapsulated packet. The NAT device will keep this translated LISP encapsulated packet. The NAT device will keep this translated
state so when packets arrive from the public side of the NAT, they state so when packets arrive from the public side of the NAT, they
can be translated back to the stored state. For remote LISP ITRs, can be translated back to the stored state. For remote LISP ITRs,
PITRs, and RTRs, will need to know the translated RLOC address and PITRs, and RTRs, will need to know the translated RLOC address and
port so they can encapsulate to the LISP-MN traversing the NAT port so they can encapsulate to the LISP-MN traversing the NAT
device. device.
Procedures a LISP-MN should follow when it resides behind a NAT, will Procedures a LISP-MN should follow when it resides behind a NAT, will
follow the LISP xTRs procedures in specification follow the LISP xTRs procedures in specification
[I-D.ermagan-lisp-nat-traversal]. [I-D.ermagan-lisp-nat-traversal]. There are LISP-MN implementations
that follow procedures in [I-D.farinacci-lisp-simple-nat].
11. Mobility Example 11. Mobility Example
This section provides an example of how the LISP-MN is integrated This section provides an example of how the LISP-MN is integrated
into the base LISP Design [I-D.ietf-lisp-rfc6830bis]. into the base LISP Design [I-D.ietf-lisp-rfc6830bis].
11.1. Provisioning 11.1. Provisioning
The LISP-MN needs to be configured with the following information: The LISP-MN needs to be configured with the following information:
skipping to change at page 21, line 26 skipping to change at page 21, line 26
LISP Map-Register Header Bits LISP Map-Register Header Bits
15. References 15. References
15.1. Normative References 15.1. Normative References
[I-D.ietf-lisp-rfc6830bis] [I-D.ietf-lisp-rfc6830bis]
Farinacci, D., Fuller, V., Meyer, D., Lewis, D., and A. Farinacci, D., Fuller, V., Meyer, D., Lewis, D., and A.
Cabellos-Aparicio, "The Locator/ID Separation Protocol Cabellos-Aparicio, "The Locator/ID Separation Protocol
(LISP)", draft-ietf-lisp-rfc6830bis-30 (work in progress), (LISP)", draft-ietf-lisp-rfc6830bis-33 (work in progress),
January 2020. July 2020.
[I-D.ietf-lisp-rfc6833bis] [I-D.ietf-lisp-rfc6833bis]
Farinacci, D., Maino, F., Fuller, V., and A. Cabellos- Farinacci, D., Maino, F., Fuller, V., and A. Cabellos-
Aparicio, "Locator/ID Separation Protocol (LISP) Control- Aparicio, "Locator/ID Separation Protocol (LISP) Control-
Plane", draft-ietf-lisp-rfc6833bis-27 (work in progress), Plane", draft-ietf-lisp-rfc6833bis-28 (work in progress),
January 2020. July 2020.
[RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G., [RFC1918] Rekhter, Y., Moskowitz, B., Karrenberg, D., de Groot, G.,
and E. Lear, "Address Allocation for Private Internets", and E. Lear, "Address Allocation for Private Internets",
BCP 5, RFC 1918, DOI 10.17487/RFC1918, February 1996, BCP 5, RFC 1918, DOI 10.17487/RFC1918, February 1996,
<https://www.rfc-editor.org/info/rfc1918>. <https://www.rfc-editor.org/info/rfc1918>.
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", [RFC2131] Droms, R., "Dynamic Host Configuration Protocol",
RFC 2131, DOI 10.17487/RFC2131, March 1997, RFC 2131, DOI 10.17487/RFC2131, March 1997,
<https://www.rfc-editor.org/info/rfc2131>. <https://www.rfc-editor.org/info/rfc2131>.
skipping to change at page 22, line 35 skipping to change at page 22, line 35
[RFC6836] Fuller, V., Farinacci, D., Meyer, D., and D. Lewis, [RFC6836] Fuller, V., Farinacci, D., Meyer, D., and D. Lewis,
"Locator/ID Separation Protocol Alternative Logical "Locator/ID Separation Protocol Alternative Logical
Topology (LISP+ALT)", RFC 6836, DOI 10.17487/RFC6836, Topology (LISP+ALT)", RFC 6836, DOI 10.17487/RFC6836,
January 2013, <https://www.rfc-editor.org/info/rfc6836>. January 2013, <https://www.rfc-editor.org/info/rfc6836>.
15.2. Informative References 15.2. Informative References
[I-D.ermagan-lisp-nat-traversal] [I-D.ermagan-lisp-nat-traversal]
Ermagan, V., Farinacci, D., Lewis, D., Maino, F., Ermagan, V., Farinacci, D., Lewis, D., Maino, F.,
Portoles-Comeras, M., Skriver, J., and C. White, "NAT Portoles-Comeras, M., Skriver, J., White, C., and A.
traversal for LISP", draft-ermagan-lisp-nat-traversal-16 Bresco, "NAT traversal for LISP", draft-ermagan-lisp-nat-
(work in progress), June 2019. traversal-17 (work in progress), August 2020.
[I-D.farinacci-lisp-simple-nat]
Farinacci, D., "A Simple LISP NAT-Traversal
Implementation", draft-farinacci-lisp-simple-nat-00 (work
in progress), May 2020.
Appendix A. Acknowledgments Appendix A. Acknowledgments
Albert Cabellos, Noel Chiappa, Pierre Francois, Michael Menth, Andrew Albert Cabellos, Noel Chiappa, Pierre Francois, Michael Menth, Andrew
Partan, Chris White and John Zwiebel provided insightful comments on Partan, Chris White and John Zwiebel provided insightful comments on
the mobile node concept and on this document. A special thanks goes the mobile node concept and on this document. A special thanks goes
to Mary Nickum for her attention to detail and effort in editing to Mary Nickum for her attention to detail and effort in editing
early versions of this document. early versions of this document.
Appendix B. Document Change Log Appendix B. Document Change Log
B.1. Changes to draft-ietf-lisp-mn-07
B.1. Changes to draft-ietf-lisp-mn-08
o Posted August 2020.
o Update references and document timer.
B.2. Changes to draft-ietf-lisp-mn-07
o Posted March 2020. o Posted March 2020.
o Update references and document timer. o Update references and document timer.
B.2. Changes to draft-ietf-lisp-mn-06 B.3. Changes to draft-ietf-lisp-mn-06
o Posted September 2019. o Posted September 2019.
o Update references and document timer. o Update references and document timer.
B.3. Changes to draft-ietf-lisp-mn-05 B.4. Changes to draft-ietf-lisp-mn-05
o Posted March IETF week 2019. o Posted March IETF week 2019.
o Update references and document timer. o Update references and document timer.
B.4. Changes to draft-ietf-lisp-mn-04 B.5. Changes to draft-ietf-lisp-mn-04
o Posted October 2018. o Posted October 2018.
o Make IANA Considerations section formatted like o Make IANA Considerations section formatted like
[I-D.ietf-lisp-rfc6833bis]. [I-D.ietf-lisp-rfc6833bis].
o Change all references for RFC6830 to [I-D.ietf-lisp-rfc6830bis] o Change all references for RFC6830 to [I-D.ietf-lisp-rfc6830bis]
and for RFC6833 to [I-D.ietf-lisp-rfc6833bis]. and for RFC6833 to [I-D.ietf-lisp-rfc6833bis].
B.5. Changes to draft-ietf-lisp-mn-03 B.6. Changes to draft-ietf-lisp-mn-03
o Posted October 2018. o Posted October 2018.
o Request m-bit allocation in Map-Register message in IANA o Request m-bit allocation in Map-Register message in IANA
Considerations section. Considerations section.
B.6. Changes to draft-ietf-lisp-mn-02 B.7. Changes to draft-ietf-lisp-mn-02
o Posted April 2018. o Posted April 2018.
o Update document timer and references. o Update document timer and references.
B.7. Changes to draft-ietf-lisp-mn-01 B.8. Changes to draft-ietf-lisp-mn-01
o Posted October 2017. o Posted October 2017.
o Update document timer and references. o Update document timer and references.
B.8. Changes to draft-ietf-lisp-mn-00 B.9. Changes to draft-ietf-lisp-mn-00
o Posted April 2017. o Posted April 2017.
o Changed draft-meyer-lisp-mn-16 to working group document. o Changed draft-meyer-lisp-mn-16 to working group document.
Authors' Addresses Authors' Addresses
Dino Farinacci Dino Farinacci
lispers.net lispers.net
San Jose, CA 95134 San Jose, CA 95134
 End of changes. 18 change blocks. 
30 lines changed or deleted 44 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/