idnits 2.17.1 draft-ietf-dime-capablities-update-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (December 1, 2009) is 5259 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 3588 (Obsoleted by RFC 6733) -- Obsolete informational reference (is this intentional?): RFC 4960 (Obsoleted by RFC 9260) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group K. Jiao 3 Internet-Draft Huawei 4 Intended status: Standards Track G. Zorn 5 Expires: June 4, 2010 Network Zen 6 December 1, 2009 8 The Diameter Capabilities Update Application 9 draft-ietf-dime-capablities-update-01 11 Abstract 13 This document defines a new Diameter application and associated 14 command codes. The Capabilities Update application is intended to 15 allow the dynamic update of Diameter peer capabilities while the 16 peer-to-peer connection is in the open state. 18 Status of this Memo 20 This Internet-Draft is submitted to IETF in full conformance with the 21 provisions of BCP 78 and BCP 79. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that 25 other groups may also distribute working documents as Internet- 26 Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt. 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html. 39 This Internet-Draft will expire on June 4, 2010. 41 Copyright Notice 43 Copyright (c) 2009 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (http://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. Specification of Requirements . . . . . . . . . . . . . . . . . 3 60 3. Diameter Protocol Considerations . . . . . . . . . . . . . . . 3 61 4. Capabilities Update . . . . . . . . . . . . . . . . . . . . . . 3 62 4.1. Command-Code Values . . . . . . . . . . . . . . . . . . . . 4 63 4.1.1. Capabilities-Update-Request . . . . . . . . . . . . . . 5 64 4.1.2. Capabilities-Update-Answer . . . . . . . . . . . . . . 5 65 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 66 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 67 6.1. Application Identifier . . . . . . . . . . . . . . . . . . 6 68 6.2. Command Codes . . . . . . . . . . . . . . . . . . . . . . . 6 69 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 70 7.1. Normative References . . . . . . . . . . . . . . . . . . . 6 71 7.2. Informative References . . . . . . . . . . . . . . . . . . 6 72 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 74 1. Introduction 76 Capabilities exchange is an important component of the Diameter Base 77 Protocol [RFC3588], allowing peers to exchange identities and 78 Diameter capabilities (protocol version number, supported Diameter 79 applications, security mechanisms, etc.). As defined in RFC 3588, 80 however, the capabilities exchange process takes place only once, at 81 the inception of a transport connection between a given pair of 82 peers. Therefore, if a peer's capabilities change (due to software 83 update, for example), the existing connection(s) must be torn down 84 (along with all of the associated user sessions) and restarted before 85 the modified capabilities can be advertised. 87 This document defines a new Diameter application intended to allow 88 the dynamic update of Diameter peer capabilities over an existing 89 connection. Because the Capabilities Update application specified 90 here operates over an existing transport connection, modification of 91 the security mechanism in use is not allowed; if the security method 92 used between a pair of peers is changed the affected connection MUST 93 be restarted. 95 Discussion of this draft may be directed to the dime Working Group of 96 the IETF (dime@ietf.org). 98 2. Specification of Requirements 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 102 document are to be interpreted as described in RFC 2119 [RFC2119]. 104 3. Diameter Protocol Considerations 106 This section details the relationship of the Diameter Capabilities 107 Update application to the Diameter Base Protocol. 109 This document specifies Diameter Application-ID . Diameter 110 nodes conforming to this specification MUST advertise support by 111 including the value in the Auth-Application-Id of the 112 Capabilities-Exchange-Req and Capabilities-Exchange-Answer commands 113 [RFC3588]. 115 4. Capabilities Update 117 When the capabilities of a Diameter node conforming to this 118 specification change, it SHOULD notify all of the nodes with which it 119 has an open transport connection and have also advertised support for 120 the Capabilities Update application using the Capabilities-Update- 121 Request message Section 4.1.1. This message allows the update of a 122 peer's capabilities (protocol version number, supported Diameter 123 applications, etc.). 125 The receiver only issues commands to its peers that have advertised 126 support for the Diameter application that defines the command. A 127 Diameter node MUST cache the supported applications in order to 128 ensure that unrecognized commands and/or AVPs are not unnecessarily 129 sent to a peer. 131 The receiver of the CUR MUST determine common applications by 132 computing the intersection of its own set of supported Application Id 133 against all of the application identifier AVPs (Auth-Application-Id, 134 Acct-Application-Id and Vendor-Specific- Application-Id) present in 135 the CUR. The value of the Vendor-Id AVP in the Vendor-Specific- 136 Application-Id MUST NOT be used during computation. 138 If the receiver of a Capabilities-Update-Req (CUR) message does not 139 have any applications in common with the sender then it MUST return a 140 Capabilities-Update-Answer (CUA) Section 4.1.2 with the Result-Code 141 AVP set to DIAMETER_NO_COMMON_APPLICATION, and SHOULD disconnect the 142 transport layer connection; however, if active sessions are using the 143 connection, peers MAY delay disconnection until the sessions can be 144 redirected or gracefully terminated. Note that receiving a CUA from 145 a peer advertising itself as a Relay (see [RFC3588], Section 2.4) 146 MUST be interpreted as having common applications with the peer. 148 The CUR and CUA messages MUST NOT be proxied, redirected or relayed. 150 Even though the CUR/CUA messages cannot be proxied, it is still 151 possible for an upstream agent to receive a message for which there 152 are no peers available to handle the application that corresponds to 153 the Command-Code. This could happen if, for example, the peers are 154 too busy or down. In such instances, the 'E' bit MUST be set in the 155 answer message with the Result-Code AVP set to 156 DIAMETER_UNABLE_TO_DELIVER to inform the downstream peer to take 157 action (e.g., re-routing requests to an alternate peer). 159 4.1. Command-Code Values 161 This section defines Command-Code [RFC3588] values that MUST be 162 supported by all Diameter implementations conforming to this 163 specification. The following Command Codes are defined in this 164 document: Capabilities-Update-Request (CUR, Section 4.1.1) and 165 Capabilities-Update-Answer (CUA, Section 4.1.2). 167 4.1.1. Capabilities-Update-Request 169 The Capabilities-Update-Request (CUR), indicated by the Command-Code 170 set to and the Command Flags' 'R' bit set, is sent to update 171 local capabilities. Upon detection of a transport failure, this 172 message MUST NOT be sent to an alternate peer. 174 When Diameter is run over SCTP [RFC4960], which allows connections to 175 span multiple interfaces and multiple IP addresses, the Capabilities- 176 Update-Request message MUST contain one Host-IP-Address AVP for each 177 potential IP address that may be locally used when transmitting 178 Diameter messages. 180 Message Format 182 ::= < Diameter Header: TBD2, REQ > 183 { Origin-Host } 184 { Origin-Realm } 185 1* { Host-IP-Address } 186 { Vendor-Id } 187 { Product-Name } 188 [ Origin-State-Id ] 189 * [ Supported-Vendor-Id ] 190 * [ Auth-Application-Id ] 191 * [ Acct-Application-Id ] 192 * [ Vendor-Specific-Application-Id ] 193 [ Firmware-Revision ] 194 * [ AVP ] 196 4.1.2. Capabilities-Update-Answer 198 The Capabilities-Update-Answer indicated by the Command-Code set to 199 and the Command Flags' 'R' bit set, is sent in response to a 200 CUR message. 202 Message Format 204 ::= < Diameter Header: TBD3 > 205 { Origin-Host } 206 { Origin-Realm } 207 { Result-Code } 208 [ Error-Message ] 209 * [ AVP ] 211 5. Security Considerations 213 The security considerations applicable to the Diameter Base Protocol 214 [RFC3588] are also applicable to this document. 216 6. IANA Considerations 218 This section explains the criteria to be used by the IANA for 219 assignment of numbers within namespaces used within this document. 221 6.1. Application Identifier 223 This specification assigns the value from the Application 224 Identifiers namespace defined in RFC 3588. See Section 3 for the 225 assignment of the namespace in this specification. 227 6.2. Command Codes 229 This specification assigns the values and from the 230 Command Codes namespace defined in RFC 3588. See Section 4.1 for the 231 assignment of the namespace in this specification. 233 7. References 235 7.1. Normative References 237 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 238 Requirement Levels", BCP 14, RFC 2119, March 1997. 240 [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. 241 Arkko, "Diameter Base Protocol", RFC 3588, September 2003. 243 7.2. Informative References 245 [RFC4960] Stewart, R., "Stream Control Transmission Protocol", 246 RFC 4960, September 2007. 248 Authors' Addresses 250 Jiao Kang 251 Huawei Technologies 252 Section B1, Huawei Industrial Base 253 Bantian, Longgang District 254 Shenzhen 518129 255 P.R. China 257 Phone: +86 755 2878-6690 258 Email: kangjiao@huawei.com 260 Glen Zorn 261 Network Zen 262 1310 East Thomas Street 263 Seattle, Washington 98102 264 USA 266 Email: gwz@net-zen.net