idnits 2.17.1 draft-ietf-megaco-h248j-00.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** 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. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction 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. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 169 has weird spacing: '...defined by th...' == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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.) -- The document date (July 2000) is 8687 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) -- Missing reference section? '1' on line 13 looks like a reference -- Missing reference section? '2' on line 43 looks like a reference -- Missing reference section? '3' on line 180 looks like a reference Summary: 8 errors (**), 0 flaws (~~), 2 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Media Gateway Control (Megaco) Selvam Rengasami 2 Internet Draft Telcordia Technologies 3 Document: draft-ietf-megaco-h248j-00.txt Zacharias Bilalis 4 Category: Standards Track Siemens 5 July 2000 7 H.248 Annex J (Pre-Decision White Document) 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance with 12 all provisions of Section 10 of RFC2026 [1]. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that 16 other groups may also distribute working documents as Internet- 17 Drafts. Internet-Drafts are draft documents valid for a maximum of 18 six months and may be updated, replaced, or obsoleted by other 19 documents at any time. It is inappropriate to use Internet- Drafts 20 as reference material or to cite them other than as "work in 21 progress." 22 The list of current Internet-Drafts can be accessed at 23 http://www.ietf.org/ietf/1id-abstracts.txt 24 The list of Internet-Draft Shadow Directories can be accessed at 25 http://www.ietf.org/shadow.html. 27 1. Abstract 29 This document reproduces the content of the ITU-T Study Group 16 30 White Document draft of H.248 Annex J, which is scheduled for 31 decision in Geneva in November 2000. H.248 Annex J provides the 32 Dynamic Tone Generation package. 34 This document is submitted for IETF comment prior to ITU-T decision, 35 in accordance with procedures currently being negotiated between 36 ITU-T Study Group and ISOC on behalf of the IETF. 38 2. Conventions used in this document 40 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 41 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 42 this document are to be interpreted as described in RFC-2119 [2]. 44 3. Dynamic Tone definition package 46 PackageID: dtd, 0x001c 47 Version: 1 48 Extends: None 50 Bilalis, Rengasami Standards Track - Expires January 2001 1 51 This package defines a mechanism to redefine existing tones and 52 create new tones for playback. The existing tones are the ones 53 described in supported packages that extend the tonegen generic 54 package. 56 3.1 Properties 58 Tone ID 59 PropertyID: tid (0x0001) 60 Description: Indicates the new or existing tone to be modified 61 or who's tone string is to be read. 62 Type: expanding enumeration 63 Possible Values: existing package_id, tone id described in 64 supported packages that extend tonegen or new tones to be 65 added. 66 Defined in: TerminationState. 68 If the termination is in a context, the changes to the tones 69 apply only to the termination in the context. When the 70 termination leaves the context, the changes are lost. If the 71 termination is in the null context, the changes apply to the 72 termination from then on. If the termination is root, the 73 changes apply to the whole gateway. 75 Characteristics: both read and write. 77 Tone String 78 PropertyID: tst (0x0002) 79 Description: Tone description string. See procedures 80 Type: String 81 Possible Values: See procedures. 82 Defined in: TerminationState. 83 Characteristics: both read and write: 85 3.2 Events 87 None 89 3.3 Signals 91 None 93 3.4 Statistics 95 None 97 Bilalis, Rengasami Standards Track - Expires January 2000 2 98 3.5 Procedures 100 3.5.1 Updating Tone Definition 102 To modify or create a new tone: 103 1- set tid to an existing or new package_id,tone id value 104 2- set tst to the new tone description 105 if tst is null the id is decommissioned and removed. Only newly 106 defined tonids can be removed. 108 3.5.2 Reading existing tones 110 To read the list of tones defined: 111 1- read tid 113 To read an already defined tone string: 114 1- set tid 115 2- read tst 116 Some package-defined tones may not have a tone string in the 117 gateway. In that case the tst read will have the value "Not 118 Available" 120 3.5.3 Tone String (tst) description 122 The syntax for the tone definition string is recursive and uses 123 parenthesis as a delimiter of elements. DefToneString below is the 124 tone string(tst) 126 DefToneString = "(" DefToneElement ["*" RepeatCount ] ")" 127 [","/"+"/"X" DefToneString] 129 NOTE: a separator of ',' indicates that the next definition 130 follows sequentially in time; a separator of '+' indicates 131 that the following tone is to be mixed with the previous tone 132 and is simultaneous with it; a separator of 'X' indicates that 133 the first tone is modulated by the second tone. 135 NOTE: All implementations must support sequential definitions 136 (',' separator). Mixing ('+') and modulation ('X') support are 137 optional, however the implementation must make a best effort 138 and return no error in these cases. 140 NOTE: Recursion is limited to a maximum of 32 Levels. All 141 implementations must support at least 2 levels of recursion. 143 RepeatCount = %d1-32767 / %d0 144 NOTE: repeatcount of 0 indicates infinite repeating. 146 DefToneElement = ToneName ["," ToneDuration [ "," ToneAmplitude ]] 148 ToneName = (Package id, Tone id) / "#"FreqValue / 149 "&"AnnouncementParameterList 151 Bilalis, Rengasami Standards Track - Expires January 2000 3 152 Package id = 1*VCHAR; Unique package identity string or value 154 Tone id = 1*VCHAR; Unique tone identity string or value 156 FreqValue = %d0-4000; in Hertz 158 AnnouncementParameterList = AnnouncementID ["," SubstitutionString] 160 AnnouncementID = 1*VCHAR; Unique identifier for an audio 161 announcement 163 SubstitutionString = """1*VCHAR"""; a string to be inserted into an 164 announcement. 166 ToneDuration = %d1-32767 / %d0 ; In Milliseconds 168 NOTE: ToneDuration of 0 indicates infinite duration or duration 169 defined by the Tone id. 171 ToneAmplitude = "-"%d32-1 / %d0; In dBm0 173 An example of tone definition follows. 175 RingingTone = ((0x0005,0x0031),((#480)+(#620)),250,-24)*0 177 5. Security Considerations 179 Security considerations regarding media gateway control are 180 discussed in section 10 of [3]. 182 6. References 184 1 Bradner, S., "The Internet Standards Process -- Revision 3", BCP 185 9, RFC 2026, October 1996. 187 2 Bradner, S., "Key words for use in RFCs to Indicate Requirement 188 Levels", BCP 14, RFC 2119, March 1997. 190 3 ITU-T Recommendation H.248, "Gateway Control Protocol", Geneva, 191 June 2000. Also to appear as RFC xxxx (currently draft-ietf- 192 megaco-merged-01.txt). 194 7. Acknowledgments 196 This document reflects the work of the TIA (Telecommunications 197 Industry Association) TR-41.3.4 subcommittee under the leadership of 198 Phil Holland. 200 Bilalis, Rengasami Standards Track - Expires January 2000 4 201 8. Authors' Addresses 203 Selvam Rengasami (editor) 204 Telcordia Technologies 205 Phone: + 1 732 758 5260 206 Email: srengasa@telcordia.com 208 Zacharias Bilalis (editor) 209 Siemens 210 Phone: + 49 89 722 28391 211 Email: zacharias.bilalis@icn.siemens.de 213 Bilalis, Rengasami Standards Track - Expires January 2000 5