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

"WORLEY, Dale R (Dale)" <dworley@avaya.com> Wed, 02 June 2010 21:21 UTC

Return-Path: <dworley@avaya.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 14E233A68F0 for <dispatch@core3.amsl.com>; Wed, 2 Jun 2010 14:21:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.617
X-Spam-Level:
X-Spam-Status: No, score=-0.617 tagged_above=-999 required=5 tests=[AWL=-0.618, 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 MS2RgKCRCmVe for <dispatch@core3.amsl.com>; Wed, 2 Jun 2010 14:21:54 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id DEA243A67FB for <dispatch@ietf.org>; Wed, 2 Jun 2010 14:21:53 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,348,1272859200"; d="scan'208";a="221128078"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 02 Jun 2010 17:21:40 -0400
X-IronPort-AV: E=Sophos;i="4.53,348,1272859200"; d="scan'208";a="480391805"
Received: from unknown (HELO DC-US1HCEX3.global.avaya.com) ([135.11.52.22]) by co300216-co-erhwest-out.avaya.com with ESMTP; 02 Jun 2010 17:21:40 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.2.188]) by DC-US1HCEX3.global.avaya.com ([135.11.52.22]) with mapi; Wed, 2 Jun 2010 17:21:40 -0400
From: "WORLEY, Dale R (Dale)" <dworley@avaya.com>
To: Cullen Jennings <fluffy@cisco.com>, DISPATCH list <dispatch@ietf.org>
Date: Wed, 02 Jun 2010 17:20:25 -0400
Thread-Topic: [dispatch] Charter Proposal: Verification Involving PSTN Reachability (VIPR)
Thread-Index: AcsBqzrFyHd4No72Q/iGb4t2HVczUgA7i/sq
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FD736157@DC-US1MBEX4.global.avaya.com>
References: <D92721E4-36AC-4B75-BCDF-E90A9242A286@cisco.com>
In-Reply-To: <D92721E4-36AC-4B75-BCDF-E90A9242A286@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Wed, 02 Jun 2010 21:21:55 -0000

I've improved the wording in various places and carefully removed any presumptions regarding the specific solution to be delivered:

ViPR Charter Proposal (a revision)

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:  E.164 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 allow 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 one or more
peer-to-peer based approaches to determining and validating the SIP
URI(s) that are equivalent to a given phone number, without requiring
reference to a global, accurate database.

One approach to be considered 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.  This approach is
described in:

draft-rosenberg-dispatch-vipr-overview
draft-rosenberg-dispatch-vipr-reload-usage
draft-rosenberg-dispatch-vipr-pvp
draft-rosenberg-dispatch-vipr-sip-antispam

Other validation techniques (such as examining fingerprints or
watermarking of PSTN media) may be considered by the working group.

To help mitigate SPAM over SIP issues, the WG also define one or more
authorization schemes allowing a recipient to verify that an
incoming SIP call is from a source that has previously executed a
validation protocol with the recipient.

The working group will carefully coordinate with the security area,
O&M area, and the appropriate RAI WGs (including sipcore and p2psip).

Dale