[Iptel] New charter items
Jonathan Rosenberg <jdrosen@dynamicsoft.com> Tue, 03 December 2002 07:03 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 CAA04785 for <iptel-archive@odin.ietf.org>; Tue, 3 Dec 2002 02:03:39 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gB3768w08401 for iptel-archive@odin.ietf.org; Tue, 3 Dec 2002 02:06:08 -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 gB3768v08398 for <iptel-web-archive@optimus.ietf.org>; Tue, 3 Dec 2002 02:06:08 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04094 for <iptel-web-archive@ietf.org>; Tue, 3 Dec 2002 02:03:08 -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 gB3763v08369; Tue, 3 Dec 2002 02:06:03 -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 gB375nv08277 for <iptel@optimus.ietf.org>; Tue, 3 Dec 2002 02:05:49 -0500
Received: from mail3.dynamicsoft.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03674 for <iptel@ietf.org>; Tue, 3 Dec 2002 02:02:49 -0500 (EST)
Received: from dynamicsoft.com ([63.113.46.55]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id gB375eYH011117 for <iptel@ietf.org>; Tue, 3 Dec 2002 02:05:41 -0500 (EST)
Message-ID: <3DEC57C1.2090000@dynamicsoft.com>
From: Jonathan Rosenberg <jdrosen@dynamicsoft.com>
Organization: dynamicsoft
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: iptel@ietf.org
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Iptel] New charter items
Sender: iptel-admin@ietf.org
Errors-To: iptel-admin@ietf.org
X-BeenThere: iptel@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/iptel>, <mailto:iptel-request@ietf.org?subject=unsubscribe>
List-Id: IP Telephony <iptel.ietf.org>
List-Post: <mailto:iptel@ietf.org>
List-Help: <mailto:iptel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iptel>, <mailto:iptel-request@ietf.org?subject=subscribe>
List-Archive: <https://www.ietf.org/pipermail/iptel/>
Date: Tue, 03 Dec 2002 02:05:37 -0500
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Folks, As I mentioned during the meeting, the iptel group has been asked to be the new home for telephony URI related work. This work encompasses a number of drafts which we need to formally adopt as working group items. I'd like to gauge general group interest in pursuing this work. Please comment (privately or on the list) on your desire to work on the following: 1. http://www.ietf.org/internet-drafts/draft-antti-rfc2806bis-06.txt We have formally been asked to own this document. We have already been actively working on it so I dont anticipate there will be any objections. 2. http://www.ietf.org/internet-drafts/draft-yu-tel-url-06.txt We have also formally been asked to own this document. Not many comments on it yet. 3. http://www.ietf.org/internet-drafts/draft-ietf-iptel-trunk-group-00.txt This is a new draft. While I think the draft itself requires more work, the main question is whether the group is interested in specifying extensions to the tel URI for supporting trunk groups, and whether this document can serve as a useful starting point for that work. During the meeting, I pointed out that the h323 URL http://www.ietf.org/internet-drafts/draft-levin-iptel-h323-url-scheme-05.txt would also need to be added to our charter. However, in subsequent discussions with the author and Scott B., it turns out that the iptel group does not have change control over this work. It is therefore not appropriate for us to work on it, and it will be handled outside of the iptel group. On the subject of the enum URI, I believe there is not consensus on whether or not it even makes sense to have a separate URI for this. Its therefore inappropriate to make any charter decisions at this time. I'd like to see some more discussion of the specific problem, though. As I pointed out during the meeting, I believe it is closely related to the imprecise semantics of the tel URI itself. THus, I believe we own the general problem as part of the tel URI work. On the CPC work, I think there is even less consensus on that, with a lot more discussion needed. Thanks, Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave. Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PHONE: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel
- [Iptel] New charter items Jonathan Rosenberg