RFC 5807 on Definition of Master Key between PANA Client and Enforcement Point

rfc-editor@rfc-editor.org Wed, 10 March 2010 06:00 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 05D3E3A6BF3 for <ietf-announce@core3.amsl.com>; Tue, 9 Mar 2010 22:00:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.836
X-Spam-Level:
X-Spam-Status: No, score=-1.836 tagged_above=-999 required=5 tests=[AWL=-0.448, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_93=0.6]
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 td6jZ-spf9zw for <ietf-announce@core3.amsl.com>; Tue, 9 Mar 2010 22:00:29 -0800 (PST)
Received: from rfc-editor.org (rfcpa [64.170.98.47]) by core3.amsl.com (Postfix) with ESMTP id 285353A6BEF for <ietf-announce@ietf.org>; Tue, 9 Mar 2010 22:00:29 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 58EC4E075E; Tue, 9 Mar 2010 22:00:34 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5807 on Definition of Master Key between PANA Client and Enforcement Point
From: rfc-editor@rfc-editor.org
Message-Id: <20100310060034.58EC4E075E@rfc-editor.org>
Date: Tue, 9 Mar 2010 22:00:34 -0800 (PST)
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Wed, 10 Mar 2010 06:00:30 -0000

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

        
        RFC 5807

        Title:      Definition of Master Key between 
                    PANA Client and Enforcement Point 
        Author:     Y. Ohba, A. Yegin
        Status:     Standards Track
        Date:       March 2010
        Mailbox:    yoshihiro.ohba@toshiba.co.jp, 
                    alper.yegin@yegin.org
        Pages:      7
        Characters: 13808
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ohba-pana-pemk-04.txt

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

This document defines a master key used between a client of the
Protocol for carrying Authentication for Network Access (PANA) and an
enforcement point, for bootstrapping lower-layer ciphering.  The
master key is derived from the Master Session Key of the Extensible
Authentication Protocol as a result of successful PANA
authentication.  The master key guarantees cryptographic independence
among enforcement points bootstrapped from PANA authentication across
different address families.  [STANDARDS TRACK]

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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC