RE: New name for TRIP-GW
Dhaval Shah <[email protected]> Sat, 07 Sep 2002 11:14:07 -0700
| Newsgroups | gmane.ietf.iptel |
|---|---|
| Message-ID | <[email protected]> |
--=====================_55217017==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed Hi Folx, Based on: 1. Jonathan's initial analogy with grep, which is cool 2. The suggestion for something denoting telephony in the name 3. Sounding, my 2 cents on this is TGREP (Telephony Gateway Registration Protocol). Thx, Dhaval At 12:44 PM 9/7/2002 +0530, [email protected] wrote: >I too agree with Radhika and Roberto. I believe the iptel workgroup should >not do away with "T" (read telephony) in the protocol naming convention. >Telephony is the essence of iptel and its work. TGRP conveys the functional >meaning succinctly. > > >Regards, >Rakesh Khemani. >L & T Infotech Ltd. >Bangalore, India. > > > > > > > > "Crizza, > Roberto" > <[email protected] To: list iptel > <[email protected]> > om> cc: > > Sent by: Subject: RE: [IPTEL] > New name for TRIP-GW > [email protected] > > l-labs.com > > > > > > 07/09/2002 06:23 > AM > > > > > > > > >I agree with Radhika and in my opinion the pronunciation of TGRP is better >than GREP. > >Regards > >Roberto Crizza >EDS Brazil > >-----Original Message----- >From: Roy, Radhika R, ALASO [mailto:[email protected]] >Sent: Friday, September 06, 2002 17:09 >To: Jonathan Rosenberg; list iptel >Subject: RE: [IPTEL] New name for TRIP-GW > > >I believe that the Gateway Registration Protocol (GREP) is too broad a >term. In fact, this registration protocol is only applicable for the >PSTN-IP Telephony GWs for registration of the routable telephone >numbers. > >So, I propose the name as follows: > >"Telephony Gateway Registration Protocol (TGRP)" > >Thanks, > >Radhika R. Roy >AT&T > >-----Original Message----- >From: Jonathan Rosenberg [mailto:[email protected]] >Sent: Friday, September 06, 2002 3:42 PM >To: list iptel >Subject: [IPTEL] New name for TRIP-GW > > >Folks, > >I'd like to propose a name change for the TRIP-GW (aka TRIP-LITE) >protocol. > >The reason is, as written, TRIP-GW is not actually an extension to TRIP. > >Nor is it a subset of TRIP. It differs in the consolidation process >defined in the spec. This process, which allows an LS to keep multiple >routes to the same prefix, for example, is not compatible with the >decision process of TRIP. Its complementary, to be certain, but thats >not the same. If you took a normal TRIP LS and put it in front of a >TRIP-GW gateway, it would probably not do the right thing. It would >function, I think, but you would not be able to implement the >appropriate policies to process the information being generated by the >gateways. > >Do people concur with this view? > >If so, I would propose that we rename the protocol to the Gateway >Registration Protocol (GREP). I think the acronym is neat; the protocol >is used to search for a gateway, sort of, so grep (in the unix sense) >kind of works. > >The protocol syntax and semantics remain unchanged. We will simply >indicate that large pieces of TRIP are used wholesale by this protocol, >referring the user to the appropriate sections of the TRIP spec. > >Thoughts? > >Thanks, >Jonathan R. >-- >Jonathan D. Rosenberg, Ph.D. 72 Eagle Rock Ave. >Chief Scientist First Floor >dynamicsoft East Hanover, NJ 07936 >[email protected] FAX: (973) 952-5050 >http://www.jdrosen.net PHONE: (973) 952-5000 >http://www.dynamicsoft.com > >_______________________________________________ >IPTEL mailing list >[email protected] >http://lists.bell-labs.com/mailman/listinfo/iptel >_______________________________________________ >IPTEL mailing list >[email protected] >http://lists.bell-labs.com/mailman/listinfo/iptel >_______________________________________________ >IPTEL mailing list >[email protected] >http://lists.bell-labs.com/mailman/listinfo/iptel > > > > >_______________________________________________ >IPTEL mailing list >[email protected] >http://lists.bell-labs.com/mailman/listinfo/iptel --=====================_55217017==_.ALT Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <font size=3D3>Hi Folx,<br> <br> Based on:<br> <br> 1. Jonathan's initial analogy with grep, which is cool<br> 2. The suggestion for something denoting telephony in the name<br> 3. Sounding,<br> <br> my 2 cents on this is TGREP (Telephony Gateway Registration Protocol).<br> <br> Thx,<br> Dhaval<br> <br> At 12:44 PM 9/7/2002 +0530, [email protected] wrote:<br> <br> <blockquote type=3Dcite cite>I too agree with Radhika and Roberto. I believe the iptel workgroup should<br> not do away with "T" (read telephony) in the protocol naming convention.<br> Telephony is the essence of iptel and its work. TGRP conveys the functional<br> meaning succinctly.<br> <br> <br> Regards,<br> Rakesh Khemani.<br> L & T Infotech Ltd.<br> Bangalore, India.<br> <br> <br> <br> <br> <br> &nbs= p; &n= bsp; = &nbs= p; &n= bsp; = &nbs= p; <br> &nbs= p; "Crizza, Roberto" &nb= sp; &= nbsp;  = ; &nb= sp; <br> &nbs= p; <[email protected] To: list iptel <[email protected]> <br> &nbs= p; om> &nbs= p; cc: &= nbsp;  = ; &nb= sp; <br> &nbs= p; Sent by: &= nbsp; Subject: RE: [IPTEL] New name for TRIP-GW <br> &nbs= p; [email protected] &= nbsp;  = ; &nb= sp; &= nbsp; <br> &nbs= p; l-labs.com = &nbs= p; &n= bsp; = &nbs= p; <br> &nbs= p; &n= bsp; = &nbs= p; &n= bsp; = &nbs= p; <br> &nbs= p; &n= bsp; = &nbs= p; &n= bsp; = &nbs= p; <br> &nbs= p; 07/09/2002 06:23 AM &n= bsp; = &nbs= p; &n= bsp; <br> &nbs= p; &n= bsp; = &nbs= p; &n= bsp; = &nbs= p; <br> &nbs= p; &n= bsp; = &nbs= p; &n= bsp; = &nbs= p; <br> <br> <br> <br> <br> I agree with Radhika and in my opinion the pronunciation of TGRP is better<br> than GREP.<br> <br> Regards<br> <br> Roberto Crizza<br> EDS Brazil<br> <br> -----Original Message-----<br> From: Roy, Radhika R, ALASO [<a href=3D"mailto:[email protected]"= eudora=3D"autourl">mailto:[email protected]</a>]<br> Sent: Friday, September 06, 2002 17:09<br> To: Jonathan Rosenberg; list iptel<br> Subject: RE: [IPTEL] New name for TRIP-GW<br> <br> <br> I believe that the Gateway Registration Protocol (GREP) is too broad a<br> term. In fact, this registration protocol is only applicable for=20 the<br> PSTN-IP Telephony GWs for registration of the routable telephone<br> numbers.<br> <br> So, I propose the name as follows:<br> <br> "Telephony Gateway Registration Protocol (TGRP)"<br> <br> Thanks,<br> <br> Radhika R. Roy<br> AT&T<br> <br> -----Original Message-----<br> From: Jonathan Rosenberg [<a href=3D"mailto:[email protected]"= eudora=3D"autourl">mailto:[email protected]</a>]<br> Sent: Friday, September 06, 2002 3:42 PM<br> To: list iptel<br> Subject: [IPTEL] New name for TRIP-GW<br> <br> <br> Folks,<br> <br> I'd like to propose a name change for the TRIP-GW (aka TRIP-LITE)<br> protocol.<br> <br> The reason is, as written, TRIP-GW is not actually an extension to TRIP.<br> <br> Nor is it a subset of TRIP. It differs in the consolidation process<br> defined in the spec. This process, which allows an LS to keep multiple<br> routes to the same prefix, for example, is not compatible with the<br> decision process of TRIP. Its complementary, to be certain, but thats<br> not the same. If you took a normal TRIP LS and put it in front of a<br> TRIP-GW gateway, it would probably not do the right thing. It would<br> function, I think, but you would not be able to implement the<br> appropriate policies to process the information being generated by the<br> gateways.<br> <br> Do people concur with this view?<br> <br> If so, I would propose that we rename the protocol to the Gateway<br> Registration Protocol (GREP). I think the acronym is neat; the protocol<br> is used to search for a gateway, sort of, so grep (in the unix sense)<br> kind of works.<br> <br> The protocol syntax and semantics remain unchanged. We will simply<br> indicate that large pieces of TRIP are used wholesale by this protocol,<br> referring the user to the appropriate sections of the TRIP spec.<br> <br> Thoughts?<br> <br> Thanks,<br> Jonathan R.<br> --<br> Jonathan D. Rosenberg, Ph.D.  = ; 72 Eagle Rock Ave.<br> Chief Scientist &= nbsp;  = ; First Floor<br> dynamicsoft  = ; &nb= sp; East Hanover, NJ 07936<br> [email protected]  = ; FAX: (973) 952-5050<br> <a href=3D"http://www.jdrosen.net=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0/" eudora=3D"autourl">http://www.jdrosen.net  = ; &nb= sp; </a> PHONE: (973) 952-5000<br> <a href=3D"http://www.dynamicsoft.com/"= eudora=3D"autourl">http://www.dynamicsoft.com</a><br> <br> _______________________________________________<br> IPTEL mailing list<br> [email protected]<br> <a href=3D"http://lists.bell-labs.com/mailman/listinfo/iptel"= eudora=3D"autourl">http://lists.bell-labs.com/mailman/listinfo/iptel</a><br= > _______________________________________________<br> IPTEL mailing list<br> [email protected]<br> <a href=3D"http://lists.bell-labs.com/mailman/listinfo/iptel"= eudora=3D"autourl">http://lists.bell-labs.com/mailman/listinfo/iptel</a><br= > _______________________________________________<br> IPTEL mailing list<br> [email protected]<br> <a href=3D"http://lists.bell-labs.com/mailman/listinfo/iptel"= eudora=3D"autourl">http://lists.bell-labs.com/mailman/listinfo/iptel</a><br= > <br> <br> <br> <br> _______________________________________________<br> IPTEL mailing list<br> [email protected]<br> <a href=3D"http://lists.bell-labs.com/mailman/listinfo/iptel" eudora=3D"auto= url">http://lists.bell-labs.com/mailman/listinfo/iptel</a> </font></blockquote></html> --=====================_55217017==_.ALT--