Individual Contribution Pat R. Calhoun Internet-Draft Dave Frascone Category: Informational Sun Microsystems, Inc. March 2001 Diameter Sun Ping Extensions Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. 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 document is an individual contribution for consideration by the AAA Working Group of the Internet Engineering Task Force. Comments should be submitted to the diameter@diameter.org mailing list. Distribution of this memo is unlimited. Copyright (C) The Internet Society 2001. All Rights Reserved. Calhoun expires August 2001 [Page 1] Internet-Draft March 2001 Abstract This document describes the Sun vendor-specific Diameter Ping extension. The Diameter Ping is a very useful troubleshooting tool, allowing a Diameter node to determine whether reachability to a domain is possible. Table of Contents 1.0 Introduction 1.1 Specification of Requirements 2.0 Command-Code Values 2.1 Sun-Ping-Request (SDP) 2.1 Sun-Ping-Answer (SDA) 3.0 IANA Considerations 4.0 Security Considerations 5.0 References 6.0 Authors' Addresses 7.0 Full Copyright Statement 1.0 Introduction This document describes the Sun vendor-specific Diameter Ping extension. The Diameter Ping is a very useful troubleshooting tool, allowing a Diameter node to determine whether reachability to a domain is possible. The Extension number for this draft is 555. Diameter nodes conforming to this specification MUST include an Extension-Id AVP with a value of 555 in the Device-Reboot-Ind Command [1]. 1.1 Specification of Requirements In this document, the key words "MAY", "MUST", "MUST NOT", "optional", "recommended", "SHOULD", and "SHOULD NOT", are to be interpreted as described in [2]. 2.0 Command-Code Values This section defines Command-Code [1] values that MUST be supported by all Diameter implementations conforming to this specification. The following Command Codes are defined in this specification: Calhoun expires August 2001 [Page 2] Internet-Draft March 2001 Command-Name Abbrev. Code Reference -------------------------------------------------------- Sun-Ping-Request SDP 511/42 2.1 Sun-Ping-Answer SDA 512/42 2.2 2.1 Sun-Ping-Request (SDP) The Sun-Ping-Request (SDP), indicated by the Command-Code field set to 511, and Vendor Id set to 32, MAY be sent by a Diameter client to any Diameter server to request reachability to a particular domain. The routing procedures described in [1] will ensure that the request is sent to a Diameter server in the requested domain. Message Format ::= < Diameter Header: 511, vid: 42 > { Origin-FQDN } { Origin-Realm } { Destination-Realm } { Session-Id } { User-Name } [ Destination-FQDN ] * [ Proxy-State ] * [ Route-Record ] * [ Routing-Realm ] 0*1< Integrity-Check-Value > 2.2 Sun-Ping-Answer (SPA) The Sun-Ping-Answer (SPA), indicated by the Command-Code field set to 512, and Vendor Id set to 32, is sent as a response to the Sun-Ping- Request message. Message Format Calhoun expires August 2001 [Page 3] Internet-Draft March 2001 ::= < Diameter Header: 512 vid: 42 > { Origin-FQDN } { Origin-Realm } { Destination-Realm } { Result-Code } { Session-Id } { User-Name } [ Destination-FQDN ] * [ AVP ] * [ Proxy-State ] * [ Route-Record ] * [ Routing-Realm ] 0*1< Integrity-Check-Value > 3.0 IANA Considerations The command codes defined in Section 2.0 are vendor-specific Commands, which is privately managed, and does not falls within the the Command-Code address space defined in [1]. 4.0 Security Considerations This Diameter extension assumes that messages are secured either through a hop-by-hop authentication mechanism, as described in [1], or using a strong authentication mechanism as defined in [3]. 5.0 References [1] P. Calhoun, A. Rubens, H. Akhtar, E. Guttman, "Diameter Base Protocol", draft-calhoun-diameter-18.txt (work in progress), February 2001. [2] S. Bradner, "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [3] P. Calhoun, W. Bulley, S. Farrell, "Diameter Strong Security Extension", draft-calhoun-diameter-strong-crypto-06.txt (work in progress), February 2001. 6.0 Authors' Addresses Questions about this memo can be directed to: Calhoun expires August 2001 [Page 4] Internet-Draft March 2001 Pat R. Calhoun Network and Security Research Center, Sun Labs Sun Microsystems, Inc. 15 Network Circle Menlo Park, California, 94025 USA Phone: +1 650-786-7733 Fax: +1 650-786-6445 E-mail: pcalhoun@eng.sun.com David Frascone Sun Labs California 1600 North Dallas Parkway, Suite 700 Dallas, TX 75248 Phone: +1 972 386 1283 E-Mail: codemonkey@sun.com 7.0 Full Copyright Statement Copyright (C) The Internet Society (2001). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this docu- ment itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of develop- ing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The lim- ited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DIS- CLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 8.0 Expiration Date Calhoun expires August 2001 [Page 5] Internet-Draft March 2001 This memo is filed as and expires in August 2001. Calhoun expires August 2001 [Page 6]