Secure Network Access Authentication (SeNAA)
draft-forsberg-pana-secure-network-access-auth-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dan Forsberg , Jarno Rajahalme | ||
| Last updated | 2002-10-31 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This draft describes how reliable Secure Network Access Authentication (SeNAA) protocol over UDP carries Transport Layer Security (TLS) protocol. SeNAA messages are formatted like Diameter messages and contain Attribute Value Pairs (AVPs) that are protected with TLS Record Layer. SeNAA provides secure transport for Extended Authentication Protocol (EAP) between PANA Client (PaC) and PANA Authentication Agent (PAA). PANA stands for Protocol for carrying Authentication for Network Access.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)