2006
DOI: 10.17487/rfc4284
|View full text |Cite
|
Sign up to set email alerts
|

Identity Selection Hints for the Extensible Authentication Protocol (EAP)

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
21
0

Year Published

2007
2007
2009
2009

Publication Types

Select...
9

Relationship

3
6

Authors

Journals

citations
Cited by 12 publications
(21 citation statements)
references
References 10 publications
0
21
0
Order By: Relevance
“…In order to determine the privacy configuration on link layers (such as IEEE 802 wired networks) that do not support network advertisement, it may be desirable to utilize information provided in the server certificate (such as the subject and subjectAltName fields) or within identity selection hints [RFC4284] to determine the appropriate configuration.…”
Section: Base Casementioning
confidence: 99%
“…In order to determine the privacy configuration on link layers (such as IEEE 802 wired networks) that do not support network advertisement, it may be desirable to utilize information provided in the server certificate (such as the subject and subjectAltName fields) or within identity selection hints [RFC4284] to determine the appropriate configuration.…”
Section: Base Casementioning
confidence: 99%
“…For example, the identity provided in the EAP-Response/Identity can be a privacy identifier as described in "The Network Access Identifier" [RFC4282] Section 2. As noted in [RFC4284], it is also possible to utilize a Network Access Identifier (NAI) for the purposes of source routing; an NAI utilized for source routing is said to be "decorated" as described in [RFC4282] Section 2.7.…”
Section: Peer Identificationmentioning
confidence: 99%
“…Most of these networks have no means to carry any information about what is expected from the authentication process. EAP itself is severely limited in carrying any additional information, as noted in [RFC4284] and [RFC5113]. Even if these networks or EAP were extended to carry additional information, it would not affect millions of deployed access networks and clients attaching to them.…”
Section: Appendix a Changes From Rfc 4187mentioning
confidence: 99%