[HOKEY] RFC 6440 on The EAP Re-authentication Protocol (ERP) Local Domain Name DHCPv6 Option

rfc-editor@rfc-editor.org Fri, 16 December 2011 20:52 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: hokey@ietfa.amsl.com
Delivered-To: hokey@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 917591F0C73; Fri, 16 Dec 2011 12:52:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.117
X-Spam-Level:
X-Spam-Status: No, score=-102.117 tagged_above=-999 required=5 tests=[AWL=-0.117, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TYgdDClza0hd; Fri, 16 Dec 2011 12:52:58 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 345961F0C65; Fri, 16 Dec 2011 12:52:58 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4009A72E008; Fri, 16 Dec 2011 12:51:51 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20111216205151.4009A72E008@rfc-editor.org>
Date: Fri, 16 Dec 2011 12:51:51 -0800 (PST)
Cc: hokey@ietf.org, rfc-editor@rfc-editor.org
Subject: [HOKEY] RFC 6440 on The EAP Re-authentication Protocol (ERP) Local Domain Name DHCPv6 Option
X-BeenThere: hokey@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: HOKEY WG Mailing List <hokey.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hokey>, <mailto:hokey-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hokey>
List-Post: <mailto:hokey@ietf.org>
List-Help: <mailto:hokey-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hokey>, <mailto:hokey-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Dec 2011 20:52:58 -0000

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

        
        RFC 6440

        Title:      The EAP Re-authentication Protocol (ERP) 
                    Local Domain Name DHCPv6 Option 
        Author:     G. Zorn, Q. Wu,
                    Y. Wang
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2011
        Mailbox:    gwz@net-zen.net, 
                    sunseawq@huawei.com, 
                    w52006@huawei.com
        Pages:      6
        Characters: 10158
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-hokey-ldn-discovery-10.txt

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

In order to derive a Domain-Specific Root Key (DSRK) from the
Extended Master Session Key (EMSK) generated as a side effect of an
Extensible Authentication Protocol (EAP) method, the EAP peer must
discover the name of the domain to which it is attached.

This document specifies a Dynamic Host Configuration Protocol
Version 6 (DHCPv6) option designed to allow a DHCPv6 server to inform
clients using the EAP Re-authentication Protocol (ERP) EAP method of
the name of the local domain for ERP.  [STANDARDS-TRACK]

This document is a product of the Handover Keying 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-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