From extest-admin@lists.bell-labs.com Tue Jul 1 06:26:19 2003 Received: from share.research.bell-labs.com (share.research.bell-labs.com [204.178.16.58]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA05336 for ; Tue, 1 Jul 2003 06:26:19 -0400 (EDT) Received: from share.research.bell-labs.com (localhost [127.0.0.1]) by share.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h61AQbj25464 for ; Tue, 1 Jul 2003 06:26:37 -0400 Date: Tue, 1 Jul 2003 06:26:37 -0400 Message-Id: <200307011026.h61AQbj25464@share.research.bell-labs.com> Subject: lists.bell-labs.com mailing list memberships reminder From: mailman-owner@lists.bell-labs.com To: iptel-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: extest-admin@lists.bell-labs.com Errors-To: extest-admin@lists.bell-labs.com X-BeenThere: extest@lists.bell-labs.com X-Mailman-Version: 2.0.8 Precedence: bulk This is a reminder, sent out once a month, about your lists.bell-labs.com mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, iptel-request@lists.bell-labs.com) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@lists.bell-labs.com. Thanks! Passwords for iptel-archive@lists.ietf.org: List Password // URL ---- -------- iptel@lists.bell-labs.com nexaew http://lists.bell-labs.com/mailman/options/iptel/iptel-archive%40lists.ietf.org From exim@www1.ietf.org Tue Jul 1 09:04:43 2003 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 JAA18572 for ; Tue, 1 Jul 2003 09:04:43 -0400 (EDT) Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h61D4FG29541 for iptel-archive@odin.ietf.org; Tue, 1 Jul 2003 09:04:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XKnv-0007gO-A7 for iptel-web-archive@optimus.ietf.org; Tue, 01 Jul 2003 09:04:15 -0400 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 JAA18383 for ; Tue, 1 Jul 2003 09:04:12 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XKnQ-0007Is-Ua for iptel-web-archive@ietf.org; Tue, 01 Jul 2003 09:03:44 -0400 Date: Tue, 01 Jul 2003 09:03:44 -0400 Message-ID: <20030701130344.18162.57643.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: iptel-web-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: sip-admin@ietf.org Errors-To: sip-admin@ietf.org X-BeenThere: sip@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, iptel-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for iptel-web-archive@ietf.org: List Password // URL ---- -------- iptel@ietf.org aroxgu https://www.ietf.org/mailman/options/iptel/iptel-web-archive%40ietf.org From exim@www1.ietf.org Wed Jul 2 06:56:32 2003 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 GAA02917 for ; Wed, 2 Jul 2003 06:56:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XfHQ-0002iQ-LQ for iptel-archive@odin.ietf.org; Wed, 02 Jul 2003 06:56:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h62Au4n0010438 for iptel-archive@odin.ietf.org; Wed, 2 Jul 2003 06:56:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XfHQ-0002iH-IN for iptel-web-archive@optimus.ietf.org; Wed, 02 Jul 2003 06:56:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02769 for ; Wed, 2 Jul 2003 06:56:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XfHM-00018P-00 for iptel-web-archive@ietf.org; Wed, 02 Jul 2003 06:56:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XfHL-00018L-00 for iptel-web-archive@ietf.org; Wed, 02 Jul 2003 06:55:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XfHO-0002h6-76; Wed, 02 Jul 2003 06:56:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XfGh-0002g0-5Q for iptel@optimus.ietf.org; Wed, 02 Jul 2003 06:55:19 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA02578; Wed, 2 Jul 2003 06:55:15 -0400 (EDT) Message-Id: <200307021055.GAA02578@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: iptel@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Iptel] I-D ACTION:draft-ietf-iptel-tgrep-02.txt 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 02 Jul 2003 06:55:15 -0400 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP Telephony Working Group of the IETF. Title : A Telephony Gateway REgistration Protocol (TGREP) Author(s) : M. Bangalore et al. Filename : draft-ietf-iptel-tgrep-02.txt Pages : 27 Date : 2003-7-1 This document describes the Telephony Gateway Registration Protocol (TGREP) for registration of telephony prefixes supported by telephony gateways and soft switches. The registration mechanism can also be used to export resource information. The prefix and resource information can then be passed on to a TRIP Location Server, which in turn can propogate that routing information within the same, and other internet telephony administrative domains (ITAD). TGREP shares a lot of similarites with the TRIP Protocol. It has similar procedures and Finite State Machine for session establishment. It also shares the same format for messaages and a subset of attributes with TRIP. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-iptel-tgrep-02.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-iptel-tgrep-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-iptel-tgrep-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-7-1134517.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-iptel-tgrep-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-iptel-tgrep-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-7-1134517.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Wed Jul 2 16:33:30 2003 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 QAA13080 for ; Wed, 2 Jul 2003 16:33:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XoHo-0002in-IV for iptel-archive@odin.ietf.org; Wed, 02 Jul 2003 16:33:04 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h62KX4WM010444 for iptel-archive@odin.ietf.org; Wed, 2 Jul 2003 16:33:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XoHo-0002iL-Es for iptel-web-archive@optimus.ietf.org; Wed, 02 Jul 2003 16:33:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12916 for ; Wed, 2 Jul 2003 16:32:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XoHk-0007ID-00 for iptel-web-archive@ietf.org; Wed, 02 Jul 2003 16:33:00 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19XoHj-0007I6-00 for iptel-web-archive@ietf.org; Wed, 02 Jul 2003 16:32:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XoHk-0002gU-RJ; Wed, 02 Jul 2003 16:33:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XoGv-0002ZJ-NT for iptel@optimus.ietf.org; Wed, 02 Jul 2003 16:32:09 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12600; Wed, 2 Jul 2003 16:32:04 -0400 (EDT) Message-Id: <200307022032.QAA12600@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: iptel@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Iptel] I-D ACTION:draft-ietf-iptel-rfc2806bis-02.txt 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 02 Jul 2003 16:32:03 -0400 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP Telephony Working Group of the IETF. Title : The tel URI for Telephone Calls Author(s) : H. Schulzrinne, A. Vaha-Sipila Filename : draft-ietf-iptel-rfc2806bis-02.txt Pages : 18 Date : 2003-7-2 This document specifies the URI (Uniform Resource Identifier) scheme 'tel'. The 'tel' URI describes resources identified by telephone numbers A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-iptel-rfc2806bis-02.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-iptel-rfc2806bis-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-iptel-rfc2806bis-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-7-2161504.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-iptel-rfc2806bis-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-iptel-rfc2806bis-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-7-2161504.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Thu Jul 3 18:43:39 2003 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 SAA13897 for ; Thu, 3 Jul 2003 18:33:17 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YCdB-00045a-8k for iptel-archive@odin.ietf.org; Thu, 03 Jul 2003 18:32:45 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h63MWjDv015705 for iptel-archive@odin.ietf.org; Thu, 3 Jul 2003 18:32:45 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YCdB-000456-22 for iptel-web-archive@optimus.ietf.org; Thu, 03 Jul 2003 18:32:45 -0400 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 SAA13308 for ; Thu, 3 Jul 2003 18:32:39 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YCcd-0003Co-G1 for iptel-web-archive@ietf.org; Thu, 03 Jul 2003 18:32:11 -0400 Date: Thu, 03 Jul 2003 18:32:11 -0400 Message-ID: <20030703223211.4508.42032.Mailman@www1.ietf.org> Subject: ietf.org mailing list memberships reminder From: mailman-owner@www1.ietf.org To: iptel-web-archive@ietf.org X-No-Archive: yes X-Ack: no Sender: mailman-admin@ietf.org Errors-To: mailman-admin@ietf.org X-BeenThere: mailman@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk There was an error in the last monthly reminder, in that the NOTE WELL statement (below) was not included. Therefore, the reminder is being sent out again. This is a reminder, sent out once a month, about your ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, iptel-request@ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. *************************************************************************** Note Well All statements related to the activities of the IETF and addressed to the IETF are subject to all provisions of Section 10 of RFC 2026, which grants to the IETF and its participants certain licenses and rights in such statements. Such statements include verbal statements in IETF meetings, as well as written and electronic communications made at any time or place, which are addressed to * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function Statements made outside of an IETF meeting, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not subject to these provisions. *************************************************************************** If you have questions, problems, comments, etc, send them to mailman-owner@www1.ietf.org. Thanks! Passwords for iptel-web-archive@ietf.org: List Password // URL ---- -------- iptel@ietf.org aroxgu https://www.ietf.org/mailman/options/iptel/iptel-web-archive%40ietf.org From exim@www1.ietf.org Sun Jul 6 05:19:31 2003 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 FAA10101 for ; Sun, 6 Jul 2003 05:19:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Z5fk-0007yl-Gk for iptel-archive@odin.ietf.org; Sun, 06 Jul 2003 05:19:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h669J4c5030667 for iptel-archive@odin.ietf.org; Sun, 6 Jul 2003 05:19:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Z5fk-0007yY-DM for iptel-web-archive@optimus.ietf.org; Sun, 06 Jul 2003 05:19:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10098 for ; Sun, 6 Jul 2003 05:18:59 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Z5fh-00012W-00 for iptel-web-archive@ietf.org; Sun, 06 Jul 2003 05:19:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Z5fg-00012S-00 for iptel-web-archive@ietf.org; Sun, 06 Jul 2003 05:19:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Z5fh-0007y6-6n; Sun, 06 Jul 2003 05:19:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Z5fT-0007xv-EY for iptel@optimus.ietf.org; Sun, 06 Jul 2003 05:18:47 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10093 for ; Sun, 6 Jul 2003 05:18:42 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Z5fQ-00012O-00 for iptel@ietf.org; Sun, 06 Jul 2003 05:18:44 -0400 Received: from ierw.net.avaya.com ([198.152.13.101]) by ietf-mx with esmtp (Exim 4.12) id 19Z5fP-00012L-00 for iptel@ietf.org; Sun, 06 Jul 2003 05:18:43 -0400 Received: from ierw.net.avaya.com (localhost [127.0.0.1]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id FAA22125 for ; Sun, 6 Jul 2003 05:15:59 -0400 (EDT) Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by ierw.net.avaya.com (8.9.3+Sun/8.9.3) with ESMTP id FAA22117 for ; Sun, 6 Jul 2003 05:15:57 -0400 (EDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3439F.9742A1D4" Message-ID: Thread-Topic: Comments on draft-ietf-iptel-trip-mib-06.txt Thread-Index: AcNDn5diUUPVSr8WR+66sejXqQ09nQ== From: "Romascanu, Dan (Dan)" To: Cc: "Jon Peterson (E-mail)" , "Bert Wijnen (E-mail)" , "David Zinman" , , , , Subject: [Iptel] Comments on draft-ietf-iptel-trip-mib-06.txt 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Sun, 6 Jul 2003 12:18:41 +0300 This is a multi-part message in MIME format. ------_=_NextPart_001_01C3439F.9742A1D4 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Here are my comments on the latest TRIP MIB I-D. I congratulate the = authors for the considerable improvement of the document, and thank them = for taking into account most of my comments in the review of the = previous version. There are still a few problems: 1) smilint complains of two indices possibly exceeding the OID size = limitation: TRIP-MIB.txt:328: [5] {index-exceeds-too-large} warning: index of row = `tripRouteTypeEntry' can exceed OID size limit by 138 subidentifier(s) TRIP-MIB.txt:511: [5] {index-exceeds-too-large} warning: index of row = `tripPeerEntry' can exceed OID size limit by 136 subidentifier(s) This is probably because of use of multiple indices with a syntax of = OBJECT STRING or OBJECT IDENTIFIER. According to Section 4.6.5 in = http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-= 01.txt, ' It is RECOMMENDED that all MIB documents make explicit any limitations = on index component lengths that management software must observe. This = may be done either by including SIZE constraints on the index components = or by specifying applicable constraints in the conceptual row = DESCRIPTION clause or in the surrounding documentation. ' =20 2) One of my comments in the review of draft-05 was about the need to = improve the DESCRIPTION clause of tripRouteUnknown. If I were an = implementer, I still do not know what this object is supposed to = contain, and how the information is encoded. 3) Two of comments in the previous review were ignored. I would not = block this document because of these, but I still think that they were = valid, and the authors would like to consider following them for = improved readability and consistency. These comments were: '4. The readability of the document would be much improved if an = abbreviation section would be included. Some of the abbreviations are = not detailed, some other are explained only after a few occurrences in = the text (LS, ITAD) -- LS is now explained at the first occurrence, but = ITAD is still not explained. -- 10. 'location server' in the DESCRIPTION clause of tripPeerOutUpdates is = inconsistent with the other clauses in the same table where it is = abbreviated.' 4) You would like to swap the order of the two phrases that compose = Section 4, and remove the double reference in the same section. 5) Year in copyright notes and the Copyright Section should be updated = to 2003. Regards, Dan =20 ------_=_NextPart_001_01C3439F.9742A1D4 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Comments on draft-ietf-iptel-trip-mib-06.txt

