The IESG has approved the following document:
- 'Media Access Control (MAC) Addresses in X.509 Certificates'
  (draft-ietf-lamps-macaddress-on-07.txt) as Proposed Standard

This document is the product of the Limited Additional Mechanisms for PKIX
and SMIME 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-lamps-macaddress-on/




Technical Summary

   This document defines a new otherName for inclusion in the X.509
   Subject Alternative Name (SAN) and Issuer Alternative Name (IAN)
   extensions to carry an IEEE Media Access Control (MAC) address.  The
   new name form makes it possible to bind a layer-2 interface
   identifier to a public key certificate.  Additionally, this document
   defines how constraints on this name form can be encoded and
   processed in the X.509 Name Constraints extension.

Working Group Summary

   The draft is straightforward and there was broad agreement during the LAMPS
   meeting at IETF 124 that it was a good idea. The WG consensus represents 
broad
   agreement rather than just a few individuals.

Document Quality

There are plans by at least one vendor to implement this specification.

This document does not define any MIBs, YANG modules, media types, or URI
schemes.  It does contains an ASN.1 module in Section 6. The module has been
validated with an ASN.1 compiler.

This document interacts with IEEE 802 for MAC address format definitions
(EUI-48/EUI-64).  The IEEE MAC address formats are well-established standards. 
No additional external reviews are necessary.

RFC 5912 is an Informational RFC being referenced normatively from a Proposed 
Standard.
However, RFC 5912 is already listed in the DOWNREF registry, so no new downref
approval is required.

Personnel

   The Document Shepherd for this document is Tim Hollebeek. The
   Responsible Area Director is Deb Cooley.

_______________________________________________
IETF-Announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to