Skip to main content

Locator/ID Separation Protocol (LISP) Threat Analysis
draft-ietf-lisp-threats-15

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: lisp-chairs@ietf.org, lisp@ietf.org, db3546@att.com, draft-ietf-lisp-threats@ietf.org, "The IESG" <iesg@ietf.org>, jmh@joelhalpern.com, rfc-editor@rfc-editor.org
Subject: Document Action: 'LISP Threats Analysis' to Informational RFC (draft-ietf-lisp-threats-15.txt)

The IESG has approved the following document:
- 'LISP Threats Analysis'
  (draft-ietf-lisp-threats-15.txt) as Informational RFC

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

The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah
Brungard.

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


Ballot Text

Technical Summary

This document review the kinds of security threats that arise when LISP is being used.
It discusses the kinds of attacks and mechanisms, so as to note clearly where LISP modifies
the normal assumptions.   It then discusses particular attacks that can be mounted.  The
document concludes with some general recommendations on deployment and configuration
techniques that can ameliorate some of the attacks.

 
Working Group Summary

The document has going through multiple reviews and restructurings.  The current document
is very clear and readable.  The documented is intended to provide information to the
community, and does not modify the protocol nor mandate specific techniques.  As such, the
working group is requesting that this be published as an Informational RFC.
In addition, there were multiple reviews by different people to ensure that the full range of
threats were covered and accurately described. Finding the right wording was challenging, but
was accomplished. 

Document Quality

The shepherd has performed a final review, and agrees that this document is useful and ready
for publication as an Informational RFC.

Personnel

   Who is the Document Shepherd for this document?  Joel Halpern
   Who is the Responsible Area Director?  Deborah Brungard

RFC Editor Note