Re: [stir] current draft charter

Dave Crocker <dhc2@dcrocker.net> Thu, 13 June 2013 04:01 UTC

Return-Path: <dhc2@dcrocker.net>
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 9B7EB21F894E for <stir@ietfa.amsl.com>; Wed, 12 Jun 2013 21:01:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 tB4uWiON1ioH for <stir@ietfa.amsl.com>; Wed, 12 Jun 2013 21:01:34 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8056E21F9949 for <stir@ietf.org>; Wed, 12 Jun 2013 21:01:34 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r5D41RUW024152 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 12 Jun 2013 21:01:30 -0700
Message-ID: <51B94411.3090502@dcrocker.net>
Date: Wed, 12 Jun 2013 21:01:21 -0700
From: Dave Crocker <dhc2@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "Peterson, Jon" <jon.peterson@neustar.biz>
References: <CDDE3A21.1F6AF%jon.peterson@neustar.biz>
In-Reply-To: <CDDE3A21.1F6AF%jon.peterson@neustar.biz>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 12 Jun 2013 21:01:30 -0700 (PDT)
Cc: "stir@ietf.org" <stir@ietf.org>
Subject: Re: [stir] current draft charter
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
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: Thu, 13 Jun 2013 04:01:47 -0000

On 6/12/2013 3:01 PM, Peterson, Jon wrote:
> But we don't even have to be asking ourselves about the relevance of
> public ENUM to the proposed work here in STIR unless we want to try to
> base everything on keying in the public DNS for telephone numbers. There
> are other models for this that don't have the liabilities I described
> above, anyway. Keying in private DNS is more viable, for example. I think
> a PKI is more viable.


Other models?

Is there a written description of the integrated query service that you 
folks are considering, in terms of design, administration and operation?

It would help to also hear where such a design has already been 
successfully deployed.

As the Enum experience showed, schemes can be intelligent and appealing 
but not succeed.  So for any new deployment, any analysis needs to start 
with skepticism and work its way up with pragmatics.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net