[dispatch] VIPR - relation to public ENUM text

[Cullen Jennings <[e-mail]>]

Thanks - I changed that a little bit and put it in the updated version.


On Jun 2, 2010, at 12:49 PM, Peter Musgrave wrote:

> How about:
> 
> "The essential characteristic of ViPR is establishing authentication
> by PSTN reachability and not by e.g. direct reference to ENUM
> databases or other assertions of PSTN number ownership. Elements such
> as public ENUM may be employed indirectly as part of assessing the
> PSTN reachability but no direct interaction with ENUM will be
> required. "
> 
> Peter
> 
> On Wed, Jun 2, 2010 at 2:35 PM, Cullen Jennings <[e-mail]> wrote:
>> 
>> I kept trying to write something about the relation of ViPR to ENUM but it kept coming out sounding like public ENUM had failed - which was not really what I wanted to say so I eventually deleted it. If someone had some good text about ENUM, would be nice to add it.
>> 
>> I view infrastructure and carrier ENUM as somewhat unrelated to this but public ENUM is related. However, ENUM talks about how to query the database, but it is somewhat silent on how data gets in the database. How does the database authorize that someone is authoritative for a number and can put write a record into the ENUM database. VIPR is more about that side of the problem.
>> 
>> And +1 to Paul's answers of the other questions ....
>> 
>> On Jun 1, 2010, at 12:28 PM, Peter Musgrave wrote:
>> 
>>> Hi Cullen,
>>> 
>>> Does the charter need to say anything explicitly about not relying on
>>> any of the work which uses ENUMs in DNS as a way of associating SIP
>>> endpoints and IP addresses?
>>> 
>>> AFAIK ViPR is about *using* a SIP call to determine a path to the
>>> endpoint (however that happens to work).
>>> 
>>> Does the charter need to stipulate that the mapping from a PSTN number
>>> to a SIP device is a one-to-one mapping? Does there need to be text
>>> about how multiple endpoints which are behind a border device (and all
>>> appear as the same PSTN number) are to be handled?.
>>> 
>>> ViPR so far describes an "edge-device" approach. Is the charter
>>> restricted to this approach?
>>> 
>>> Thanks,
>>> 
>>> Peter Musgrave
>>> 
>>> 
>>> 
>>> On Tue, Jun 1, 2010 at 12:55 PM, Cullen Jennings <[e-mail]> wrote:
>>>> 
>>>> I've been talking to a lot of people about the VIPR drafts  - here is a first cut of a proposal for a WG that could do this. I'm sure the charter proposal needs a bunch of work but I wanted to get the discussion rolling on the list.
>>>> 
>>>> Thanks, Cullen
>>>> 
>>>> (PS - this is sent in my individual contributor role. Take all my posts about VIPR to be in my individual role not my co-chair role)
>>>> 
>>>> -------------------------------------------------------
>>>> 
>>>> ViPR Charter Proposal (Version 0)
>>>> 
>>>> WG Name:  Verification Involving PSTN Reachability (VIPR)
>>>> 
>>>> There are two globally deployed address spaces for communications that more than a billion people use on a daily basis. They are phone numbers and DNS rooted address such as web servers and email addresses. The federation design of SIP is primarily designed for email style addresses yet a large percentage of SIP deployments primarily use phone numbers for identifying users. The goal of this working group is to allows people to use SIP to federate over the the internet while still using phone numbers to identify the person they wish to communicate with.
>>>> 
>>>> The VIPR WG will address this problem by developing a peer to peer based approach to finding SIP domains that claim to be responsible for a given phone number and the WG will design validation protocols to ensure a reasonable likelihood that a given domain actually is responsible for the phone number. One initial validation protocol will be based on a domain being able to prove it received a particular phone call over the PSTN based on both sides knowing the start and stop times of that call. Other validation schemes, such as examining fingerprints or watermarking of PSTN media, to show that a domain received a particular PSTN phone call may be considered by the working group. To help mitigate SPAM over SIP issues, the WG will define an token based authorization scheme so that domain using SIP to federate can choose to check that incoming SIP calls are from a domain that successfully validated a phone number.
>>>> 
>>>> The problem statement and some possible starting points for solutions are further desired in the following internet drafts which shall form the bases of the WG documents:
>>>> draft-rosenberg-dispatch-vipr-overview
>>>> draft-rosenberg-dispatch-vipr-reload-usage
>>>> draft-rosenberg-dispatch-vipr-pvp
>>>> draft-rosenberg-dispatch-vipr-sip-antispam
>>>> 
>>>> The working group will carefully coordinate with the security area, O&M area, as well as the appropriate RAI WG including sipcore and p2psip.
>>>> 
>>>> 
>>>> _______________________________________________
>>>> dispatch mailing list
>>>> [e-mail]
>>>> https://www.ietf.org/mailman/listinfo/dispatch
>>>> 
>>> 
>> 
>> 
>> Cullen Jennings
>> For corporate legal information go to:
>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>> 
>> 
>> 
>> 


Cullen Jennings
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html