IETF Logo Mail Archive

Re: [mif] Generalising PVD IDs

Ted Lemon <Ted.Lemon@nominum.com> Fri, 08 November 2013 05:04 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFA6511E8202 for <mif@ietfa.amsl.com>; Thu, 7 Nov 2013 21:04:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.588
X-Spam-Level:
X-Spam-Status: No, score=-106.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 untET0t9pSGk for <mif@ietfa.amsl.com>; Thu, 7 Nov 2013 21:04:30 -0800 (PST)
Received: from exprod7og106.obsmtp.com (exprod7og106.obsmtp.com [64.18.2.165]) by ietfa.amsl.com (Postfix) with ESMTP id 35A7211E8105 for <mif@ietf.org>; Thu, 7 Nov 2013 21:04:30 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob106.postini.com ([64.18.6.12]) with SMTP ID DSNKUnxw3ZQ7i+uLQfA2jWPtPeNM9h+q9Z7a@postini.com; Thu, 07 Nov 2013 21:04:30 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 777D91B82CB for <mif@ietf.org>; Thu, 7 Nov 2013 21:04:29 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 59196190043; Thu, 7 Nov 2013 21:04:29 -0800 (PST) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-01.WIN.NOMINUM.COM ([64.89.228.131]) with mapi id 14.03.0158.001; Thu, 7 Nov 2013 21:04:29 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Thread-Topic: [mif] Generalising PVD IDs
Thread-Index: AQHO3ASBM83RfGWE70+Hf84rir8GaJobGpuAgAAETACAAC8rgA==
Date: Fri, 08 Nov 2013 05:04:28 +0000
Message-ID: <8D074B6B-17B2-42DB-8768-8310553A2D76@nominum.com>
References: <527C0C36.1050008@gmail.com> <BD1B039A-7202-4176-8CD0-F9BDD089DE2D@nominum.com> <527C494A.50804@gmail.com>
In-Reply-To: <527C494A.50804@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <7C999FD75276C84289C25F5A11905B8F@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: MIF Mailing List <mif@ietf.org>
Subject: Re: [mif] Generalising PVD IDs
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Nov 2013 05:04:37 -0000

On Nov 7, 2013, at 6:15 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> My_ISP_Lemon

Possibly something like "Example WiFi".   OTOH, it would be good if the identifier also looked like this: wifi.example.com.   If it did, we could hang a DANE cert off the name and use it to validate the key for leap-of-faith associations.   So maybe what I'd like to see in the UI is "Example WiFi (wifi.example.com)".   Or maybe that's too much to ask of the end user—I don't know.   Do we have the right expertise on this mailing list to answer this question, or should we be looking for additional advice?

v2.23.0 | Report a Bug | By Email