Here are my comments on the = latest TRIP MIB I-D. I congratulate the authors for the considerable = improvement of the document, and thank them for taking into account most = of my comments in the review of the previous version.

There are still a few = problems:

1) smilint complains of two = indices possibly exceeding the OID size limitation:

TRIP-MIB.txt:328: [5] = {index-exceeds-too-large} warning: index of row `tripRouteTypeEntry' can = exceed OID size limit by 138 subidentifier(s)

TRIP-MIB.txt:511: [5] = {index-exceeds-too-large} warning: index of row `tripPeerEntry' can = exceed OID size limit by 136 subidentifier(s)

This is probably because of = use of multiple indices with a  syntax of OBJECT STRING or OBJECT = IDENTIFIER. According to  Section 4.6.5 in http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-re= view-guidelines-01.txt,

' It is RECOMMENDED that = all MIB documents make explicit any limitations on index component = lengths that management software must observe. This may be done either = by including SIZE constraints on the index components or by specifying = applicable constraints in the conceptual row DESCRIPTION clause or in = the surrounding documentation. '

  =

2)  = One of my comments in the review of draft-05 was about the need to = improve the DESCRIPTION clause of tripRouteUnknown. If I were an = implementer, I still do not know what this object is supposed to = contain, and how the information is encoded.


