idnits 2.17.1 draft-ietf-megaco-protocol-02.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-25) 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 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. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 2) being 61 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 2 pages 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.) ** The document seems to lack an Authors' Addresses Section. 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) No issues found here. Summary: 9 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force Fernando Cuervo 2 INTERNET DRAFT Nortel Networks 3 December 25, 1999 Christian Huitema 4 Expires October 16, 1999 Telcordia Technologies 5 Keith Kelly 6 NetSpeak 7 Brian Rosen 8 FORE Systems 9 Paul Sijben 10 Lucent Technologies 11 Eric Zimmerer 12 Level 3 Communications 14 MEGACO Protocol 16 Status of this document 18 This document is an Internet-Draft and is in full conformance with all 19 provisions of Section 10 of RFC2026 21 Internet-Drafts are working documents of the Internet Engineering Task 22 Force (IETF), its areas, and its working groups. Note that other groups 23 may also distribute working documents as Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet- Drafts as reference material 28 or to cite them other than as "work in progress." 30 To view the entire list of current Internet-Drafts, please check the 31 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 32 Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern Europe), 33 ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific Rim), 34 ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 36 ABSTRACT 38 IMPORTANT NOTE 40 In accordance with agreements reached between IETF and ITU, the text of 41 the protocol, IETF version 02, is found at: 42 ftp://standards.nortelnetworks.com/megaco/docs/Oslo99/megacoHGCP5.pdf 44 The source for this document may be found at: 46 Internet draft MEGACO Protocol June 25, 1999 48 ftp://standards.nortelnetworks.com/megaco/docs/Oslo99/megacoHGCP5.pdf 50 MEGACO/Recommendation H.GCP defines the protocols used between elements 51 of a physically decomposed multimedia gateway. There are no functional 52 differences from a system view between a decomposed gateway, with dis- 53 tributed sub-components potentially on more than one physical devices, 54 and a monolithic gateway. 56 This RFC/recommendation does not define how gateways, multipoint control 57 units or integrated voice response units (IVRs) work. Instead it 58 creates a general framework that is suitable for these applications. 60 Packet network interfaces may include IP, ATM or possibly others. The 61 interfaces will support a variety of SCN signalling systems, including 62 tone signalling, ISDN, ISUP, QSIG, and GSM. National variants of these 63 signaling systems will be supported where applicable.