attachment
<html>
<font size=3>If there is going to be a separate "E.164" URL
type for voice and fax, how <br>
does mechanism work for phone numbers that are both voice and fax -- many
<br>
homes have a system that takes voice messages and faxes. <br>
<br>
Bob Herriot<br>
<br>
<br>
At 06:14 AM 7/13/98 , Keith Moore wrote:<br>
>> 2. In cases where people handle URL's, I think the
"http:" URL is better<br>
>> from a number of perspectives which I have already
described. Some how<br>
>> people seem to figure out business cards that say:<br>
>> <br>
>> Phone: 606-232-4808<br>
>> Fax: 606-232-6740<br>
>> <br>
><br>
>It's interesting that you should cite that case. The discussion
recently<br>
>came up on the URI list as to whether there should be a single
"E.164"<br>
>URL type for all phone numbers, or whether there should be separate
URL<br>
>types for voice, fax, etc.<br>
><br>
>The conclusion was that they had to be separate, because the user
<br>
>interfaces for the handling of fax and phone needed to be different,
<br>
>and also because in some cases (e.g. ISDN) the call setup actually
<br>
>needed to know which was being used before the call was placed.<br>
><br>
>The http/ipp argument seems very similar to me, with a similar
conclusion.<br>
><br>
>Keith<br>
> </font><br>
</html>