RE: [Megaco] Megaco: which spec to use?

"Kevin Boyle" <kboyle@nortelnetworks.com> Tue, 12 November 2002 20:30 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 PAA13848 for <megaco-archive@lists.ietf.org>; Tue, 12 Nov 2002 15:30:03 -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 gACKVlv27516; Tue, 12 Nov 2002 15:31:47 -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 gACKUev27445 for <megaco@optimus.ietf.org>; Tue, 12 Nov 2002 15:30:40 -0500
Received: from zrtps0kp.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13786 for <Megaco@ietf.org>; Tue, 12 Nov 2002 15:28:01 -0500 (EST)
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kp.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id gACKUXe23980 for <Megaco@ietf.org>; Tue, 12 Nov 2002 15:30:33 -0500 (EST)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id <4GF6LFRS>; Tue, 12 Nov 2002 15:30:34 -0500
Message-ID: <ABA227A15B80D511BD1A00508BF93A1C06577DC8@zrtpd0jq.us.nortel.com>
From: Kevin Boyle <kboyle@nortelnetworks.com>
To: Pascal Lambers <pascal.lambers@pandora.be>, Megaco@ietf.org
Subject: RE: [Megaco] Megaco: which spec to use?
Date: Tue, 12 Nov 2002 15:30:32 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
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>

You have a misunderstanding as to what does and does not constitute a
standard.
 
RFC 3015 is a "Proposed Standard" that outlines the original draft of the
Megaco/H.248 specification.  In accordance with the agreement between the
IETF and ITU, it is subject to the amendments contained within the
Implementors' Guide.  draft-ietf-megaco-3015corr is being pushed toward RFC
status to replace 3015.  It is identical to ITU-T Recommendation H.248.1,
02/2002 (hereafter referred to as H.248.1 v1).  draft-ietf-megaco-h248v2 is
being pushed toward RFC status as well.  It is identical to ITU-T
Recommendation H.248.1, 05/2002 (hereafter referred to as H.248.1 v2).  Both
of these will go forward as "Proposed Standards".
 
However, this only describes the status of these items as they pertain to
the IETF.  The ITU has issued both of the documents as Recommendations,
meaning that they have full weight and status as standards, as far as the
ITU is concerned.  The ITU and IETF are both widely recognized as standards
bodies that have authority to declare and retract standards as they see fit.
Megaco-H.248 work is progressed under a joint agreement between the two.
However, just because one body or the other is lagging in declaration of the
standard does not make it any less a standard.
 
One other small correction:  H.248.2 is NOT H.248 v2.  H.248.2 is what used
to be H.248 Annex F.  The annexes were renumbered to make for easier
reference.  The base spec is H.248.1 (with a version 1 and version 2) and
the annexes are H.248.2 through H.248.20 (currently).  I anticipate that we
will add H.248.21 in May.
 
Kevin

-----Original Message-----
From: Pascal Lambers [mailto:pascal.lambers@pandora.be] 
Sent: Tuesday, November 12, 2002 3:07 PM
To: Megaco@ietf.org
Subject: [Megaco] Megaco: which spec to use?


Hello, 
 
May I ask some questions about which Megaco spec to hold on to...
 
 
For Megaco, Ietf has different documents:

*	Gateway Control Protocol Version 1: RFC 3015
(http://www.ietf.org/rfc/rfc3015.txt?number=3015
<http://www.ietf.org/rfc/rfc3015.txt?number=3015> ) 

*	draft-ietf-megaco-3015corr-01.txt 

*	draft-ietf-megaco-3015corr-02.txt
(http://www.ietf.org/internet-drafts/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

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco