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

John C Klensin <klensin@jck.com> Mon, 27 July 2009 17:11 UTC

Return-Path: <klensin@jck.com>
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 5294A28C2F6 for <ima@core3.amsl.com>; Mon, 27 Jul 2009 10:11:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.411
X-Spam-Level:
X-Spam-Status: No, score=-2.411 tagged_above=-999 required=5 tests=[AWL=0.188, BAYES_00=-2.599]
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 OiL6aUzS8YoH for <ima@core3.amsl.com>; Mon, 27 Jul 2009 10:11:53 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 61BDB28C1C1 for <ima@ietf.org>; Mon, 27 Jul 2009 10:11:53 -0700 (PDT)
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1MVTjY-000E10-7P; Mon, 27 Jul 2009 13:11:32 -0400
Date: Mon, 27 Jul 2009 13:11:31 -0400
From: John C Klensin <klensin@jck.com>
To: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, ima@ietf.org
Message-ID: <EB90F7A6E26237FE818E3367@JcK-eee9.meeting.ietf.org>
In-Reply-To: <Pg19vTtgeaaCi1W4fWmFpw.md5@lochnagar.oryx.com>
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>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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 17:11:54 -0000

--On Friday, July 24, 2009 10:59 +0200 Arnt Gulbrandsen
<arnt@gulbrandsen.priv.no> wrote:

> Alternative proposal: Extend VRFY to optionally return a
> fuzzily correctified version of an email address. If VRFY is
> disabled or doesn't return an address, correction isn't
> available for that address. I think this is better because it
> permits the fuzzy fuzziness to be invoked when the address is
> entered into e.g. an address database, instead of when a
> message is transmitted. As a bonus it's 99% independent of EAI.

First, as Tony points out, that has been part of VRFY forever
and, historically, systems used to fairly commonly generate real
addresses.  In particular, it was common in some systems for one
to be able to send
   VRFY John Klensin
and get an address back, and VRFY was designed to accommodate
that use when systems wanted to support it.

Second, what you are suggesting is a member of a family of
solutions we've discussed before.  Some of them would fall under
Harald's Global Universal Directory project, others don't, but
all are members of the set of "if downgrading of
forward-pointing addresses is needed, it needs to be done at the
originating MUA or Submission server and downgrading does not
need to be done in transit (at SMTP time).

    john