rfc-4334

Certificate Extensions and Attributes Supporting Authentication in Point-to-Point Protocol (PPP) and Wireless Local Area Networks (WLAN)

R. Housley, T. Moore
date2006-02 streamIETF areasec wgpkix statusPROPOSED STANDARD pages11 canonicalhttps://www.rfc-editor.org/rfc/rfc4334 doi10.17487/RFC4334 errataview
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]

obsoletes

Extracted elements (20)

design-rationale §4

A companion attribute certificate carrying the SSID list is provided as an alternative when the public key certificate itself cannot be modified, allowing SSID association without reissuing the base certificate.

pkix

design-rationale §1

Certificate extensions identifying the intended environment (PPP vs. WLAN, specific SSIDs) enable automated client certificate selection, minimizing user input and facilitating administrative separation of certificates used for different environments.

pkix, security

interoperability-note §1.1

RFC 3770 contained a typographical error in the OID for the Wireless LAN SSID Attribute Certificate Attribute (id-aca-wlanSSID). RFC 4334 corrects this error; implementations based on RFC 3770 may have used the wrong OID arc.

pkix, security

interoperability-note §1.1

The SSID extension MAY appear in certificates that do not include the extended key usage extension, clarifying that the two extensions are independently optional.

pkix

normative-requirement §2 MUST

If a certificate contains both a key usage extension and an extended key usage extension, both extensions MUST be processed independently, and the certificate MUST only be used for a purpose consistent with both extensions.

pkix, security

normative-requirement §3 MUST

If the extended key usage extension appears in the same certificate as the SSID extension, then the extended key usage extension MUST indicate that the certified public key is appropriate for use with EAP in the LAN environment by including the id-kp-eapOverLAN KeyPurposeId value.

pkix, security

normative-requirement §2 MUST NOT

If there is no purpose consistent with both a key usage extension and an extended key usage extension present in the same certificate, the certificate-using application MUST NOT use the certificate for any purpose.

pkix, security

normative-requirement §3 MAY

In cases where a human user is unavailable and automatic SSID-based certificate selection fails, each potential certificate MAY be tried until one succeeds.

pkix, security

normative-requirement §5 MUST

The CA MUST ensure that the correct values for the extended key usage extension and SSID extension are inserted in each certificate that is issued, as incorrect representation could cause relying parties to incorrectly accept or reject certificates.

pkix, security

normative-requirement §2 MAY

The extended key usage extension MAY, at the option of the certificate issuer, be either critical or non-critical.

pkix

normative-requirement §3 SHOULD

When automatic certificate selection fails due to duplicate SSIDs across different WLANs, the implementation SHOULD obtain help from the user to choose the correct certificate.

pkix, security

protocol-element §4

The WLAN SSID attribute certificate attribute (id-aca-wlanSSID, { id-aca 7 }) associates a list of SSIDs with a public key certificate via an attribute certificate when the public key certificate does not include the WLAN SSID certificate extension. It uses the same SSIDList syntax.

pkix, security

protocol-element §3

The WLAN SSID public key certificate extension (id-pe-wlanSSID, { id-pe 13 }) is always non-critical and contains a list of SSIDs encoded as SSIDList ::= SEQUENCE SIZE (1..MAX) OF SSID, where SSID ::= OCTET STRING (SIZE (1..32)).

pkix, security

protocol-element §2

Two EAP extended key usage OID values are defined: id-kp-eapOverPPP ({ id-kp 13 }) for EAP in PPP environments and id-kp-eapOverLAN ({ id-kp 14 }) for EAP in LAN/WLAN environments. Inclusion of both indicates the certified public key is appropriate for either environment.

pkix, security

registry §6

OIDs used in this document (id-kp-eapOverPPP, id-kp-eapOverLAN, id-pe-wlanSSID, id-aca-wlanSSID) were assigned from an arc delegated by IANA; no further IANA action is required for this document.

pkix, registry

security-consideration §5

In practice, SSID disclosure via certificates is of little concern because other WLAN management messages already include the SSID, so masking the SSID in AP beacons only forces an attacker to eavesdrop on management messages instead. Placing the SSID in the certificate does not worsen the security posture.

pkix, security

security-consideration §5

When automatic certificate selection fails due to non-unique SSIDs, sequentially trying each certificate discloses the list of SSIDs associated with each certificate. It is RECOMMENDED that sequential certificate trials only be employed when user selection is unavailable or impractical.

pkix, security, privacy

security-consideration §5

When the same peer certificate is used to authenticate to multiple WLANs, the list of SSIDs is available from servers associated with each WLAN and is also exposed to eavesdroppers. When SSID disclosure is a concern, different peer certificates SHOULD be used for each WLAN.

pkix, security, privacy

wire-format §3

The SSID field is encoded as an OCTET STRING of SIZE (1..32) bytes. The SSIDList extension value is a SEQUENCE of one or more such SSID values, using ASN.1 DER encoding per X.690.

pkix

wire-format §4

The WLAN SSID attribute certificate attribute syntax is identical to the certificate extension: SSIDList ::= SEQUENCE SIZE (1..MAX) OF SSID, where SSID ::= OCTET STRING (SIZE (1..32)).

pkix