idnits 2.17.1 draft-kzhang-crane-protocol-05.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3423 5 Title: XACCT's Common Reliable Accounting for Network 6 Element (CRANE) Protocol Specification Version 1.0 7 Author(s): K. Zhang, E. Elkin 8 Status: Informational 9 Date: November 2002 10 Mailbox: kevinzhang@ieee.org, eitan@xacct.com 11 Pages: 45 12 Characters: 97731 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-kzhang-crane-protocol-05.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3423.txt 19 This document defines the Common Reliable Accounting for Network 20 Element (CRANE) protocol that enables efficient and reliable delivery 21 of any data, mainly accounting data from Network Elements to any 22 systems, such as mediation systems and Business Support 23 Systems (BSS)/ Operations Support Systems (OSS). The protocol is 24 developed to address the critical needs for exporting high volume of 25 accounting data from NE's with efficient use of network, storage, and 26 processing resources. 28 This document specifies the architecture of the protocol and the 29 message format, which MUST be supported by all CRANE protocol 30 implementations. 32 This memo provides information for the Internet community. It does 33 not specify an Internet standard of any kind. Distribution of this 34 memo is unlimited. 36 This announcement is sent to the IETF list and the RFC-DIST list. 37 Requests to be added to or deleted from the IETF distribution list 38 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 39 added to or deleted from the RFC-DIST distribution list should 40 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 42 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 43 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 44 help: ways_to_get_rfcs. For example: 46 To: rfc-info@RFC-EDITOR.ORG 47 Subject: getting rfcs 49 help: ways_to_get_rfcs 51 Requests for special distribution should be addressed to either the 52 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 53 specifically noted otherwise on the RFC itself, all RFCs are for 54 unlimited distribution.echo 55 Submissions for Requests for Comments should be sent to 56 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 57 Authors, for further information.