[rfc-dist] RFC 5191 on Protocol for Carrying Authentication for Network Access (PANA)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Tue May 13 14:38:42 PDT 2008

A new Request for Comments is now available in online RFC libraries.

        RFC 5191

        Title:      Protocol for Carrying Authentication for 
                    Network Access (PANA) 
        Author:     D. Forsberg, Y. Ohba,
                    Ed., B. Patil, H. Tschofenig, A. Yegin
        Status:     Standards Track
        Date:       May 2008
        Mailbox:    dan.forsberg at nokia.com, 
                    yohba at tari.toshiba.com, 
                    basavaraj.patil at nsn.com,
                    hannes.tschofenig at nsn.com, 
                    a.yegin at partner.samsung.com
        Pages:      46
        Characters: 96716
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pana-pana-18.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5191.txt

This document defines the Protocol for Carrying Authentication for
Network Access (PANA), a network-layer transport for Extensible
Authentication Protocol (EAP) to enable network access authentication
between clients and access networks.  In EAP terms, PANA is a
UDP-based EAP lower layer that runs between the EAP peer and the EAP
authenticator.  [STANDARDS TRACK]

This document is a product of the Protocol for carrying Authentication for Network Access 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

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

        help: ways_to_get_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
unlimited distribution.

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.

The RFC Editor Team
USC/Information Sciences Institute


More information about the rfc-dist mailing list