IETF Logo Mail Archive

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

"Anil Jangam" <anilj@mahindrabt.com> Wed, 13 November 2002 08:33 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 DAA24689 for <megaco-archive@lists.ietf.org>; Wed, 13 Nov 2002 03:33:44 -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 gAD8Zbv12104; Wed, 13 Nov 2002 03:35:37 -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 gAD8YOv12036 for <megaco@optimus.ietf.org>; Wed, 13 Nov 2002 03:34:33 -0500
Received: from shardagate.mahindrabt.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA24600 for <Megaco@ietf.org>; Wed, 13 Nov 2002 03:30:52 -0500 (EST)
Received: from thisdomain (mailscan.sharda.mahindrabt.com [10.5.0.97]) by shardagate.mahindrabt.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id OAA22886 for <Megaco@ietf.org>; Wed, 13 Nov 2002 14:02:22 +0530
Received: from intranet.sharda.mahindrabt.com by mahindrabt.com ; Wed, 13 Nov 2002 13:53:26 +0530
Date: Wed, 13 Nov 2002 13:53:26 +0530
X-Originating-IP: 10.5.0.15
X-Auth-User: anilj@mahindrabt.com
Received: from dscp00986 ([10.5.6.22]) by intranet.sharda.mahindrabt.com (8.9.3/8.9.3) with SMTP id OAA26361; Wed, 13 Nov 2002 14:02:12 +0530
Message-ID: <004001c28aef$ce5c0870$1606050a@mahindrabt.com>
From: Anil Jangam <anilj@mahindrabt.com>
To: Tom-PT Taylor <taylor@nortelnetworks.com>, Megaco@ietf.org
References: <4D79C746863DD51197690002A52CDA00047A70B1@zcard0kc.ca.nortel.com>
Subject: Re: [Megaco] Megaco: which spec to use?
Date: Wed, 13 Nov 2002 14:06:47 +0530
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
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>
Content-Transfer-Encoding: 7bit

inline..

----- Original Message -----
From: "Tom-PT Taylor" <taylor@nortelnetworks.com>
To: "Pascal Lambers" <pascal.lambers@pandora.be>; <Megaco@ietf.org>
Sent: Wednesday, November 13, 2002 12:50 PM
Subject: RE: [Megaco] Megaco: which spec to use?

> Let's hope you haven't opened up a Pandora's box here!
>
> Turning to the IETF side: the IESG has approved
> draft-ietf-megaco-3015corr-02.txt as an RFC, obsoleting RFC 3015.  I'm not
> sure I passed this news on to the list!  Pardon me for my oversight.

I think you have not. Will this draft (draft-ietf-megaco-3015corr-02.txt)
be turned in to the Version 2 for the rfc3015 (Earlier drafts mention
Version 1)???

> Anyway, typically it will take a few months for this document to pass
> through the RFC Editor's queue and be assigned an RFC number.
>
> I will recycle version 2, fixing the missing initial characters and draft
> date, then pass it to the IESG for approval.  My intention is that this
will
> update but not obsolete the 3015corr RFC, but I just realized that I
should
> put that question to the list.  Do people want two versions of Megaco to
> coexist, or do they want to follow the ITU-T viewpoint and allow v2 to
> obsolete v1?
>
I feel both the versions be available for public access. Its quite possible
that most of the people are following Version1 (not necesary though) for
their current implementation and it would be a good idea to have both the
references in hand. However I hope that any new version will always contain
a list of changes from its previous release.

/anil.

*********************************************************
Disclaimer

This message (including any attachments) contains 
confidential information intended for a specific 
individual and purpose, and is protected by law. 
If you are not the intended recipient, you should 
delete this message and are hereby notified that 
any disclosure, copying, or distribution of this
message, or the taking of any action based on it, 
is strictly prohibited.

*********************************************************
Visit us at http://www.mahindrabt.com



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

v2.23.0 | Report a Bug | By Email