Re: [dispatch] Charter Proposal: Verification Involving PSTN Reachability (VIPR)

[Paul Kyzivat <[e-mail]>]

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).

As I understand it, the new WG is about coming up with technique(s) that 
work and are deployable in the real world. While in principle public 
ENUM could be used for this, in practice it isn't deployed and so isn't 
really usable. The technique of using a pstn call to determine the path 
is one technique that is demonstrably deployable.

> 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?.

IIUC, its likely to be a server responsible for a phone number AOR that 
will participate in ViPR, rather than individual phone devices. 
Certainly there can be additional routing after a ViPR call reaches that 
server. Typically there will only be one of those, or a cooperative 
cluster of them sharing the same DNS name or ip address. That is really 
no different than normal sip routing to AORs.

Also, AFAIK it doesn't have to be 1:1.
Multiple claims can be made for ownership of a phone number. If calls to 
them can be verified, then they can all be valid candidates for calls to 
that number. (However, this will logistically be hard to accomplish.)

	Thanks,
	Paul

> 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
>>
> _______________________________________________
> dispatch mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/dispatch
>