From extest-admin@lists.bell-labs.com Fri Mar 1 05:38:13 2002 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 FAA05911 for ; Fri, 1 Mar 2002 05:38:13 -0500 (EST) 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 g21AcFM11607 for ; Fri, 1 Mar 2002 05:38:15 -0500 Date: Fri, 1 Mar 2002 05:38:15 -0500 Message-Id: <200203011038.g21AcFM11607@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 iptel-admin@lists.bell-labs.com Fri Mar 1 14:32:55 2002 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 OAA18287 for ; Fri, 1 Mar 2002 14:32:54 -0500 (EST) 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 g21JW5M14286; Fri, 1 Mar 2002 14:32:05 -0500 Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49]) by share.research.bell-labs.com (8.11.6/8.11.6) with SMTP id g21JVoM14273 for ; Fri, 1 Mar 2002 14:31:50 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Fri Mar 1 14:30:05 EST 2002 Received: by lists.bell-labs.com (Postfix) id 1BAA54439E; Fri, 1 Mar 2002 14:29:50 -0500 (EST) Delivered-To: iptel@sunny.research.bell-labs.com Received: from grubby.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.9]) by lists.bell-labs.com (Postfix) with ESMTP id ECD824439D for ; Fri, 1 Mar 2002 14:29:49 -0500 (EST) Received: from dusty.research.bell-labs.com (dusty.research.bell-labs.com [135.104.2.7]) by grubby.research.bell-labs.com (8.11.6/8.11.6) with SMTP id g21JTmt85195 for ; Fri, 1 Mar 2002 14:29:48 -0500 (EST) Received: from sj-msg-core-2.cisco.com ([171.69.24.11]) by dusty; Fri Mar 1 14:25:57 EST 2002 Received: from mira-sjc5-9.cisco.com (mira-sjc5-9.cisco.com [171.71.163.32]) by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id g21JTkZ26452 for ; Fri, 1 Mar 2002 11:29:46 -0800 (PST) Received: from oranlt ([161.44.238.50]) by mira-sjc5-9.cisco.com (Mirapoint) with ESMTP id ACD67585; Fri, 1 Mar 2002 11:29:54 -0800 (PST) From: "David R. Oran" To: Organization: Cisco Systems Message-ID: <046601c1c157$73027160$32ee2ca1@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 In-Reply-To: <200202281206.HAA17909@ietf.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Subject: [IPTEL] RE:draft-burg-iptel-trip-gw-id-00.txt Sender: iptel-admin@lists.bell-labs.com Errors-To: iptel-admin@lists.bell-labs.com X-BeenThere: iptel@lists.bell-labs.com X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Date: Fri, 1 Mar 2002 14:29:46 -0500 Content-Transfer-Encoding: 7bit This draft completely loses me. What is in here that cannot be derived from the FQDN of the gateway? I'm particularly worried about the idea, if I read this correctly, than non-globally unique information is proposed to be propagated in TRIP-GW. This would be like an IP router saying "I can reach stuff that has the following in the last byte of the IP address. Here's some arbitrary string 'Chicago'. I hope you can figure out the correct prefix to apply to these IP addresses based on my telling you 'Chicago'." Hope I'm misreading this short ID. Dave. _______________________________________________ IPTEL mailing list IPTEL@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/iptel From iptel-admin@lists.bell-labs.com Mon Mar 4 17:52:30 2002 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 RAA28802 for ; Mon, 4 Mar 2002 17:52:29 -0500 (EST) 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 g24MoFM05144; Mon, 4 Mar 2002 17:50:15 -0500 Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49]) by share.research.bell-labs.com (8.11.6/8.11.6) with SMTP id g24MnsM05122 for ; Mon, 4 Mar 2002 17:49:54 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Mon Mar 4 17:48:13 EST 2002 Received: by lists.bell-labs.com (Postfix) id DBD6D4439E; Mon, 4 Mar 2002 17:48:02 -0500 (EST) Delivered-To: iptel@sunny.research.bell-labs.com Received: from scummy.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.10]) by lists.bell-labs.com (Postfix) with ESMTP id AD7CC4439D for ; Mon, 4 Mar 2002 17:48:02 -0500 (EST) Received: from dusty.research.bell-labs.com (dusty.research.bell-labs.com [135.104.2.7]) by scummy.research.bell-labs.com (8.11.6/8.11.6) with SMTP id g24Mm1k35345 for ; Mon, 4 Mar 2002 17:48:01 -0500 (EST) Received: from imo-r05.mx.aol.com ([152.163.225.101]) by dusty; Mon Mar 4 17:44:06 EST 2002 Received: from Mpierce1@aol.com by imo-r05.mx.aol.com (mail_out_v32.5.) id r.172.4849421 (25510) for ; Mon, 4 Mar 2002 17:47:52 -0500 (EST) From: Mpierce1@aol.com Message-ID: <172.4849421.29b55396@aol.com> To: iptel@lists.bell-labs.com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 138 Subject: [IPTEL] Comments on RFC2806bis Sender: iptel-admin@lists.bell-labs.com Errors-To: iptel-admin@lists.bell-labs.com X-BeenThere: iptel@lists.bell-labs.com X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Date: Mon, 4 Mar 2002 17:47:50 EST Content-Transfer-Encoding: 7bit To all, The latest draft of the revision to rfc2806 in draft-antti-rfc2806bis-02 really looks good. I have the following comments on some of the text: 2. In the 7th paragraph (beginning "The approach pursued...") Extensions of a PBX can be specified if they are a part of the global number (i.e., when DID is used). Propose that the words "when direct inward dialing is not used" be added after "PBX". 5.1.2 Maybe it would be helpful to emphasize that, while the uri format does not support alphabetic characters, it is expected that the user agent would support entry of such characters by the user and translation based on some standard. The mapping of alphabetic characters to numeric digits is in fact standardized in E.161 as well as in American National Standard T1.703-1995 (R1999). However, it is still a good idea to not use this mapping as a basis for the uri. It is suggested that this final sentence be: "The URI format does not support this since the mapping of alphabetic characters to nurmeric digits is not completely uniform internationally, although there are standards addressing this mapping." It is unclear why the second paragraph states that "F is currently not used." and "These do not designate the fourth column of the DTMF tone matrix." The term "Terminal number" is not the usual one used. These statements lead to confusion. In fact, ISUP defines the additional six values as "code 11, code 12, ST, and 3 spares", not A-F. It uses the "1111" or "F" value. As shown in the ABNF, the digits of the global-number are limited to 0-9. While the digits of the local-number are shown as HEXDIGIT, it is unknown where this would be used for a tel:uri. It is suggested that this paragraph be reworded to: "Since called and calling party numbers are encoded in BCD in ISUP, this allows for six additional values per digit, sometimes represented as the HEX characters A through F. However, in accordance with E.164, they may not be included in global numbers. Their use in local numbers is not defined, but is not prohibited." 5.1.3 In the first paragraph, the phrase "if the client is properly configured" should be deleted. International numbers themselves are unambiguous. It is unrelated to the "configuration" of "the client". In the second paragraph, it is unclear why the second sentence states that "some numbers may work from several networks but not from the whole world; these SHOULD be written in international form". Since it follows the first sentence, it is presumed to be referring to "local numbers". It is impossible to write a local number (which does not work everywhere) in "international form". 7.3 3rd paragraph: It is unknown why "/" is mentioned here as a possible character separator. In fact, in E.123, the "/" means something else. This mention here may confuse people. 7.4 While this section is interesting, it has nothing to do with the subject of the document and should be deleted. It might confuse someone into thinking that it has some impact on the uri. 7.5 To avoid confusion, the number 00123456789 in the example should not be referred to as a "local phone number". This sentence should say: "Tel URIs should, in general, not contain the local dialing prefixes such as the "00" in 00123456789..." It might also be helpful here to mention that, according to E.164, the "+" in the writing of the international number actually means that an international prefix is required ("00" in this example). 8. The last example in this section should show a valid E.164 number with a valid US area code, even though the number/letters displayed may contain extraneous characters to spell a word, as is the common practice (at least in the US). I would expect that an implementation might discard a uri that it knows to be incorrect, such as one beginning with +1 that is not followed by exactly 10 digits. (Not required to do this, but it might.) The example should be: a href="tel:+17034383785">1-703-IETF-RULZ-OK; Tue, 5 Mar 2002 16:05:14 -0500 (EST) 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 g25L4CM11221; Tue, 5 Mar 2002 16:04:12 -0500 Received: from dirty.research.bell-labs.com (dirty.research.bell-labs.com [204.178.16.6]) by share.research.bell-labs.com (8.11.6/8.11.6) with SMTP id g25L3jM11208 for ; Tue, 5 Mar 2002 16:03:45 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Tue Mar 5 16:03:48 EST 2002 Received: by lists.bell-labs.com (Postfix) id 057584439E; Tue, 5 Mar 2002 16:03:31 -0500 (EST) Delivered-To: iptel@sunny.research.bell-labs.com Received: from grubby.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.9]) by lists.bell-labs.com (Postfix) with ESMTP id CB4464439D for ; Tue, 5 Mar 2002 16:03:30 -0500 (EST) Received: from dusty.research.bell-labs.com (dusty.research.bell-labs.com [135.104.2.7]) by grubby.research.bell-labs.com (8.11.6/8.11.6) with SMTP id g25L3To32659 for ; Tue, 5 Mar 2002 16:03:29 -0500 (EST) Received: from tomts23-srv.bellnexxia.net ([209.226.175.185]) by dusty; Tue Mar 5 15:59:32 EST 2002 Received: from dizzy2 ([64.230.113.135]) by tomts23-srv.bellnexxia.net (InterMail vM.4.01.03.23 201-229-121-123-20010418) with SMTP id <20020305210104.JKCB24345.tomts23-srv.bellnexxia.net@dizzy2> for ; Tue, 5 Mar 2002 16:01:04 -0500 Message-ID: <005301c1c489$b2cb0de0$9772fea9@dizzy2> From: "David Zinman" To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0050_01C1C45F.C6D0E280" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [IPTEL] I-D ACTION:draft-ietf-iptel-trip-mib-02.txt Sender: iptel-admin@lists.bell-labs.com Errors-To: iptel-admin@lists.bell-labs.com X-BeenThere: iptel@lists.bell-labs.com X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Date: Tue, 5 Mar 2002 16:06:57 -0500 This is a multi-part message in MIME format. ------=_NextPart_000_0050_01C1C45F.C6D0E280 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit 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-02.txt Pages : 43 Date : 04-Mar-02 This memo defines a portion of the Management Information Base (MIB) 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 Telephony Routing over IP (TRIP) [RFC3219] devices. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-iptel-trip-mib-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-trip-mib-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-trip-mib-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_000_0050_01C1C45F.C6D0E280 Content-Type: application/octet-stream; name="ATT00075.dat" Content-Disposition: attachment; filename="ATT00075.dat" Content-Transfer-Encoding: 7bit Content-Type: text/plain Content-ID: <20020304133428.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-iptel-trip-mib-02.txt ------=_NextPart_000_0050_01C1C45F.C6D0E280 Content-Type: text/plain; name="draft-ietf-iptel-trip-mib-02.txt" Content-Disposition: attachment; filename="draft-ietf-iptel-trip-mib-02.txt" Content-Transfer-Encoding: 7bit Content-Type: text/plain Content-ID: <20020304133428.I-D@ietf.org> ------=_NextPart_000_0050_01C1C45F.C6D0E280-- _______________________________________________ IPTEL mailing list IPTEL@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/iptel From consultoriaemp7g@yahoo.com.mx Wed Mar 6 15:01:30 2002 Received: from smtp.prodigy.net.mx (dfproxy00.prodigy.net.mx [148.235.168.49] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02048 for ; Wed, 6 Mar 2002 15:01:29 -0500 (EST) Received: from frezzer (du-148-233-89-136.prodigy.net.mx [148.233.89.136]) by SMTP.Prodigy.Net.mx (Sun Internet Mail Server sims.4.0.2001.07.26.11.50.p9) with SMTP id <0GSK00J5XIE3NB@SMTP.Prodigy.Net.mx>; Wed, 6 Mar 2002 14:04:14 -0600 (CST) Date: Wed, 06 Mar 2002 13:58:12 -0600 From: "Lic. Alfredo Martinez Zepeda." Subject: UNICO DIA 16 DE MARZO, SEMINARIO EL CERRADOR DE VENTAS. To: iptel-archive@ietf.org Reply-to: consultoriaemp7@yahoo.com.mx Message-id: <0GSK00J6OIEZNB@SMTP.Prodigy.Net.mx> MIME-version: 1.0 X-Mailer: Mailer Signature Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 8BIT Content-Transfer-Encoding: 8BIT SEMINARIO EL CERRADOR PROFESIONAL DE VENTAS Temario: 1. Los factores claves para lograr un buen control del proceso de ventas. 2. Como incrementar los ingresos de su empresa por medio de un excelente control del cierre de ventas. 3. La importancia de la comunicacion efectiva en el cierre de ventas. 4. Como interesar al cliente en nuestro producto o servicio. 5. Como manejar en forma experta las objeciones del cliente. 6. Los pasos exactos para lograr el cierre de ventas. 7. Como incrementar su porcentaje de cierres de ventas. 8. Profesionalismo en ventas. 9. Los ingredientes claves para triunfar en ventas. 10. Ejercicios practicos en cada uno de los temas expuestos. Los ejercicios estan dirigidos a la aplicacion de los conocimientos aprendidos para lograr resultados de inmediato. Fecha: Sabado 16 de Marzo del 2002 Lugar: Hotel Bristol, Salon Bristol, Plaza Necaxa No. 17 Rio Panuco esq. Rio Sena, Col. Cuauhtemoc, D.F. Duracion: 8 horas, 50% del tiempo se dedica a la realizacion de ejercicios practicos. Horario: Seminario de las 9:00 A.M. a las 18:30 P.M. Dirigido a: Ejecutivos de ventas, vendedores y propietarios de negocios. Inversion: $2,100.00 por participante (mas I.V.A.) Incluye: Material de apoyo Coffee Breaks y comida. Conferencista Lic. Alfredo Martinez Zepeda. CON MAS DE 7 ANOS DE EXPERIENCIA CAPACITANDO A MILES DE VENDEDORES PARA LA INDUSTRIA. RESERVE HOY MISMO TEL: 5543 5961 y 5543 4061 CON LAURA AGUILAR DIRECTORA DE RELACIONES PUBLICAS, CONSULTORIA EMPRESARIAL PD: Conforme a las leyes nacionales como internacionales este e-mail no podrá ser considerado como SPAM si incluye un procedimiento para ser removido de la lista. Si desea ser removido envienos un e-mail a consultoriaemp7@yahoo.com.mx indicandonos a que correo le hemos contactado y en el asunto indique "REMOVER DE LA LISTA" From iptel-admin@lists.bell-labs.com Fri Mar 8 02:31:51 2002 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 CAA24196 for ; Fri, 8 Mar 2002 02:31:51 -0500 (EST) 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 g287IXM26491; Fri, 8 Mar 2002 02:18:37 -0500 Received: from dirty.research.bell-labs.com (dirty.research.bell-labs.com [204.178.16.6]) by share.research.bell-labs.com (8.11.6/8.11.6) with SMTP id g287HiM26478 for ; Fri, 8 Mar 2002 02:17:44 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Fri Mar 8 02:16:55 EST 2002 Received: by lists.bell-labs.com (Postfix) id 98D584439E; Fri, 8 Mar 2002 02:16:39 -0500 (EST) Delivered-To: iptel@sunny.research.bell-labs.com Received: from scummy.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.10]) by lists.bell-labs.com (Postfix) with ESMTP id 6A7D44439D for ; Fri, 8 Mar 2002 02:16:39 -0500 (EST) Received: from dusty.research.bell-labs.com (dusty.research.bell-labs.com [135.104.2.7]) by scummy.research.bell-labs.com (8.11.6/8.11.6) with SMTP id g287Gck59331 for ; Fri, 8 Mar 2002 02:16:38 -0500 (EST) Received: from mail3.dynamicsoft.com ([63.113.44.69]) by dusty; Fri Mar 8 02:12:41 EST 2002 Received: from dynamicsoft.com ([63.113.46.68]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g287HN6Y029100 for ; Fri, 8 Mar 2002 02:17:25 -0500 (EST) Message-ID: <3C886549.67696357@dynamicsoft.com> From: Jonathan Rosenberg Organization: dynamicsoft X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: list iptel Subject: Re: [IPTEL] A proposal for moving iptel forward References: <3C75B290.386DA141@dynamicsoft.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: iptel-admin@lists.bell-labs.com Errors-To: iptel-admin@lists.bell-labs.com X-BeenThere: iptel@lists.bell-labs.com X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Date: Fri, 08 Mar 2002 02:16:25 -0500 Content-Transfer-Encoding: 7bit It seems that there is strong consensus to move forward with my proposed plan of action. As such, it is appropriate to now begin discussion on technical open issues or comments on the current trip-gw draft. This draft will be revved after IETF with the proper draft-ietf-iptel moniker. I've had no requests for agenda slots, even though we had a few drafts submitted. If I don't hear soon I will cancel the iptel slot at IETF 53. Thanks, Jonathan R. Jonathan Rosenberg wrote: > > Folks, > > Things have been very quiet for the iptel group over the past few > months. I'd like to summarize where we are, we we are going, and propose > a path forward. > > Where are we? > ------------- > > CPL was approved as an RFC, and TRIP issued as RFC 3219. The TRIP MIB > went to IESG, we've gotten some feedback already, and some late comments > have come in from group participants. So, all is generally OK there. The > big stumbling block for us has been the other remaining item on our > charter - delivery of the protocol for "gateway registration". This work > has been caught up in a debate about the general approach. We've had > three distinct proposals: > > 1. TRIP-GW > http://search.ietf.org/internet-drafts/draft-rs-trip-gw-03.txt > > 2. SLP > http://www.ietf.org/internet-drafts/draft-zhao-iptel-gwloc-slp-03.txt > > 3. Radhikas proposals > http://search.ietf.org/internet-drafts/draft-roy-iptel-gw-server-registr > ation-00.txt > http://search.ietf.org/internet-drafts/draft-roy-iptel-gw-server-discove > ry-00.txt > http://search.ietf.org/internet-drafts/draft-roy-iptel-intra-itad-fw-00. > txt > http://search.ietf.org/internet-drafts/draft-roy-iptel-itrp-00.txt > (which I ruled out of scope) > > With advocates in each camp (primarily the authors). We made an attempt > to get around this impasse through requirements work, but there was not > sufficient working group effort expended to bear fruit in that > direction. So, the result has been no progress. > > Where do we need to go? > ------------------------ > > I believe that, given the general way this group has worked, we will > only have success if we can choose one of them, and then work from > there. I do not think that comparison documents, additional requirements > work, or debate on the merits of each approach will bear fruit. I have > seen such things consume endless time in other working groups. So, we > need to pick one, now. > > A proposal > ----------- > > I've had some private conversations with the various players, and I > think I can present a proposal that is acceptable to everyone. Here is > the proposal: > > 1. The group will adopt draft-rs-trip-gw as a working group item in > fulfillment of our charter task. The scope is as chartered, focusing on > allowing a server to make call routing decisions based on information > propagated from a PSTN gateway of some variant. SIP to H.323 and other > protocol converters are out of scope. > > 2. draft-zhao-iptel-gwloc-slp is really solving a different problem, > more along the lines of discovery. In an SLP system within an > enterprise, it is a perfectly reasonable thing to do. Fortunately, SLP > allows for IANA registration of templates, so that this work can > actually proceed to facilitate gateway discovery, outside of our > charter. However, since the attributes in such a template will be > similar to the kinds of things we will be doing in draft-rs-trip-gw, it > makes sense to use the iptel list as a discussion forum, and to allow > meeting time, if needed, to discuss. > > THe model is similar to what we did with the SLP template for SIP > servers; it was never chartered in the SIP group, but it had discussion > on the list and a bit of airtime at meetings, and then the template got > registered and was done. > > So, I am going to ask for a consensus call. Please respond to this post > with YEA or NAY, if you agree or disagree with this proposal, > respectively. I'd like to make a decision next week some time. > > If this proposal is accepted > ----------------------------- > > Assuming this proposal is accepted, the above draft can be resubmitted > (after IETF 53) as draft-ietf-iptel-trip-gw-00. Our task will then be to > focus on bringing it to completion. To do that, we would focus on the > open issues, which I suspect are primarily on the attribute set. > Discussion can begin immediately, of course, on the existing draft. > > What about IETF 53? > -------------------- > > I have, in fact, reserved a one hour slot at IETF 53. However, I am not > sure that this time is needed. Assuming we move forward with the > proposal, I do not think that there has been sufficient discussion of > the draft on the list to require any meeting time. If the proposal is > not accepted, we could possibly need the meeting to further discuss it. > So, for the moment, I will hold on to the slot. However, if the proposal > is accepted, and I hear no requests for specific agenda topics at the > meeting, I will cancel the slot. There is no shame in doing this. > > So, if you do feel a pressing need to discuss something at IETF 53, > please let me know. > > I'd then like to wrap up the work rapidly, which is still achievable by > the end of March, as specified in our charter. > > Comments solicited. > > Thanks, > Jonathan R. > > -- > Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Avenue > Chief Scientist First Floor > dynamicsoft East Hanover, NJ 07936 > jdrosen@dynamicsoft.com FAX: (973) 952-5050 > http://www.jdrosen.net PH: (973) 952-5000 > http://www.dynamicsoft.com > _______________________________________________ > IPTEL mailing list > IPTEL@lists.bell-labs.com > http://lists.bell-labs.com/mailman/listinfo/iptel -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Avenue Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PH: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ IPTEL mailing list IPTEL@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/iptel From iptel-admin@lists.bell-labs.com Tue Mar 12 23:03:55 2002 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 XAA18559 for ; Tue, 12 Mar 2002 23:03:54 -0500 (EST) 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 g2D3uMM27784; Tue, 12 Mar 2002 22:56:22 -0500 Received: from dirty.research.bell-labs.com (dirty.research.bell-labs.com [204.178.16.6]) by share.research.bell-labs.com (8.11.6/8.11.6) with SMTP id g2D3tfM27771 for ; Tue, 12 Mar 2002 22:55:41 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Tue Mar 12 22:55:21 EST 2002 Received: by lists.bell-labs.com (Postfix) id B9BC24439E; Tue, 12 Mar 2002 22:55:01 -0500 (EST) Delivered-To: iptel@sunny.research.bell-labs.com Received: from grubby.research.bell-labs.com (guard.research.bell-labs.com [135.104.2.9]) by lists.bell-labs.com (Postfix) with ESMTP id 9389D4439D for ; Tue, 12 Mar 2002 22:55:01 -0500 (EST) Received: from dusty.research.bell-labs.com (dusty.research.bell-labs.com [135.104.2.7]) by grubby.research.bell-labs.com (8.11.6/8.11.6) with SMTP id g2D3t0o85997 for ; Tue, 12 Mar 2002 22:55:00 -0500 (EST) Received: from mail3.dynamicsoft.com ([63.113.44.69]) by dusty; Tue Mar 12 22:50:59 EST 2002 Received: from dynamicsoft.com ([63.113.46.117]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g2D3tuTE002762 for ; Tue, 12 Mar 2002 22:55:58 -0500 (EST) Message-ID: <3C8ECD8E.C39B5BBA@dynamicsoft.com> From: Jonathan Rosenberg Organization: dynamicsoft X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: list iptel Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [IPTEL] iptel meeting at IETF 53 cancelled Sender: iptel-admin@lists.bell-labs.com Errors-To: iptel-admin@lists.bell-labs.com X-BeenThere: iptel@lists.bell-labs.com X-Mailman-Version: 2.0.8 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Date: Tue, 12 Mar 2002 22:54:54 -0500 Content-Transfer-Encoding: 7bit Folks, I have decided to cancel the 1 hour iptel slot scheduled for IETF 53. Since there appears to be general consensus on using draft-rs-trip-gw as the starting point for our gateway registration work, and since there was little to no email discussion on the other drafts submitted to iptel, and since I had no requests for agenda slots, there did not seem to be any value in having a meeting. That does not mean we are giving up; it merely means that we would not get enough value from a meeting to justify keeping the slot. Thanks, Jonathan R. -- Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Avenue Chief Scientist First Floor dynamicsoft East Hanover, NJ 07936 jdrosen@dynamicsoft.com FAX: (973) 952-5050 http://www.jdrosen.net PH: (973) 952-5000 http://www.dynamicsoft.com _______________________________________________ IPTEL mailing list IPTEL@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/iptel