Re: preliminary notes from the WG meeting in Philidelphia ..

FYI ..this is what I have so far ..you can obviously suggest another data
type.


Comments are welcome 


**********************

IANA Registration Template for URI "pstndata:" 

  

  URI scheme name.

     The name of the URI is "pstndata:".

   Status.
 

  The intended status is Permanent.  NOTE: The distribution of CNAM data is
often highly restricted. Usage of this URI should either be within

  a service providers internal network, or on a private basis between one or
more parties using a variety of security mechanisms to prevent

  general public access. The records described herein should not be part of
the e164.arpa or any other portion of the DNS tree.

  

  URI scheme syntax.

    

    pstndatauri  = "pstndata:" datatype ["/" telephone-subscriber ] ";"

              (content / reason)

    datatype     = "cnam"

                 ; Other datatypes can be defined by adding

                 alternative values.

    content      = [ mediatype ] [ ":base64" ] "," data

    mediatype    = [ type "/" subtype ] *( ";" parameter )

    data         = *urlchar

    parameter    = attribute "=" value

    reason       = "available=" ("p" / "u")

  

  where "telephone-subscriber" is imported from RFC 3966 [19], "urlchar" is
imported from RFC 2396 [20], and "attribute" and "value"

  are imported from RFC 2045 [21].

  

  URI scheme semantics.

     

    Two optional parameters are defined.

  

  a) Calling Name Privacy Indicator: 'available=p'  

  

  This parameter defined as the Calling Name information may be available
but the Calling Party does not wish to have their Calling

  Name data displayed by Called Party User Agents. 

 

  Intended usage: 'available=p'

  

  b) Calling Name Status Indicator: 'available=u' 

  

  This parameter is defined as there is no Calling Name data for that  E.164
number available.

  

  Intended usage: 'unavailable=u'

  

  Encoding considerations.

  

  The purpose of this URI is to enable service providers to place   Calling
Name Delivery information (CNAM) into RFC 3761 [ENUM]  databases or to send
ENUM queries to a protocol converter that would  have access to the
Signaling System 7 (SS7) Network.  This, in turn, could enable such parties
to offer Calling Name Delivery services  using the technology provided by
RFC 3761.

  

  The information stored in these databases can be encoded to  facilitate
storage and retrieval operations.  The type of encoding used is identified
using appropriate media type parameters.  If not  otherwise identified,
character data is presumed to be encoded using

  US-ASCII [9].

  

  Applications and/or protocols that use this URI scheme name.

  

  This URI scheme is intended for use in RFC 3761 [ENUM] databases.

  

  Interoperability considerations.

  

  The URI is designed to be used specifically in conjunction with trusted
systems that utilize the RFC 3761 [ENUM] databases. 

  

  Security considerations:

  

  The distribution of CNAM data is often highly restricted.    Distribution
of this data would typically be either within a service  providers internal
network, or on a private basis between one or more parties using a variety
of security mechanisms to prohibit  general public access.  It should be
noted that this content type is  designed to carry potentially personal
information and as such, may be subject to restrictions within various
national jurisdictions. .  In many cases, the actual information that needs
to be protected is the combination of the Name associated with the Telephone
Number or the association of the name with the telephone call.  So, it will
be necessary to protect the response to the query that provides the
association between the two elements.

 The pstn URI defined in this document is assumed to be used in an
environment where elements are trusted and where attackers are not supposed
to have access to the protocol messages between those elements.  Traffic
protection between network elements is sometimes achieved by using IPSec [A]
and sometimes by physically protecting the underlying network. In any case,
the provider should ensure that measures are taken to prevent both fraud and
unauthorized disclosure by using a combination of authentication and
Encryption.

 

  

>  
>  Jon - are we supposed to invent a new URI scheme to represent this?
>  FWIW
>  - there are UK Neustar people involved with this particular project
>  too.
>  
>  cheers,
>  
>  Ray
>  
>  --
>  Ray Bellis, MA(Oxon)
>  Senior Researcher in Advanced Projects, Nominet
>  e: [email protected], t: +44 1865 332211