The eap.arpa. domain and EAP provisioning
draft-ietf-emu-eap-arpa-10

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: The IESG <iesg@ietf.org>, draft-ietf-emu-eap-arpa@ietf.org, emu-chairs@ietf.org, emu@ietf.org, paul.wouters@aiven.io, peter@akayla.com, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'The eap.arpa. domain and EAP provisioning' to Proposed Standard (draft-ietf-emu-eap-arpa-10.txt)

The IESG has approved the following document:
- 'The eap.arpa. domain and EAP provisioning'
  (draft-ietf-emu-eap-arpa-10.txt) as Proposed Standard

This document is the product of the EAP Method Update Working Group.

The IESG contact persons are Paul Wouters and Deb Cooley.

A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-emu-eap-arpa/

Ballot Text

Technical Summary

   This document defines the eap.arpa domain as a way for Extensible
   Authentication Protocol (EAP) peers to signal to EAP servers that
   they wish to obtain limited, and unauthenticated, network access.
   EAP peers signal which kind of access is required via certain pre-
   defined identifiers which use the Network Access Identifier (NAI)
   format of RFC 7542.  A table of identifiers and meanings is defined,
   which includes entries for RFC 9140.

Working Group Summary

   Of those active in the WG, there was broad agreement to advance this ancillary
   specification. Perhaps more telling, there’s already another (Standards Track)
   draft that makes use of this specification. The IETF LC and its Directorate
   reviews also gathered more reviews and a revision.


Document Quality

   This is an ancillary document in so much as it specifies the contents of an EAP
   NAI and an IANA registry for those values. Thus, the implementations of this
   specification are embodied in the implementation of specific EAP methods. It is
   already compatible with existing EAP implementations. Those implementations
   will not, of course, reference this specification, but the WIP
   draft-ietf-emu-bootstrapped-tls does reference this draft and use its IANA NAI
   registry.

Personnel

   The Document Shepherd for this document is Peter E. Yee. The Responsible
   Area Director is Paul Wouters.

RFC Editor Note