IETF Logo Mail Archive

Re: Last Call: draft-klensin-rfc2821bis

Pekka Savola <pekkas@netcore.fi> Wed, 26 March 2008 08:56 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietfarch-ietf-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3980D3A6E24; Wed, 26 Mar 2008 01:56:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.489
X-Spam-Level:
X-Spam-Status: No, score=-100.489 tagged_above=-999 required=5 tests=[AWL=-0.052, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
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 4+Zt6rQ+pc4W; Wed, 26 Mar 2008 01:56:18 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 303CD28C314; Wed, 26 Mar 2008 01:56:18 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C17C53A6E32 for <ietf@core3.amsl.com>; Wed, 26 Mar 2008 01:56:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
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 jYd+VjOj8xIj for <ietf@core3.amsl.com>; Wed, 26 Mar 2008 01:56:13 -0700 (PDT)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1]) by core3.amsl.com (Postfix) with ESMTP id 45E2C3A6E24 for <ietf@ietf.org>; Wed, 26 Mar 2008 01:56:12 -0700 (PDT)
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.13.8/8.13.8) with ESMTP id m2Q8qgaQ012674; Wed, 26 Mar 2008 10:52:42 +0200
Received: from localhost (pekkas@localhost) by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id m2Q8qf0h012670; Wed, 26 Mar 2008 10:52:42 +0200
Date: Wed, 26 Mar 2008 10:52:41 +0200
From: Pekka Savola <pekkas@netcore.fi>
To: Markku Savela <msa@moth.iki.fi>
Subject: Re: Last Call: draft-klensin-rfc2821bis
In-Reply-To: <200803260645.m2Q6j3JX024997@burp.tkv.asdf.org>
Message-ID: <alpine.LRH.1.10.0803261044440.12376@netcore.fi>
References: <20080325133807.GA12616@boreas.isi.edu> <200803252230.m2PMURNF072389@drugs.dv.isc.org> <20080326023244.GB26917@boreas.isi.edu> <01MSUMAAFHKW00007A@mauve.mrochek.com> <200803260645.m2Q6j3JX024997@burp.tkv.asdf.org>
User-Agent: Alpine 1.10 (LRH 962 2008-03-14)
MIME-Version: 1.0
X-Virus-Scanned: ClamAV 0.92.1/6391/Tue Mar 25 12:09:55 2008 on otso.netcore.fi
X-Virus-Status: Clean
Cc: hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com, Mark_Andrews@isc.org, Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org, bmanning@ISI.EDU
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Wed, 26 Mar 2008, Markku Savela wrote:
>> You seem to be of the opinion that fallback behavior should be extended to
>> AAAA, and you seem to be the first one to express that opinion. (I myself have
>> no opinion on how to resolve this other than believing it has to be resolved -
>> the present ambigiuty is unacceptable.)
>
> As a private person using the "A record only" way of receiving mail, I
> find it useful.

It might be helpful in this context if you could elaborate a bit why 
you find it useful?

The only reason I can think of is if (web?) UI of DNS hosting company 
would make it burdensome to update both MX and the A record.

As John Klensin wrote on Tue, 25 Mar 2008 23:40:12 -0400 
(<AADD02274043C6E6681E0407@p3.JCK.COM>), MX can refer to a name so for 
typical usage scenarios I can think of, just updating your A record 
would automatically update MX settings as well.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email