3) Two of = comments in the previous review were ignored. I would not block this = document because of these, but I still think that they were valid, and = the authors would like to consider following them for improved = readability and consistency.

These = comments were:

'4. The = readability of the document would be much improved if an abbreviation = section would be included. Some of the abbreviations are not detailed, = some other are explained only after a few occurrences in the text (LS, = ITAD) -- LS is now explained at the first occurrence, but ITAD is still = not explained. --

10. = 'location server' in the DESCRIPTION clause of tripPeerOutUpdates is = inconsistent with the other clauses in the same table where it is = abbreviated.'

4) You = would like to swap the order of the two phrases that compose Section 4, = and remove the double reference in the same section.

5) Year in = copyright notes and the Copyright Section should be updated to = 2003.

Regards,

Dan




 

------_=_NextPart_001_01C3439F.9742A1D4-- _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Thu Jul 10 14:56:35 2003 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 OAA16348 for ; Thu, 10 Jul 2003 14:56:35 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19agaQ-0003lI-BV for iptel-archive@odin.ietf.org; Thu, 10 Jul 2003 14:56:10 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6AIuAp8014457 for iptel-archive@odin.ietf.org; Thu, 10 Jul 2003 14:56:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19agaP-0003l5-Ny for iptel-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 14:56:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16340 for ; Thu, 10 Jul 2003 14:56:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19agaM-0006D8-00 for iptel-web-archive@ietf.org; Thu, 10 Jul 2003 14:56:06 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19agaM-0006D4-00 for iptel-web-archive@ietf.org; Thu, 10 Jul 2003 14:56:06 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19agaH-0003kJ-VP; Thu, 10 Jul 2003 14:56:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19agZo-0003jy-QS for iptel@optimus.ietf.org; Thu, 10 Jul 2003 14:55:32 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16305 for ; Thu, 10 Jul 2003 14:55:27 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19agZl-0006CW-00 for iptel@ietf.org; Thu, 10 Jul 2003 14:55:29 -0400 Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com) by ietf-mx with esmtp (Exim 4.12) id 19agZl-0006CL-00 for iptel@ietf.org; Thu, 10 Jul 2003 14:55:29 -0400 Received: from dynamicsoft.com ([63.113.46.12]) by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id h6AIt3iB007740 for ; Thu, 10 Jul 2003 14:55:03 -0400 (EDT) Message-ID: <3F0DB681.4000709@dynamicsoft.com> From: Jonathan Rosenberg Organization: dynamicsoft User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: list iptel Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Iptel] Getting CPL off of rfc-ed queue 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 10 Jul 2003 14:54:57 -0400 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Folks, The iptel group completed the CPL spec, and got it approved by IESG, quite a long time ago (well over a year). The CPL spec is still in the rfc editors queue, blocked on a reference to the caller preferences spec. As you may know, caller prefs has had a rocky history in the SIP group, and its not clear that its going to be done really soon either. As a result, caller prefs was split in half. One half covers capabilities, which is more stable, and the other half, the actual caller preferences, which needs additional work and review. Unfortunately, CPL has a bunch of features which make direct use of caller preferences (not just the capabilities stuff), and thus it continues to have a normative reference to it. In order to make progress on CPL, and get it as an RFC already, I discussed a plan with our ADs, Cullen, and the CPL authors, which we would like working group input on: 1. We will remove CPL from the rfc-ed, and bring it back into iptel for another revision. 2. In that revision, we will: A. remove the features that make CPL dependent on caller preferences, B. convert the DTD to a schema, such that there is no loss of interoperability with any implementations which are using the DTD C. update references D. typos We will NOT be introducing any other features or capabilities. All changes are restricted to one of the above four groups. 3. These changes will be made fairly quickly (one month or so), and after that, we will issue a wglc for the document, and then send it to iesg for approval once more and reinsertion onto the rfc-ed queue. Please provide input on whether you are in agreement or disagreement with this plan. Thanks, Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza Chief Technology Officer Parsippany, NJ 07054-2711 dynamicsoft 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 From exim@www1.ietf.org Thu Jul 10 15:04:28 2003 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 PAA16668 for ; Thu, 10 Jul 2003 15:04:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19agi2-0004a7-Ru for iptel-archive@odin.ietf.org; Thu, 10 Jul 2003 15:04:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6AJ42oD017607 for iptel-archive@odin.ietf.org; Thu, 10 Jul 2003 15:04:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19agi2-0004Zu-Ns for iptel-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 15:04:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16618 for ; Thu, 10 Jul 2003 15:03:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aghz-0006GM-00 for iptel-web-archive@ietf.org; Thu, 10 Jul 2003 15:03:59 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19aghz-0006GJ-00 for iptel-web-archive@ietf.org; Thu, 10 Jul 2003 15:03:59 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19agi0-0004ZI-Vv; Thu, 10 Jul 2003 15:04:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19agh8-0004Pa-Oh for iptel@optimus.ietf.org; Thu, 10 Jul 2003 15:03:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16538 for ; Thu, 10 Jul 2003 15:03:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19agh5-0006Fs-00 for iptel@ietf.org; Thu, 10 Jul 2003 15:03:03 -0400 Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 19agh5-0006Fi-00 for iptel@ietf.org; Thu, 10 Jul 2003 15:03:03 -0400 Received: from cisco.com (171.68.223.137) by sj-iport-2.cisco.com with ESMTP; 10 Jul 2003 12:00:39 -0700 Received: from [10.32.254.183] (stealth-10-32-254-183.cisco.com [10.32.254.183]) by sj-core-3.cisco.com (8.12.6/8.12.6) with SMTP id h6AJ2UpZ000015; Thu, 10 Jul 2003 12:02:30 -0700 (PDT) From: "David R. Oran" To: Jonathan Rosenberg , list iptel Subject: Re: [Iptel] Getting CPL off of rfc-ed queue Message-ID: <143585203.1057849349@[10.32.254.183]> In-Reply-To: <3F0DB681.4000709@dynamicsoft.com> References: <3F0DB681.4000709@dynamicsoft.com> X-Mailer: Mulberry/3.0.3 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 10 Jul 2003 15:02:29 -0400 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Seems like a good plan to me. Dave. --On Thursday, July 10, 2003 2:54 PM -0400 Jonathan Rosenberg wrote: > Folks, > > The iptel group completed the CPL spec, and got it approved by IESG, > quite a long time ago (well over a year). The CPL spec is still in the > rfc editors queue, blocked on a reference to the caller preferences spec. > As you may know, caller prefs has had a rocky history in the SIP group, > and its not clear that its going to be done really soon either. As a > result, caller prefs was split in half. One half covers capabilities, > which is more stable, and the other half, the actual caller preferences, > which needs additional work and review. > > Unfortunately, CPL has a bunch of features which make direct use of > caller preferences (not just the capabilities stuff), and thus it > continues to have a normative reference to it. > > In order to make progress on CPL, and get it as an RFC already, I > discussed a plan with our ADs, Cullen, and the CPL authors, which we > would like working group input on: > > 1. We will remove CPL from the rfc-ed, and bring it back into iptel for > another revision. > > 2. In that revision, we will: > > A. remove the features that make CPL dependent on caller preferences, > B. convert the DTD to a schema, such that there is no loss of > interoperability with any implementations which are using the DTD C. > update references > D. typos > > We will NOT be introducing any other features or capabilities. All > changes are restricted to one of the above four groups. > > 3. These changes will be made fairly quickly (one month or so), and after > that, we will issue a wglc for the document, and then send it to iesg for > approval once more and reinsertion onto the rfc-ed queue. > > > Please provide input on whether you are in agreement or disagreement with > this plan. > > Thanks, > Jonathan R. > > -- > Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza > Chief Technology Officer Parsippany, NJ 07054-2711 > dynamicsoft > 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 ------------------------ David R. Oran Cisco Systems 7 Ladyslipper Lane Acton, MA 01720 Office: +1 978 264 2048 VoIP: +1 408 571 4576 Email: oran@cisco.com _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Thu Jul 10 16:34:29 2003 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 QAA20714 for ; Thu, 10 Jul 2003 16:34:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ai79-0005Nx-Q1 for iptel-archive@odin.ietf.org; Thu, 10 Jul 2003 16:34:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6AKY3VG020700 for iptel-archive@odin.ietf.org; Thu, 10 Jul 2003 16:34:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ai79-0005Nn-JH for iptel-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 16:34:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20706 for ; Thu, 10 Jul 2003 16:33:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ai77-00074P-00 for iptel-web-archive@ietf.org; Thu, 10 Jul 2003 16:34:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ai77-00074M-00 for iptel-web-archive@ietf.org; Thu, 10 Jul 2003 16:34:01 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ai76-0005NM-Vf; Thu, 10 Jul 2003 16:34:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ai6a-0005D6-3K for iptel@optimus.ietf.org; Thu, 10 Jul 2003 16:33:28 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20697 for ; Thu, 10 Jul 2003 16:33:23 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ai6X-000741-00 for iptel@ietf.org; Thu, 10 Jul 2003 16:33:26 -0400 Received: from auemail2.lucent.com ([192.11.223.163] helo=auemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19ai6W-00073m-00 for iptel@ietf.org; Thu, 10 Jul 2003 16:33:25 -0400 Received: from ihmail.ih.lucent.com (h135-1-218-70.lucent.com [135.1.218.70]) by auemail2.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h6AKWtP08447; Thu, 10 Jul 2003 15:32:55 -0500 (CDT) Received: from lucent.com (il0015vkg1.ih.lucent.com [135.185.173.147]) by ihmail.ih.lucent.com (8.11.6+Sun/EMS-1.5 sol2) id h6AKWl911157; Thu, 10 Jul 2003 15:32:47 -0500 (CDT) Message-ID: <3F0DCD62.70509@lucent.com> From: "Vijay K. Gurbani" Organization: Wireless Netwoks Group 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: Jonathan Rosenberg CC: list iptel Subject: Re: [Iptel] Getting CPL off of rfc-ed queue References: <3F0DB681.4000709@dynamicsoft.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 10 Jul 2003 15:32:34 -0500 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Jonathan Rosenberg wrote: > Please provide input on whether you are in agreement or disagreement > with this plan. Agreement, sounds reasonable. One question, though: > 2. In that revision, we will: > > A. remove the features that make CPL dependent on caller preferences, Will the removal of the caller preference features hobble CPL or limit is usability in any way? Thanks, - vijay -- Vijay K. Gurbani vkg@{lucent.com,research.bell-labs.com,acm.org} Wireless Networks Group/Internet Software and Services Lucent Technologies/Bell Labs Innovations, 2000 Lucent Lane, Rm 6G-440 Naperville, Illinois 60566 Voice: +1 630 224 0216 _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Thu Jul 10 17:01:58 2003 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 RAA21576 for ; Thu, 10 Jul 2003 17:01:58 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aiXl-00083n-4Y for iptel-archive@odin.ietf.org; Thu, 10 Jul 2003 17:01:33 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6AL1X5R030982 for iptel-archive@odin.ietf.org; Thu, 10 Jul 2003 17:01:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aiXl-00083d-0G for iptel-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 17:01:33 -0400 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 RAA21520 for ; Thu, 10 Jul 2003 17:01:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aiXG-0007wc-5f; Thu, 10 Jul 2003 17:01:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19aiWV-0007li-CL for iptel@optimus.ietf.org; Thu, 10 Jul 2003 17:00:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21375 for ; Thu, 10 Jul 2003 17:00:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19aiWT-0007FZ-00 for iptel@ietf.org; Thu, 10 Jul 2003 17:00:13 -0400 Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com) by ietf-mx with esmtp (Exim 4.12) id 19aiWR-0007D8-00 for iptel@ietf.org; Thu, 10 Jul 2003 17:00:12 -0400 Received: from dynamicsoft.com ([63.113.46.12]) by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id h6AKxjiB007829; Thu, 10 Jul 2003 16:59:45 -0400 (EDT) Message-ID: <3F0DD3BB.3000903@dynamicsoft.com> From: Jonathan Rosenberg Organization: dynamicsoft User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Vijay K. Gurbani" CC: list iptel Subject: Re: [Iptel] Getting CPL off of rfc-ed queue References: <3F0DB681.4000709@dynamicsoft.com> <3F0DCD62.70509@lucent.com> In-Reply-To: <3F0DCD62.70509@lucent.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 10 Jul 2003 16:59:39 -0400 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Vijay K. Gurbani wrote: > Jonathan Rosenberg wrote: > > > Please provide input on whether you are in agreement or disagreement > > with this plan. > > Agreement, sounds reasonable. One question, though: > >> 2. In that revision, we will: >> >> A. remove the features that make CPL dependent on caller preferences, > > > Will the removal of the caller preference features hobble CPL or > limit is usability in any way? TO my knowledge, no one is using these features of CPL. But, thats why we are polling the group. Do speak up if you think these capabilities are essential. Given the limited support caller prefs itself sees in products, I suspect there is really no usage. -Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza Chief Technology Officer Parsippany, NJ 07054-2711 dynamicsoft 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 From exim@www1.ietf.org Thu Jul 10 19:58:33 2003 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 TAA27363 for ; Thu, 10 Jul 2003 19:58:33 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19alIb-0005bp-RZ for iptel-archive@odin.ietf.org; Thu, 10 Jul 2003 19:58:06 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6ANw5JF021557 for iptel-archive@odin.ietf.org; Thu, 10 Jul 2003 19:58:05 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19alIb-0005bc-Nm for iptel-web-archive@optimus.ietf.org; Thu, 10 Jul 2003 19:58:05 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA27358 for ; Thu, 10 Jul 2003 19:58:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19alIZ-0000Yj-00 for iptel-web-archive@ietf.org; Thu, 10 Jul 2003 19:58:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19alIZ-0000Yg-00 for iptel-web-archive@ietf.org; Thu, 10 Jul 2003 19:58:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19alIX-0005at-8u; Thu, 10 Jul 2003 19:58:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19akSn-0001VW-Az for iptel@optimus.ietf.org; Thu, 10 Jul 2003 19:04:33 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26308 for ; Thu, 10 Jul 2003 19:04:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19akSj-0000II-00 for iptel@ietf.org; Thu, 10 Jul 2003 19:04:29 -0400 Received: from fep02-mail.bloor.is.net.cable.rogers.com ([66.185.86.72]) by ietf-mx with esmtp (Exim 4.12) id 19akSh-0000I5-00 for iptel@ietf.org; Thu, 10 Jul 2003 19:04:28 -0400 Received: from dizzy2 ([24.156.96.49]) by fep02-mail.bloor.is.net.cable.rogers.com (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP id <20030710230338.QELF384956.fep02-mail.bloor.is.net.cable.rogers.com@dizzy2>; Thu, 10 Jul 2003 19:03:38 -0400 Message-ID: <003c01c34738$4b9b1060$31609c18@ym.phub.net.cable.rogers.com> From: "David Zinman" To: "Romascanu, Dan \(Dan\)" , Cc: "Jon Peterson \(E-mail\)" , "Bert Wijnen \(E-mail\)" , , "Jonathan Rosenberg" , References: Subject: Re: [Iptel] Comments on draft-ietf-iptel-trip-mib-06.txt MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0039_01C34716.C42DE2E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Authentication-Info: Submitted using SMTP AUTH LOGIN at fep02-mail.bloor.is.net.cable.rogers.com from [24.156.96.49] using ID at Thu, 10 Jul 2003 19:03:33 -0400 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 10 Jul 2003 19:09:20 -0400 This is a multi-part message in MIME format. ------=_NextPart_000_0039_01C34716.C42DE2E0 Content-Type: text/plain; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Comments on draft-ietf-iptel-trip-mib-06.txtFixes in = draft-ietf-iptel-trip-mib-07.txt ----- Original Message -----=20 From: Romascanu, Dan (Dan)=20 To: iptel@ietf.org=20 Cc: Jon Peterson (E-mail) ; Bert Wijnen (E-mail) ; David Zinman ; = fluffy@cisco.com ; jdrosen@dynamicsoft.com ; drwalker@ss8.com ; = jianping@ss8.com=20 Sent: Sunday, July 06, 2003 5:18 AM Subject: [Iptel] Comments on draft-ietf-iptel-trip-mib-06.txt Here are my comments on the latest TRIP MIB I-D. I congratulate the = authors for the considerable improvement of the document, and thank them = for taking into account most of my comments in the review of the = previous version. There are still a few problems: 1) smilint complains of two indices possibly exceeding the OID size = limitation: TRIP-MIB.txt:328: [5] {index-exceeds-too-large} warning: index of row = `tripRouteTypeEntry' can exceed OID size limit by 138 subidentifier(s) TRIP-MIB.txt:511: [5] {index-exceeds-too-large} warning: index of row = `tripPeerEntry' can exceed OID size limit by 136 subidentifier(s) This is probably because of use of multiple indices with a syntax of = OBJECT STRING or OBJECT IDENTIFIER. According to Section 4.6.5 in = http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-= 01.txt, ' It is RECOMMENDED that all MIB documents make explicit any = limitations on index component lengths that management software must = observe. This may be done either by including SIZE constraints on the = index components or by specifying applicable constraints in the = conceptual row DESCRIPTION clause or in the surrounding documentation. ' Fixed, with appropriate comments. =20 2) One of my comments in the review of draft-05 was about the need to = improve the DESCRIPTION clause of tripRouteUnknown. If I were an = implementer, I still do not know what this object is supposed to = contain, and how the information is encoded. I have changed this, with the help of Jonathan Rosenberg to make it much = clearer. 3) Two of comments in the previous review were ignored. I would not = block this document because of these, but I still think that they were = valid, and the authors would like to consider following them for = improved readability and consistency. These comments were: '4. The readability of the document would be much improved if an = abbreviation section would be included. Some of the abbreviations are = not detailed, some other are explained only after a few occurrences in = the text (LS, ITAD) -- LS is now explained at the first occurrence, but = ITAD is still not explained. -- I explain the ITAD in section 5.1 of the draft, before the MIB = definitions in section 6. I will add the description to the MIB too. 10. 'location server' in the DESCRIPTION clause of tripPeerOutUpdates = is inconsistent with the other clauses in the same table where it is = abbreviated.' Missed that one. 4) You would like to swap the order of the two phrases that compose = Section 4, and remove the double reference in the same section. Done. 5) Year in copyright notes and the Copyright Section should be updated = to 2003. done Regards, Dan DZ ------=_NextPart_000_0039_01C34716.C42DE2E0 Content-Type: text/html; charset="windows-1255" Content-Transfer-Encoding: quoted-printable Comments on draft-ietf-iptel-trip-mib-06.txt
Fixes in=20 draft-ietf-iptel-trip-mib-07.txt
----- Original Message -----
From:=20 Romascanu, Dan=20 (Dan)
Cc: Jon Peterson (E-mail) ; = Bert = Wijnen=20 (E-mail) ; David Zinman ; fluffy@cisco.com ;=20 jdrosen@dynamicsoft.com ; = drwalker@ss8.com ;=20 jianping@ss8.com=20
Sent: Sunday, July 06, 2003 = 5:18 AM
Subject: [Iptel] Comments on=20 draft-ietf-iptel-trip-mib-06.txt

