--- 1/draft-ietf-dime-rfc4005bis-03.txt 2011-01-07 12:23:28.000000000 +0100 +++ 2/draft-ietf-dime-rfc4005bis-04.txt 2011-01-07 12:23:28.000000000 +0100 @@ -1,19 +1,19 @@ Network Working Group G. Zorn Internet-Draft Network Zen -Obsoletes: 4005 (if approved) January 2, 2011 +Obsoletes: 4005 (if approved) January 7, 2011 Intended status: Standards Track -Expires: July 6, 2011 +Expires: July 11, 2011 Diameter Network Access Server Application - draft-ietf-dime-rfc4005bis-03 + draft-ietf-dime-rfc4005bis-04 Abstract This document describes the Diameter protocol application used for Authentication, Authorization, and Accounting (AAA) services in the Network Access Server (NAS) environment. When combined with the Diameter Base protocol, Transport Profile, and Extensible Authentication Protocol specifications, this application specification satisfies typical network access services requirements. @@ -25,21 +25,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on July 6, 2011. + This Internet-Draft will expire on July 11, 2011. Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -1748,21 +1748,21 @@ This AVP MUST only be present in an authorization response. Multiple instances of this AVP in the same message are not allowed. The codification of this field's allowed range is outside the scope of this specification. 4.4.10.8. AppleTalk Remote Access AVPs The AVPs defined in this section are used when the user requests, or is being granted, access to the AppleTalk network via the AppleTalk - Remote Access Protocol [ARAP] They are only present if the Framed- + Remote Access Protocol [ARAP]. They are only present if the Framed- Protocol AVP Section 4.4.10.1 is set to ARAP. Section 2.2 of RFC 2869 [RFC2869] describes the operational use of these attributes. 4.4.10.8.1. ARAP-Features AVP The ARAP-Features AVP (AVP Code 71) is of type OctetString and MAY be present in the AA-Accept message if the Framed-Protocol AVP is set to the value of ARAP. See [RFC2869] for more information about the format of this AVP. @@ -2894,27 +2894,27 @@ Krumviede, Fergal Ladley, Ryan Moats, Victor Muslin, Kenneth Peirce, Sumit Vakil, John R. Vollbrecht, and Jeff Weisberg. Finally, Pat Calhoun would like to thank Sun Microsystems, as most of the effort put into this document was done while he was in their employ. A.2. RFC 4005bis The vast majority of the text in this document was lifted directly - fro RFC 4005; the editor owes a debt of gratitude to the authors + from RFC 4005; the editor owes a debt of gratitude to the authors thereof (especially Dave Mitton, who somehow managed to make nroff paginate the AVP Occurance Tables correctly!). Thanks (in no particular order) to Jai-Jin Lim, Liu Hans, Sebastien - Decugis and Stefan Winter for their useful reviews and helpful - comments. + Decugis, Jouni Korhonen and Stefan Winter for their useful reviews + and helpful comments. Author's Address Glen Zorn Network Zen 227/358 Thanon Sanphawut Bang Na, Bangkok 10260 Thailand Phone: +66 (0) 87-040-4617