[dispatch] VIPR - proposed charter version 2
Cullen Jennings <fluffy@cisco.com> Tue, 15 June 2010 17:24 UTC
Return-Path: <fluffy@cisco.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 1DC513A6852 for <dispatch@core3.amsl.com>; Tue, 15 Jun 2010 10:24:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.711
X-Spam-Level:
X-Spam-Status: No, score=-108.711 tagged_above=-999 required=5 tests=[AWL=-0.712, BAYES_50=0.001, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 hl35MjdB2JiS for <dispatch@core3.amsl.com>; Tue, 15 Jun 2010 10:24:48 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 3B3943A687C for <dispatch@ietf.org>; Tue, 15 Jun 2010 10:24:48 -0700 (PDT)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEANNTF0yrR7Ht/2dsb2JhbACedHGmT5otglmCQQSDTw
X-IronPort-AV: E=Sophos;i="4.53,421,1272844800"; d="scan'208";a="335353356"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-1.cisco.com with ESMTP; 15 Jun 2010 17:24:52 +0000
Received: from [192.168.4.177] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o5FHNENF018261 for <dispatch@ietf.org>; Tue, 15 Jun 2010 17:24:52 GMT
From: Cullen Jennings <fluffy@cisco.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Impp: xmpp:cullenfluffyjennings@jabber.org
Date: Tue, 15 Jun 2010 11:24:51 -0600
Message-Id: <DB6CA94F-0EC9-4E27-A190-D12029CA61AE@cisco.com>
To: DISPATCH list <dispatch@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1078)
X-Mailer: Apple Mail (2.1078)
Subject: [dispatch] VIPR - proposed charter version 2
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 17:24:49 -0000
Thanks for all the comments on the list. Here is a revised version: (PS. If anyone else wants to edit, this is in SVN and glad to get anyone write permission) ======================================== ViPR Charter Proposal (Version 2) 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 inter-domain signaling design of SIP is primarily designed for email style addresses yet a large percentage of SIP deployments mostly use phone numbers for identifying users. The goal of this working group is to enable inter-domains communications over the the internet, using protocol such as SIP, while still allowing people to use 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 domains that claim to be responsible for a given phone number and validation protocols to ensure a reasonable likelihood that a given domain actually is responsible for the phone number. In this context, we use "responsible" to mean an administrative domain would would be at least one of the administrative domains that a PSTN call to this phone number would be routed to. Once the domain responsible for the phone number is found, existing protocols such as SIP and XMPP can be used for inter-domain communications. Some validation protocols may be based on knowledge gathered around a SIP call, for example, the ability to prove a call was received over the PSTN based on start and stop times. Other validation schemes, such as examining fingerprints or watermarking of PSTN media, to show that a domain received a particular PSTN phone call may also be considered by the working group. The WG will select and standardize at least one validation scheme. To help mitigate SPAM issues when using SIP between domains, the WG will define a mechanisms to enable one domain to check that incoming SIP messages from a different domain are coming from a domain that successfully validated a phone number. The working group will define new SIP headers and option tags to enable this. The essential characteristic of ViPR is establishing authentication by PSTN reachability when it is not possible to use a direct reference to ENUM databases or other direct assertions of PSTN number ownership. Elements such as public ENUM easily coexist with VIPR but no direct interaction with ENUM will be required. The problem statement and some possible starting points for solutions are further discussed 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.
- Re: [dispatch] VIPR - proposed charter version 2 Cullen Jennings
- [dispatch] VIPR - proposed charter version 2 Cullen Jennings
- Re: [dispatch] VIPR - proposed charter version 2 … Roni Even
- Re: [dispatch] VIPR - proposed charter version 2 … Peter Musgrave
- Re: [dispatch] VIPR - proposed charter version 2 … Paul Kyzivat
- Re: [dispatch] VIPR - proposed charter version 2 Elwell, John
- Re: [dispatch] VIPR - proposed charter version 2 WORLEY, Dale R (Dale)
- Re: [dispatch] VIPR - proposed charter version 2 … Cullen Jennings
- Re: [dispatch] VIPR - proposed charter version 2 … Cullen Jennings
- Re: [dispatch] VIPR - proposed charter version 2 … Roni Even
- Re: [dispatch] VIPR - proposed charter version 2 … Jonathan Rosenberg
- Re: [dispatch] VIPR - proposed charter version 2 Jonathan Rosenberg
- Re: [dispatch] VIPR - proposed charter version 2 … Milinski, Alexander (NSN - DE/Munich)
- Re: [dispatch] VIPR - proposed charter version 2 … Jonathan Rosenberg