[rfc-dist] RFC 4334 on Certificate Extensions and Attributes Supporting Authentication in Point-to-Point Protocol (PPP) and Wireless Local Area Networks (WLAN)
rfc-editor at rfc-editor.org
Fri Feb 3 16:21:01 PST 2006
A new Request for Comments is now available in online RFC libraries.
Title: Certificate Extensions and Attributes Supporting
Authentication in Point-to-Point Protocol (PPP) and
Wireless Local Area Networks (WLAN)
Author: R. Housley, T. Moore
Status: Standards Track
Date: February 2006
Mailbox: housley at vigilsec.com,
timmoore at microsoft.com
I-D Tag: draft-ietf-pkix-rfc3770bis-03.txt
This document defines two Extensible Authentication Protocol (EAP)
extended key usage values and a public key certificate extension to
carry Wireless LAN (WLAN) System Service identifiers (SSIDs). This
document obsoletes RFC 3770. [STANDARDS TRACK]
This document is a product of the Public-Key Infrastructure (X.509) Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of
the Internet Official Protocol Standards (STD 1) for the
standardization state and status of this protocol. Distribution of
this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info at RFC-EDITOR.ORG
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
More information about the rfc-dist