idnits 2.17.1 draft-greene-diameter-devconf-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-18) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://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 Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == The page length should not exceed 58 lines per page, but there was 10 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 11 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 67: '... MUST This word, or the adjecti...' RFC 2119 keyword, line 71: '... MUST NOT This phrase means that th...' RFC 2119 keyword, line 74: '... SHOULD This word, or the adjecti...' RFC 2119 keyword, line 80: '... MAY This word, or the adjecti...' RFC 2119 keyword, line 82: '...hich does not include this option MUST...' (32 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '1' is defined on line 434, but no explicit reference was found in the text == Unused Reference: '2' is defined on line 436, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 438, but no explicit reference was found in the text == Outdated reference: A later version (-18) exists of draft-calhoun-diameter-05 -- Possible downref: Normative reference to a draft: ref. '1' ** Obsolete normative reference: RFC 1700 (ref. '2') (Obsoleted by RFC 3232) == Outdated reference: A later version (-09) exists of draft-calhoun-diameter-framework-00 -- Possible downref: Normative reference to a draft: ref. '3' Summary: 11 errors (**), 0 flaws (~~), 7 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET DRAFT Nancy Greene 3 Category: Standards Track Nortel 4 Title: draft-greene-diameter-devconf-00.txt Pat R. Calhoun 5 Date: August 1998 Sun Microsystems, Inc. 7 DIAMETER 8 Device Configuration Extensions 9 11 Status of this Memo 13 This document is an Internet-Draft. Internet-Drafts are working 14 documents of the Internet Engineering Task Force (IETF), its areas, 15 and its working groups. Note that other groups may also distribute 16 working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet-Drafts as reference 21 material or to cite them other than as ``work in progress.'' 23 To learn the current status of any Internet-Draft, please check the 24 ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow 25 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 26 munnari.oz.au (Pacific Rim), ftp.ietf.org (US East Coast), or 27 ftp.isi.edu (US West Coast). 29 Abstract 31 This DIAMETER Extension defines commands and AVPs that are used by 32 two peers to exchange DIAMETER configuration information. The intent 33 of this draft is to minimize configuration of devices prior to 34 deployment. 36 Table of Contents 38 1.0 Introduction 39 1.1 Definitions 40 1.2 Terminology 41 2.0 Command Codes 42 2.1 Device-Config-Request (DCR) 43 2.2 Device-Config-Answer (DCA) 44 3.0 DIAMETER AVPs 45 3.1 Message-Timer 46 3.2 Message-In-Progress-Timer 47 3.3 Message-Retry-Count 48 3.4 Maximum-Forward-Count 49 4.0 Protocol Definition 50 4.1 Device Configuration 51 5.0 References 52 6.0 Acknowledgements 53 7.0 Author's Address 55 1.0 Introduction 57 This DIAMETER Extension defines commands and AVPs that are used by 58 two peers to exchange DIAMETER configuration information. The intent 59 of this draft is to minimize configuration of devices prior to 60 deployment. 62 1.1 Definitions 64 In this document, several words are used to signify the requirements 65 of the specification. These words are often capitalized. 67 MUST This word, or the adjective "required", means that the 68 definition is an absolute requirement of the 69 specification. 71 MUST NOT This phrase means that the definition is an absolute 72 prohibition of the specification. 74 SHOULD This word, or the adjective "recommended", means that 75 there may exist valid reasons in particular circumstances 76 to ignore this item, but the full implications must be 77 understood and carefully weighed before choosing a 78 different course. 80 MAY This word, or the adjective "optional", means that this 81 item is one of an allowed set of alternatives. An 82 implementation which does not include this option MUST 83 be prepared to interoperate with another implementation 84 which does include the option. 86 2.0 Command Codes 88 This document defines the following DIAMETER Commands. All DIAMETER 89 implementations supporting this extension MUST support all of the 90 following commands: 92 Command Name Command Code 93 ----------------------------------- 94 Device-Config-Request 304 95 Device-Config-Answer 305 97 2.1 Device-Config-Request (DCR) 99 Description 101 The Device-Config-Request message is sent by a DIAMETER device to 102 provide configuration information to peers under administrative 103 control of the sender. Peers receiving this information SHOULD use 104 it when communicating with the originator of this message. The 105 peer MUST respond to the message with a Device-Config-Answer. 107 This message MAY contain vendor specific AVPs which MAY be ignored 108 by the receiver. 110 Message Format 112 ::= 113 114 115 [] 116 [] 117 [] 118 [] 119 [] 120 [] 121 [] 122 [] 123 124 125 { || 126 ::= 178 179 180 181 [] 182 [] 183 [] 184 [] 185 [] 186 [] 187 [] 188 [] 189 [] 190 191 192 { || 193