draft-ietf-dime-capablities-update-00.txt   draft-ietf-dime-capablities-update-01.txt 
Network Working Group G. Zorn Network Working Group K. Jiao
Internet-Draft Network Zen Internet-Draft Huawei
Intended status: Standards Track K. Jiao Intended status: Standards Track G. Zorn
Expires: January 28, 2010 Huawei Technologies Expires: June 4, 2010 Network Zen
July 27, 2009 December 1, 2009
The Diameter Capabilities Update Application The Diameter Capabilities Update Application
draft-ietf-dime-capablities-update-00.txt draft-ietf-dime-capablities-update-01
Abstract
This document defines a new Diameter application and associated
command codes. The Capabilities Update application is intended to
allow the dynamic update of Diameter peer capabilities while the
peer-to-peer connection is in the open state.
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79.
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 Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 28, 2010. This Internet-Draft will expire on June 4, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents
publication of this document (http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
Abstract include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
This document defines a new Diameter application and associated described in the BSD License.
command codes. The Capabilities Update application is intended to
allow the dynamic update of Diameter peer capabilities while the
peer-to-peer connection is in the open state.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Specification of Requirements . . . . . . . . . . . . . . . . . 3 2. Specification of Requirements . . . . . . . . . . . . . . . . . 3
3. Diameter Protocol Considerations . . . . . . . . . . . . . . . 3 3. Diameter Protocol Considerations . . . . . . . . . . . . . . . 3
4. Capabilities Update . . . . . . . . . . . . . . . . . . . . . . 3 4. Capabilities Update . . . . . . . . . . . . . . . . . . . . . . 3
4.1. Command-Code Values . . . . . . . . . . . . . . . . . . . . 4 4.1. Command-Code Values . . . . . . . . . . . . . . . . . . . . 4
4.1.1. Capabilities-Update-Request . . . . . . . . . . . . . . 5 4.1.1. Capabilities-Update-Request . . . . . . . . . . . . . . 5
4.1.2. Capabilities-Update-Answer . . . . . . . . . . . . . . 5 4.1.2. Capabilities-Update-Answer . . . . . . . . . . . . . . 5
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
5.1. Application Identifier . . . . . . . . . . . . . . . . . . 6 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
5.2. Command Codes . . . . . . . . . . . . . . . . . . . . . . . 6 6.1. Application Identifier . . . . . . . . . . . . . . . . . . 6
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 6.2. Command Codes . . . . . . . . . . . . . . . . . . . . . . . 6
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. Normative References . . . . . . . . . . . . . . . . . . . 6 7.1. Normative References . . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . . 6 7.2. Informative References . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
Capabilities exchange is an important component of the Diameter Base Capabilities exchange is an important component of the Diameter Base
Protocol [RFC3588], allowing peers to exchange identities and Protocol [RFC3588], allowing peers to exchange identities and
Diameter capabilities (protocol version number, supported Diameter Diameter capabilities (protocol version number, supported Diameter
skipping to change at page 3, line 26 skipping to change at page 3, line 26
the modified capabilities can be advertised. the modified capabilities can be advertised.
This document defines a new Diameter application intended to allow This document defines a new Diameter application intended to allow
the dynamic update of Diameter peer capabilities over an existing the dynamic update of Diameter peer capabilities over an existing
connection. Because the Capabilities Update application specified connection. Because the Capabilities Update application specified
here operates over an existing transport connection, modification of here operates over an existing transport connection, modification of
the security mechanism in use is not allowed; if the security method the security mechanism in use is not allowed; if the security method
used between a pair of peers is changed the affected connection MUST used between a pair of peers is changed the affected connection MUST
be restarted. be restarted.
Discussion of this draft may be directed to the authors. Discussion of this draft may be directed to the dime Working Group of
the IETF (dime@ietf.org).
2. Specification of Requirements 2. Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
3. Diameter Protocol Considerations 3. Diameter Protocol Considerations
This section details the relationship of the Diameter Capabilities This section details the relationship of the Diameter Capabilities
Update application to the Diameter Base Protocol. Update application to the Diameter Base Protocol.
This document specifies Diameter Application-ID <TBD1>. Diameter This document specifies Diameter Application-ID <TBD1>. Diameter
nodes conforming to this specification MAY advertise support by nodes conforming to this specification MUST advertise support by
including the value of <TBD1> in the Auth-Application-Id of the including the value <TBD1> in the Auth-Application-Id of the
Capabilities-Exchange-Req and Capabilities-Exchange-Answer commands Capabilities-Exchange-Req and Capabilities-Exchange-Answer commands
[RFC3588]. [RFC3588].
4. Capabilities Update 4. Capabilities Update
When the capabilities of a Diameter node conforming to this When the capabilities of a Diameter node conforming to this
specification change, it SHOULD notify all of the nodes with which it specification change, it SHOULD notify all of the nodes with which it
has an open transport connection using the Capabilities-Update-Req has an open transport connection and have also advertised support for
message (Section 4.1.1). This message allows the update of a peer's the Capabilities Update application using the Capabilities-Update-
identity and its capabilities (protocol version number, supported Request message Section 4.1.1. This message allows the update of a
Diameter applications, etc.). peer's capabilities (protocol version number, supported Diameter
applications, etc.).
The receiver only issues commands to its peers that have advertised The receiver only issues commands to its peers that have advertised
support for the Diameter application that defines the command. A support for the Diameter application that defines the command. A
Diameter node MUST cache the supported applications in order to Diameter node MUST cache the supported applications in order to
ensure that unrecognized commands and/or AVPs are not unnecessarily ensure that unrecognized commands and/or AVPs are not unnecessarily
sent to a peer. sent to a peer.
The receiver of the Capabilities-Update-Request (CUR) MUST determine The receiver of the CUR MUST determine common applications by
common applications by computing the intersection of its own set of computing the intersection of its own set of supported Application Id
supported Application Id against all of the application identifier against all of the application identifier AVPs (Auth-Application-Id,
AVPs (Auth-Application-Id, Acct-Application-Id and Vendor-Specific- Acct-Application-Id and Vendor-Specific- Application-Id) present in
Application-Id) present in the CUR. The value of the Vendor-Id AVP the CUR. The value of the Vendor-Id AVP in the Vendor-Specific-
in the Vendor-Specific-Application-Id MUST NOT be used during Application-Id MUST NOT be used during computation.
computation.
If the receiver of a Capabilities-Update-Req (CUR) message does not 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 have any applications in common with the sender then it MUST return a
Capabilities-Update-Answer (CUA) with the Result-Code AVP set to Capabilities-Update-Answer (CUA) Section 4.1.2 with the Result-Code
DIAMETER_NO_COMMON_APPLICATION, and SHOULD disconnect the transport AVP set to DIAMETER_NO_COMMON_APPLICATION, and SHOULD disconnect the
layer connection; however, if active sessions are using the transport layer connection; however, if active sessions are using the
connection, peers MAY delay disconnection until the sessions can be connection, peers MAY delay disconnection until the sessions can be
redirected or gracefully terminated. Note that receiving a CUR or redirected or gracefully terminated. Note that receiving a CUA from
CUA from a peer advertising itself as a Relay (see [RFC3588], Section a peer advertising itself as a Relay (see [RFC3588], Section 2.4)
2.4) MUST be interpreted as having common applications with the peer. MUST be interpreted as having common applications with the peer.
The CUR and CUA messages MUST NOT be proxied, redirected or relayed. The CUR and CUA messages MUST NOT be proxied, redirected or relayed.
Since the CUR/CUA messages cannot be proxied, it is still possible Even though the CUR/CUA messages cannot be proxied, it is still
that an upstream agent receives a message for which it has no possible for an upstream agent to receive a message for which there
available peers to handle the application that corresponds to the are no peers available to handle the application that corresponds to
Command-Code. In such instances, the 'E' bit is set in the answer the Command-Code. This could happen if, for example, the peers are
message with the Result-Code AVP set to DIAMETER_UNABLE_TO_DELIVER to too busy or down. In such instances, the 'E' bit MUST be set in the
inform the downstream peer to take action (e.g., re-routing requests answer message with the Result-Code AVP set to
to an alternate peer). DIAMETER_UNABLE_TO_DELIVER to inform the downstream peer to take
action (e.g., re-routing requests to an alternate peer).
4.1. Command-Code Values 4.1. Command-Code Values
This section defines Command-Code [RFC3588] values that MUST be This section defines Command-Code [RFC3588] values that MUST be
supported by all Diameter implementations conforming to this supported by all Diameter implementations conforming to this
specification. The following Command Codes are defined in this specification. The following Command Codes are defined in this
document: Capabilities-Update-Request (CUR)Section 4.1.1 and document: Capabilities-Update-Request (CUR, Section 4.1.1) and
Capabilities-Update-Answer (CUA) Section 4.1.2. Capabilities-Update-Answer (CUA, Section 4.1.2).
4.1.1. Capabilities-Update-Request 4.1.1. Capabilities-Update-Request
The Capabilities-Update-Request (CUR), indicated by the Command-Code The Capabilities-Update-Request (CUR), indicated by the Command-Code
set to <TBD2> and the Command Flags' 'R' bit set, is sent to update set to <TBD2> and the Command Flags' 'R' bit set, is sent to update
local capabilities. Upon detection of a transport failure, this local capabilities. Upon detection of a transport failure, this
message MUST NOT be sent to an alternate peer. message MUST NOT be sent to an alternate peer.
When Diameter is run over SCTP [RFC2960], which allows connections to When Diameter is run over SCTP [RFC4960], which allows connections to
span multiple interfaces and multiple IP addresses, the Capabilities- span multiple interfaces and multiple IP addresses, the Capabilities-
Update-Request message MUST contain one Host-IP-Address AVP for each Update-Request message MUST contain one Host-IP-Address AVP for each
potential IP address that may be locally used when transmitting potential IP address that may be locally used when transmitting
Diameter messages. Diameter messages.
Message Format Message Format
<CUR> ::= < Diameter Header: TBD2, REQ > <CUR> ::= < Diameter Header: TBD2, REQ >
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
1* { Host-IP-Address } 1* { Host-IP-Address }
{ Vendor-Id } { Vendor-Id }
{ Product-Name } { Product-Name }
[ Origin-State-Id ] [ Origin-State-Id ]
* [ Supported-Vendor-Id ] * [ Supported-Vendor-Id ]
* [ Auth-Application-Id ] * [ Auth-Application-Id ]
* [ Acct-Application-Id ] * [ Acct-Application-Id ]
* [ Vendor-Specific-Application-Id ] * [ Vendor-Specific-Application-Id ]
[ Firmware-Revision ] [ Firmware-Revision ]
* [ AVP ] * [ AVP ]
4.1.2. Capabilities-Update-Answer 4.1.2. Capabilities-Update-Answer
The Capabilities-Update-Answer indicated by the Command-Code set to The Capabilities-Update-Answer indicated by the Command-Code set to
<TBD3> and the Command Flags' 'R' bit set, is sent in response to a <TBD3> and the Command Flags' 'R' bit set, is sent in response to a
CUR message. CUR message.
Message Format Message Format
<CUA> ::= < Diameter Header: TBD3 > <CUA> ::= < Diameter Header: TBD3 >
{ Origin-Host } { Origin-Host }
{ Origin-Realm } { Origin-Realm }
{ Result-Code } { Result-Code }
[ Error-Message ] [ Error-Message ]
* [ AVP ] * [ AVP ]
5. IANA Considerations 5. Security Considerations
The security considerations applicable to the Diameter Base Protocol
[RFC3588] are also applicable to this document.
6. IANA Considerations
This section explains the criteria to be used by the IANA for This section explains the criteria to be used by the IANA for
assignment of numbers within namespaces used within this document. assignment of numbers within namespaces used within this document.
5.1. Application Identifier 6.1. Application Identifier
This specification assigns the value <TBD1> from the Application This specification assigns the value <TBD1> from the Application
Identifiers namespace defined in RFC 3588. See section Section 3 for Identifiers namespace defined in RFC 3588. See Section 3 for the
the assignment of the namespace in this specification. assignment of the namespace in this specification.
5.2. Command Codes 6.2. Command Codes
This specification assigns the values <TBD2> and <TBD3> from the This specification assigns the values <TBD2> and <TBD3> from the
Command Codes namespace defined in RFC 3588. See section Section 4.1 Command Codes namespace defined in RFC 3588. See Section 4.1 for the
for the assignment of the namespace in this specification. assignment of the namespace in this specification.
6. Security Considerations
This document does not introduce any new vulnerabilities into the
Diameter protocol.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
Arkko, "Diameter Base Protocol", RFC 3588, September 2003. Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
7.2. Informative References 7.2. Informative References
[RFC2960] Stewart, R., Xie, Q., Morneault, K., Sharp, C., [RFC4960] Stewart, R., "Stream Control Transmission Protocol",
Schwarzbauer, H., Taylor, T., Rytina, I., Kalla, M., RFC 4960, September 2007.
Zhang, L., and V. Paxson, "Stream Control Transmission
Protocol", RFC 2960, October 2000.
Authors' Addresses Authors' Addresses
Glen Zorn
Network Zen
1310 East Thomas Street
#306
Seattle, Washington 98102
USA
Phone: +1 (206) 377-9035
Email: gwz@net-zen.net
Jiao Kang Jiao Kang
Huawei Technologies Huawei Technologies
Section B1, Huawei Industrial Base Section B1, Huawei Industrial Base
Bantian, Longgang District Bantian, Longgang District
Shenzhen 518129 Shenzhen 518129
P.R. China P.R. China
Phone: +86 755 28786690 Phone: +86 755 2878-6690
Email: kangjiao@huawei.com Email: kangjiao@huawei.com
Glen Zorn
Network Zen
1310 East Thomas Street
Seattle, Washington 98102
USA
Email: gwz@net-zen.net
 End of changes. 29 change blocks. 
112 lines changed or deleted 96 lines changed or added

This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/