[Megaco] Megaco: which spec to use?

"Pascal Lambers" <pascal.lambers@pandora.be> Tue, 12 November 2002 20:05 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12919 for <megaco-archive@lists.ietf.org>; Tue, 12 Nov 2002 15:05:45 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACK7fv26551; Tue, 12 Nov 2002 15:07:41 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gACK6Qv25918 for <megaco@optimus.ietf.org>; Tue, 12 Nov 2002 15:06:26 -0500
Received: from eos.telenet-ops.be (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12873 for <Megaco@ietf.org>; Tue, 12 Nov 2002 15:03:47 -0500 (EST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by eos.telenet-ops.be (Postfix) with SMTP id 82382210C7 for <Megaco@ietf.org>; Tue, 12 Nov 2002 21:06:19 +0100 (CET)
Received: from pentiumiii (D5778868.kabel.telenet.be [213.119.136.104]) by eos.telenet-ops.be (Postfix) with SMTP id 1A3DA21568 for <Megaco@ietf.org>; Tue, 12 Nov 2002 21:06:19 +0100 (CET)
Message-ID: <001801c28a87$0cb67f60$688877d5@pandora.be>
Reply-To: Pascal Lambers <pascal.lambers@pandora.be>
From: Pascal Lambers <pascal.lambers@pandora.be>
To: Megaco@ietf.org
Date: Tue, 12 Nov 2002 21:06:55 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0015_01C28A8F.6E3022C0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Subject: [Megaco] Megaco: which spec to use?
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-BeenThere: megaco@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=unsubscribe>
List-Id: Media Gateway Control <megaco.ietf.org>
List-Post: <mailto:megaco@ietf.org>
List-Help: <mailto:megaco-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/megaco>, <mailto:megaco-request@ietf.org?subject=subscribe>

Hello, 

May I ask some questions about which Megaco spec to hold on to...


For Megaco, Ietf has different documents:
  a.. Gateway Control Protocol Version 1: RFC 3015 (http://www.ietf.org/rfc/rfc3015.txt?number=3015) 
  b.. draft-ietf-megaco-3015corr-01.txt
  c.. draft-ietf-megaco-3015corr-02.txt (http://www.ietf.org/internet-drafts/draft-ietf-megaco-3015corr-02.txt)
As there is no RFC for version 2 yet, the only norm is version 1. Vendors who implemented specifcic corrections and amendements specified in the corrective documents are in fact not conform to the official Megaco spec, as "it is inappropriate to use Internet-Drafts as reference material or to cite them other than as work in progress." Is this interpretation correct?

Now, my second question: what about ITU-T's H.248 specifications? I understand that RFC 3015 corresponds to H.248. But what about H.248.1, H.248.2, etc. Are they official or just corrections and ideas for a new official spec yet to come?


Is any vendor relying on this spec, or does everybody take the RFC 3015?



Thanks in advance,
Pascal