From extest-admin@lists.bell-labs.com Mon Apr 1 05:46: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 FAA15975 for ; Mon, 1 Apr 2002 05:46: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 g31AkrM10469 for ; Mon, 1 Apr 2002 05:46:53 -0500 Date: Mon, 1 Apr 2002 05:46:53 -0500 Message-Id: <200204011046.g31AkrM10469@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 Wed Apr 3 15:44:45 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 PAA15221 for ; Wed, 3 Apr 2002 15:44:45 -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 g33KWJM25491; Wed, 3 Apr 2002 15:32:19 -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 g33KVbM25478 for ; Wed, 3 Apr 2002 15:31:37 -0500 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Wed Apr 3 15:31:05 EST 2002 Received: by lists.bell-labs.com (Postfix) id B1CE34439E; Wed, 3 Apr 2002 15:30:40 -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 8E7A04439D for ; Wed, 3 Apr 2002 15:30:40 -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 g33KUdk58308 for ; Wed, 3 Apr 2002 15:30:39 -0500 (EST) Received: from acmepacket.com ([63.67.143.10]) by dusty; Wed Apr 3 15:26:24 EST 2002 Received: from BobP [63.67.143.2] by acmepacket.com (SMTPD32-7.05) id A66850890174; Wed, 03 Apr 2002 15:30:32 -0500 Message-ID: <002001c1db4d$bdfca360$2300000a@acmepacket.com> From: "Bob Penfield" To: "list iptel" References: <3C8ECD8E.C39B5BBA@dynamicsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Subject: [IPTEL] carrier codes in draft-rs-trip-gw-03.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: Wed, 3 Apr 2002 15:25:48 -0500 Content-Transfer-Encoding: 7bit The carrier code attribute and address family defined in this draft does not support carrier codes for anywhere other than North America. It should include a country code prefix similar to that proposed in draft-yu-tel-url-04.txt or draft-walker-iptel-trip-tns-01.txt. cheers, (-:bob Robert F. Penfield Chief Software Architect Acme Packet, Inc. 130 New Boston Street Woburn, MA 01801 bpenfield@acmepacket.com _______________________________________________ IPTEL mailing list IPTEL@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/iptel From a1120@terra.com Sun Apr 7 22:53:44 2002 Received: from smtp.prodigy.net.mx (dfproxy01.prodigy.net.mx [148.235.168.56] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05642 for ; Sun, 7 Apr 2002 22:53:43 -0400 (EDT) Received: from frezzer (du-148-233-89-86.prodigy.net.mx [148.233.89.86]) by SMTP.Prodigy.Net.mx (Sun Internet Mail Server sims.4.0.2001.07.26.11.50.p9) with SMTP id <0GU8006SIAJXOQ@SMTP.Prodigy.Net.mx>; Sun, 7 Apr 2002 21:51:00 -0500 (CDT) Date: Sun, 07 Apr 2002 21:54:00 -0600 From: "Lic. Alfredo Martinez Zepeda." Subject: "COMO INCREMENTAR LAS VENTAS A TRAVES DEL SERVICIO" To: iptel-archive@ietf.org Reply-to: consultoriaemp7@yahoo.com.mx Message-id: <0GU8006TDAKXOQ@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 "COMO INCREMENTAR LAS VENTAS A TRAVES DEL SERVICIO" TEMARIO: 1. ¿ Que es realmente el servicio al cliente? 2. Errores que se deben evitar al dar atención y servicio al cliente 3. ¿ Cómo afecta a la empresa un cliente descontento? 4. Cómo descubrir las necesidades del cliente. 5. Cómo establecer una excelente relación con el cliente 6. Eficiencia en la entrega del servicio. 7. Velocidad de servicio. 8. Cómo incrementar los ingresos de la empresa mediante un excelente servicio 9. Profesionalismo en la atención y servicio al cliente. 10. Ejercicios prácticos dirigidos a la aplicación de las técnicas y conocimientos aprendidos Fecha: 13 de Abril del 2002 Lugar: Hotel Bristol Plaza Necaxa Nº17 Entre Río Panuco y Río Sena Col. Cuauhtemoc, D.F. Duración: 8 horas, 50% del tiempo se dedica a la realización de ejercicios prácticos. Horario: Registro 8:30 A.M. Seminario de las 9:00 A.M. a las 6:30 P.M. Dirigido a: Ejecutivos de ventas, vendedores y propietarios de negocios. Inversión: $2,900.00 por participante (más IVA.) Incluye: Material de apoyo, coffee breaks y comida. Conferencista Internacional: Lic. Alfredo Martinez Zepeda Ha capacitando a miles de ejecutivos y vendedores de importantes empresas como: Bancomer, Seguros Inbursa, Univ.Iberoamericana, Grupo Lumen entre muchas otras. RESERVE SUS LUGARES HOY MISMO TELS: 55 43 59 61 Y 55 43 40 61 LIC. LAURA AGUILAR E. From iptel-admin@lists.bell-labs.com Thu Apr 11 09:27:32 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 JAA26813 for ; Thu, 11 Apr 2002 09:27:32 -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 g3BDQIM11942; Thu, 11 Apr 2002 09:26:18 -0400 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 g3BDPaM11929 for ; Thu, 11 Apr 2002 09:25:36 -0400 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Thu Apr 11 09:24:32 EDT 2002 Received: by lists.bell-labs.com (Postfix) id 1B8B24439E; Thu, 11 Apr 2002 09:24:05 -0400 (EDT) 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 D13C24439D for ; Thu, 11 Apr 2002 09:24:04 -0400 (EDT) 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 g3BDO3k63037 for ; Thu, 11 Apr 2002 09:24:03 -0400 (EDT) Received: from sj-msg-core-1.cisco.com ([171.71.163.11]) by dusty; Thu Apr 11 09:19:40 EDT 2002 Received: from mira-sjc5-9.cisco.com (IDENT:mirapoint@mira-sjc5-9.cisco.com [171.71.163.32]) by sj-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g3BDNmq6013836; Thu, 11 Apr 2002 06:23:48 -0700 (PDT) Received: from OranLT ([161.44.238.53]) by mira-sjc5-9.cisco.com (Mirapoint) with ESMTP id ACP67409; Thu, 11 Apr 2002 06:23:59 -0700 (PDT) From: "David R. Oran" To: "'Bob Penfield'" , "'list iptel'" Cc: "Scott Bradner" , "'Allison Mankin'" Subject: RE: [IPTEL] carrier codes in draft-rs-trip-gw-03.txt Organization: Cisco Systems Message-ID: <00d301c1e15b$21f56b50$35ee2ca1@OranLT> 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: <002001c1db4d$bdfca360$2300000a@acmepacket.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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: Thu, 11 Apr 2002 09:16:45 -0400 Content-Transfer-Encoding: 7bit If there are multiple drafts with these things, would it not be better to create an IANA registry for these values? For the ADs: are there some special considerations or problems with having an IANA registry of numbers which map to (possibly by the identity mapping) numbers whose ownership and assignment actually comes from elsewhere? Dave. > -----Original Message----- > From: iptel-admin@lists.bell-labs.com > [mailto:iptel-admin@lists.bell-labs.com] On Behalf Of Bob Penfield > Sent: Wednesday, April 03, 2002 3:26 PM > To: list iptel > Subject: [IPTEL] carrier codes in draft-rs-trip-gw-03.txt > > > The carrier code attribute and address family defined in this > draft does not support carrier codes for anywhere other than > North America. It should include a country code prefix > similar to that proposed in draft-yu-tel-url-04.txt or > draft-walker-iptel-trip-tns-01.txt. > > cheers, > (-:bob > > Robert F. Penfield > Chief Software Architect > Acme Packet, Inc. > 130 New Boston Street > Woburn, MA 01801 > bpenfield@acmepacket.com > > > _______________________________________________ > IPTEL mailing list > IPTEL@lists.bell-labs.com > http://lists.bell-> labs.com/mailman/listinfo/iptel > _______________________________________________ IPTEL mailing list IPTEL@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/iptel From iptel-admin@lists.bell-labs.com Thu Apr 11 11:20: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 LAA29732 for ; Thu, 11 Apr 2002 11:20:27 -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 g3BFK3M12699; Thu, 11 Apr 2002 11:20:03 -0400 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 g3BFJZM12677 for ; Thu, 11 Apr 2002 11:19:35 -0400 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Thu Apr 11 11:19:14 EDT 2002 Received: by lists.bell-labs.com (Postfix) id 009484439E; Thu, 11 Apr 2002 11:18:47 -0400 (EDT) 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 CEE024439D for ; Thu, 11 Apr 2002 11:18:46 -0400 (EDT) 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 g3BFIjo45751 for ; Thu, 11 Apr 2002 11:18:45 -0400 (EDT) Received: from newdev.harvard.edu ([140.247.60.212]) by dusty; Thu Apr 11 11:14:22 EDT 2002 Received: (from sob@localhost) by newdev.harvard.edu (8.10.2/8.10.2) id g3BFIfX19550; Thu, 11 Apr 2002 11:18:41 -0400 (EDT) From: Scott Bradner Message-Id: <200204111518.g3BFIfX19550@newdev.harvard.edu> To: bpenfield@acmepacket.com, iptel@lists.bell-labs.com, oran@cisco.com Subject: RE: [IPTEL] carrier codes in draft-rs-trip-gw-03.txt Cc: mankin@isi.edu, sob@harvard.edu In-Reply-To: <00d301c1e15b$21f56b50$35ee2ca1@OranLT> 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: Thu, 11 Apr 2002 11:18:41 -0400 (EDT) I need more detail (not following close enough I guess) but in general the IANA maintains registries where it assigns values Scott --- From oran@cisco.com Thu Apr 11 09:23:55 2002 From: "David R. Oran" To: "'Bob Penfield'" , "'list iptel'" Cc: "Scott Bradner" , "'Allison Mankin'" Subject: RE: [IPTEL] carrier codes in draft-rs-trip-gw-03.txt Date: Thu, 11 Apr 2002 09:16:45 -0400 Organization: Cisco Systems 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: <002001c1db4d$bdfca360$2300000a@acmepacket.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 If there are multiple drafts with these things, would it not be better to create an IANA registry for these values? For the ADs: are there some special considerations or problems with having an IANA registry of numbers which map to (possibly by the identity mapping) numbers whose ownership and assignment actually comes from elsewhere? Dave. > -----Original Message----- > From: iptel-admin@lists.bell-labs.com > [mailto:iptel-admin@lists.bell-labs.com] On Behalf Of Bob Penfield > Sent: Wednesday, April 03, 2002 3:26 PM > To: list iptel > Subject: [IPTEL] carrier codes in draft-rs-trip-gw-03.txt > > > The carrier code attribute and address family defined in this > draft does not support carrier codes for anywhere other than > North America. It should include a country code prefix > similar to that proposed in draft-yu-tel-url-04.txt or > draft-walker-iptel-trip-tns-01.txt. > > cheers, > (-:bob > > Robert F. Penfield > Chief Software Architect > Acme Packet, Inc. > 130 New Boston Street > Woburn, MA 01801 > bpenfield@acmepacket.com > > > _______________________________________________ > IPTEL mailing list > IPTEL@lists.bell-labs.com > http://lists.bell-> labs.com/mailman/listinfo/iptel > _______________________________________________ IPTEL mailing list IPTEL@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/iptel From iptel-admin@lists.bell-labs.com Thu Apr 11 15:00:28 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 PAA09633 for ; Thu, 11 Apr 2002 15:00:27 -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 g3BIhDM13905; Thu, 11 Apr 2002 14:43:14 -0400 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 g3BIgPM13891 for ; Thu, 11 Apr 2002 14:42:25 -0400 Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Thu Apr 11 14:40:07 EDT 2002 Received: by lists.bell-labs.com (Postfix) id 1A6B94439E; Thu, 11 Apr 2002 14:40:28 -0400 (EDT) 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 E5E664439D for ; Thu, 11 Apr 2002 14:40:27 -0400 (EDT) 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 g3BIeQo64288 for ; Thu, 11 Apr 2002 14:40:26 -0400 (EDT) Received: from acmepacket.com ([63.67.143.10]) by dusty; Thu Apr 11 14:36:01 EDT 2002 Received: from BobP [63.67.143.2] by acmepacket.com (SMTPD32-7.05) id A88FE705014A; Thu, 11 Apr 2002 14:40:15 -0400 Message-ID: <000201c1e188$050ca080$2300000a@acmepacket.com> From: "Bob Penfield" To: "Scott Bradner" , , Cc: References: <200204111518.g3BFIfX19550@newdev.harvard.edu> Subject: Re: [IPTEL] carrier codes in draft-rs-trip-gw-03.txt MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 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: Thu, 11 Apr 2002 13:32:53 -0400 Content-Transfer-Encoding: 7bit Within the context of TRIP and PSTN/GSTN gateway location, the idea is to use the carrier identification codes (CICs) already used in the PSTN/GSTN. The problem is that each country has its own carrier codes. Thus the need for a country code. However, since there is already a naming authority for country codes and within each country a naming authority for carrier codes (at least those in circuit switched networks), we do not need an IANA registry for those. The point of the original mail was that if we are using legacy CICs in the IP world, there should be a consistent way to represent and handle them. If these CICs start getting used across the IP Telephony protocols, and new CICs are needed for IP tel networks and providers, how would you then manage the CIC namespace? Would the same authorities continue to give out CICs? Or would IANA manage the IP-specific CICs? I have not thought much about this and don't really have any strong opinions at this point. Just something to think about. cheers, (-:bob Robert F. Penfield Chief Software Architect Acme Packet, Inc. 130 New Boston Street Woburn, MA 01801 bpenfield@acmepacket.com ----- Original Message ----- From: "Scott Bradner" To: ; ; Cc: ; Sent: Thursday, April 11, 2002 11:18 AM Subject: RE: [IPTEL] carrier codes in draft-rs-trip-gw-03.txt > I need more detail (not following close enough I guess) > > but in general the IANA maintains registries where it assigns values > > Scott > > --- > >From oran@cisco.com Thu Apr 11 09:23:55 2002 > From: "David R. Oran" > To: "'Bob Penfield'" , > "'list iptel'" > Cc: "Scott Bradner" , "'Allison Mankin'" > Subject: RE: [IPTEL] carrier codes in draft-rs-trip-gw-03.txt > Date: Thu, 11 Apr 2002 09:16:45 -0400 > Organization: Cisco Systems > 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: <002001c1db4d$bdfca360$2300000a@acmepacket.com> > Importance: Normal > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 > > If there are multiple drafts with these things, would it not be better > to create an IANA registry for these values? > > For the ADs: are there some special considerations or problems with > having an IANA registry of numbers which map to (possibly by the > identity mapping) numbers whose ownership and assignment actually comes > from elsewhere? > > Dave. > > > -----Original Message----- > > From: iptel-admin@lists.bell-labs.com > > [mailto:iptel-admin@lists.bell-labs.com] On Behalf Of Bob Penfield > > Sent: Wednesday, April 03, 2002 3:26 PM > > To: list iptel > > Subject: [IPTEL] carrier codes in draft-rs-trip-gw-03.txt > > > > > > The carrier code attribute and address family defined in this > > draft does not support carrier codes for anywhere other than > > North America. It should include a country code prefix > > similar to that proposed in draft-yu-tel-url-04.txt or > > draft-walker-iptel-trip-tns-01.txt. > > > > cheers, > > (-:bob > > > > Robert F. Penfield > > Chief Software Architect > > Acme Packet, Inc. > > 130 New Boston Street > > Woburn, MA 01801 > > bpenfield@acmepacket.com > > > > > > _______________________________________________ > > IPTEL mailing list > > IPTEL@lists.bell-labs.com > > http://lists.bell-> labs.com/mailman/listinfo/iptel > > > > _______________________________________________ IPTEL mailing list IPTEL@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/iptel From iptel-admin@lists.bell-labs.com Thu Apr 11 15:02:20 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 PAA09762 for ; Thu, 11 Apr 2002 15:02:20 -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 g3BIq1M14006; Thu, 11 Apr 2002 14:52:01 -0400 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 g3BIpYM13992 for ; Thu, 11 Apr 2002 14:51:34 -0400 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Thu Apr 11 14:50:39 EDT 2002 Received: by lists.bell-labs.com (Postfix) id C01A44439E; Thu, 11 Apr 2002 14:50:11 -0400 (EDT) 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 A007C4439D for ; Thu, 11 Apr 2002 14:50:11 -0400 (EDT) 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 g3BIoAo65169 for ; Thu, 11 Apr 2002 14:50:10 -0400 (EDT) Received: from newdev.harvard.edu ([140.247.60.212]) by dusty; Thu Apr 11 14:45:47 EDT 2002 Received: (from sob@localhost) by newdev.harvard.edu (8.10.2/8.10.2) id g3BIo6g20478; Thu, 11 Apr 2002 14:50:06 -0400 (EDT) From: Scott Bradner Message-Id: <200204111850.g3BIo6g20478@newdev.harvard.edu> To: bpenfield@acmepacket.com, iptel@lists.bell-labs.com, oran@cisco.com, sob@harvard.edu Subject: Re: [IPTEL] carrier codes in draft-rs-trip-gw-03.txt Cc: mankin@isi.edu In-Reply-To: <000201c1e188$050ca080$2300000a@acmepacket.com> 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: Thu, 11 Apr 2002 14:50:06 -0400 (EDT) it seems that the IANA should not be recording values that someone else assigns since they will get out of sync Scott _______________________________________________ IPTEL mailing list IPTEL@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/iptel From iptel-admin@lists.bell-labs.com Fri Apr 12 10:56:04 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 KAA02727 for ; Fri, 12 Apr 2002 10:56:04 -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 g3CEtDM19577; Fri, 12 Apr 2002 10:55:13 -0400 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 g3CEsNM19558 for ; Fri, 12 Apr 2002 10:54:23 -0400 Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Fri Apr 12 10:53:58 EDT 2002 Received: by lists.bell-labs.com (Postfix) id 324C14439E; Fri, 12 Apr 2002 10:54:19 -0400 (EDT) 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 06A954439D for ; Fri, 12 Apr 2002 10:54:18 -0400 (EDT) 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 g3CEsHo37545 for ; Fri, 12 Apr 2002 10:54:17 -0400 (EDT) Received: from rtp-msg-core-1.cisco.com ([161.44.11.97]) by dusty; Fri Apr 12 10:49:53 EDT 2002 Received: from cia.cisco.com (localhost [127.0.0.1]) by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g3CEsM1v010091; Fri, 12 Apr 2002 10:54:22 -0400 (EDT) Received: from MHAMMER-W2K.cisco.com (hrn2-dhcp-161-44-87-145.cisco.com [161.44.87.145]) by cia.cisco.com (Mirapoint) with ESMTP id AAT81307; Fri, 12 Apr 2002 10:48:55 -0400 (EDT) Message-Id: <4.3.2.7.2.20020412104928.00b1ce10@cia.cisco.com> X-Sender: mhammer@cia.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 To: "Bob Penfield" From: Michael Hammer Subject: Re: [IPTEL] carrier codes in draft-rs-trip-gw-03.txt Cc: "Scott Bradner" , , , In-Reply-To: <000201c1e188$050ca080$2300000a@acmepacket.com> References: <200204111518.g3BFIfX19550@newdev.harvard.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed 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, 12 Apr 2002 10:53:55 -0400 Bob, The E.164 number space, the country codes, the CIC codes are all part of the PSTN realm. I don't see a need for any redundant management of those values. Previously it was pointed out that the CIC codes combined with the country codes, as described in draft-yu-tel-url-04.txt, would make them globally unique. Hopefully, that convention will answer your needs. If there was another issue here, I missed it. Mike At 01:32 PM 4/11/2002 -0400, Bob Penfield wrote: >Within the context of TRIP and PSTN/GSTN gateway location, the idea is to >use the carrier identification codes (CICs) already used in the PSTN/GSTN. >The problem is that each country has its own carrier codes. Thus the need >for a country code. However, since there is already a naming authority for >country codes and within each country a naming authority for carrier codes >(at least those in circuit switched networks), we do not need an IANA >registry for those. The point of the original mail was that if we are using >legacy CICs in the IP world, there should be a consistent way to represent >and handle them. > >If these CICs start getting used across the IP Telephony protocols, and new >CICs are needed for IP tel networks and providers, how would you then manage >the CIC namespace? Would the same authorities continue to give out CICs? Or >would IANA manage the IP-specific CICs? I have not thought much about this >and don't really have any strong opinions at this point. Just something to >think about. > >cheers, >(-:bob > >Robert F. Penfield >Chief Software Architect >Acme Packet, Inc. >130 New Boston Street >Woburn, MA 01801 >bpenfield@acmepacket.com > >----- Original Message ----- >From: "Scott Bradner" >To: ; ; > >Cc: ; >Sent: Thursday, April 11, 2002 11:18 AM >Subject: RE: [IPTEL] carrier codes in draft-rs-trip-gw-03.txt > > > > I need more detail (not following close enough I guess) > > > > but in general the IANA maintains registries where it assigns values > > > > Scott > > > > --- > > >From oran@cisco.com Thu Apr 11 09:23:55 2002 > > From: "David R. Oran" > > To: "'Bob Penfield'" , > > "'list iptel'" > > Cc: "Scott Bradner" , "'Allison Mankin'" > > Subject: RE: [IPTEL] carrier codes in draft-rs-trip-gw-03.txt > > Date: Thu, 11 Apr 2002 09:16:45 -0400 > > Organization: Cisco Systems > > 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: <002001c1db4d$bdfca360$2300000a@acmepacket.com> > > Importance: Normal > > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 > > > > If there are multiple drafts with these things, would it not be better > > to create an IANA registry for these values? > > > > For the ADs: are there some special considerations or problems with > > having an IANA registry of numbers which map to (possibly by the > > identity mapping) numbers whose ownership and assignment actually comes > > from elsewhere? > > > > Dave. > > > > > -----Original Message----- > > > From: iptel-admin@lists.bell-labs.com > > > [mailto:iptel-admin@lists.bell-labs.com] On Behalf Of Bob Penfield > > > Sent: Wednesday, April 03, 2002 3:26 PM > > > To: list iptel > > > Subject: [IPTEL] carrier codes in draft-rs-trip-gw-03.txt > > > > > > > > > The carrier code attribute and address family defined in this > > > draft does not support carrier codes for anywhere other than > > > North America. It should include a country code prefix > > > similar to that proposed in draft-yu-tel-url-04.txt or > > > draft-walker-iptel-trip-tns-01.txt. > > > > > > cheers, > > > (-:bob > > > > > > Robert F. Penfield > > > Chief Software Architect > > > Acme Packet, Inc. > > > 130 New Boston Street > > > Woburn, MA 01801 > > > bpenfield@acmepacket.com > > > > > > > > > _______________________________________________ > > > IPTEL mailing list > > > IPTEL@lists.bell-labs.com > > > http://lists.bell-> labs.com/mailman/listinfo/iptel > > > > > > > > >_______________________________________________ >IPTEL mailing list >IPTEL@lists.bell-labs.com >http://lists.bell-labs.com/mailman/listinfo/iptel _______________________________________________ IPTEL mailing list IPTEL@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/iptel From iptel-admin@lists.bell-labs.com Fri Apr 12 12:23:12 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 MAA14243 for ; Fri, 12 Apr 2002 12:23:11 -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 g3CGN7M20216; Fri, 12 Apr 2002 12:23:07 -0400 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 g3CGMNM20201 for ; Fri, 12 Apr 2002 12:22:23 -0400 Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Fri Apr 12 12:21:56 EDT 2002 Received: by lists.bell-labs.com (Postfix) id 511644439E; Fri, 12 Apr 2002 12:22:16 -0400 (EDT) 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 2AE2B4439D for ; Fri, 12 Apr 2002 12:22:16 -0400 (EDT) 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 g3CGMEo46614 for ; Fri, 12 Apr 2002 12:22:14 -0400 (EDT) Received: from mail.trest.com ([209.132.91.55]) by dusty; Fri Apr 12 12:17:52 EDT 2002 Received: from miketrest.TREST.COM (adsl-66-125-25-78.dsl.sndg02.pacbell.net [66.125.25.78]) by mail.trest.com (8.11.2/8.11.6) with ESMTP id g3CGMAW32670 for ; Fri, 12 Apr 2002 09:22:10 -0700 Message-Id: <5.1.0.14.2.20020412090743.00ac97d8@pop3.norton.antivirus> X-Sender: mike/mail.TREST.COM@pop3.norton.antivirus X-Mailer: QUALCOMM Windows Eudora Version 5.1 To: iptel@lists.bell-labs.com From: "Mike@TREST.COM" Subject: Re: [IPTEL] carrier codes in draft-rs-trip-gw-03.txt Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed 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, 12 Apr 2002 09:23:45 -0700 Scott, Bob, Michael, et. al. From the perspective of a current operator with over xx VoIP carrier interconnects running traffic, we (the current operators) have been solving the problem with our respective DIAL-PEER prefix management. This approach is somewhat of a pain to maintain, but current practice seems to muddle along without use of externally "blessed" numbering schemes. These prefix numbers are unique to specific gateway-gateway or gateway-gatekeeper pairs. They are, therefore, cryptic enough to maintain "proprietary information" boundaries that would be exposed if a public COUNTRY/CIC code plan were mandatory. That brings up a HUGE issue of how to deal with the thousands of "un-official" operators in the international (and domestic) VoIP community who quite freely interact with the "official" carriers of the world. As a protocol development group, we do not want to fall into the middle of that muddle! ..mike.. =========================================================== Date: Thu, 11 Apr 2002 14:50:06 -0400 (EDT) X-UIDL: !:f"!paQ!!nF]!!F8j"! it seems that the IANA should not be recording values that someone else assigns since they will get out of sync Scott San Diego, HQ Office: +1 858 720 8000 Fax: +1 858 259 2868 San Diego, Home Office: +1 858 689 1248 Fax: +1 858 689 1248 _______________________________________________ IPTEL mailing list IPTEL@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/iptel From iptel-admin@lists.bell-labs.com Fri Apr 12 22:52: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 WAA10600 for ; Fri, 12 Apr 2002 22:52:13 -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 g3D2q7M23115; Fri, 12 Apr 2002 22:52:07 -0400 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 g3D2pYM23102 for ; Fri, 12 Apr 2002 22:51:35 -0400 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Fri Apr 12 22:50:47 EDT 2002 Received: by lists.bell-labs.com (Postfix) id CDF124439E; Fri, 12 Apr 2002 22:50:20 -0400 (EDT) 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 A88234439D for ; Fri, 12 Apr 2002 22:50:20 -0400 (EDT) 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 g3D2oJk19060 for ; Fri, 12 Apr 2002 22:50:19 -0400 (EDT) Received: from imo-d10.mx.aol.com ([205.188.157.42]) by dusty; Fri Apr 12 22:45:56 EDT 2002 Received: from JustMeUnOr@aol.com by imo-d10.mx.aol.com (mail_out_v32.5.) id o.b6.9db7ffe (25308); Fri, 12 Apr 2002 22:49:50 -0400 (EDT) From: JustMeUnOr@aol.com Message-ID: Subject: Re: [IPTEL] carrier codes in draft-rs-trip-gw-03.txt To: Mike@TREST.COM, iptel@lists.bell-labs.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="part1_b6.9db7ffe.29e8f6ce_boundary" X-Mailer: AOL 6.0 for Windows US sub 10560 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, 12 Apr 2002 22:49:50 EDT --part1_b6.9db7ffe.29e8f6ce_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit I dont know what global siginifcance this would put on the TRIP protocol, but I thought of this as a 'Just for giggles' idea since were on the subject... :/ in relation to CIC/CC mapping (If someone were to attempt to unify dialing plans of the rest of the world, with their own), couldent there be some type of an addendum to the regestry that IANA keeps, where they could cross reference CIC codes with CC codes, and see what ITAD identity owns (or takes partial responcibility at least)them (Relational / Manageable database, can be queried on whatever criteria sepcified) or course, this would be implicitly for carriers that transport and/or terminate their own CIC's or would this be out of scope? -Darby --part1_b6.9db7ffe.29e8f6ce_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: 7bit I dont know what global siginifcance this would put on the TRIP protocol, but I thought of this as a 'Just for giggles' idea since were on the subject...   :/

in relation to CIC/CC mapping (If someone were to attempt to unify dialing plans of the rest of the world, with their own), couldent there be some type of an addendum to the regestry that IANA keeps, where they could cross reference CIC codes with CC codes, and see what ITAD identity owns (or takes partial responcibility at least)them (Relational / Manageable database, can be queried on whatever criteria sepcified) or course, this would be implicitly for carriers that transport and/or terminate their own CIC's

or would this be out of scope?
-Darby --part1_b6.9db7ffe.29e8f6ce_boundary-- _______________________________________________ IPTEL mailing list IPTEL@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/iptel From iptel-admin@lists.bell-labs.com Mon Apr 15 10:33:52 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 KAA19084 for ; Mon, 15 Apr 2002 10:33:52 -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 g3FDxGM10590; Mon, 15 Apr 2002 09:59:16 -0400 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 g3FDwOM10576 for ; Mon, 15 Apr 2002 09:58:24 -0400 Received: from lists.bell-labs.com ([135.104.27.211]) by crufty; Mon Apr 15 09:56:17 EDT 2002 Received: by lists.bell-labs.com (Postfix) id 1D98E4439E; Mon, 15 Apr 2002 09:56:34 -0400 (EDT) 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 94C874439D for ; Mon, 15 Apr 2002 09:56:33 -0400 (EDT) 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 g3FDuWo98578 for ; Mon, 15 Apr 2002 09:56:32 -0400 (EDT) Received: from rtp-msg-core-1.cisco.com ([161.44.11.97]) by dusty; Mon Apr 15 09:52:05 EDT 2002 Received: from cia.cisco.com (localhost [127.0.0.1]) by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g3FDulS7003835; Mon, 15 Apr 2002 09:56:47 -0400 (EDT) Received: from MHAMMER-W2K.cisco.com (hrn2-dhcp-161-44-87-145.cisco.com [161.44.87.145]) by cia.cisco.com (Mirapoint) with ESMTP id AAT93038; Mon, 15 Apr 2002 09:51:16 -0400 (EDT) Message-Id: <4.3.2.7.2.20020415095230.00b22b58@cia.cisco.com> X-Sender: mhammer@cia.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 To: JustMeUnOr@aol.com From: Michael Hammer Subject: Re: [IPTEL] carrier codes in draft-rs-trip-gw-03.txt Cc: Mike@TREST.COM, iptel@lists.bell-labs.com In-Reply-To: Mime-Version: 1.0 Content-Type: text/html; charset="us-ascii" 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, 15 Apr 2002 09:56:20 -0400 What if, instead of treating this like a registry issue, the TRIP databases would do a little data-mining and eventually extract the relevant prefix information from the gateway entries.  Wouldn't this naturally fall out of data aggregation?

Mike


At 10:49 PM 4/12/2002 -0400, JustMeUnOr@aol.com wrote:
I dont know what global siginifcance this would put on the TRIP protocol, but I thought of this as a 'Just for giggles' idea since were on the subject...   :/

in relation to CIC/CC mapping (If someone were to attempt to unify dialing plans of the rest of the world, with their own), couldent there be some type of an addendum to the regestry that IANA keeps, where they could cross reference CIC codes with CC codes, and see what ITAD identity owns (or takes partial responcibility at least)them (Relational / Manageable database, can be queried on whatever criteria sepcified) or course, this would be implicitly for carriers that transport and/or terminate their own CIC's

or would this be out of scope?
-Darby
_______________________________________________ IPTEL mailing list IPTEL@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/iptel From iptel-admin@lists.bell-labs.com Mon Apr 15 14:24:25 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 OAA01173 for ; Mon, 15 Apr 2002 14:24:25 -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 g3FI88M11897; Mon, 15 Apr 2002 14:08:08 -0400 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 g3FI7YM11884 for ; Mon, 15 Apr 2002 14:07:34 -0400 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Mon Apr 15 14:07:23 EDT 2002 Received: by lists.bell-labs.com (Postfix) id B82DD4439E; Mon, 15 Apr 2002 14:06:54 -0400 (EDT) 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 926394439D for ; Mon, 15 Apr 2002 14:06:54 -0400 (EDT) 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 g3FI6qo25473 for ; Mon, 15 Apr 2002 14:06:53 -0400 (EDT) Received: from imo-d10.mx.aol.com ([205.188.157.42]) by dusty; Mon Apr 15 14:02:28 EDT 2002 Received: from JustMeUnOr@aol.com by imo-d10.mx.aol.com (mail_out_v32.5.) id c.14d.c4b2c0a (3967); Mon, 15 Apr 2002 14:06:25 -0400 (EDT) From: JustMeUnOr@aol.com Message-ID: <14d.c4b2c0a.29ec70a1@aol.com> Subject: Re: [IPTEL] carrier codes in draft-rs-trip-gw-03.txt To: mhammer@cisco.com Cc: Mike@TREST.COM, iptel@lists.bell-labs.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="part1_14d.c4b2c0a.29ec70a1_boundary" X-Mailer: AOL 7.0 for Windows US sub 259 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, 15 Apr 2002 14:06:25 EDT --part1_14d.c4b2c0a.29ec70a1_boundary Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Sounds plauseable... but would everyone's RouteServ need to "Dip" (as in SP ~> STP ~> SCP SS7 relationships) from IANA, or a similar entity for that data, or would everyone's RouteServ export the data to IANA?? Also if everyone doesnt particularly want to route their traffic based on CC/CIC's currently used by the ITU, this becomes a non-issue, since all similar carrier class routing can be accomplished via ITAD identies, or other route criteria (QoS, LCR, Destination address, etc.) correct? -Darby --part1_14d.c4b2c0a.29ec70a1_boundary Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: 7bit Sounds plauseable...

but would everyone's RouteServ need to "Dip" (as in SP ~> STP ~> SCP SS7 relationships) from IANA, or a similar entity for that data, or would everyone's RouteServ export the data to IANA??

Also if everyone doesnt particularly want to route their traffic based on CC/CIC's currently used by the ITU, this becomes a non-issue, since all similar carrier class routing can be accomplished via ITAD identies, or other route criteria (QoS, LCR, Destination address, etc.) correct?

-Darby --part1_14d.c4b2c0a.29ec70a1_boundary-- _______________________________________________ IPTEL mailing list IPTEL@lists.bell-labs.com http://lists.bell-labs.com/mailman/listinfo/iptel From iptel-admin@lists.bell-labs.com Sat Apr 27 15:19:28 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 PAA12134 for ; Sat, 27 Apr 2002 15:19:28 -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 g3RJIAN28975; Sat, 27 Apr 2002 15:18:10 -0400 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 g3RJHVN28962 for ; Sat, 27 Apr 2002 15:17:32 -0400 Received: from lists.bell-labs.com ([135.104.27.211]) by dirty; Sat Apr 27 15:16:04 EDT 2002 Received: by lists.bell-labs.com (Postfix) id 7FA014439E; Sat, 27 Apr 2002 15:15:35 -0400 (EDT) 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 15A1A4439D for ; Sat, 27 Apr 2002 15:15:35 -0400 (EDT) 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 g3RJFXk51494 for ; Sat, 27 Apr 2002 15:15:33 -0400 (EDT) Received: from mail3.dynamicsoft.com ([63.113.44.69]) by dusty; Sat Apr 27 15:11:01 EDT 2002 Received: from dynamicsoft.com ([63.113.46.12]) by mail3.dynamicsoft.com (8.12.1/8.12.1) with ESMTP id g3RJGpLC007590; Sat, 27 Apr 2002 15:16:51 -0400 (EDT) Message-ID: <3CCAF8D0.C13E6383@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: JustMeUnOr@aol.com Cc: mhammer@cisco.com, Mike@TREST.COM, iptel@lists.bell-labs.com Subject: Re: [IPTEL] carrier codes in draft-rs-trip-gw-03.txt References: <14d.c4b2c0a.29ec70a1@aol.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: Sat, 27 Apr 2002 15:15:28 -0400 Content-Transfer-Encoding: 7bit I don't think any of this is our problem. The TRIP-gw spec only needs to be carry the information. Its not our job to fix the fact that there is no one central place to obtain the codes right now. -Jonathan R. JustMeUnOr@aol.com wrote: > > Sounds plauseable... > > but would everyone's RouteServ need to "Dip" (as in SP ~> STP ~> SCP SS7 > relationships) from IANA, or a similar entity for that data, or would > everyone's RouteServ export the data to IANA?? > > Also if everyone doesnt particularly want to route their traffic based > on CC/CIC's currently used by the ITU, this becomes a non-issue, since > all similar carrier class routing can be accomplished via ITAD identies, > or other route criteria (QoS, LCR, Destination address, etc.) correct? > > -Darby -- 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