Here are my comments on the = latest TRIP MIB=20 I-D. I congratulate the authors for the considerable improvement of = the=20 document, and thank them for taking into account most of my comments = in the=20 review of the previous version.

There are still a few = problems:

1) smilint complains of two = indices=20 possibly exceeding the OID size limitation:

TRIP-MIB.txt:328: [5]=20 {index-exceeds-too-large} warning: index of row `tripRouteTypeEntry' = can=20 exceed OID size limit by 138 subidentifier(s)

TRIP-MIB.txt:511: [5]=20 {index-exceeds-too-large} warning: index of row `tripPeerEntry' can = exceed OID=20 size limit by 136 subidentifier(s)

This is probably because of = use of multiple=20 indices with a  syntax of OBJECT STRING or OBJECT IDENTIFIER. = According=20 to  Section 4.6.5 in http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-re= view-guidelines-01.txt,

' It is=20 RECOMMENDED that all MIB documents make explicit any limitations on = index=20 component lengths that management software must observe. This may be = done=20 either by including SIZE constraints on the index components or by = specifying=20 applicable constraints in the conceptual row DESCRIPTION clause or in = the=20 surrounding documentation. '

Fixed, with = appropriate=20 comments. 

2)  One = of my comments=20 in the review of draft-05 was about the need to improve the = DESCRIPTION clause=20 of tripRouteUnknown. If I were an implementer, I still do not know = what this=20 object is supposed to contain, and how the information is=20 encoded.

