RFC 5191 on Protocol for Carrying Authentication for Network Access (PANA)

rfc-editor@rfc-editor.org Tue, 13 May 2008 23:43 UTC

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F81B3A6854; Tue, 13 May 2008 16:43:23 -0700 (PDT)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7E8723A68B5; Tue, 13 May 2008 16:43:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.184
X-Spam-Level:
X-Spam-Status: No, score=-17.184 tagged_above=-999 required=5 tests=[AWL=-0.185, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BDv+96cUvUXn; Tue, 13 May 2008 16:43:20 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 981393A6854; Tue, 13 May 2008 16:43:20 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 3A73812A87B; Tue, 13 May 2008 14:38:42 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5191 on Protocol for Carrying Authentication for Network Access (PANA)
From: rfc-editor@rfc-editor.org
Message-Id: <20080513213842.3A73812A87B@bosco.isi.edu>
Date: Tue, 13 May 2008 14:38:42 -0700 (PDT)
Cc: pana@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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@nokia.com, 
                    yohba@tari.toshiba.com, 
                    basavaraj.patil@nsn.com,
                    hannes.tschofenig@nsn.com, 
                    a.yegin@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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info@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@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@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce