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

Roni Even <Even.roni@huawei.com> Tue, 15 June 2010 22:25 UTC

Return-Path: <Even.roni@huawei.com>
X-Original-To: dispatch@core3.amsl.com
Delivered-To: dispatch@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 299183A697A for <dispatch@core3.amsl.com>; Tue, 15 Jun 2010 15:25:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2z4EPLDsF1yz for <dispatch@core3.amsl.com>; Tue, 15 Jun 2010 15:25:39 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 0A4333A68DF for <dispatch@ietf.org>; Tue, 15 Jun 2010 15:25:39 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L4200F44UAUGL@szxga04-in.huawei.com> for dispatch@ietf.org; Wed, 16 Jun 2010 06:25:42 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L42002JMUAU5Q@szxga04-in.huawei.com> for dispatch@ietf.org; Wed, 16 Jun 2010 06:25:42 +0800 (CST)
Received: from windows8d787f9 ([109.67.36.119]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L42002XEUAON7@szxml02-in.huawei.com>; Wed, 16 Jun 2010 06:25:42 +0800 (CST)
Date: Wed, 16 Jun 2010 01:23:18 +0300
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <D92721E4-36AC-4B75-BCDF-E90A9242A286@cisco.com>
To: 'Cullen Jennings' <fluffy@cisco.com>, 'DISPATCH list' <dispatch@ietf.org>
Message-id: <018901cb0cd9$5ebc5af0$1c3510d0$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset="us-ascii"
Content-language: en-us
Content-transfer-encoding: 7bit
Thread-index: AcsBqzwgd0aRgVLbTRuXJn4D04wnPALLaH1w
References: <D92721E4-36AC-4B75-BCDF-E90A9242A286@cisco.com>
Subject: Re: [dispatch] Charter Proposal: Verification Involving PSTN Reachability (VIPR)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jun 2010 22:25:40 -0000

Hi Cullen,
I think that other standard body should be consulted like ITU. The reason is
that I see that one assumption is to use the PSTN numbering plan using also
the caller id. My experience is that this is not information that can be
reliable when going between PSTN service providers and it gets worse on
international calls. 
Roni Even

> -----Original Message-----
> From: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] On
> Behalf Of Cullen Jennings
> Sent: Tuesday, June 01, 2010 7:55 PM
> To: DISPATCH list
> Subject: [dispatch] Charter Proposal: Verification Involving PSTN
> Reachability (VIPR)
> 
> 
> 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
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch