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

Hello Tom/ Anil

But, then how H.248 (06/2000 the one that relates to
RFC 3015 or vice-versa as Tom specified) is still in
force on the ITU's site when H.248.1 (corr 03/2002)
has been superseded by H.248.1 (05/2002)?
I think creation of H.248.1 (-->.1) has changed the
lineage of the H.248 in ITU. So, is the original H.248
(ITU) going to survive this later onslaught? If yes,
how can IETF obsolete RFC3015?

Only Tom can clear this confusion.

--shri

 --- Anil Jangam <anilj@mahindrabt.com> wrote: >
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 

________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
       visit http://in.tv.yahoo.com
_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco