RE: [Megaco] FW: SG16 Feb 2002 outputs
"Tom-PT Taylor"<taylor@nortelnetworks.com> Thu, 28 February 2002 14:32 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24904 for <megaco-archive@odin.ietf.org>; Thu, 28 Feb 2002 09:32:31 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA01383; Thu, 28 Feb 2002 09:10:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id JAA01352 for <megaco@optimus.ietf.org>; Thu, 28 Feb 2002 09:10:48 -0500 (EST)
Received: from zcars0m9.ca.nortel.com (zcars0m9.nortelnetworks.com [47.129.242.157]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23810 for <megaco@ietf.org>; Thu, 28 Feb 2002 09:10:43 -0500 (EST)
Received: from zcars04e.ca.nortel.com (zcars04e.ca.nortel.com [47.129.242.56]) by zcars0m9.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g1SEABD16757 for <megaco@ietf.org>; Thu, 28 Feb 2002 09:10:11 -0500 (EST)
Received: from zcard015.ca.nortel.com (zcard015.ca.nortel.com [47.129.30.7]) by zcars04e.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g1SEA9S24480 for <megaco@ietf.org>; Thu, 28 Feb 2002 09:10:09 -0500 (EST)
Received: by zcard015.ca.nortel.com with Internet Mail Service (5.5.2653.19) id <FYCHG1HN>; Thu, 28 Feb 2002 09:10:11 -0500
Message-ID: <4D79C746863DD51197690002A52CDA000102B0CE@zcard0kc.ca.nortel.com>
From: Tom-PT Taylor <taylor@nortelnetworks.com>
To: 'Dan Elbert' <delbert@radvision.com>, "'megaco@ietf.org'" <megaco@ietf.org>
Subject: RE: [Megaco] FW: SG16 Feb 2002 outputs
Date: Thu, 28 Feb 2002 09:10:16 -0500
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: megaco-admin@ietf.org
Errors-To: megaco-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Media Gateway Control <megaco.ietf.org>
X-BeenThere: megaco@ietf.org
Yes, that's right. Assuming no objections, the IESG advises the RFC Editor that the document can be published as a Standards Track RFC. The RFC Editor's queue is generally a few months long, so it could be up to 6 months before H.248v2 actually appears as an RFC. -----Original Message----- From: Dan Elbert [mailto:delbert@radvision.com] Sent: Thursday, February 28, 2002 8:50 AM To: Taylor, Tom-PT [CAR:B800:EXCH]; Dan Elbert; 'megaco@ietf.org' Subject: RE: [Megaco] FW: SG16 Feb 2002 outputs Thanks I'm not very familiar with IETF processes. After last call, does it goes through formal ratification ? -----Original Message----- From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com] Sent: Thursday, February 28, 2002 3:39 PM To: 'Dan Elbert'; 'megaco@ietf.org' Subject: RE: [Megaco] FW: SG16 Feb 2002 outputs I have submitted H.248v2 as an Internet Draft; it should appear shortly. At that point, unless people object, I propose to pass it straight on to the IESG for IETF Last Call. We did have an extended WG Last Call over the last two months. SG 16 has also published H.248v1 with all the IG corrections merged in as H.248 Corrigendum 1. I propose to move that forward also to RFC status. Basically, H.248 Corrigendum 1 as an RFC will OBSOLETE RFC 3015, and H.248v2 will UPDATE H.248 Corrigendum 1. Is this acceptable, or should we just leave custodianship of H.248v1 in SG 16's hands? -----Original Message----- From: Dan Elbert [mailto:delbert@radvision.com] Sent: Thursday, February 28, 2002 8:21 AM To: Taylor, Tom-PT [CAR:B800:EXCH]; 'megaco@ietf.org' Subject: RE: [Megaco] FW: SG16 Feb 2002 outputs Hi After reviewing the meeting summary, I'm not clear on how the process is being done with the IETF. Are they going to accept v2 as a new Megaco version or a new RFC ? If so, when? Thanks Dan Elbert RADVISION -----Original Message----- From: Tom-PT Taylor [mailto:taylor@nortelnetworks.com] Sent: Thursday, February 28, 2002 2:59 PM To: 'megaco@ietf.org' Subject: [Megaco] FW: SG16 Feb 2002 outputs FYI -----Original Message----- From: OKUBO Sakae [mailto:okubo@GITI.WASEDA.AC.JP] Sent: Thursday, February 28, 2002 1:49 AM To: ITU-SG16@echo.jf.INTEL.COM Subject: Re: SG16 Feb 2002 outputs Dear Christian, >I have uploaded to the following Geneve outputs: >pl-023_H248_Annex_M5.zip >pl-024_H248_Annex_N.zip >pl-027_H248_Packages_Guide.zip >pl-034_H248_Annex_L_amm1.zip >2-073r2_Q3_meeting_report.zip They have been moved to the following place: using browser http://standard.pictel.com/ftp/avc-site/0202_Gen/ using ftp tool ftp://standard.pictel.com/avc-site/0202_Gen/ Please note that 0202_Gen.html is the index for all the documents there. Best regards, OKUBO Sakae ********************************************************* Global Information and Telecommunication Institute (GITI) Waseda University 29-7 Waseda University Bldg. 1-3-10 Nishi-Waseda, Shinjuku-ku, Tokyo 169-0051 Japan e-mail: okubo@giti.waseda.ac.jp Tel: +81 3 3204 8194 Fax: +81 3 5286 3832 ********************************************************* _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco _______________________________________________ Megaco mailing list Megaco@ietf.org https://www1.ietf.org/mailman/listinfo/megaco
- [Megaco] FW: SG16 Feb 2002 outputs Tom-PT Taylor
- RE: [Megaco] FW: SG16 Feb 2002 outputs Dan Elbert
- RE: [Megaco] FW: SG16 Feb 2002 outputs Tom-PT Taylor
- RE: [Megaco] FW: SG16 Feb 2002 outputs Dan Elbert
- RE: [Megaco] FW: SG16 Feb 2002 outputs Tom-PT Taylor