Re: Use of ENUM RFC2916 by Internet Fax
Richard Shockey <[email protected]>
| Newsgroups | gmane.ietf.fax |
|---|---|
| Message-ID | <[email protected]> |
At 10:03 AM 2/26/2002 +0100, Claudio Allocchio wrote: > > We have the Addressing I-D by Claudio now. So, I think it is meaningful. > > > > Claudio, > > is it OK for you? > >Yes! > >The "phone number syntax" (actually it is not addressing) I-D just gives >the way to write down E.164 numbers in a text string, but ENUM >capabilities an be used by I-fax... just a few ones: is there an I-fax >gateway associated to that E.164 number? ... True but then you get into the famous ENUM vs TRIP issues :-) ...but of particular interest to some of us in the ENUM WG is the issue of how granular must the NAPTR service field be for any particular application. Internet Fax represents a interesting case since it is based on SMTP the question what hinds of hints might be required to identify the capabilities of the endpoint come to the forefront. It back to the old issues of how do you discover the capabilities of a IFax client that haunted the Simple mode. Well that was the basis for most of the RESCAP work but at least in ENUM you can query in advance of sending the document and discover not only the URL for the endpoint but perhaps pointers to its capabilities. Is there requirements for things like [ IFAX-S+E2U ] for the simple mode ? [ IFAX-FX+E2U] for advanced? I don't know. This is why a discussion ENUM applicability to fax could be very interesting. I'll plan on a simple review of where the ENUM WG is going.. >Claudio >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Richard Shockey, Senior Manager, Strategic Technology Initiatives NeuStar Inc. 45980 Center Oak Plaza Bldg 8 Sterling, VA 20166 1120 Vermont Ave NW Suite 400 Washington DC 20005 Voice +1 571.434.5651 Cell : +1 314.503.0640, Fax: +1 815.333.1237 <mailto: [email protected]> or <mailto: [email protected]> <http://www.neustar.biz> <http://www.enum.org> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<