idnits 2.17.00 (12 Aug 2021) /tmp/idnits53304/draft-rosen-megaco-atm-package-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. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. ** 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.) ** There are 34 instances of too long lines in the document, the longest one being 13 characters in excess of 72. 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 (February 2001) is 7758 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Missing reference section? '1' on line 12 looks like a reference -- Missing reference section? '2' on line 33 looks like a reference -- Missing reference section? '0x00' on line 70 looks like a reference -- Missing reference section? '0x01' on line 92 looks like a reference -- Missing reference section? '0x02' on line 93 looks like a reference -- Missing reference section? '0x03' on line 94 looks like a reference -- Missing reference section? '0x04' on line 95 looks like a reference Summary: 7 errors (**), 0 flaws (~~), 1 warning (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Megaco B. Rosen 2 Internet Draft Marconi 3 Document: draft-rosen-megaco-atm-package-00.txt February 2001 4 Category: Informational 6 Megaco ATM Package 8 Status of this Memo 10 This document is an Internet-Draft and is in full conformance with all provisions 11 of Section 10 of RFC2026 [1]. 13 Internet-Drafts are working documents of the Internet Engineering Task Force 14 (IETF), its areas, and its working groups. Note that other groups may also 15 distribute working documents as Internet-Drafts. Internet-Drafts are draft 16 documents valid for a maximum of six months and may be updated, replaced, or 17 obsoleted by other documents at any time. It is inappropriate to use Internet- 18 Drafts as reference material or to cite them other than as "work in progress." 19 The list of current Internet-Drafts can be accessed at 20 http://www.ietf.org/ietf/1id-abstracts.txt 21 The list of Internet-Draft Shadow Directories can be accessed at 22 http://www.ietf.org/shadow.html. 24 1. Abstract 26 Defines a Package for ATM bearer management for Megaco/H.248 28 2. Conventions used in this document 30 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", 31 "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be 32 interpreted as described in RFC-2119 [2]. 34 3. ATM Package 36 PackageID: atm (0x00xx) 37 Version: 1 38 Extends: Network Package version 1 40 This package is used to support cell based multimedia data 41 transfer by ATM. 43 3.1 Properties 45 None 47 3.2 Events 49 3.2.1 VC Change 50 Megaco ATM Package February 2001 52 Event name: VCChange 54 EventID: 0x01 56 Description: This event occurs whenever a change to VC occurs. 57 For example VC has been established or a VC has been modified. 59 EventsDescriptor Parameters: 61 Type 62 ---------- 63 Parameter Name: Type 65 ParameterID: 0x01 67 Type: Enumeration 69 Possible values: 70 All, [0x00] All Bearer Events 71 Est, [0x01] Bearer Established 72 Mod, [0x02] Bearer Modified 73 Cut, [0x03] Bearer Cut-through 74 Mfail, [0x04] Bearer Modification Failure 75 Note: For release indication see: General Package H.248 Sect 76 E.1.2 Cause Event. 78 Description: This is used to request the MG to notify it of a 79 VC event. 81 ObservedEventsDescriptor Parameters: 83 Type 84 ---------- 85 Parameter Name: Type 87 ParameterID: 0x01 89 Type: Enumeration 91 Possible values: 92 Est, [0x01] Bearer Established 93 Mod, [0x02] Bearer Modified 94 Cut, [0x03] Bearer Cut-through 95 Mfail, [0x04] Bearer Modification Failure 96 Note: For release indication, see General Package H.248 Sect 97 E.1.2 Cause Event. 99 Description: This is used to indicate why the VC Change was 100 generated by the MG. 102 3.2.2 Profile Element Transition 103 EventID: pftrans, 0x0001 104 Megaco ATM Package February 2001 106 This event is used with AAL2 adaptation only. Indicates a change 107 in the profile element sent. Profile elements indicating silence 108 should not trigger this event. 110 EventDescriptor parameters 112 None 114 ObservedEventsDescriptor parameters 116 Profile Element 117 ---------- 118 ParameterID: pfelmt, 0x01 120 Type: integer. 122 Possible values: a row number in a profile table to which 123 the switch is made. Rows are counted downward, beginning 124 from 1. 126 3.3 Signals 128 None 130 3.4 Statistics 132 Cells Sent 133 ------------ 134 StatisticID: cs (0x0004) 136 Type: double 138 Possible Values: any 64 bit integer 140 Cells Received 141 ---------------- 142 StatisticID: cr (0x0005) 144 Type: double 146 Possible Values: any 64 bit integer 148 Cell Loss 149 ----------- 150 StatisticID: cl (0x0006) 152 If the termination represents a VCC, this is the total number of 153 ATM cells lost, in the direction towards the gateway. 154 If the termination represents a CID within an AAL2, it is the 155 number of AAL2 common part sublayer (CPS) packets lost, in the 156 direction towards the gateway. For other terminations, or if 157 these losses cannot be assessed, then the MG omits this 158 parameter. 160 Megaco ATM Package February 2001 162 Type: double 164 Possible Values: any 64 bit integer 166 Jitter 167 ------ 168 StatisticID: jit (0x0007) 170 If the termination represents a VCC, this is the interarrival 171 jitter for ATM cells. If the termination represents a CID within 172 an AAL2 VCC, this is the interarrival jitter for AAL2 common part 173 sublayer (CPS) packets. If this cannot be determined, then it is 174 omitted. 176 Delay 177 ----- 178 StatisticID:delay (0x0008) 180 Average cell transmission delay. This requires the use of ATM 181 performance monitoring techniques. If it is not possible to 182 assess this delay, it is omitted. 184 3.5 Procedures 186 Terminations representing VCCs are placed in a special context. 187 The contextId of that context may be specified by a profile, or by provisioning. 188 PVCs known to the MG would appear in that context at boot time. An SVC is created 189 by Adding an appropriate (ephemeral) termination to that context. An SVC is torn 190 down by Subtracting the termination from the Context. For AAL1 or AAL2 VCCs, 191 terminations are created with the Add command specifying the channel identifier in 192 the CID field of the SDP or Annex C and referencing the VPI/VCI of the VCC the 193 channel is part of. For AAL1 VCCs, channels not assigned such a termination are 194 idle. 196 4. Acknowledgments 198 This work is based on the MGCP package draft by Rajesh Kumar of Cisco Systems. 199 The VC Change event is modeled after the BNCChange 200 Event of ITU-T Q.1950. 202 5. Author's Addresses 204 Brian Rosen 205 Marconi 206 1000 FORE Drive 207 Warrendale PA 15086 USA 208 Phone: +1 724 742 6826 209 Email: brian.rosen@marconi.com 210 Megaco ATM Package February 2001 212 Full Copyright Statement 214 "Copyright (C) The Internet Society (date). All Rights Reserved. This document and 215 translations of it may be copied and furnished to others, and derivative works 216 that comment on or otherwise explain it or assist in its implmentation may be 217 prepared, copied, published and distributed, in whole or in part, without 218 restriction of any kind, provided that the above copyright notice and this 219 paragraph are included on all such copies and derivative works. However, this 220 document itself may not be modified in any way, such as by removing the copyright 221 notice or references to the Internet Society or other Internet organizations, 222 except as needed for the purpose of developing Internet standards in which case 223 the procedures for copyrights defined in the Internet Standards process must be 224 followed, or as required to translate it into