idnits 2.17.1 draft-cornel-megaco-enhancedd-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: ---------------------------------------------------------------------------- ** 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 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 5 longer pages, the longest (page 2) being 62 lines 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 140 has weird spacing: '...d to be reset...' == 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: Informational ---------------------------------------------------------------------------- -- Missing reference section? '1' on line 14 looks like a reference -- Missing reference section? '2' on line 39 looks like a reference -- Missing reference section? '3' on line 153 looks like a reference Summary: 9 errors (**), 0 flaws (~~), 3 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Media Gateway Control Sarah Cornel 3 C. Michael Brown 4 Internet Draft Nortel Networks 5 Document: draft-cornel-megaco-enhancedd-00.txt July 2000 6 Category: Informational 8 Enhanced DTMF Detection Package for Megaco/H.248 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of Section 10 of RFC2026 [1]. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. Internet-Drafts are draft documents valid for a maximum of 19 six months and may be updated, replaced, or obsoleted by other 20 documents at any time. It is inappropriate to use Internet- Drafts 21 as reference material or to cite them other than as "work in 22 progress." 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt 25 The list of Internet-Draft Shadow Directories can be accessed at 26 http://www.ietf.org/shadow.html. 28 1. Abstract 30 This document provides proposed definitions for a supplemental 31 package for Megaco/H.248. This package addresses enhanced support of 32 DTMF detection. 34 2. Conventions used in this document 36 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 37 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 38 this document are to be interpreted as described in RFC-2119 [2]. 40 3. Enhanced DTMF Detection Package Definition 42 3.1 Enhanced DTMF Detection Package 43 PackageID: edd 44 Version: 1 45 Extends: dd version 1 47 This packages extends the mechanisms for detecting and reporting 48 DTMF tones. Additionally, it changes the way the digit maps are 49 interpreted. 51 cornel 1 52 draft-cornel-megaco-enhancedd-00.txt July 2000 54 The package depends on tones described in packages dg and dd (basic 55 DTMF generator package and DTMF detection package). 57 Properties 58 None. 60 Events 61 DigitMap Matched Completion Event 62 EventID: mce 63 EventsDescriptor parameters: 65 Digit map processing is activated only if a digit map parameter is 66 present, specifying a digit map by name or by value. Other 67 parameters such as a KeepActive flag, embedded Events or Signals 68 Descriptors may be present. 70 ObservedEventsDescriptor parameters: 71 DigitString 72 ParameterID: ds (0x0001) 73 Type: string of digit map symbols (possibly empty) returned as 74 a quotedString. 75 Possible values: a sequence of the characters "0" through "9", 76 "A" through "F", and the long duration modifier "Z". 77 Description: the portion of the current dial string as 78 described in the procedures section which matched all of an 79 alternative event sequence specified in the digit map. 80 Termination Method 81 ParameterID: Meth (0x0003) 82 Type: enumeration 83 Possible values: 84 "UM" (0x0001) Unambiguous match 85 "FM" (0x0003) Full match, completion by timer expiry 86 or unmatched event 87 Description: indicates the reason for generation of the event. 88 See the procedures section. 90 Signals 91 None. 93 Statistics 94 None. 96 Procedures 98 Procedures for detecting this event are different than those for the 99 completion event (dd/ce). Procedures for invoking these procedures 100 apply if the matched completion event is requested. It should be 101 noted that the completion event (dd/ce) and the matched completion 102 event (edd/mce) are incompatible. A request for both these events 103 should treat the completion event (dd/ce) as the event with 104 precedence. 106 Cornel Informational - Expires: January 2001 2 107 draft-cornel-megaco-enhancedd-00.txt July 2000 109 The following describes the procedures for the matched digit map 110 completion event.A digit map is active while the events descriptor 111 which invoked it is active and it has not completed. A digit map 112 completes when: 114 an alternative event sequence has been matched and no other 115 alternative event sequence in the digit map could be matched through 116 detection of an additional event (unambiguous match), or 118 an event has been detected (usually another digit or timer expiry) 119 such that a match to a complete alternative event sequence of the 120 digit map will be impossible no matter what additional events are 121 received, and at least one event sequence is matched (full match). 123 Upon completion, a digit map completion event as defined in this 124 package providing the events being mapped into the digit map shall 125 be generated. At that point the digit map is deactivated, however 126 collection of events into the _event buffer_ continues until 127 explicitly stopped. 129 Alternatively, one of the following conditions may be detected: 131 an event has been detected such that a match to a complete 132 alternative event sequence of the digit map will be impossible no 133 matter what additional events are received, and no event sequence is 134 matched, or 136 a timer has expired and no sequence is matched. 138 If these conditions occur, the contents of the current dial string 139 should have the first event in its buffer flushed, and the current 140 digit map should be reapplied. These are considered to be reset 141 conditions for the digit map. This process continues until either 142 there is a match, or the request is terminated. 144 Additionally, unless noted here, the processing of the current dial 145 string and the digit map proceeds like the processing of a 146 completion event (dd/ce) . 148 4. Formal Syntax 150 Not Applicable 152 The following syntax specification uses the augmented Backus-Naur 153 Form (BNF) as described in RFC-2234 [3]. 155 5. Security Considerations 157 Not Applicable 159 6. References 161 Cornel Informational - Expires: January 2001 3 162 draft-cornel-megaco-enhancedd-00.txt July 2000 164 1 Bradner, S., "The Internet Standards Process -- Revision 3", BCP 165 9, RFC 2026, October 1996. 167 2 Bradner, S., "Key words for use in RFCs to Indicate Requirement 168 Levels", BCP 14, RFC 2119, March 1997 170 3 Crocker, D. and Overell, P.(Editors), "Augmented BNF for Syntax 171 Specifications: ABNF", RFC 2234, Internet Mail Consortium and 172 Demon Internet Ltd., November 1997 174 7. Acknowledgments 176 8. Author's Addresses 178 Sarah Cornel 179 Nortel Networks 180 4008 Chapel Hill Road 181 Research Triangle Park, NC USA 27709 182 Phone: (919) 991-2853 183 Email: sarahc@nortelnetworks.com 185 C. Michael Brown 186 Nortel Networks 187 4008 Chapel Hill Road 188 Research Triangle Park, NC USA 27709 189 Phone: (919) 991-7767 190 Email: C.Michael.Brown@nortelnetworks.com 192 9. Full Copyright Statement 194 "Copyright (C) The Internet Society (date). All Rights Reserved. 195 This document and translations of it may be copied and furnished to 196 others, and derivative works that comment on or otherwise explain it 197 or assist in its implementation may be prepared, copied, published 198 and distributed, in whole or in part, without restriction of any 199 kind, provided that the above copyright notice and this paragraph 200 are included on all such copies and derivative works. However, this 201 document itself may not be modified in any way, such as by removing 202 the copyright notice or references to the Internet Society or other 203 Internet organizations, except as needed for the purpose of 204 developing Internet standards in which case the procedures for 205 copyrights defined in the Internet Standards process must be 206 followed, or as required to translate it into languages other than 207 English. The limited permissions granted above are perpetual and 208 will not be revoked by the Internet Society or its successors or 209 assigns. This document and the information contained herein is 210 provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE 211 INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 212 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 214 Cornel Informational - Expires: January 2001 4 215 draft-cornel-megaco-enhancedd-00.txt July 2000 217 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 218 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." 220 10. Expiration Date 222 This memo is filed as draft-cornel-megaco-enhancedd-00.txt, and 223 expires January 2001. 225 Cornel Informational - Expires: January 2001 5