IETF Logo Mail Archive

Re: [EAI] NFC/NFD (Re: Test - driven schedule (Re: Rechartering))

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Mon, 27 July 2009 14:16 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: ima@core3.amsl.com
Delivered-To: ima@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BAEA33A6BFB for <ima@core3.amsl.com>; Mon, 27 Jul 2009 07:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.182
X-Spam-Level:
X-Spam-Status: No, score=-2.182 tagged_above=-999 required=5 tests=[AWL=0.416, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
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 vAA7w-IEASDA for <ima@core3.amsl.com>; Mon, 27 Jul 2009 07:16:26 -0700 (PDT)
Received: from strange.aox.org (strange.aox.org [80.244.248.170]) by core3.amsl.com (Postfix) with ESMTP id E15073A697D for <ima@ietf.org>; Mon, 27 Jul 2009 07:16:25 -0700 (PDT)
Received: from fri.gulbrandsen.priv.no (unknown [195.30.37.30]) by strange.aox.org (Postfix) with ESMTP id 1C858FA0416 for <ima@ietf.org>; Mon, 27 Jul 2009 14:16:24 +0000 (UTC)
Received: from arnt@gulbrandsen.priv.no (HELO lochnagar.oryx.com) by fri.gulbrandsen.priv.no (Archiveopteryx 3.1.0) with esmtp id 1248704071-36606-36605/5/20 for ima@ietf.org; Mon, 27 Jul 2009 16:14:31 +0200
Message-Id: <+elcs7Yf+RctuuQTQahrtw.md5@lochnagar.oryx.com>
Date: Mon, 27 Jul 2009 16:16:42 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ima@ietf.org
References: <mailman.13830.1247508102.4936.ima@ietf.org> <CAD7705D4A93814F97D3EF00790AF0B315FA6650@tk5ex14mbxc105.redmond.corp.microsoft.com> <4A5BABF8.4080900@isode.com> <CAD7705D4A93814F97D3EF00790AF0B315FA6AAF@tk5ex14mbxc105.redmond.corp.microsoft.com> <4A60AA0B.4000106@alvestrand.no> <CAD7705D4A93814F97D3EF00790AF0B315FCA179@TK5EX14MBXC104.redmond.corp.microsoft.com> <EA9664FBEBEB7127550C3D30@[192.168.1.110]> <CAD7705D4A93814F97D3EF00790AF0B315FCB1CA@TK5EX14MBXC104.redmond.corp.microsoft.com> <F2BC6EC973C4D97B22FB5FE1@p3.int.jck.com> <CAD7705D4A93814F97D3EF00790AF0B315FDE04F@tk5ex14mbxc105.redmond.corp.microsoft.com> <448328271.18687@cnnic.cn> <448338030.08886@cnnic.cn> <021001ca0b70$4bf6ab20$236ff1da@whatisfuture> <8BC1BBA8349DC191FB83819F@JcK-eee9.example.com> <CAD7705D4A93814F97D3EF00790AF0B315FDF9E5@tk5ex14mbxc105.redmond.corp.microsoft.com> <4A696140.4090902@alvestrand.no> <52385C598A7B129EE974A987@JcK-eee9.example.com> <Pg19vTtgeaaCi1W4fWmFpw.md5@lochnagar.oryx.com> <4A6DB2E4.5010406@alvestrand.no>
In-Reply-To: <4A6DB2E4.5010406@alvestrand.no>
Content-Type: text/plain; format="flowed"
Mime-Version: 1.0
Subject: Re: [EAI] NFC/NFD (Re: Test - driven schedule (Re: Rechartering))
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Jul 2009 14:16:26 -0000

Sorry about my address. Problems I can't solve right now.

Harald Alvestrand writes:
> and in this case, NFC wouldn't help either....

Exactly. Nothing is equivalent to the typos humans make.

> Fuzzy matching is a very interesting subject, and I'd argue that it's 
> 100% orthogonal to EAI - I still remember the mail I got as a new 
> postmaster after a new fuzzy-match algorithm had rerouted a 
> misspelling of one man's wife's mail to his mailbox - "how did the 
> system know we are married?".
>
> I'd like to punt this issue to the Single Global Directory, but that's 
> just reducing it to a previously unsolved problem.....

(One solved long ago by spammers, *sigh* ;)

I'm serious, though: EAI should suggest that before storing an address, 
the software might attempt to check its accuracy using RCPT or VRFY, 
and do _nothing_ more.

The heuristics fit in VRFY, and at that data entry time it's possible to 
ask "uh, was there a typo, did you mean <x>?" if the VRFY responds 
suitably.

Arnt

v2.28.0 | Report a Bug | By Email | System Status