Re: problem dealing w/ ietf.org mail servers

John C Klensin <john-ietf@jck.com> Fri, 04 July 2008 13:10 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 345E63A6B2C; Fri, 4 Jul 2008 06:10:34 -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 C6B203A6B78 for <ietf@core3.amsl.com>; Fri, 4 Jul 2008 06:10:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.775
X-Spam-Level:
X-Spam-Status: No, score=-1.775 tagged_above=-999 required=5 tests=[AWL=0.824, 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 tFhKO2rTSaFC for <ietf@core3.amsl.com>; Fri, 4 Jul 2008 06:10:32 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id BF7803A6B6C for <ietf@ietf.org>; Fri, 4 Jul 2008 06:10:31 -0700 (PDT)
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1KEl3T-0003Dt-5r; Fri, 04 Jul 2008 09:10:27 -0400
Date: Fri, 04 Jul 2008 09:10:26 -0400
From: John C Klensin <john-ietf@jck.com>
To: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>, Jeroen Massar <jeroen@unfix.org>
Subject: Re: problem dealing w/ ietf.org mail servers
Message-ID: <06595477BCEAFD54D608797C@p3.JCK.COM>
In-Reply-To: <F06CDCB1-D97B-4BB9-8F0D-8BB3CCC96A86@kurtis.pp.se>
References: <013301c8dca5$22ca0a80$685e1f80$@us> <20080703054752.GM6185@lark.songbird.com> <20080703134655.GA17472@boreas.isi.edu> <486CDAE1.4040905@spaghetti.zurich.ibm.com> <F06CDCB1-D97B-4BB9-8F0D-8BB3CCC96A86@kurtis.pp.se>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Disposition: inline
Cc: Richard Shockey <richard@shockey.us>, ietf@ietf.org, Dave Crocker <dcrocker@bbiw.net>
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 Friday, 04 July, 2008 10:46 +0200 Kurt Erik Lindqvist
<kurtis@kurtis.pp.se> wrote:

> On 3 jul 2008, at 15.57, Jeroen Massar wrote:
> 
>> On Wed, Jul 02, 2008 at 10:47:53PM -0700, 'kent' wrote:
>> [..]
>>> However, this last address,
>>> 2001:470:1:76:2c0:9fff:fe3e:4009, is not explicitly
>>> configured on the sending server; instead, it is being  
>>> implicitly
>>> configured through ip6 autoconf stuff:
>> 
>> Which (autoconfig) you should either not be using on servers,
>> or you   should be configuring your software properly to
>> select the correct   outbound address. (I prefer to use the
>> autoconfig one for   'management' and using a 'service
>> address' for the service).
> 
> 
> What a shame that's not what's in the RFCs..:-)

Despite the ":-)", I think there is an important question here.

Does it imply that this is a use case from which we should be
learning... and then fixing the RFCs?  Or that you believe that
the RFCs are correct and Jeroen's analysis is incorrect?   

I hope it doesn't mean "the RFCs ought to govern, even when
reality and experience seem to contradict them".

   john

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf