Re: [dispatch] VIPR - proposed charter version 2 - PSTN?

Cullen Jennings <fluffy@cisco.com> Thu, 17 June 2010 20:54 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 633B63A6927 for <dispatch@core3.amsl.com>; Thu, 17 Jun 2010 13:54:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.749
X-Spam-Level:
X-Spam-Status: No, score=-108.749 tagged_above=-999 required=5 tests=[AWL=-0.750, 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 m7BdjBwZ9BMg for <dispatch@core3.amsl.com>; Thu, 17 Jun 2010 13:54:41 -0700 (PDT)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 5DC563A68A3 for <dispatch@ietf.org>; Thu, 17 Jun 2010 13:54:41 -0700 (PDT)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAL8oGkyrR7Hu/2dsb2JhbACee3GoA5o2glmCQQSDUg
X-IronPort-AV: E=Sophos;i="4.53,434,1272844800"; d="scan'208";a="146200776"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 17 Jun 2010 20:54:46 +0000
Received: from [192.168.4.177] (rcdn-fluffy-8711.cisco.com [10.99.9.18]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o5HKsj8j003717; Thu, 17 Jun 2010 20:54:46 GMT
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset="us-ascii"
Impp: xmpp:cullenfluffyjennings@jabber.org
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <01a601cb0d1c$61ccd3d0$25667b70$%roni@huawei.com>
Date: Thu, 17 Jun 2010 14:54:45 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <E31AEB83-56E5-4695-B2E0-9D2922C6319C@cisco.com>
References: <DB6CA94F-0EC9-4E27-A190-D12029CA61AE@cisco.com> <01a601cb0d1c$61ccd3d0$25667b70$%roni@huawei.com>
To: Roni Even <Even.roni@huawei.com>
X-Mailer: Apple Mail (2.1078)
Cc: 'DISPATCH list' <dispatch@ietf.org>
Subject: Re: [dispatch] VIPR - proposed charter version 2 - PSTN?
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: Thu, 17 Jun 2010 20:54:42 -0000

I'm having a real hard time actually understand what you are objecting too. More  inline ...

On Jun 16, 2010, at 12:22 AM, Roni Even wrote:

> Hi,
> I read the charter and the listed drafts. I have no problem with the first
> two paragraph of the charter
> 
> "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 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."
> 
> I have a concern about using PSTN infrastructure for the reachability. My
> understanding so far was that SIP is trying to provide a new way for end to
> end communication that will replace the existing circuit switch
> infrastructure. This proposal says that the way to achieve end to end
> connectivity requires to have an end to end PSTN frastructure.

No this proposal says one of the way we can make PSTN address usable in inter domain SIP is this. Clearly this approach would no longer be valid when the PSTN was gone but by that point, presumably people would be using more internet style address in SIP. Keep in mind the only thing this work is trying to solve is mapping a PSTN address to a internet address. When the PSTN is gone, that problem goes with it. However the PSTN is far from gone - if I had to bet, I would guess that phone numbers were around longer than v6 addresses (and than email style address outlive them both). The issue is phone numbers are used by humans which makes them very hard to transition off of while things like v6 addresses are easier to transition off of as they are come and go with the technologies that use them. My point being all these addresses are around for a long time and the IETF works on standards to help transition and interwork between them. The Telegram service was emulated on top of other technologies long after it had been supplanted by fax - the PSTN will be similar. 

> 
> The third paragraph is talking about validation using PSTN calls. I think
> that we can look at validation of number ownership but should say that
> requiring PSTN calls to do it is not the recommended approach.
> This will
> allow managing of PSTN numbers not in the scope of PSTN infrastructure. Even
> the PSTN network is using external protocol like SS7 to route calls using
> databases for achieving reachability so why not say we can use similar
> infrastructure that will be IP based.

We did standardize and IP based database approach - it's called public ENUM. However, from a practical point of view the only people that could do the validations for ENUM are the carriers that have every business incentive to not do it. Regulators do not have the right incentives to regulate it into existence. VIPR on the other hand only requires carriers to route calls. Routing calls is something they do today, it is in their business interest so they will likely continue doing it, and the regulation around common carriage often require them to route calls. Both the existing regulations and economics favor that the carriers will do what is needed to enable a solution that leverages the PSTN for validation. 

> 
> I can understand this as a temporary solution but not as a standard
> developed by the IETF.

How temporary do you think the PSTN is? How many years?  Do you think we should not be doing standards for WG like MARTINI that only WG document limited itself to phone numbers? Should we not have standards about SIP / PSTN interoperability? I don't hear you objecting to any of the other work we do hat is "temporary" in the sense it is only useful as long as the PSTN is around.

Seriously, I read this and just feel like you are grasping at straws for something to objet to since this proposal came from Cisco. 


> 
> 
> Thanks
> 
> Roni Even
>