One document matched: draft-zorn-dime-doc-set-00.txt
Network Working Group G. Zorn
Internet-Draft Network Zen
Intended status: BCP July 5, 2009
Expires: January 6, 2010
The Diameter Document Set
draft-zorn-dime-doc-set-00
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from
the person(s) controlling the copyright in such materials, this
document may not be modified outside the IETF Standards Process, and
derivative works of it may not be created outside the IETF Standards
Process, except to format it for publication as an RFC or to
translate it into languages other than English.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
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."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 6, 2010.
Copyright Notice
Copyright (c) 2009 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
Zorn Expires January 6, 2010 [Page 1]
Internet-Draft The Diameter Document Set July 2009
Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights
and restrictions with respect to this document.
Abstract
This note contains a brief description of the current Diameter
document set. Although the document included are all published RFCs,
not all are products of the IETF.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. The Diameter Document Set . . . . . . . . . . . . . . . . . . . 3
3.1. IETF Documents . . . . . . . . . . . . . . . . . . . . . . 3
3.1.1. Diameter Base Protocol . . . . . . . . . . . . . . . . 3
3.1.2. AAA Transport Profile . . . . . . . . . . . . . . . . . 3
3.1.3. Applications . . . . . . . . . . . . . . . . . . . . . 4
3.1.3.1. Mobile IPv4 . . . . . . . . . . . . . . . . . . . . 4
3.1.3.2. Network Access Server (NASREQ) . . . . . . . . . . 4
3.1.3.3. Diameter Credit Control . . . . . . . . . . . . . . 4
3.1.3.4. EAP . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1.3.5. SIP . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1.3.6. Mobile IPv6 . . . . . . . . . . . . . . . . . . . . 4
3.2. Other RFCs . . . . . . . . . . . . . . . . . . . . . . . . 4
3.2.1. 3GPP EPS Command Codes . . . . . . . . . . . . . . . . 5
3.2.2. ITU-T Rw Policy Enforcement Interface . . . . . . . . . 5
3.2.3. Diameter Policy Processing Application . . . . . . . . 5
3.2.4. 3GPP Release 5 Command Codes . . . . . . . . . . . . . 5
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
5. IANA considerations . . . . . . . . . . . . . . . . . . . . . . 5
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 6
7. Informative References . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7
Zorn Expires January 6, 2010 [Page 2]
Internet-Draft The Diameter Document Set July 2009
1. Introduction
This document is intended to provide a stable reference to the
dynamic set of RFCs describing the Diameter protocol. As such, it is
expected that it will be updated/obsoleted shortly after any new
Diameter-related RFC is published.
2. Terminology
AAA
Authentication, Authorization and Accounting
3. The Diameter Document Set
The Diameter document set has two components:
o products of the IETF itself, generally Standards-Track [RFC2026]
RFCs
and
o RFCs relating to Diameter-based protocols developed outside the
IETF.
3.1. IETF Documents
Currently, the IETF Diameter specification consists of the Base
protocol specification [RFC3588], Transport Profile [RFC3539] and
several applications: Mobile IPv4 [RFC4004], Network Access Server
(NASREQ) [RFC4005], Credit Control [RFC4006], Extensible
Authentication Protocol (EAP) [RFC4072], Session Initiation Protocol
(SIP) [RFC4740], and Mobile IPv6 [RFC5447].
The following subsections briefly summarize the documents included in
the present set.
3.1.1. Diameter Base Protocol
The Base Protocol document [RFC3588] defines the fundamental protocol
specification for Diameter AAA, which includes support for
accounting.
3.1.2. AAA Transport Profile
The Transport Profile document [RFC3539] discusses transport layer
issues that arise with AAA protocols and contains recommendations on
Zorn Expires January 6, 2010 [Page 3]
Internet-Draft The Diameter Document Set July 2009
how to overcome these issues. This document also defines the
Diameter failover algorithm and state machine.
3.1.3. Applications
3.1.3.1. Mobile IPv4
The Mobile IPv4 [RFC4004] document defines a Diameter application
that allows a Diameter server to perform AAA functions for MobileIPv4
services to a mobile node.
3.1.3.2. Network Access Server (NASREQ)
This document [RFC4005] describes the Diameter protocol application
used for AAA services in the Network Access Server (NAS) environment.
When combined with the Diameter Base protocol [RFC3588], Transport
Profile [RFC3539], and EAP [RFC4072] specifications, this application
specification satisfies typical network access service requirements.
3.1.3.3. Diameter Credit Control
This document [RFC4006] specifies a Diameter application that can be
used to implement real-time credit-control for a variety of end user
services such as network access, Session Initiation Protocol (SIP)
[RFC3261] services, messaging services, and download services.
3.1.3.4. EAP
This document [RFC4072] defines the Diameter Command-Codes and AVPs
necessary to carry EAP packets between a Network Access Server (NAS)
and a back-end authentication server.
3.1.3.5. SIP
This application [RFC4740] is designed to be used in conjunction with
SIP and provides a Diameter client co-located with a SIP server, with
the ability to request the authentication of users and authorization
of SIP resources usage from a Diameter server.
3.1.3.6. Mobile IPv6
This document [RFC5447] describes Mobile IPv6 bootstrapping using the
Diameter Network Access Server to home AAA server interface.
3.2. Other RFCs
Zorn Expires January 6, 2010 [Page 4]
Internet-Draft The Diameter Document Set July 2009
3.2.1. 3GPP EPS Command Codes
This document [RFC5516] registers a set of Diameter Command Codes to
be used in new vendor-specific Diameter applications defined for the
Third Generation Partnership Project (3GPP) Evolved Packet System
(EPS), specifically those related to the Mobile Management Entity
(MME) and Serving GPRS (General Packet Radio Service) Support Node
(SGSN) interfaces in the architecture for the Evolved 3GPP Packet
Switched Domain.
3.2.2. ITU-T Rw Policy Enforcement Interface
This document [RFC5431] describes the need for a new pair of IANA
Diameter Command Codes to be used in a vendor-specific new
application, namely for the ITU-T Rec. Q.3303.3 - Rw interface used
to send a request/response for authorizing network Quality of Service
(QoS) resources and policy enforcement in a network element, as one
of the recommendations of the International Telecommunication Union -
Telecommunication Standardization Sector (ITU-T).
3.2.3. Diameter Policy Processing Application
This document [RFC5224] describes the need for a Diameter Command
Code to be used in a vendor-specific application for invocation of
Policy Processing (Policy Evaluation, or Evaluation and Enforcement).
This application is one of the implementations of the Open Mobile
Alliance (OMA) Policy Evaluation, Enforcement and Management (PEEM)
enabler.
3.2.4. 3GPP Release 5 Command Codes
This document [RFC3589] describes the IANA allocation of a block of
Diameter Command Codes for the Third Generation Partnership Project
(3GPP) Release 5.
4. Security Considerations
This document has no relevance for security.
5. IANA considerations
This document makes no requests of IANA.
Zorn Expires January 6, 2010 [Page 5]
Internet-Draft The Diameter Document Set July 2009
6. Acknowledgments
Most of this note was lifted from RFC 3588, Section 1.1.1.
7. Informative References
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision
3", BCP 9, RFC 2026, October 1996.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002.
[RFC3539] Aboba, B. and J. Wood, "Authentication, Authorization and
Accounting (AAA) Transport Profile", RFC 3539, June 2003.
[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
[RFC3589] Loughney, J., "Diameter Command Codes for Third Generation
Partnership Project (3GPP) Release 5", RFC 3589,
September 2003.
[RFC4004] Calhoun, P., Johansson, T., Perkins, C., Hiller, T., and
P. McCann, "Diameter Mobile IPv4 Application", RFC 4004,
August 2005.
[RFC4005] Calhoun, P., Zorn, G., Spence, D., and D. Mitton,
"Diameter Network Access Server Application", RFC 4005,
August 2005.
[RFC4006] Hakala, H., Mattila, L., Koskinen, J-P., Stura, M., and J.
Loughney, "Diameter Credit-Control Application", RFC 4006,
August 2005.
[RFC4072] Eronen, P., Hiller, T., and G. Zorn, "Diameter Extensible
Authentication Protocol (EAP) Application", RFC 4072,
August 2005.
[RFC4740] Garcia-Martin, M., Belinchon, M., Pallares-Lopez, M.,
Canales-Valenzuela, C., and K. Tammi, "Diameter Session
Initiation Protocol (SIP) Application", RFC 4740,
November 2006.
[RFC5224] Brenner, M., "Diameter Policy Processing Application",
RFC 5224, March 2008.
Zorn Expires January 6, 2010 [Page 6]
Internet-Draft The Diameter Document Set July 2009
[RFC5431] Sun, D., "Diameter ITU-T Rw Policy Enforcement Interface
Application", RFC 5431, March 2009.
[RFC5447] Korhonen, J., Bournelle, J., Tschofenig, H., Perkins, C.,
and K. Chowdhury, "Diameter Mobile IPv6: Support for
Network Access Server to Diameter Server Interaction",
RFC 5447, February 2009.
[RFC5516] Jones, M. and L. Morand, "Diameter Command Code
Registration for the Third Generation Partnership Project
(3GPP) Evolved Packet System (EPS)", RFC 5516, April 2009.
Author's Address
Glen Zorn
Network Zen
1310 East Thomas Street
#306
Seattle, Washington 98102
USA
Phone: +1 (206) 377-9035
Email: gwz@net-zen.net
Zorn Expires January 6, 2010 [Page 7]
| PAFTECH AB 2003-2026 | 2026-04-23 02:33:09 |