Subject: [VIPR] The ViPR database

From: "Worley, Dale R (Dale)" <[email-masked]>
Date: Mon, 18 Apr 2011 15:37:55 -0400

These are my suggestions for the abstract data structure of the ViPR database entries.  They contain a bunch of suggestions to maximize extensibility, etc.

An entry is the database is a mapping:

* from a URI

(In the initial case, the "from" URI will be a "tel" URI, but allowing general URIs allows expanding the source address set in the future.  Although in the near future we will probably need to define an extension to specify prefix groups of E.164 numbers.  URIs are composed only of characters in the ASCII set, so there are no encoding issues.)

* to a URI

(In the initial case, the "to" URI will be a "sip" or "sips" URI.)

* with additional information giving the specifications for verification, which are a set of zero or more:

(A set of zero verification methods may be needed to effectively retract a previously published mapping.)

** structures, 

*** the first element being a one-octet number specifying a verification scheme that is supported by the mapping:

**** numbers 0 and 255 are reserved for all time

**** numbers 245 through 254 are reserved for private/experimental usage

**** standardized methods are numbered from 1 upward

*** the second element is auxiliary data for the verification scheme, which is a sequence of zero or more octets.

Dale