draft-ietf-lisp-mn-02.txt   draft-ietf-lisp-mn-03.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: October 25, 2018 cisco Systems Expires: April 5, 2019 cisco Systems
D. Meyer D. Meyer
1-4-5.net 1-4-5.net
C. White C. White
Logical Elegance, LLC. Logical Elegance, LLC.
April 23, 2018 October 2, 2018
LISP Mobile Node LISP Mobile Node
draft-ietf-lisp-mn-02 draft-ietf-lisp-mn-03
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 October 25, 2018. This Internet-Draft will expire on April 5, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 20 skipping to change at page 2, line 20
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4 2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4
3. Design Overview . . . . . . . . . . . . . . . . . . . . . . . 6 3. Design Overview . . . . . . . . . . . . . . . . . . . . . . . 6
4. Design Requirements . . . . . . . . . . . . . . . . . . . . . 6 4. Design Requirements . . . . . . . . . . . . . . . . . . . . . 6
4.1. User Requirements . . . . . . . . . . . . . . . . . . . . 6 4.1. User Requirements . . . . . . . . . . . . . . . . . . . . 6
4.2. Network Requirements . . . . . . . . . . . . . . . . . . 7 4.2. Network Requirements . . . . . . . . . . . . . . . . . . 7
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 . . . . . . . . . . . . . . . . . 8 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 . . . . . . . . . . . . . . . . . . . . . 10 7. Protocol Operation . . . . . . . . . . . . . . . . . . . . . 10
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 . . . . . . . . . . . . . 12
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
skipping to change at page 2, line 43 skipping to change at page 2, line 43
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 . . . . . . . . . . . . . . . . . . . . . . . . . 20 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 21
15.1. Normative References . . . . . . . . . . . . . . . . . . 20 15.1. Normative References . . . . . . . . . . . . . . . . . . 21
15.2. Informative References . . . . . . . . . . . . . . . . . 21 15.2. Informative References . . . . . . . . . . . . . . . . . 22
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 21 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 22
Appendix B. Document Change Log . . . . . . . . . . . . . . . . 22 Appendix B. Document Change Log . . . . . . . . . . . . . . . . 22
B.1. Changes to draft-ietf-lisp-mn-02.txt . . . . . . . . . . 22 B.1. Changes to draft-ietf-lisp-mn-03 . . . . . . . . . . . . 22
B.2. Changes to draft-ietf-lisp-mn-01.txt . . . . . . . . . . 22 B.2. Changes to draft-ietf-lisp-mn-02 . . . . . . . . . . . . 22
B.3. Changes to draft-ietf-lisp-mn-00.txt . . . . . . . . . . 22 B.3. Changes to draft-ietf-lisp-mn-01 . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 22 B.4. Changes to draft-ietf-lisp-mn-00 . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
1. Introduction 1. Introduction
The Locator/ID Separation Protocol (LISP) [RFC6830] specifies a The Locator/ID Separation Protocol (LISP) [RFC6830] specifies a
design and mechanism for replacing the addresses currently used in design and mechanism for replacing the addresses currently used in
the Internet with two separate name spaces: Endpoint Identifiers the Internet with two separate name spaces: Endpoint Identifiers
(EIDs), used within sites, and Routing Locators (RLOCs), used by the (EIDs), used within sites, and Routing Locators (RLOCs), used by the
transit networks that make up the Internet infrastructure. To transit networks that make up the Internet infrastructure. To
achieve this separation, LISP defines protocol mechanisms for mapping achieve this separation, LISP defines protocol mechanisms for mapping
from EIDs to RLOCs. The mapping infrastructure is comprised of LISP from EIDs to RLOCs. The mapping infrastructure is comprised of LISP
skipping to change at page 20, line 25 skipping to change at page 20, line 25
13.2. LISP Mobile Node using an EID as its RLOC 13.2. LISP Mobile Node using an EID as its RLOC
For LISP packets to be sent to a LISP-MN which has an EID assigned to For LISP packets to be sent to a LISP-MN which has an EID assigned to
it as an RLOC as described in Section 9.1), the LISP site must allow it as an RLOC as described in Section 9.1), the LISP site must allow
for incoming and outgoing LISP data packets. Firewalls and stateless for incoming and outgoing LISP data packets. Firewalls and stateless
packet filtering mechanisms must be configured to allow UDP port 4341 packet filtering mechanisms must be configured to allow UDP port 4341
and UDP port 4342 packets. and UDP port 4342 packets.
14. IANA Considerations 14. IANA Considerations
This document creates no new requirements on IANA namespaces This document is requesting bit allocations in the Map-Request and
[RFC5226]. Map-Register messages.
The first 4 octets of the Map-Request message are:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Type=1 |A|M|P|S|p|s|m|I| Rsvd |L|D| IRC | Record Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This document requests allocation of bit position 10 labeled "m" in
the above diagram. The IANA name label is "map-request-m-bit". When
a LISP mobile-node sends a Map-Request message to the mapping system,
it sets the m-bit to 1.
The first 4 octets of the Map-Register message are:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Type=3 |P|S|I| Reserved |E|T|a|m|M| Record Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This document requests allocation of bit position 22 labeled "m" in
the above diagram. The IANA name label is "map-register-m-bit".
When a LISP mobile-node sends a Map-Register message to the mapping
system, it sets the m-bit to 1.
15. References 15. References
15.1. Normative References 15.1. Normative References
[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>.
skipping to change at page 21, line 41 skipping to change at page 22, line 20
[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., Skriver, J., Maino, Ermagan, V., Farinacci, D., Lewis, D., Skriver, J., Maino,
F., and C. White, "NAT traversal for LISP", draft-ermagan- F., and C. White, "NAT traversal for LISP", draft-ermagan-
lisp-nat-traversal-14 (work in progress), April 2018. lisp-nat-traversal-15 (work in progress), October 2018.
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-02.txt B.1. Changes to draft-ietf-lisp-mn-03
o Posted October 2018.
o Request m-bit allocation in Map-Register message in IANA
Considerations section.
B.2. 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.2. Changes to draft-ietf-lisp-mn-01.txt B.3. 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.3. Changes to draft-ietf-lisp-mn-00.txt B.4. 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. 12 change blocks. 
19 lines changed or deleted 54 lines changed or added

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