idnits 2.17.1 draft-ietf-megaco-h248k-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: ---------------------------------------------------------------------------- == 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 8686 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 172 looks like a reference Summary: 8 errors (**), 0 flaws (~~), 1 warning (==), 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-h248k-00.txt Zacharias Bilalis 4 Category: Standards Track Siemens 5 July 2000 7 H.248 Annex K (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 K, which is scheduled for 31 decision in Geneva in November 2000. H.248 Annex K provides the 32 Generic Announcement 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. Generic Announcement PACKAGE 46 PackageID: an, 0x001d 47 Version: 1 48 Extends: None 50 Bilalis, Rengasami Standards Track - Expires January 2001 1 51 That package supports announcement functionality at a Media Gateway 53 3.1 Properties 55 None 57 3.2 Events 59 3.2.1 Announcement completed 61 EventID: ac (0x0001) 63 Description: Indicates the completion of the announcement. 65 EventDescriptor parameters: 67 None 69 ObservedEventDescriptor parameters: 71 None 73 3.2.2 Announcement failure 75 EventID: af (0x0002) 77 Description: Indicates the failure of the announcement. 79 EventDescriptor parameters 81 None 83 ObservedEventDescriptor parameters 85 None 87 3.3 Signals 89 3.3.1 Fixed - Announcement play 91 SignalID: apf (0x0003) 93 Description: Initiates the play of a fixed announcement 95 Parameters: 97 Announcement name 98 ParameterID: an (0x0001) 99 Type: enumeration of announcements. 100 Default is TO 102 Bilalis, Rengasami Standards Track - Expires January 2000 2 103 Number of cycles 104 ParameterID: noc (0x0002) 105 Type: integer. 106 Values: any 107 Default: 1 109 3.3.2 Variable - Announcement play 111 SignalID: apv (0x0004) 113 Description: Initiates the play of a variable announcement 115 Parameters: 117 Announcement name 118 ParameterID: an (0x0001) 119 Type: enumeration of announcements. 120 Default is TO 122 Number of cycles 123 ParameterID: noc (0x0002) 124 Type: integer. 125 Values: any 126 Default: 1 128 Number 129 ParameterID: num (0x0003) 130 Type: integer 131 Values: any 133 Specific parameters interpretation 134 ParameterID: spi (0x0004) 135 Type: enumeration 136 Values: any 138 Specific parameters 139 ParameterID: sp (0x0005) 140 Type: string 141 Values: any 142 Default is provisioned for every anouncement. 144 3.3.3 Statistics 146 None 148 3.3.4 Procedures 150 An MGC may send a fixed play announcements message to the MG. An MG 151 receiving such a signal plays the indicated announcement (indicated 153 Bilalis, Rengasami Standards Track - Expires January 2000 3 154 by the name parameter) for the duration specified by the noc 155 parameter. If an noc parameter is not included, the MG uses a 156 default of 1 cycle. 158 To provide additional information when an announcement is to be 159 played, the MGC sends a play variable announcement signal to the MG. 160 An MG receiving such a signal plays the indicated announcement 161 (indicated by the name parameter) for the duration specified by the 162 noc parameter. If an noc parameter is not included, the MG uses a 163 default of 1. If the sp parameter is included, the MG uses the 164 Specific parameters interpretation parameter to identify the 165 particular type of information to be included in the announcement. 166 Examples of the types of Specific parameters include a telephone 167 number, date, or time. 169 4. Security Considerations 171 Security considerations regarding media gateway control are 172 discussed in section 10 of [3]. 174 5. References 176 1 Bradner, S., "The Internet Standards Process -- Revision 3", BCP 177 9, RFC 2026, October 1996. 179 2 Bradner, S., "Key words for use in RFCs to Indicate Requirement 180 Levels", BCP 14, RFC 2119, March 1997. 182 3 ITU-T Recommendation H.248, "Gateway Control Protocol", Geneva, 183 June 2000. Also to appear as RFC xxxx (currently draft-ietf- 184 megaco-merged-01.txt). 186 6. Authors' Addresses 188 Selvam Rengasami (editor) 189 Telcordia Technologies 190 Phone: + 1 732 758 5260 191 Email: srengasa@telcordia.com 193 Zacharias Bilalis (editor) 194 Siemens 195 Phone: + 49 89 722 28391 196 Email: zacharias.bilalis@icn.siemens.de 198 Bilalis, Rengasami Standards Track - Expires January 2000 4