LISP EID Anonymity
draft-ietf-lisp-eid-anonymity-04
Network Working Group D. Farinacci
Internet-Draft lispers.net
Intended status: Experimental P. Pillay-Esnault
Expires: April 25, 2019 Huawei Technologies
W. Haddad
Ericsson
October 22, 2018
LISP EID Anonymity
draft-ietf-lisp-eid-anonymity-04
Abstract
This specification will describe how ephemeral LISP EIDs can be used
to create source anonymity. The idea makes use of frequently
changing EIDs much like how a credit-card system uses a different
credit-card numbers for each transaction.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 25, 2019.
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
Farinacci, et al. Expires April 25, 2019 [Page 1]
Internet-Draft LISP EID Anonymity October 2018
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Design Details . . . . . . . . . . . . . . . . . . . . . . . 4
5. Other Types of Ephemeral-EIDs . . . . . . . . . . . . . . . . 5
6. Interworking Considerations . . . . . . . . . . . . . . . . . 5
7. Multicast Considerations . . . . . . . . . . . . . . . . . . 5
8. Performance Improvements . . . . . . . . . . . . . . . . . . 6
9. Security Considerations . . . . . . . . . . . . . . . . . . . 6
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
11.1. Normative References . . . . . . . . . . . . . . . . . . 6
11.2. Informative References . . . . . . . . . . . . . . . . . 8
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 8
Appendix B. Document Change Log . . . . . . . . . . . . . . . . 8
B.1. Changes to draft-ietf-lisp-eid-anonymity-04 . . . . . . . 8
B.2. Changes to draft-ietf-lisp-eid-anonymity-03 . . . . . . . 8
B.3. Changes to draft-ietf-lisp-eid-anonymity-02 . . . . . . . 9
B.4. Changes to draft-ietf-lisp-eid-anonymity-01 . . . . . . . 9
B.5. Changes to draft-ietf-lisp-eid-anonymity-00 . . . . . . . 9
B.6. Changes to draft-farinacci-lisp-eid-anonymity-02 . . . . 9
B.7. Changes to draft-farinacci-lisp-eid-anonymity-01 . . . . 9
B.8. Changes to draft-farinacci-lisp-eid-anonymity-00 . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
The LISP architecture [RFC6830] specifies two namespaces, End-Point
IDs (EIDs) and Routing Locators (RLOCs). An EID identifies a node in
the network and the RLOC indicates the EID's topological location.
Typically EIDs are globally unique so a end-node system can connect
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
that scope. Therefore, address allocation is required by network
administration to avoid address collisions or duplicate address use.
Show full document text