--- 1/draft-ietf-dime-capablities-update-03.txt 2010-05-24 07:12:20.000000000 +0200 +++ 2/draft-ietf-dime-capablities-update-04.txt 2010-05-24 07:12:20.000000000 +0200 @@ -1,64 +1,58 @@ Network Working Group K. Jiao Internet-Draft Huawei Intended status: Standards Track G. Zorn -Expires: August 30, 2010 Network Zen - February 26, 2010 +Expires: November 25, 2010 Network Zen + May 24, 2010 The Diameter Capabilities Update Application - draft-ietf-dime-capablities-update-03 + draft-ietf-dime-capablities-update-04 Abstract This document defines a new Diameter application and associated command codes. The Capabilities Update application is intended to allow the dynamic update of certain Diameter peer capabilities while the peer-to-peer connection is in the open state. Status of this Memo - This Internet-Draft is submitted to IETF in full conformance with the + 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), its areas, and its working groups. Note that - other groups may also distribute working documents as Internet- - Drafts. + 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." - 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 August 30, 2010. + This Internet-Draft will expire on November 25, 2010. Copyright Notice Copyright (c) 2010 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 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 BSD License. + described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Specification of Requirements . . . . . . . . . . . . . . . . . 3 3. Diameter Protocol Considerations . . . . . . . . . . . . . . . 3 4. Capabilities Update . . . . . . . . . . . . . . . . . . . . . . 3 4.1. Command-Code Values . . . . . . . . . . . . . . . . . . . . 4 4.1.1. Capabilities-Update-Request . . . . . . . . . . . . . . 5 4.1.2. Capabilities-Update-Answer . . . . . . . . . . . . . . 5 @@ -114,40 +108,39 @@ including the value in the Auth-Application-Id of the Capabilities-Exchange-Req and Capabilities-Exchange-Answer commands [RFC3588]. 4. Capabilities Update When the capabilities of a Diameter node conforming to this specification change, it SHOULD notify all of the nodes with which it has an open transport connection and have also advertised support for the Capabilities Update application using the Capabilities-Update- - Request message Section 4.1.1. This message allows the update of a - peer's capabilities (protocol version number, supported Diameter - applications, etc.). + Request message (Section 4.1.1). This message allows the update of a + peer's capabilities (supported Diameter applications, etc.). A Diameter node only issues a given command to those peers that have advertised support for the Diameter application that defines the command. A Diameter node MUST cache the supported applications in order to ensure that unrecognized commands and/or AVPs are not unnecessarily sent to a peer. The receiver of the CUR MUST determine common applications by computing the intersection of its own set of supported Application Id against all of the application identifier AVPs (Auth-Application-Id, Acct-Application-Id and Vendor-Specific- Application-Id) present in the CUR. The value of the Vendor-Id AVP in the Vendor-Specific- Application-Id MUST NOT be used during computation. If the receiver of a Capabilities-Update-Req (CUR) message does not have any applications in common with the sender then it MUST return a - Capabilities-Update-Answer (CUA) Section 4.1.2 with the Result-Code + Capabilities-Update-Answer (CUA) (Section 4.1.2) with the Result-Code AVP set to DIAMETER_NO_COMMON_APPLICATION, and SHOULD disconnect the transport layer connection; however, if active sessions are using the connection, peers MAY delay disconnection until the sessions can be redirected or gracefully terminated. Note that receiving a CUA from a peer advertising itself as a Relay (see [RFC3588], Section 2.4) MUST be interpreted as having common applications with the peer. The CUR and CUA messages MUST NOT be proxied, redirected or relayed. Even though the CUR/CUA messages cannot be proxied, it is still