LISP Generic Protocol Extension

Approval announcement
Draft of message to be sent after approval:

From: The IESG <>
To: IETF-Announce <>
Cc:,,, The IESG <>, Luigi Iannone <>,,,
Subject: Protocol Action: 'LISP Generic Protocol Extension' to Proposed Standard (draft-ietf-lisp-gpe-05.txt)

The IESG has approved the following document:
- 'LISP Generic Protocol Extension'
  (draft-ietf-lisp-gpe-05.txt) as Proposed Standard

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

The IESG contact persons are Alvaro Retana, Martin Vigoureux and Deborah

A URL of this Internet Draft is:

Technical Summary

The document describes an extension of the LISP Header to enhance the LISP data plane
to support multi-protocol encapsulation. The main LISP specifications allow only IPv4 or
IPv6 encapsulation. Such feature is achieved by allocating the last remaining reserved flag
as the "next Protocol" bit. If set the flag indicates the presence of a 8 bit next protocol field.
Next Protocol code-points are listed in a new IANA LISP registry.

Working Group Summary

The document was first published in 2013, but because the WG was not chartered to work on
multi-protocol support the document was left to expire. Things changed with the rechartering
of the LISP WG, which now explicitly includes multi-protocol support. After the LISP WG
concluded the bulk of the work on the bis documents, representing the basic LISP Standard Track
specifications, the LISP-GPE document has been updated and the WG adopted it right away. Some
technical discussion took place concerning the way LISP-GPE boxes have to interoperate with legacy
LISP boxes, but the WG always showed support and willingness to move the document forward.
The version of the document that was approved during WG Last Call is -03. Shepherd required a few
editorial changes to the document to fix some nits.

Document Quality

There are three independent implementations of the proposed extensions.


   Who is the Document Shepherd for this document?  Luigi Iannone <>
   Who is the Responsible Area Director? Deborah Brungard <>


  (Insert IRTF Note here or remove section)


  (Insert IESG Note here or remove section)


  (Insert IANA Note here or remove section)