draft-ietf-hokey-erp-aak-10.txt | draft-ietf-hokey-erp-aak-11.txt | |||
---|---|---|---|---|
Network Working Group Z. Cao | Network Working Group Z. Cao | |||
Internet-Draft H. Deng | Internet-Draft H. Deng | |||
Intended status: Standards Track China Mobile | Intended status: Standards Track China Mobile | |||
Expires: August 20, 2012 Q. Wu | Expires: November 3, 2012 Q. Wu | |||
Huawei | Huawei | |||
G. Zorn, Ed. | G. Zorn, Ed. | |||
Network Zen | Network Zen | |||
February 17, 2012 | May 2, 2012 | |||
EAP Re-authentication Protocol Extensions for Authenticated Anticipatory | EAP Re-authentication Protocol Extensions for Authenticated Anticipatory | |||
Keying (ERP/AAK) | Keying (ERP/AAK) | |||
draft-ietf-hokey-erp-aak-10 | draft-ietf-hokey-erp-aak-11 | |||
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. | supporting multiple types of authentication methods. | |||
The EAP Re-authentication Protocol (ERP) specifies extensions to EAP | The EAP Re-authentication Protocol (ERP) specifies extensions to EAP | |||
and the EAP keying hierarchy to support an EAP method-independent | and the EAP keying hierarchy to support an EAP method-independent | |||
protocol for efficient re-authentication between the peer and an EAP | protocol for efficient re-authentication between the peer and an EAP | |||
re-authentication server through any authenticator. | re-authentication server through any authenticator. | |||
skipping to change at page 1, line 49 | skipping to change at page 1, line 49 | |||
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 August 20, 2012. | This Internet-Draft will expire on November 3, 2012. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2012 IETF Trust and the persons identified as the | Copyright (c) 2012 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 | |||
skipping to change at page 16, line 35 | skipping to change at page 16, line 35 | |||
o Authorization restriction: All the keys derived are limited in | o Authorization restriction: All the keys derived are limited in | |||
lifetime by that of the parent key or by server policy. Any | lifetime by that of the parent key or by server policy. Any | |||
domain-specific keys are further restricted to be used only in the | domain-specific keys are further restricted to be used only in the | |||
domain for which the keys are derived. Any other restrictions of | domain for which the keys are derived. Any other restrictions of | |||
session keys may be imposed by the specific lower layer and are | session keys may be imposed by the specific lower layer and are | |||
out of scope for this specification. | out of scope for this specification. | |||
9. IANA Considerations | 9. IANA Considerations | |||
IANA is requested to assign four TLV type values from the registry of | IANA is requested to assign five TLV type values from the registry of | |||
EAP Initiate and Finish Attributes maintained at | EAP Initiate and Finish Attributes maintained at | |||
http://www.iana.org/assignments/eap-numbers/eap-numbers.xml. | http://www.iana.org/assignments/eap-numbers/eap-numbers.xml. | |||
with the following numbers: | with the following numbers: | |||
o Sequence number: This is a TV payload. The type is 7. | o Sequence number: This is a TV payload. The type is 7. | |||
o ERP/AAK-Key: This is a TLV payload. The type is 8. | o ERP/AAK-Key: This is a TLV payload. The type is 8. | |||
o pRK Lifetime: This is a TLV payload. The type is 9. | o pRK Lifetime: This is a TLV payload. The type is 9. | |||
skipping to change at page 17, line 24 | skipping to change at page 17, line 24 | |||
(E) 0x80 | (E) 0x80 | |||
The rest of the values in the 8-bit field are reserved. New values | The rest of the values in the 8-bit field are reserved. New values | |||
can be assigned by Standards Action or IESG approval. | can be assigned by Standards Action or IESG approval. | |||
This document also creates a new registry for the flags in the EAP | This document also creates a new registry for the flags in the EAP | |||
Initiate/Re-auth message called the "EAP Initiate/Re-auth Flags". | Initiate/Re-auth message called the "EAP Initiate/Re-auth Flags". | |||
The following flag are reserved: | The following flag are reserved: | |||
(R) 0x80 [RFC5296] | ||||
(B) 0x40 [RFC5296] | (B) 0x40 [RFC5296] | |||
(L) 0x20 [RFC5296] | (L) 0x20 [RFC5296] | |||
This document assigns a new flag (E) as follows: | This document assigns a new flag (E) as follows: | |||
(E) 0x10 | (E) 0x10 | |||
The rest of the values in the 8-bit field are reserved. New values | The rest of the values in the 8-bit field are reserved. New values | |||
can be assigned by Standards Action or IESG approval. | can be assigned by Standards Action or IESG approval. | |||
Further,this document creates a new registry for the flags in the EAP | Further,this document creates a new registry for the flags in the EAP | |||
Finish/Re-auth message called the "EAP Finish/Re-auth Flags". The | Finish/Re-auth message called the "EAP Finish/Re-auth Flags". The | |||
following values are reserved. | following values are reserved. | |||
(R) 0x80 [RF5296] | (R) 0x80 [RFC5296] | |||
(B) 0x40 [RFC5296] | (B) 0x40 [RFC5296] | |||
(L) 0x20 [RFC5296] | (L) 0x20 [RFC5296] | |||
This document assigns a new flag (E) as follows: | This document assigns a new flag (E) as follows: | |||
(E) 0x10 | (E) 0x10 | |||
The rest of the values in the 8-bit field are reserved. New values | The rest of the values in the 8-bit field are reserved. New values | |||
End of changes. 7 change blocks. | ||||
6 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/ |