
From wwwrun@core3.amsl.com  Sun Mar 27 01:32:49 2011
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: vipr@ietf.org
Delivered-To: vipr@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id A89263A69B3; Sun, 27 Mar 2011 01:32:49 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20110327083249.A89263A69B3@core3.amsl.com>
Date: Sun, 27 Mar 2011 01:32:49 -0700 (PDT)
X-Mailman-Approved-At: Sun, 27 Mar 2011 02:25:31 -0700
Cc: vipr@ietf.org, d.malas@cablelabs.com, jon.peterson@neustar.biz
Subject: [VIPR] WG Action: Verification Involving PSTN Reachability (vipr)
X-BeenThere: vipr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Verification Involving PSTN Reachability working group <vipr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vipr>
List-Post: <mailto:vipr@ietf.org>
List-Help: <mailto:vipr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Mar 2011 08:32:49 -0000

A new IETF working group has been formed in the Real-time Applications and
Infrastructure Area.  For additional information, please contact the Area
Directors or the WG Chairs.

Verification Involving PSTN Reachability (vipr)
---------------------------------------------------
Current Status: Active Working Group

Chairs:
  Jon Peterson <jon.peterson@neustar.biz>
  Daryl Malas <d.malas@cablelabs.com>

Real-time Applications and Infrastructure Area Director(s):
  Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
  Robert Sparks <rjsparks@nostrum.com>

Real-time Applications and Infrastructure Area Advisor:
  Robert Sparks <rjsparks@nostrum.com>

Mailing Lists:
  General Discussion: vipr@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/vipr
  Archive: http://www.ietf.org/mail-archive/web/vipr/

There are two globally deployed address spaces for communications used
by more than a billion people daily - 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, thus DNS lookups are not sufficient.  The goal of 
this working group is to enable inter-domain communications over the 
Internet, using protocols such as SIP, while still allowing people to 
use phone numbers to identify the person with whom they wish to 
communicate.

The VIPR WG will develop a peer to peer based approach to finding
domains that claim to be responsible for a given phone number
to mitigate the involvement of centralized entities to avoid some of
the issues encountered by past attempts to support SIP inter-domain
communications.  Validation protocols will be developed to ensure a
reasonable likelihood that a given domain actually is responsible for
the phone number.  In this context, "responsible" means an
administrative domain, which is at least one of the domains, to which
a PSTN call to this phone number would be routed.  Once the domain
responsible for the phone number is found, existing protocols, such
as SIP, can be used for inter-domain communications.

Some validation protocols may be based on knowledge gathered around a
PSTN 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.  This validation will be accomplished using publicly
available open interfaces to the PSTN, so the validation can be
performed by any domain wishing to participate.  The WG will select and
standardize at least one validation scheme.

The validation mechanism requires a domain to gather and maintain
information related to PSTN calls.  This information is used by call
agents such as phones, SBCs and IP PBXs to route calls.  The WG will
also develop mechanisms to detect in a timely manner that a given domain
is no longer responsible for a phone number.  The WG will define a
client-server protocol between these call agents and the entity within a
domain that maintains the information.

To help mitigate SPAM issues when using SIP between domains, the WG will
define a mechanism to enable one domain to check that incoming SIP
messages are coming from a validated phone number.  A phone number is
considered validated if it is coming from a domain to which the calling
domain had previously successfully placed a PSTN call.  The working
group will define new SIP headers and option tags, as necessary, 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 solution set defined
by this WG will be incrementally deployable using only existing
interfaces to the PSTN.  No changes will be required to existing PSTN
capabilities, no new database access is needed nor is any new support
from PSTN service providers required.

The WG will produce the following deliverables:

1) A document describing the requirements, problem statement and
architectural approach to support SIP inter-domain communications.
2) A document describing the use of the p2psip protocol (RELOAD) as
applied to this problem space.
3) A document defining a scheme for validating the phone numbers using
publicly available open interfaces to the PSTN.
4) A document defining client-server protocol between call agents and 
the entity within a domain that gathers and maintains information 
related to PSTN calls.
5) A document describing a mechanism to mitigate SPAM issues.

The working group will carefully coordinate with the security area, O&M
area, as well as the appropriate RAI WGs such as sipcore and p2psip.

Goals and Milestones:

Sep 2011  Submit Requirements, Problem statement, and architecture 
          overview for publication as Informational
Dec 2011  Submit Peer to peer base protocol specification for 
          publication as Proposed Standard 
