draft-ietf-lisp-eid-anonymity-03.txt   draft-ietf-lisp-eid-anonymity-04.txt 
Network Working Group D. Farinacci Network Working Group D. Farinacci
Internet-Draft lispers.net Internet-Draft lispers.net
Intended status: Experimental P. Pillay-Esnault Intended status: Experimental P. Pillay-Esnault
Expires: April 18, 2019 Huawei Technologies Expires: April 25, 2019 Huawei Technologies
W. Haddad W. Haddad
Ericsson Ericsson
October 15, 2018 October 22, 2018
LISP EID Anonymity LISP EID Anonymity
draft-ietf-lisp-eid-anonymity-03 draft-ietf-lisp-eid-anonymity-04
Abstract Abstract
This specification will describe how ephemeral LISP EIDs can be used This specification will describe how ephemeral LISP EIDs can be used
to create source anonymity. The idea makes use of frequently to create source anonymity. The idea makes use of frequently
changing EIDs much like how a credit-card system uses a different changing EIDs much like how a credit-card system uses a different
credit-card numbers for each transaction. credit-card numbers for each transaction.
Requirements Language Requirements Language
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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 April 18, 2019. This Internet-Draft will expire on April 25, 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 21 skipping to change at page 2, line 21
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 3 2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Design Details . . . . . . . . . . . . . . . . . . . . . . . 4 4. Design Details . . . . . . . . . . . . . . . . . . . . . . . 4
5. Other Types of Ephemeral-EIDs . . . . . . . . . . . . . . . . 4 5. Other Types of Ephemeral-EIDs . . . . . . . . . . . . . . . . 5
6. Interworking Considerations . . . . . . . . . . . . . . . . . 5 6. Interworking Considerations . . . . . . . . . . . . . . . . . 5
7. Multicast Considerations . . . . . . . . . . . . . . . . . . 5 7. Multicast Considerations . . . . . . . . . . . . . . . . . . 5
8. Performance Improvements . . . . . . . . . . . . . . . . . . 5 8. Performance Improvements . . . . . . . . . . . . . . . . . . 6
9. Security Considerations . . . . . . . . . . . . . . . . . . . 6 9. Security Considerations . . . . . . . . . . . . . . . . . . . 6
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
11.1. Normative References . . . . . . . . . . . . . . . . . . 6 11.1. Normative References . . . . . . . . . . . . . . . . . . 6
11.2. Informative References . . . . . . . . . . . . . . . . . 8 11.2. Informative References . . . . . . . . . . . . . . . . . 8
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 8 Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 8
Appendix B. Document Change Log . . . . . . . . . . . . . . . . 8 Appendix B. Document Change Log . . . . . . . . . . . . . . . . 8
B.1. Changes to draft-ietf-lisp-eid-anonymity-03 . . . . . . . 8 B.1. Changes to draft-ietf-lisp-eid-anonymity-04 . . . . . . . 8
B.2. Changes to draft-ietf-lisp-eid-anonymity-02 . . . . . . . 8 B.2. Changes to draft-ietf-lisp-eid-anonymity-03 . . . . . . . 8
B.3. Changes to draft-ietf-lisp-eid-anonymity-01 . . . . . . . 8 B.3. Changes to draft-ietf-lisp-eid-anonymity-02 . . . . . . . 9
B.4. Changes to draft-ietf-lisp-eid-anonymity-00 . . . . . . . 9 B.4. Changes to draft-ietf-lisp-eid-anonymity-01 . . . . . . . 9
B.5. Changes to draft-farinacci-lisp-eid-anonymity-02 . . . . 9 B.5. Changes to draft-ietf-lisp-eid-anonymity-00 . . . . . . . 9
B.6. Changes to draft-farinacci-lisp-eid-anonymity-01 . . . . 9 B.6. Changes to draft-farinacci-lisp-eid-anonymity-02 . . . . 9
B.7. Changes to draft-farinacci-lisp-eid-anonymity-00 . . . . 9 B.7. Changes to draft-farinacci-lisp-eid-anonymity-01 . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 B.8. Changes to draft-farinacci-lisp-eid-anonymity-00 . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
The LISP architecture [RFC6830] specifies two namespaces, End-Point The LISP architecture [RFC6830] specifies two namespaces, End-Point
IDs (EIDs) and Routing Locators (RLOCs). An EID identifies a node in IDs (EIDs) and Routing Locators (RLOCs). An EID identifies a node in
the network and the RLOC indicates the EID's topological location. the network and the RLOC indicates the EID's topological location.
Typically EIDs are globally unique so a end-node system can connect Typically EIDs are globally unique so a end-node system can connect
to any other end-node system on the Internet. Privately used EIDs to any other end-node system on the Internet. Privately used EIDs
are allowed when scoped within a VPN but must always be unique within are allowed when scoped within a VPN but must always be unique within
that scope. Therefore, address allocation is required by network that scope. Therefore, address allocation is required by network
skipping to change at page 3, line 42 skipping to change at page 3, line 43
A client end-node can assign its own ephemeral EID and use it to talk A client end-node can assign its own ephemeral EID and use it to talk
to any system on the Internet. The system is acting as a client to any system on the Internet. The system is acting as a client
where it initiates communication and desires to be an inaccessible where it initiates communication and desires to be an inaccessible
resource from any other system. The ephemeral EID is used as a resource from any other system. The ephemeral EID is used as a
destination address solely to return packets to resources the destination address solely to return packets to resources the
ephemeral EID connects to. ephemeral EID connects to.
Here is the procedure a client end-node would use: Here is the procedure a client end-node would use:
1. Client end-node desires to talk on the network. It creates and 1. Client end-node desires to talk on the network. It creates and
assigns an ephemeral-EID on any interface. assigns an ephemeral-EID on any interface. The client end-node
may also assign multiple ephemeral-EIDs on the same interface or
across different interfaces.
2. If the client end-node is a LISP xTR, it will register the 2. If the client end-node is a LISP xTR, it will register ephemeral-
ephemeral-EID with a globally routable RLOC. If the client end- EIDs mapped to underlay routable RLOCs. If the client end-node
node is not a LISP xTR, it can send packets on the network where is not a LISP xTR, it can send packets on the network where a
a LISP router xTR will register the ephemeral-EID with its RLOC. LISP router xTR will register the ephemeral-EIDs with its RLOC-
set.
3. The client end-node originates packets with a source address 3. The client end-node originates packets with a source address
equal to the ephemeral-EID and will receive packets addressed to equal to the ephemeral-EID and will receive packets addressed to
the ephemeral-EID. the ephemeral-EID.
4. When the client end-node decides to stop using the ephemeral-EID, 4. When the client end-node decides to stop using an ephemeral-EID,
it will deregister it from the mapping system and create and it will deregister it from the mapping system and create and
assign a new ephemeral-EID, or decide to configure a static assign a new ephemeral-EID, or decide to configure a static
global address, or participate in DHCP to get assigned a leased global address, or participate in DHCP to get assigned a leased
address. address.
Note that the ephemeral-EID can be mobile just like any other EID so Note that the ephemeral-EID can be mobile just like any other EID so
if it is initially registered to the mapping system with one or more if it is initially registered to the mapping system with one or more
RLOCs, later the RLOC-set can change as the ephemeral-EID roams. RLOCs, later the RLOC-set can change as the ephemeral-EID roams.
4. Design Details 4. Design Details
skipping to change at page 8, line 32 skipping to change at page 8, line 37
Appendix A. Acknowledgments Appendix A. Acknowledgments
The author would like to thank the LISP WG for their review and The author would like to thank the LISP WG for their review and
acceptance of this draft. acceptance of this draft.
Appendix B. Document Change Log Appendix B. Document Change Log
[RFC Editor: Please delete this section on publication as RFC.] [RFC Editor: Please delete this section on publication as RFC.]
B.1. Changes to draft-ietf-lisp-eid-anonymity-03 B.1. Changes to draft-ietf-lisp-eid-anonymity-04
o Posted October 2018 before Bangkok IETF deadline.
o Made Padma requested changes to refer to ephemeral-EIDs allowed to
have many on one interface and can be registered with more than 1
RLOC but one RLOC-set.
B.2. Changes to draft-ietf-lisp-eid-anonymity-03
o Posted October 2018. o Posted October 2018.
o Update document timer and references. o Update document timer and references.
B.2. Changes to draft-ietf-lisp-eid-anonymity-02 B.3. Changes to draft-ietf-lisp-eid-anonymity-02
o Posted April 2018. o Posted April 2018.
o Update document timer and references. o Update document timer and references.
B.3. Changes to draft-ietf-lisp-eid-anonymity-01 B.4. Changes to draft-ietf-lisp-eid-anonymity-01
o Posted October 2017. o Posted October 2017.
o Add to section 5 that PKI can be used to authenticate EIDs. o Add to section 5 that PKI can be used to authenticate EIDs.
o Update references. o Update references.
B.4. Changes to draft-ietf-lisp-eid-anonymity-00 B.5. Changes to draft-ietf-lisp-eid-anonymity-00
o Posted August 2017. o Posted August 2017.
o Made draft-farinacci-lisp-eid-anonymity-02 a LISP working group o Made draft-farinacci-lisp-eid-anonymity-02 a LISP working group
document. document.
B.5. Changes to draft-farinacci-lisp-eid-anonymity-02 B.6. Changes to draft-farinacci-lisp-eid-anonymity-02
o Posted April 2017. o Posted April 2017.
o Added section describing how ephemeral-EIDs can use a public key o Added section describing how ephemeral-EIDs can use a public key
hash as an alternative to a random number. hash as an alternative to a random number.
o Indciate when an EID/RLOC co-located, that the xTR can register o Indciate when an EID/RLOC co-located, that the xTR can register
the EID when it is configured or changed versus waiting for a the EID when it is configured or changed versus waiting for a
packet to be sent as in the EID/RLOC separated case. packet to be sent as in the EID/RLOC separated case.
B.6. Changes to draft-farinacci-lisp-eid-anonymity-01 B.7. Changes to draft-farinacci-lisp-eid-anonymity-01
o Posted October 2016. o Posted October 2016.
o Update document timer. o Update document timer.
B.7. Changes to draft-farinacci-lisp-eid-anonymity-00 B.8. Changes to draft-farinacci-lisp-eid-anonymity-00
o Posted April 2016. o Posted April 2016.
o Initial posting. o Initial posting.
Authors' Addresses Authors' Addresses
Dino Farinacci Dino Farinacci
lispers.net lispers.net
San Jose, CA San Jose, CA
 End of changes. 17 change blocks. 
27 lines changed or deleted 39 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/