|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
to be completed
|
|
3.
|
Justification for the specific reference:
|
|
|
EAP-TLS defined in Annex D of this document uses EAP-TLS protocol specified in IETF RFC 5216
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding document is available at: https://datatracker.ietf.org/ipr/search/.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
to be completed
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
to be completed
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
to be completed
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
to be completed
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