Dec 2011  Submit PSTN based number validation techniques for publication 
          as Proposed Standard
Apr 2012  Submit Protocol for call agents to exchange call and routing 
          information for publication as Proposed Standard
Apr 2012  Submit Specification of authorization tokens to mitigate SPAM 
          for publication as Proposed Standard

From victor.pascual.avila@gmail.com  Thu Mar 31 00:21:03 2011
Return-Path: <victor.pascual.avila@gmail.com>
X-Original-To: vipr@core3.amsl.com
Delivered-To: vipr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A280A28C226 for <vipr@core3.amsl.com>; Thu, 31 Mar 2011 00:21:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.349
X-Spam-Level: 
X-Spam-Status: No, score=-3.349 tagged_above=-999 required=5 tests=[AWL=0.250,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 Ren6ZI+vVPaw for <vipr@core3.amsl.com>; Thu, 31 Mar 2011 00:21:02 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by core3.amsl.com (Postfix) with ESMTP id 8A58F28C223 for <vipr@ietf.org>; Thu, 31 Mar 2011 00:21:02 -0700 (PDT)
Received: by gyf3 with SMTP id 3so969712gyf.31 for <vipr@ietf.org>; Thu, 31 Mar 2011 00:22:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=K6jz84XI4Zh2BO2nHME5FIDSYLEXHjt/nzahp4ewdsc=; b=disbwrKl2yu8oyBFgeIfLb8+ekOTRjmSPJbGVbkYUJeXsvMFVixoSAbb+WkJzhirHH IfTiXcBjQtaLXHtUrsLoCyClhLrna5v32KMUWp2s3VqSeAnx5ZW01Cg8dW2o73JX55mp Fp2onohK11vIBQKC69CnfTccfoz/FSlyiqxmA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=bqNZ3E30t9I/0Nt3+tfZZdKji9mwftczHgzQI5BClqccPWe3umrjrdl2dXJWw0KFdv /MPOgwDXo6opsQIXUzzYS93DgletpxajGAp51lFzGPb3L23dg0onnP7EObECdHyeXs2u zn9ez4xNbJ1yYxRPENp7KdqtnR7hYpNz47PS0=
MIME-Version: 1.0
Received: by 10.90.152.8 with SMTP id z8mr2660847agd.67.1301556161594; Thu, 31 Mar 2011 00:22:41 -0700 (PDT)
Received: by 10.90.74.20 with HTTP; Thu, 31 Mar 2011 00:22:41 -0700 (PDT)
Date: Thu, 31 Mar 2011 09:22:41 +0200
Message-ID: <AANLkTi=rA_pbZagUNQ9VeOAKUsfAsV_ytnr0ucBGxQ_i@mail.gmail.com>
From: Victor Pascual Avila <victor.pascual.avila@gmail.com>
To: vipr@ietf.org
Content-Type: text/plain; charset=UTF-8
Subject: [VIPR] agenda/materials for today's meeting?
X-BeenThere: vipr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Verification Involving PSTN Reachability working group <vipr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vipr>
List-Post: <mailto:vipr@ietf.org>
List-Help: <mailto:vipr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 07:21:03 -0000

Hi,

where could I find the agenda/materials for today's meeting?

I've tried [1], [2], [3] and [4] but failed to find content there.

[1] http://tools.ietf.org/wg/vipr/agenda
[2] https://datatracker.ietf.org/meeting/80/materials.html
[3] https://datatracker.ietf.org/meeting/80/agenda/vipr-drafts.tgz
[4] https://datatracker.ietf.org/meeting/80/agenda/vipr-drafts.pdf

Cheers,
-Victor

From fluffy@cisco.com  Thu Mar 31 03:18:15 2011
Return-Path: <fluffy@cisco.com>
X-Original-To: vipr@core3.amsl.com
Delivered-To: vipr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F032B3A6A3A for <vipr@core3.amsl.com>; Thu, 31 Mar 2011 03:18:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 lH6RnnXUOOeG for <vipr@core3.amsl.com>; Thu, 31 Mar 2011 03:18:15 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id CD9583A6864 for <vipr@ietf.org>; Thu, 31 Mar 2011 03:18:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=113; q=dns/txt; s=iport; t=1301566795; x=1302776395; h=from:content-transfer-encoding:subject:date:message-id: to:mime-version; bh=FkfuoXH2NGdR/6KSSvePyYnQbkt2b/OqAZZunMv3YP8=; b=KBS9Cnap3oKKFii3aIdqA0494h2CdUpkjTE+t9tDWDYPbAc+gJYl2m8M TE0aIx/NUB3OCa7btgP20moYTToxJWYUsQ4WMdOX3nCmtK4BBgeOGsz+V Ama6xaUr9qr3e1TZusiMpKcxZxngwxXvTmMYs+D/h21kq1c9cxAxRlP89 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiUGAP5UlE2Q/khLgWdsb2JhbACYTI0BFAEBFiYliHKZXZwPhWsEjRE
X-IronPort-AV: E=Sophos;i="4.63,274,1299456000"; d="scan'208";a="81618628"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 31 Mar 2011 10:19:53 +0000
Received: from ams3-vpn-dhcp2012.cisco.com (ams3-vpn-dhcp2012.cisco.com [10.61.71.220]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p2VAJrTQ014722 for <vipr@ietf.org>; Thu, 31 Mar 2011 10:19:53 GMT
From: Cullen Jennings <fluffy@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 31 Mar 2011 12:19:53 +0200
Message-Id: <491AF5F3-8B14-4733-A9AD-B346F7CFEFF9@cisco.com>
To: vipr@ietf.org
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [VIPR] Draft Agenda
X-BeenThere: vipr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Verification Involving PSTN Reachability working group <vipr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vipr>
List-Post: <mailto:vipr@ietf.org>
List-Help: <mailto:vipr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 10:18:16 -0000

Daryl asked me to point out the the draft agenda is at 

http://www.ietf.org/proceedings/80/agenda/vipr.txt



From HKaplan@acmepacket.com  Thu Mar 31 07:34:58 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: vipr@core3.amsl.com
Delivered-To: vipr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 950623A6B55 for <vipr@core3.amsl.com>; Thu, 31 Mar 2011 07:34:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.773
X-Spam-Level: 
X-Spam-Status: No, score=-0.773 tagged_above=-999 required=5 tests=[AWL=-0.278, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
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 db9j5lBKbD4u for <vipr@core3.amsl.com>; Thu, 31 Mar 2011 07:34:57 -0700 (PDT)
Received: from ETMail2.acmepacket.com (unknown [216.41.24.9]) by core3.amsl.com (Postfix) with ESMTP id 9D6733A6B49 for <vipr@ietf.org>; Thu, 31 Mar 2011 07:34:57 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by ETMail2.acmepacket.com (216.41.24.9) with Microsoft SMTP Server (TLS) id 8.1.240.5; Thu, 31 Mar 2011 10:36:36 -0400
Received: from mailbox1.acmepacket.com ([216.41.24.12]) by mail ([127.0.0.1]) with mapi; Thu, 31 Mar 2011 10:36:36 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "vipr@ietf.org" <vipr@ietf.org>
Date: Thu, 31 Mar 2011 10:36:34 -0400
Thread-Topic: Creating an alt-root for E.164
Thread-Index: AcvvsQobIg2ja3G9QyKPYQ8EqnZMgA==
Message-ID: <24AD6F1F-1511-4DFF-AE67-EACC8DF36969@acmepacket.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
X-Brightmail-Tracker: AAAAAQAAAUA=
Subject: [VIPR] Creating an alt-root for E.164
X-BeenThere: vipr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Verification Involving PSTN Reachability working group <vipr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vipr>
List-Post: <mailto:vipr@ietf.org>
List-Help: <mailto:vipr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 14:34:58 -0000

Howdy,
I apologize if this has been hashed out already - if so please tell me to R=
TFM and I'll try and find the thread. (I did google already without luck)

I have a question about why we're ok with creating an alt-root for ITU's ow=
nership of E.164 in an IETF protocol.  By that I mean that for however long=
 the vipr client is willing to believe the vipr-resolved URI represents the=
 E.164, it is not querying the authoritative database (ie, the PSTN).  The =
truth of the matter is your phone does not own and is not authoritative for=
 the E.164 phone number - afaik only the ITU is truly authoritative for it =
(but yes assigns them out downhill).

So for example, right now if you dial the E.164 +1-781-328-4428, it resolve=
s to my desk phone (well, actually to voicemail since I never answer my des=
k phone).  Let's pretend my desk phone did vipr.  If I get fired or quit to=
morrow, my employer would re-allocate my number immediately - most likely t=
o a receptionist for some period of time, and ultimately to a new employee.=
  From my employer's perspective, they "own" +1-781-328-4428, and should ha=
ve the right/power to reallocate it at their leisure/whim.  Yet VIPR moves =
the ownership time decision to the caller, for whatever duration time it wa=
nts to use.=20

In the IETF we have a long-standing concern with creating an alt-root for D=
NS.  So to put this in terms people here may grok, imagine if we have vipr =
resolve email addresses instead of E.164 numbers.  I send an email through =
my email server to "fluffy@cisco.com".  My email server subsequently uses a=
 vipr model to learn a "direct" URI of "mail:c.jennings@ieee.org" or even "=
mail:root@10.1.2.3", and sends all my subsequent emails for "mail:fluffy@ci=
sco.com" to the "direct" one.  Would that be ok?  Would it be ok to use vip=
r to resolve-cache from "mail:chair@iab.org" to "mail:olaf@ripe.net" for th=
e next 6 months?

-hadriel


From sohel_khan@cable.comcast.com  Thu Mar 31 07:22:06 2011
Return-Path: <sohel_khan@cable.comcast.com>
X-Original-To: vipr@core3.amsl.com
Delivered-To: vipr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 403CF3A6B33 for <vipr@core3.amsl.com>; Thu, 31 Mar 2011 07:22:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.462
X-Spam-Level: 
X-Spam-Status: No, score=-108.462 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=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 ooqfbmUR8UOQ for <vipr@core3.amsl.com>; Thu, 31 Mar 2011 07:22:03 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id 340133A6A92 for <vipr@ietf.org>; Thu, 31 Mar 2011 07:22:03 -0700 (PDT)
Received: from ([24.40.55.41]) by pacdcimo01.cable.comcast.com with ESMTP with TLS id 5503620.118224937; Thu, 31 Mar 2011 10:22:41 -0400
Received: from PACDCEXMB02.cable.comcast.com ([169.254.71.78]) by PACDCEXHUB02.cable.comcast.com ([fe80::11d4:f530:37a0:9f4e%12]) with mapi id 14.01.0270.001; Thu, 31 Mar 2011 10:22:36 -0400
From: "Khan, Sohel" <Sohel_Khan@cable.comcast.com>
To: "vipr@ietf.org" <vipr@ietf.org>
Thread-Topic: Draft: SIP Extensions for Blocking VoIP Spam
Thread-Index: AcvvrxpHMsYpbblFTXmsTfvtA0mgKg==
Date: Thu, 31 Mar 2011 14:22:35 +0000
Message-ID: <837E772D16C77141BFA5FEC3F30487FF30C1C767@PACDCEXMB02.cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [76.96.111.6]
Content-Type: multipart/alternative; boundary="_000_837E772D16C77141BFA5FEC3F30487FF30C1C767PACDCEXMB02cabl_"
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 31 Mar 2011 08:17:24 -0700
Subject: [VIPR] Draft: SIP Extensions for Blocking VoIP Spam
X-BeenThere: vipr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Verification Involving PSTN Reachability working group <vipr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vipr>
List-Post: <mailto:vipr@ietf.org>
List-Help: <mailto:vipr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 14:22:06 -0000

--_000_837E772D16C77141BFA5FEC3F30487FF30C1C767PACDCEXMB02cabl_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I have many questions on this draft.

First, in section 3.0 second paragraph:
"...This INVITE will contain a ticket in the X-Cisco-ViPR-Ticket header fie=
ld value."

 Should a proprietary header such as  "X-Cisco-ViPR-Ticket" be used?

Thank You

Sincerely,

Sohel Khan, Ph.D.
Product Engineering, Comcast




--_000_837E772D16C77141BFA5FEC3F30487FF30C1C767PACDCEXMB02cabl_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:Courier;
	panose-1:2 7 4 9 2 2 5 2 4 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"Section1">
<p class=3D"MsoNormal">I have many questions on this draft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">First, in section 3.0 second paragraph:<o:p></o:p></=
p>
<p class=3D"MsoNormal" style=3D"text-autospace:none">&#8220;&#8230;<span st=
yle=3D"font-size:10.0pt;font-family:Courier">This INVITE will contain a tic=
ket in the X-Cisco-ViPR-Ticket header field value.&#8221;<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;Should a proprietary header such as &nbsp;&#82=
20;X-Cisco-ViPR-Ticket&#8221; be used?
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;color:#7030A0">Thank =
You<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;color:#7030A0"><o:p>&=
nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;color:#7030A0">Sincer=
ely,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;color:#7030A0"><o:p>&=
nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;color:#7030A0">Sohel =
Khan, Ph.D.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:9.0pt;color:#7030A0">Produc=
t Engineering, Comcast<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_837E772D16C77141BFA5FEC3F30487FF30C1C767PACDCEXMB02cabl_--

From rbarnes@bbn.com  Thu Mar 31 09:48:46 2011
Return-Path: <rbarnes@bbn.com>
X-Original-To: vipr@core3.amsl.com
Delivered-To: vipr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4FAF73A6A4C for <vipr@core3.amsl.com>; Thu, 31 Mar 2011 09:48:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level: 
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045, BAYES_00=-2.599, 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 mUOvqchPF0Ms for <vipr@core3.amsl.com>; Thu, 31 Mar 2011 09:48:44 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by core3.amsl.com (Postfix) with ESMTP id 6FF713A699E for <vipr@ietf.org>; Thu, 31 Mar 2011 09:48:44 -0700 (PDT)
Received: from [128.89.255.186] (port=54627 helo=[130.129.71.95]) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1Q5L4h-0007Fu-IE; Thu, 31 Mar 2011 12:50:23 -0400
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <24AD6F1F-1511-4DFF-AE67-EACC8DF36969@acmepacket.com>
Date: Thu, 31 Mar 2011 09:50:17 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6CDDB1C2-B05D-40B9-8B80-A6F0167765E6@bbn.com>
References: <24AD6F1F-1511-4DFF-AE67-EACC8DF36969@acmepacket.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
X-Mailer: Apple Mail (2.1082)
Cc: "vipr@ietf.org" <vipr@ietf.org>
Subject: Re: [VIPR] Creating an alt-root for E.164
X-BeenThere: vipr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Verification Involving PSTN Reachability working group <vipr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vipr>
List-Post: <mailto:vipr@ietf.org>
List-Help: <mailto:vipr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 16:48:46 -0000

Hey Hadriel,

> Yet VIPR moves the ownership time decision to the caller, for whatever =
duration time it wants to use.=20

I think you've got the wrong metaphor here.  VIPR is an empirical =
system: Since PSTN-VoIP mappings can't be queried directly (as they =
would through ENUM), VIPR infers them based on empirical observations of =
the PSTN (through calls).  This is inherently an estimate, which comes =
with experimental uncertainty.

There's actually a direct analogy here to geolocation services.  =
Telephone networks have a very good idea of where user devices are, but =
they refuse to share this information with "over-the-top" services =
(except for a very few exceptions).  So the people who were interested =
in locating mobile phones developed a system based on empirical =
measurements (i.e., wardriving), which is a major basis for =
location-based mobile applications today.  It's less accurate than the =
authoritative data that the telcos have, but it works without telco =
intervention.

The upshot of your comment is that there is some inherent uncertainty in =
VIPR mappings.  I don't think that's a controversial point.  The more =
productive question is how to manage this uncertainty, e.g., through =
mapping timeouts or frequency of measurement.

If it's directly replication of e164.arpa that you're worried about, =
that's already being done on some scale.  The biggest project I'm aware =
of is that a consortium of European NRENs are exchanging VoIP using ENUM =
under the nrenum.net tree:
<https://www.nrenum.net/>

--Richard=

From HKaplan@acmepacket.com  Thu Mar 31 15:17:26 2011
Return-Path: <HKaplan@acmepacket.com>
X-Original-To: vipr@core3.amsl.com
Delivered-To: vipr@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 744AA28C141 for <vipr@core3.amsl.com>; Thu, 31 Mar 2011 15:17:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.753
X-Spam-Level: 
X-Spam-Status: No, score=-0.753 tagged_above=-999 required=5 tests=[AWL=-0.258, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
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 rTJKFu8n9LQf for <vipr@core3.amsl.com>; Thu, 31 Mar 2011 15:17:25 -0700 (PDT)
Received: from ETMail2.acmepacket.com (unknown [216.41.24.9]) by core3.amsl.com (Postfix) with ESMTP id D03D33A69C7 for <vipr@ietf.org>; Thu, 31 Mar 2011 15:17:24 -0700 (PDT)
Received: from mail.acmepacket.com (216.41.24.7) by ETMail2.acmepacket.com (216.41.24.9) with Microsoft SMTP Server (TLS) id 8.1.240.5; Thu, 31 Mar 2011 18:19:01 -0400
Received: from mailbox1.acmepacket.com ([216.41.24.12]) by mail ([127.0.0.1]) with mapi; Thu, 31 Mar 2011 18:19:01 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: "Richard L. Barnes" <rbarnes@bbn.com>
Date: Thu, 31 Mar 2011 18:18:59 -0400
Thread-Topic: [VIPR] Creating an alt-root for E.164
Thread-Index: Acvv8aKuGUqzJJq4TfelgtzdLPYuZw==
Message-ID: <037DBBC6-A0E4-4AED-846A-A2B9FD9B4029@acmepacket.com>
References: <24AD6F1F-1511-4DFF-AE67-EACC8DF36969@acmepacket.com> <6CDDB1C2-B05D-40B9-8B80-A6F0167765E6@bbn.com>
In-Reply-To: <6CDDB1C2-B05D-40B9-8B80-A6F0167765E6@bbn.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
X-Brightmail-Tracker: AAAAAQAAAUA=
Cc: "vipr@ietf.org" <vipr@ietf.org>
Subject: Re: [VIPR] Creating an alt-root for E.164
X-BeenThere: vipr@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Verification Involving PSTN Reachability working group <vipr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vipr>
List-Post: <mailto:vipr@ietf.org>
List-Help: <mailto:vipr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vipr>, <mailto:vipr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Mar 2011 22:17:26 -0000

On Mar 31, 2011, at 12:50 PM, Richard L. Barnes wrote:

> Hey Hadriel,
>=20
>> Yet VIPR moves the ownership time decision to the caller, for whatever d=
uration time it wants to use.=20
>=20
> I think you've got the wrong metaphor here.  VIPR is an empirical system:=
 Since PSTN-VoIP mappings can't be queried directly (as they would through =
ENUM), VIPR infers them based on empirical observations of the PSTN (throug=
h calls).  This is inherently an estimate, which comes with experimental un=
certainty.
>=20
> There's actually a direct analogy here to geolocation services.  Telephon=
e networks have a very good idea of where user devices are, but they refuse=
 to share this information with "over-the-top" services (except for a very =
few exceptions).  So the people who were interested in locating mobile phon=
es developed a system based on empirical measurements (i.e., wardriving), w=
hich is a major basis for location-based mobile applications today.  It's l=
ess accurate than the authoritative data that the telcos have, but it works=
 without telco intervention.

That's not a corollary to my metaphor - the actual physical location inform=
ation has no owner, and no authoritative entity who administers it.  Wardri=
ving does not create an alternate cache of the location information for a p=
hone number or line (which is what the telco's have), but rather of the IP.=
  And even if it did do it for a phone number, it's not competing with what=
 the telco database has because the two databases aren't used by the same c=
lients/queriers.  What we're talking about here is different - you *can* an=
d *do* query the PSTN authoritative database for E.164 number to URI resolu=
tion, by making a call - the PSTN and IP-PBX's just do it on your behalf an=
d don't let you see nor cache the query result.  Once you start auto-determ=
ining the result, caching it and using it for the same purposes, it's effec=
tively removing their authority over the number. =20

Vipr is more analogous to local DNS caching, but without allowing the autho=
ritative DNS servers to set the TTL in the response.  The IETF has long str=
uggled with the problems (and benefits) caused by DNS caching, which is why=
 I find it surprising we seem to have no qualms or second thoughts about do=
ing it to someone else's resolution database.


> If it's directly replication of e164.arpa that you're worried about, that=
's already being done on some scale.  The biggest project I'm aware of is t=
hat a consortium of European NRENs are exchanging VoIP using ENUM under the=
 nrenum.net tree:
> <https://www.nrenum.net/>

Nope, not worried about that.  (1) nrenum requires you to try the authorita=
tive e164.arpa database first, before every call; (2) nrenum only adds a co=
untry if the country does not have an authoritative e164.arpa registry, and=
 if one is created the nrenum one is removed; (3) only a NREN can be delega=
ted to, so it's someone to administer it if it's wrong. =20

But of course someone can make some e164.evil registry of their own, just l=
ike someone can go create an alternate root for DNS, mapping acmepacket.com=
 to whatever they want - but if no one points to that root it won't matter,=
 and we can figure out who's doing it... and more importantly the IETF isn'=
t going to go publish RFCs on how to do it in an automated fashion. :)

-hadriel

