LISP Control-Plane ECDSA Authentication and Authorization
draft-ietf-lisp-ecdsa-auth-03
Network Working Group D. Farinacci
Internet-Draft lispers.net
Intended status: Experimental E. Nordmark
Expires: September 20, 2020 Zededa
March 19, 2020
LISP Control-Plane ECDSA Authentication and Authorization
draft-ietf-lisp-ecdsa-auth-03
Abstract
This draft describes how LISP control-plane messages can be
individually authenticated and authorized without a a priori shared-
key configuration. Public-key cryptography is used with no new PKI
infrastructure required.
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 September 20, 2020.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
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.
Farinacci & Nordmark Expires September 20, 2020 [Page 1]
Internet-Draft LISP ECDSA Authentication and Authorization March 2020
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Definition of Terms . . . . . . . . . . . . . . . . . . . . . 4
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Public-Key Hash . . . . . . . . . . . . . . . . . . . . . . . 6
5. Hash-EID Mapping Entry . . . . . . . . . . . . . . . . . . . 7
6. Hash-EID Structure . . . . . . . . . . . . . . . . . . . . . 7
7. Keys and Signatures . . . . . . . . . . . . . . . . . . . . . 8
8. Signed Map-Register Encoding . . . . . . . . . . . . . . . . 8
9. Signed Map-Request Encoding . . . . . . . . . . . . . . . . . 9
10. Signed Map-Notify Encoding . . . . . . . . . . . . . . . . . 10
11. Other Uses . . . . . . . . . . . . . . . . . . . . . . . . . 10
12. EID Authorization . . . . . . . . . . . . . . . . . . . . . . 11
13. Security Considerations . . . . . . . . . . . . . . . . . . . 13
14. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
15. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
15.1. Normative References . . . . . . . . . . . . . . . . . . 13
15.2. Informative References . . . . . . . . . . . . . . . . . 15
Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . 15
Appendix B. Document Change Log . . . . . . . . . . . . . . . . 16
B.1. Changes to draft-ietf-lisp-ecdsa-auth-03 . . . . . . . . 16
B.2. Changes to draft-ietf-lisp-ecdsa-auth-02 . . . . . . . . 16
B.3. Changes to draft-ietf-lisp-ecdsa-auth-01 . . . . . . . . 16
B.4. Changes to draft-ietf-lisp-ecdsa-auth-00 . . . . . . . . 16
B.5. Changes to draft-farinacci-lisp-ecdsa-auth-03 . . . . . . 16
B.6. Changes to draft-farinacci-lisp-ecdsa-auth-02 . . . . . . 16
B.7. Changes to draft-farinacci-lisp-ecdsa-auth-01 . . . . . . 17
B.8. Changes to draft-farinacci-lisp-ecdsa-auth-00 . . . . . . 17
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17
1. Introduction
The LISP architecture and protocols [RFC6830] introduces two new
numbering spaces, Endpoint Identifiers (EIDs) and Routing Locators
(RLOCs) which provide an architecture to build overlays on top of the
underlying Internet. Mapping EIDs to RLOC-sets is accomplished with
a Mapping Database System. EIDs and RLOCs come in many forms than
just IP addresses, using a general syntax that includes Address
Family Identifier (AFI) [RFC1700]. Not only IP addresses, but other
addressing information have privacy requirements. Access to private
information is granted only to those who are authorized and
Show full document text