I have changed = this, with the=20 help of Jonathan Rosenberg to make it much clearer.


3) Two of = comments in the=20 previous review were ignored. I would not block this document because = of=20 these, but I still think that they were valid, and the authors would = like to=20 consider following them for improved readability and=20 consistency.

These = comments=20 were:

'4. The = readability of the=20 document would be much improved if an abbreviation section would be = included.=20 Some of the abbreviations are not detailed, some other are explained = only=20 after a few occurrences in the text (LS, ITAD) -- LS is now explained = at the=20 first occurrence, but ITAD is still not explained.=20 --

I explain the = ITAD in section=20 5.1 of the draft, before the MIB definitions in section 6. I will add = the=20 description to the MIB too.

10. 'location = server' in the=20 DESCRIPTION clause of tripPeerOutUpdates is inconsistent with the = other=20 clauses in the same table where it is=20 abbreviated.'

Missed that=20 one.

4) You would = like to swap the=20 order of the two phrases that compose Section 4, and remove the double = reference in the same section.

Done.

5) Year in = copyright notes=20 and the Copyright Section should be updated to=20 2003.

done

Regards,

Dan

DZ

------=_NextPart_000_0039_01C34716.C42DE2E0-- _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Fri Jul 11 04:05:36 2003 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 EAA20138 for ; Fri, 11 Jul 2003 04:05:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19astx-0000tg-1H for iptel-archive@odin.ietf.org; Fri, 11 Jul 2003 04:05:09 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6B858Zj003440 for iptel-archive@odin.ietf.org; Fri, 11 Jul 2003 04:05:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19astv-0000tO-Fi for iptel-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 04:05:07 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20129 for ; Fri, 11 Jul 2003 04:05:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19asts-0003LP-00 for iptel-web-archive@ietf.org; Fri, 11 Jul 2003 04:05:04 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19asts-0003LM-00 for iptel-web-archive@ietf.org; Fri, 11 Jul 2003 04:05:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19astp-0000qS-TZ; Fri, 11 Jul 2003 04:05:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19astJ-0000p6-VU for iptel@optimus.ietf.org; Fri, 11 Jul 2003 04:04:30 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20092 for ; Fri, 11 Jul 2003 04:04:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19astH-0003LE-00 for iptel@ietf.org; Fri, 11 Jul 2003 04:04:27 -0400 Received: from [216.65.43.254] (helo=w13242.hostcentric.net) by ietf-mx with smtp (Exim 4.12) id 19astG-0003LA-00 for iptel@ietf.org; Fri, 11 Jul 2003 04:04:26 -0400 Received: (qmail 16060 invoked by alias); 11 Jul 2003 08:04:18 -0000 Received: from unknown (HELO indigosw.com) (217.136.220.14) by 0 with SMTP; 11 Jul 2003 08:04:18 -0000 Message-ID: <3F0E6F80.3060506@indigosw.com> From: dENIS Vandersteene Organization: Indigo Software User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: fr-BE,en MIME-Version: 1.0 To: Jonathan Rosenberg CC: list iptel Subject: Re: [Iptel] Getting CPL off of rfc-ed queue References: <3F0DB681.4000709@dynamicsoft.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 11 Jul 2003 10:04:16 +0200 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi, Seems a very good idea indeed, so that CPL can at least become a "real" standard... By the way, the draft lennox-sip-reg-payload-01.txt (Transporting User Control Information in SIP REGISTER Payloads, which gives a way to load CPL scripts on a server via REGISTER messages) is out of date since a long time. The authors told me a while ago that this mechanism would be replaced by another one... Is this work still in progress, or will the draft be updated in a near future? dENIS Jonathan Rosenberg wrote: > Folks, > > The iptel group completed the CPL spec, and got it approved by IESG, > quite a long time ago (well over a year). The CPL spec is still in the > rfc editors queue, blocked on a reference to the caller preferences > spec. As you may know, caller prefs has had a rocky history in the SIP > group, and its not clear that its going to be done really soon either. > As a result, caller prefs was split in half. One half covers > capabilities, which is more stable, and the other half, the actual > caller preferences, which needs additional work and review. > > Unfortunately, CPL has a bunch of features which make direct use of > caller preferences (not just the capabilities stuff), and thus it > continues to have a normative reference to it. > > In order to make progress on CPL, and get it as an RFC already, I > discussed a plan with our ADs, Cullen, and the CPL authors, which we > would like working group input on: > > 1. We will remove CPL from the rfc-ed, and bring it back into iptel > for another revision. > > 2. In that revision, we will: > > A. remove the features that make CPL dependent on caller preferences, > B. convert the DTD to a schema, such that there is no loss of > interoperability with any implementations which are using the DTD > C. update references > D. typos > > We will NOT be introducing any other features or capabilities. All > changes are restricted to one of the above four groups. > > 3. These changes will be made fairly quickly (one month or so), and > after that, we will issue a wglc for the document, and then send it to > iesg for approval once more and reinsertion onto the rfc-ed queue. > > > Please provide input on whether you are in agreement or disagreement > with this plan. -- ......................................................... Vandersteene dENIS Software Engineer Indigo Software Phone: +32 2 235 09 41 rue wiertz 50 Fax : +32 2 280 26 76 1050 Bruxelles dENIS@indigosw.com Belgium http://www.indigosw.com ......................................................... _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Fri Jul 11 09:22:37 2003 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 JAA28544 for ; Fri, 11 Jul 2003 09:22:37 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19axqk-00018X-FQ for iptel-archive@odin.ietf.org; Fri, 11 Jul 2003 09:22:10 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6BDMABM004363 for iptel-archive@odin.ietf.org; Fri, 11 Jul 2003 09:22:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19axqk-00018I-Bf for iptel-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 09:22:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28540 for ; Fri, 11 Jul 2003 09:22:01 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19axqd-0005bE-00 for iptel-web-archive@ietf.org; Fri, 11 Jul 2003 09:22:03 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19axqd-0005bB-00 for iptel-web-archive@ietf.org; Fri, 11 Jul 2003 09:22:03 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19axqb-00017r-14; Fri, 11 Jul 2003 09:22:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19axq9-00017a-UO for iptel@optimus.ietf.org; Fri, 11 Jul 2003 09:21:33 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA28531 for ; Fri, 11 Jul 2003 09:21:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19axq8-0005b8-00 for iptel@ietf.org; Fri, 11 Jul 2003 09:21:32 -0400 Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 19axq7-0005b2-00 for iptel@ietf.org; Fri, 11 Jul 2003 09:21:31 -0400 Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15]) by sj-core-3.cisco.com (8.12.6/8.12.6) with ESMTP id h6BDKxpZ015857 for ; Fri, 11 Jul 2003 06:21:00 -0700 (PDT) Received: from [10.0.1.6] (sjc-vpn3-309.cisco.com [10.21.65.53]) by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AFY06902; Fri, 11 Jul 2003 06:20:58 -0700 (PDT) User-Agent: Microsoft-Entourage/10.1.1.2418 From: Cullen Jennings To: Message-ID: In-Reply-To: <3F0DB681.4000709@dynamicsoft.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Iptel] draft-ietf-iptel-trip-mib-07 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 10 Jul 2003 22:42:46 -0700 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Until it shows up in the directory (after the Vienna meeting) there is a new version of the draft at http://www.softarmor.com/iptel/drafts/draft-ietf-iptel-trip-mib-07.txt _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Fri Jul 11 10:57:34 2003 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 KAA02601 for ; Fri, 11 Jul 2003 10:57:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19azKe-0000Ru-Nz for iptel-archive@odin.ietf.org; Fri, 11 Jul 2003 10:57:09 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6BEv8TT001725 for iptel-archive@odin.ietf.org; Fri, 11 Jul 2003 10:57:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19azKe-0000Rj-Kt for iptel-web-archive@optimus.ietf.org; Fri, 11 Jul 2003 10:57:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02587 for ; Fri, 11 Jul 2003 10:57:02 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19azKa-0006Fe-00 for iptel-web-archive@ietf.org; Fri, 11 Jul 2003 10:57:04 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19azKa-0006Fb-00 for iptel-web-archive@ietf.org; Fri, 11 Jul 2003 10:57:04 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19azKW-0000QX-V5; Fri, 11 Jul 2003 10:57:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19azJx-0000Ov-Mk for iptel@optimus.ietf.org; Fri, 11 Jul 2003 10:56:25 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02545 for ; Fri, 11 Jul 2003 10:56:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19azJt-0006Es-00 for iptel@ietf.org; Fri, 11 Jul 2003 10:56:21 -0400 Received: from [63.113.44.69] (helo=mail3.dynamicsoft.com) by ietf-mx with esmtp (Exim 4.12) id 19azJr-0006DV-00 for iptel@ietf.org; Fri, 11 Jul 2003 10:56:20 -0400 Received: from dynamicsoft.com ([63.113.46.12]) by mail3.dynamicsoft.com (8.12.8/8.12.1) with ESMTP id h6BEtpiB008549; Fri, 11 Jul 2003 10:55:51 -0400 (EDT) Message-ID: <3F0ECFF1.9060006@dynamicsoft.com> From: Jonathan Rosenberg Organization: dynamicsoft User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dENIS Vandersteene CC: list iptel Subject: Re: [Iptel] Getting CPL off of rfc-ed queue References: <3F0DB681.4000709@dynamicsoft.com> <3F0E6F80.3060506@indigosw.com> In-Reply-To: <3F0E6F80.3060506@indigosw.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 11 Jul 2003 10:55:45 -0400 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit dENIS Vandersteene wrote: > Hi, > > Seems a very good idea indeed, so that CPL can at least become a "real" > standard... > > By the way, the draft lennox-sip-reg-payload-01.txt (Transporting User > Control Information in SIP REGISTER Payloads, which gives a way to load > CPL scripts on a server via REGISTER messages) is out of date since a > long time. The authors told me a while ago that this mechanism would be > replaced by another one... Is this work still in progress, or will the > draft be updated in a near future? I have actually been thinkign about this. I always thought that setting of CPL was a provisioning operation, and such, seemed like a good match for xcap: http://www.ietf.org/internet-drafts/draft-ietf-simple-xcap-00.txt which we are considering in simple for setting buddy lists and authorization policy. Also under consideration for usage in setting coference policies. You'd need to define an application usage for CPL. Would be pretty easy. -Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 600 Lanidex Plaza Chief Technology Officer Parsippany, NJ 07054-2711 dynamicsoft 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 From exim@www1.ietf.org Thu Jul 24 12:32:40 2003 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 MAA13134 for ; Thu, 24 Jul 2003 12:32:40 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fj0p-0006tQ-RT for iptel-archive@odin.ietf.org; Thu, 24 Jul 2003 12:32:15 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6OGWFHj026495 for iptel-archive@odin.ietf.org; Thu, 24 Jul 2003 12:32:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fj0p-0006tG-OD for iptel-web-archive@optimus.ietf.org; Thu, 24 Jul 2003 12:32:15 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13127 for ; Thu, 24 Jul 2003 12:32:10 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19fj0o-0007Jq-00 for iptel-web-archive@ietf.org; Thu, 24 Jul 2003 12:32:14 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19fj0i-0007Jh-00 for iptel-web-archive@ietf.org; Thu, 24 Jul 2003 12:32:08 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fj0b-0006sV-Ho; Thu, 24 Jul 2003 12:32:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19fj0J-0006s1-9U for iptel@optimus.ietf.org; Thu, 24 Jul 2003 12:31:43 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13104; Thu, 24 Jul 2003 12:31:37 -0400 (EDT) Message-Id: <200307241631.MAA13104@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: iptel@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Iptel] I-D ACTION:draft-ietf-iptel-trip-mib-07.txt 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 24 Jul 2003 12:31:37 -0400 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IP Telephony Working Group of the IETF. Title : Management Information Base for Telephony Routing over IP (TRIP) Author(s) : D. Zinman, D. Walker, J. Jiang Filename : draft-ietf-iptel-trip-mib-07.txt Pages : 45 Date : 2003-7-24 This memo defines a portion of the MIB (Management Information Base) module for use with network management protocols in the Internet community. In particular, it describes a set of managed objects that are used to manage for TRIP (Telephony Routing over IP) devices A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-iptel-trip-mib-07.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-iptel-trip-mib-07.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-iptel-trip-mib-07.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-7-24122632.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-iptel-trip-mib-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-iptel-trip-mib-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-7-24122632.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel From exim@www1.ietf.org Wed Jul 30 20:01:29 2003 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 UAA24407 for ; Wed, 30 Jul 2003 20:01:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19i0sR-0003Ll-Ab for iptel-archive@odin.ietf.org; Wed, 30 Jul 2003 20:01:03 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h6V013FG012871 for iptel-archive@odin.ietf.org; Wed, 30 Jul 2003 20:01:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19i0sR-0003LW-6R for iptel-web-archive@optimus.ietf.org; Wed, 30 Jul 2003 20:01:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24385 for ; Wed, 30 Jul 2003 20:00:58 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19i0sP-0005ZC-00 for iptel-web-archive@ietf.org; Wed, 30 Jul 2003 20:01:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19i0sO-0005Z8-00 for iptel-web-archive@ietf.org; Wed, 30 Jul 2003 20:01:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19i0sO-0003L3-FF; Wed, 30 Jul 2003 20:01:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19i0rh-0003IV-2v for iptel@optimus.ietf.org; Wed, 30 Jul 2003 20:00:17 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24364 for ; Wed, 30 Jul 2003 20:00:12 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19i0rf-0005YX-00 for iptel@ietf.org; Wed, 30 Jul 2003 20:00:15 -0400 Received: from sj-core-4.cisco.com ([171.68.223.138]) by ietf-mx with esmtp (Exim 4.12) id 19i0re-0005Y6-00 for iptel@ietf.org; Wed, 30 Jul 2003 20:00:14 -0400 Received: from mira-sjc5-e.cisco.com (IDENT:mirapoint@mira-sjc5-e.cisco.com [171.71.163.15]) by sj-core-4.cisco.com (8.12.6/8.12.6) with ESMTP id h6UNxIpp016284; Wed, 30 Jul 2003 16:59:19 -0700 (PDT) Received: from [128.107.170.129] ([128.107.170.129]) by mira-sjc5-e.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AGP34221; Wed, 30 Jul 2003 16:59:14 -0700 (PDT) User-Agent: Microsoft-Entourage/10.1.1.2418 From: Cullen Jennings To: CC: Jonathan Rosenberg , Henning Schulzrinne , Cullen Jennings Message-ID: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Iptel] WGLC for rfc2806bis 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: , List-Id: IP Telephony List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 30 Jul 2003 16:59:14 -0700 Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit I would like to working group last call http://www.ietf.org/internet-drafts/draft-ietf-iptel-rfc2806bis-02.txt The WGLC will end on Friday, August 22. I would like to point out that future tel extensions can include a tel parameter flag that indicates a ENUM dip is not needed. This will optimize situations where multiple enum dips are done by different network elements during a single call. I believe the working group consensus is that ENUM lookups MAY be performed on tel URLs and a separate enum URL is not needed. Thanks, Cullen _______________________________________________ Iptel mailing list Iptel@ietf.org https://www.ietf.org/mailman/listinfo/iptel