TEAP Update and Extensions for Bootstrapping

Document Type Expired Internet-Draft (individual)
Authors Eliot Lear  , Owen Friel  , Nancy Cam-Winget  , Dan Harkins 
Last updated 2020-05-06 (latest revision 2019-11-03)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


In certain environments, in order for a device to establish any layer three communications, it is necessary for that device to be properly credentialed. This is a relatively easy problem to solve when a device is associated with a human being and has both input and display functions. It is less easy when the human, input, and display functions are not present. To address this case, this memo specifies extensions to the Tunnel Extensible Authentication Protocol (TEAP) method that leverages Bootstrapping Remote Secure Key Infrastructures (BRSKI) in order to provide a credential to a device at layer two. The basis of this work is that a manufacturer will introduce the device and the local deployment through cryptographic means. In this sense the same trust model as BRSKI is used.


Eliot Lear (lear@cisco.com)
Owen Friel (ofriel@cisco.com)
Nancy Cam-Winget (ncamwing@cisco.com)
Dan Harkins (dharkins@arubanetworks.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)