Re: [stir] current draft charter

"Richard Shockey" <richard@shockey.us> Mon, 17 June 2013 16:12 UTC

Return-Path: <richard@shockey.us>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AE2321F9CBA for <stir@ietfa.amsl.com>; Mon, 17 Jun 2013 09:12:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.974
X-Spam-Level:
X-Spam-Status: No, score=-101.974 tagged_above=-999 required=5 tests=[AWL=0.291, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0qB4QQvR5eEj for <stir@ietfa.amsl.com>; Mon, 17 Jun 2013 09:12:36 -0700 (PDT)
Received: from oproxy6-pub.bluehost.com (oproxy6-pub.bluehost.com [67.222.54.6]) by ietfa.amsl.com (Postfix) with SMTP id DD41221F9C9F for <stir@ietf.org>; Mon, 17 Jun 2013 09:12:35 -0700 (PDT)
Received: (qmail 28149 invoked by uid 0); 17 Jun 2013 16:12:00 -0000
Received: from unknown (HELO box462.bluehost.com) (74.220.219.62) by oproxy6.bluehost.com with SMTP; 17 Jun 2013 16:11:57 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shockey.us; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:Cc:To:From; bh=XafKz+nv9tba8c0oeRoo5OeDKHXcc4sKUtfVURqN888=; b=eLxLsuwxfkfcWk0tkEgs3RrAngb7TMmhCmulrTrTHt51tpsE3vu6MYQ497LLIcjrud3ZAkyLcsYsVx2b21cnmS2tXZGdeZFGdDs4e4WD7c0woL5oReR13fCNyMneB8Zp;
Received: from [72.66.111.124] (port=52496 helo=RSHOCKEYPC) by box462.bluehost.com with esmtpa (Exim 4.80) (envelope-from <richard@shockey.us>) id 1Uoc28-0006Yk-F5; Mon, 17 Jun 2013 10:11:56 -0600
From: Richard Shockey <richard@shockey.us>
To: dcrocker@bbiw.net, "'Peterson, Jon'" <jon.peterson@neustar.biz>
References: <CDE3F84B.2144F%jon.peterson@neustar.biz> <51BF2E12.8070209@dcrocker.net>
In-Reply-To: <51BF2E12.8070209@dcrocker.net>
Date: Mon, 17 Jun 2013 12:11:54 -0400
Message-ID: <012301ce6b75$63bcdb30$2b369190$@shockey.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQIgEBZoOg+Dnd5bjeekYN+dzFM5ugKIT7z4mIKFQQA=
Content-Language: en-us
X-Identified-User: {3286:box462.bluehost.com:shockeyu:shockey.us} {sentby:smtp auth 72.66.111.124 authed with richard@shockey.us}
Cc: stir@ietf.org
Subject: Re: [stir] current draft charter
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/stir>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Jun 2013 16:12:41 -0000

>> This sounds like a transitive trust model based on trust amongst telcos.
>
> Not really. example.com gets to vouch for example.com addresses, and the

Unlike email addresses, the relationship between the service provider 
and the user is not built into the identifier.  What you've been 
describing is an unspecified service in the background that establishing 
this relationship.  It's key because it authorizes the provider to vouch 
for use of the number.


[RS> ] Dave this is a very good point which creates part of the complication
here. There is a very specific relationship between service provider and the
number that traditional Internet naming and addressing abstracts. The number
is Owned by the nation state. Though the delegation process is different for
each there are some exceptions such as the wholesale numbering markets where
a provider sells blocks to an alternative service provider.. Skype, Google
Voice, WhatsApp etc. Even in those cases the number is traditionally tied to
the wholesale service provisioning by the originating provider.  This
situation created issues around who has access to national numbering
resources that has caused endless regulatory disputes.   If you are bored
sometime  you can do a search on FCC and Vonage ..