Richard Shockey | 1 Oct 16:58

To whom it may concern

The following ID contains a template for a new URI scheme to be known as
PSTN:

The rationale and usage of this new URI are contained in the document
attached.

Richard Shockey
Director, Member of the Technical Staff
NeuStar
46000 Center Oak Plaza - Sterling, VA 20166
sip:rshockey(at)iptel.org 
PSTN Office +1 571.434.5651 
PSTN Mobile: +1 703.593.2683
<mailto:richard(at)shockey.us> 
<mailto:richard.shockey(at)neustar.biz>


  ENUM Working Group                    R. Shockey - editor 
  Internet-Draft                        NeuStar 
  Expires: March 2008                   September 2007 

                                      

 
    IANA Registration for an Enumservice Calling Name Delivery (CNAM) 
         Information and IANA Registration for URI type 'pstn' 

                   draft-ietf-enum-cnam-06.txt 
(Continue reading)

Martin Duerst | 2 Oct 11:19

Re: To whom it may concern

Hello Richard,

A few comments to your proposal:

- There is already a tel: URI scheme for actually initiating telephone
  calls to telephone numbers. My understanding is that your URI scheme
  doesn't do the same, but is for use behind the scenes. But I'm not
  sure, and would like you to clarify the relationship to the tel:
  scheme, at least on this mailing list.

- From the examples, it looks like the only or main purpose of the
  proposed scheme is to encode information in a specific protocol.
  With such a limited field of use, does it make sense to provide
  a new scheme? Couldn't that data be transferred more easily in
  a different way.

- It seems that the use of "pstn" as a scheme name is a bit problematic;
  usually pstn stands for "public switched telephone network", which
  in my understanding is more a generic term than the name of a specific
  protocol.

- Some examples use "charset=ascii", the mime preferred name is
  us-ascii (see http://www.iana.org/assignments/character-sets).
  What is the reason to not use the mime preferred name?

- The draft text contains non-ASCII characters (in particular
  apostrophes/quotes). Internet Drafts have to be US-ASCII only.

- Your draft says that "This specification does not preclude 
  the use of internationalized characters within the pstn URI, nor
(Continue reading)

Richard Shockey | 4 Oct 04:08

RE: To whom it may concern


>  -----Original Message-----
>  From: Martin Duerst [mailto:duerst <at> it.aoyama.ac.jp]
>  Sent: Tuesday, October 02, 2007 5:20 AM
>  To: Richard Shockey; uri-review <at> ietf.org
>  Subject: Re: [Uri-review] To whom it may concern
>  
>  Hello Richard,
>  
>  A few comments to your proposal:
>  
>  - There is already a tel: URI scheme for actually initiating telephone
>    calls to telephone numbers. My understanding is that your URI scheme
>    doesn't do the same, but is for use behind the scenes. But I'm not
>    sure, and would like you to clarify the relationship to the tel:
>    scheme, at least on this mailing list.

Our first inclination to use the TEL: URI but I ran into massive objections
from the SIP/RAI community who adamantly rejected any use of TEL for data
not directly related to routing. CNAM is not routing data it is data
associated with a telephone number namely the verbose name of the caller.

After consulting with the usual suspects in the SIP community they suggested
using the data: URI.. fine by me but then I ran into opposition from the
IESG and others who were looking to deprecate the use of data: URI in much
the same way the IESG wants to halt the use of TXT RR in the DNS for strange
and bizarre data types that don't specifically fit into a nice neat shoe
box.

After consulting privately with Larry Masinter the author of the data URI he
(Continue reading)

Martin Duerst | 4 Oct 09:28

RE: To whom it may concern

Hello Richard,

At 11:08 07/10/04, Richard Shockey wrote:
>
>
>>  -----Original Message-----
>>  From: Martin Duerst [mailto:duerst <at> it.aoyama.ac.jp]
>>  Sent: Tuesday, October 02, 2007 5:20 AM
>>  To: Richard Shockey; uri-review <at> ietf.org
>>  Subject: Re: [Uri-review] To whom it may concern
>>  
>>  Hello Richard,
>>  
>>  A few comments to your proposal:
>>  
>>  - There is already a tel: URI scheme for actually initiating telephone
>>    calls to telephone numbers. My understanding is that your URI scheme
>>    doesn't do the same, but is for use behind the scenes. But I'm not
>>    sure, and would like you to clarify the relationship to the tel:
>>    scheme, at least on this mailing list.
>
>Our first inclination to use the TEL: URI but I ran into massive objections
>from the SIP/RAI community who adamantly rejected any use of TEL for data
>not directly related to routing.

Given your explanations of how this stuff works, which confirm my
previous vague understanding, I would have to agree.

>CNAM is not routing data it is data
>associated with a telephone number namely the verbose name of the caller.
(Continue reading)

Richard Shockey | 4 Oct 18:25

RE: To whom it may concern


In line ...

>  >>  Hello Richard,
>  >>
>  >>  A few comments to your proposal:
>  >>
>  >>  - There is already a tel: URI scheme for actually initiating
>  telephone
>  >>    calls to telephone numbers. My understanding is that your URI
>  scheme
>  >>    doesn't do the same, but is for use behind the scenes. But I'm
>  not
>  >>    sure, and would like you to clarify the relationship to the tel:
>  >>    scheme, at least on this mailing list.
>  >
>  >Our first inclination to use the TEL: URI but I ran into massive
>  objections
>  >from the SIP/RAI community who adamantly rejected any use of TEL for
>  data
>  >not directly related to routing.
>  
>  Given your explanations of how this stuff works, which confirm my
>  previous vague understanding, I would have to agree.
>  
>  >CNAM is not routing data it is data
>  >associated with a telephone number namely the verbose name of the
>  caller.
>  >
>  >After consulting with the usual suspects in the SIP community they
(Continue reading)


Gmane