draft-ietf-hokey-rfc5296bis-05.txt   draft-ietf-hokey-rfc5296bis-06.txt 
Network Working Group Q. Wu, Ed. Network Working Group Q. Wu, Ed.
Internet-Draft Huawei Internet-Draft Huawei
Obsoletes: 5296 (if approved) Z. Cao Obsoletes: 5296 (if approved) Z. Cao
Intended status: Standards Track China Mobile Intended status: Standards Track China Mobile
Expires: May 1, 2012 G. Zorn, Ed. Expires: May 18, 2012 G. Zorn, Ed.
Network Zen Network Zen
Y. Shi Y. Shi
H3C H3C
B. He B. He
CATR CATR
October 29, 2011 November 15, 2011
EAP Extensions for EAP Re-authentication Protocol (ERP) EAP Extensions for EAP Re-authentication Protocol (ERP)
draft-ietf-hokey-rfc5296bis-05 draft-ietf-hokey-rfc5296bis-06
Abstract Abstract
The Extensible Authentication Protocol (EAP) is a generic framework The Extensible Authentication Protocol (EAP) is a generic framework
supporting multiple types of authentication methods. In systems supporting multiple types of authentication methods. In systems
where EAP is used for authentication, it is desirable to avoid where EAP is used for authentication, it is desirable to avoid
repeating the entire EAP exchange with another authenticator. This repeating the entire EAP exchange with another authenticator. This
document specifies extensions to EAP and the EAP keying hierarchy to document specifies extensions to EAP and the EAP keying hierarchy to
support an EAP method-independent protocol for efficient re- support an EAP method-independent protocol for efficient re-
authentication between the peer and an EAP re-authentication server authentication between the peer and an EAP re-authentication server
through any authenticator. The re-authentication server may be in through any authenticator. The re-authentication server may be in
the home network or in the local network to which the peer is the home network or in the local network to which the peer is
connecting. connecting.
This memo obsoletes RFC 5296.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 1, 2012. This Internet-Draft will expire on May 18, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
skipping to change at page 26, line 47 skipping to change at page 26, line 47
ERP exchange, it MUST silently discard the EAP-Initiate/Re-auth-Start ERP exchange, it MUST silently discard the EAP-Initiate/Re-auth-Start
message. message.
If the EAP-Initiate/Re-auth-Start message contains the domain name, If the EAP-Initiate/Re-auth-Start message contains the domain name,
and if the peer does not already have the domain information, the and if the peer does not already have the domain information, the
peer SHOULD use the domain name contained in the message to compute peer SHOULD use the domain name contained in the message to compute
the DSRK and use the corresponding DS-rIK to send an EAP-Initiate/ the DSRK and use the corresponding DS-rIK to send an EAP-Initiate/
Re-auth message to start an ERP exchange with the local ER server. Re-auth message to start an ERP exchange with the local ER server.
If there is a local ER server between the peer and the home ER server If there is a local ER server between the peer and the home ER server
and the peer has already initiated an ERP exchange with the local ER and the peer has already initiated an ERP exchange with the local ER
server, it SHOULD not start an ERP exchange with the home ER server. server, it SHOULD NOT start an ERP exchange with the home ER server.
5.3.2. EAP-Initiate/Re-auth Packet 5.3.2. EAP-Initiate/Re-auth Packet
The EAP-Initiate/Re-auth packet contains the parameters shown in The EAP-Initiate/Re-auth packet contains the parameters shown in
Figure 9. Figure 9.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Code | Identifier | Length | | Code | Identifier | Length |
 End of changes. 7 change blocks. 
5 lines changed or deleted 8 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/