Skip to main content

Locator/ID Separation Protocol Security (LISP-SEC)
draft-ietf-lisp-sec-29

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: Luigi Iannone <ggx@gigix.net>, The IESG <iesg@ietf.org>, aretana.ietf@gmail.com, draft-ietf-lisp-sec@ietf.org, ggx@gigix.net, lisp-chairs@ietf.org, lisp@ietf.org, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'LISP-Security (LISP-SEC)' to Proposed Standard (draft-ietf-lisp-sec-29.txt)

The IESG has approved the following document:
- 'LISP-Security (LISP-SEC)'
  (draft-ietf-lisp-sec-29.txt) as Proposed Standard

This document is the product of the Locator/ID Separation Protocol Working
Group.

The IESG contact persons are Alvaro Retana, Andrew Alston and John Scudder.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-lisp-sec/


Ballot Text

Technical Summary

   This memo specifies LISP-SEC, a set of security mechanisms that
   provides origin authentication, integrity, and anti-replay protection
   to LISP's EID-to-RLOC mapping data conveyed via the mapping lookup
   process.  LISP-SEC also enables verification of authorization on EID-
   prefix claims in Map-Reply messages.

Working Group Summary

   Was there anything in the WG process that is worth noting?
   For example, was there controversy about particular points 
   or were there decisions where the consensus was
   particularly rough? 

Document Quality

   The document has been around since 2011.  There was strong 
   from the start because the WG felt that the having a mechanism 
   to protect the map lookup process is important in order to 
   make possible public deployments.

   The security review of the base LISP specifications (rfc6830bis
   and rfc6833bis) concluded that for LISP public deployments 
   LISP-SEC is required. 

Personnel

   Document Shepherd:  Luigi Iannone
   Responsible Area Director:  Alvaro Retana

RFC Editor Note