Diameter Applications Design Guidelines
draft-ietf-dime-app-design-guide-17

The information below is for an old version of the document
Document Type Active Internet-Draft (dime WG)
Last updated 2013-05-29
Replaces draft-fajardo-dime-app-design-guide
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Consensus: Waiting for Write-Up (wg milestone: May 2012 - Submit 'Diameter App... )
Document shepherd Jouni Korhonen
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Diameter Maintenance and Extensions (DIME)                L. Morand, Ed.
Internet-Draft                                               Orange Labs
Intended status: Informational                                V. Fajardo
Expires: November 30, 2013                                 H. Tschofenig
                                                  Nokia Siemens Networks
                                                            May 29, 2013

                Diameter Applications Design Guidelines
                  draft-ietf-dime-app-design-guide-17

Abstract

   The Diameter Base protocol provides facilities for protocol
   extensibility enabling to define new Diameter applications or modify
   existing applications.  This document is a companion document to the
   Diameter base protocol that further explains and clarifies the rules
   to extend the Diameter base protocol.  It is meant as a guidelines
   document and therefore it does not add, remove or change existing
   rules.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   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 November 30, 2013.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Morand, et al.         Expires November 30, 2013                [Page 1]
Internet-Draft  Diameter Applications Design Guidelines         May 2013

   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
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Reusing Existing Diameter Applications  . . . . . . . . . . .   5
     4.1.  Adding a New Command  . . . . . . . . . . . . . . . . . .   5
     4.2.  Deleting an Existing Command  . . . . . . . . . . . . . .   6
     4.3.  Reusing Existing Commands . . . . . . . . . . . . . . . .   6
       4.3.1.  Adding AVPs to a Command  . . . . . . . . . . . . . .   7
       4.3.2.  Deleting AVPs from a Command  . . . . . . . . . . . .   8
     4.4.  Reusing Existing AVPs . . . . . . . . . . . . . . . . . .   9
       4.4.1.  Setting of the AVP Flags  . . . . . . . . . . . . . .   9
       4.4.2.  Reuse of AVP of Type Enumerated . . . . . . . . . . .   9
   5.  Defining New Diameter Applications  . . . . . . . . . . . . .   9
     5.1.  Introduction  . . . . . . . . . . . . . . . . . . . . . .   9
     5.2.  Defining New Commands . . . . . . . . . . . . . . . . . .  10
     5.3.  Use of Application-Id in a Message  . . . . . . . . . . .  11
     5.4.  Application-Specific Session State Machines . . . . . . .  11
     5.5.  Session-Id AVP and Session Management . . . . . . . . . .  11
     5.6.  AVPs Defined as Boolean Flag  . . . . . . . . . . . . . .  12
     5.7.  Application-Specific Message Routing  . . . . . . . . . .  13
     5.8.  About Translation Agent . . . . . . . . . . . . . . . . .  13
     5.9.  End-to-End Application Capabilities Exchange  . . . . . .  14
     5.10. Diameter Accounting Support . . . . . . . . . . . . . . .  15
     5.11. Diameter Security Mechanisms  . . . . . . . . . . . . . .  16
   6.  Defining Generic Diameter Extensions  . . . . . . . . . . . .  17
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  18
   9.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  18
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  19
Show full document text