IETF Logo Mail Archive

Re: [stir] current draft charter - ENUM and databases

Michael Hammer <michael.hammer@yaanatech.com> Wed, 19 June 2013 13:37 UTC

Return-Path: <michael.hammer@yaanatech.com>
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 2799F21F9BD3 for <stir@ietfa.amsl.com>; Wed, 19 Jun 2013 06:37:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.578
X-Spam-Level:
X-Spam-Status: No, score=-2.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599]
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 sqpCWdC-ykTg for <stir@ietfa.amsl.com>; Wed, 19 Jun 2013 06:37:07 -0700 (PDT)
Received: from email1.corp.yaanatech.com (email1.corp.yaanatech.com [205.140.198.134]) by ietfa.amsl.com (Postfix) with ESMTP id B735321F91A5 for <stir@ietf.org>; Wed, 19 Jun 2013 06:37:07 -0700 (PDT)
Received: from EX2K10MB2.corp.yaanatech.com ([fe80::5d11:66a1:e508:6871]) by ex2k10hub1.corp.yaanatech.com ([::1]) with mapi id 14.01.0218.012; Wed, 19 Jun 2013 06:37:06 -0700
From: Michael Hammer <michael.hammer@yaanatech.com>
To: "Yiu_Lee@Cable.Comcast.com" <Yiu_Lee@Cable.Comcast.com>, "stir@ietf.org" <stir@ietf.org>
Thread-Topic: [stir] current draft charter - ENUM and databases
Thread-Index: AQHOaJxSZyaUX2cyBk2/ZGQqej7gqJk3mvQAgAG9DwCAAJEBgIAADb2AgACwEACAABbBgIAAIr8AgAA+koCAARnqAIABSTIA//+PwLA=
Date: Wed, 19 Jun 2013 13:37:04 +0000
Message-ID: <00C069FD01E0324C9FFCADF539701DB3A03DEDDE@ex2k10mb2.corp.yaanatech.com>
References: <8C77C05D-6ED2-4429-BF1C-72082F4ADE76@oracle.com> <E3FAB1F4F41F3A45B287E8D9C53522FD472CEA44@PACDCEXMB05.cable.comcast.com>
In-Reply-To: <E3FAB1F4F41F3A45B287E8D9C53522FD472CEA44@PACDCEXMB05.cable.comcast.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.17.100.216]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg="SHA1"; boundary="----=_NextPart_000_006F_01CE6CD0.8EB643B0"
MIME-Version: 1.0
Subject: Re: [stir] current draft charter - ENUM and databases
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: Wed, 19 Jun 2013 13:37:12 -0000

Is that out of scope?

Should we focus on E.164 first, email-style names second, and the
interworking of the two third?

That wouldn't preclude reuse of solution to one for the other, or thinking
about that in advance.
But, we are talking about two different authority delegation trees here and 
I am not sure if you want one constrained by solutions for the other.

If we do, then at least make it clear that is a decision being made.

Mike


-----Original Message-----
From: stir-bounces@ietf.org [mailto:stir-bounces@ietf.org] On Behalf Of Lee,
Yiu
Sent: Wednesday, June 19, 2013 9:15 AM
To: stir@ietf.org
Subject: Re: [stir] current draft charter - ENUM and databases

I am on board using dns for lookup. One question in your example: When you
receive alice@foo.com, how do you derive it to "_cid.foo.com"? Do you
suggest _cid is the tn or some other identifier?


On 6/18/13 1:36 PM, "Hadriel Kaplan" <hadriel.kaplan@oracle.com> wrote:

>I think that's still possible even for email-style names.  For example, 
>when receiving a request from'alice@foo.com' we could do a DNS lookup 
>for '_cid.foo.com' or some such pre-defined naming scheme, to get the 
>caller-id cert for 'foo.com'; or the RR for that DNS key could redirect 
>us to somewhere else if need be.  Or we could do an HTTP automatically 
>for 'http://foo.com/cid', or even 'http://foo.com/cid/ldkjhlashl' where 
>the last part is a hash of the username.

v2.23.0 | Report a Bug | By Email