Re: problem dealing w/ ietf.org mail servers

Jeroen Massar <jeroen@unfix.org> Thu, 10 July 2008 20:07 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 AE9163A6A7E; Thu, 10 Jul 2008 13:07:35 -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 11F403A69AF for <ietf@core3.amsl.com>; Thu, 10 Jul 2008 13:07:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-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 yRwcq5Q4JnSs for <ietf@core3.amsl.com>; Thu, 10 Jul 2008 13:07:33 -0700 (PDT)
Received: from abaddon.unfix.org (abaddon.unfix.org [IPv6:2001:41e0:ff00:0:216:3eff:fe00:4]) by core3.amsl.com (Postfix) with ESMTP id BE1713A6A7E for <ietf@ietf.org>; Thu, 10 Jul 2008 13:07:32 -0700 (PDT)
Received: from [IPv6:2001:41e0:ff42:b00:216:cfff:fe00:e7d0] (spaghetti.ch.unfix.org [IPv6:2001:41e0:ff42:b00:216:cfff:fe00:e7d0]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by abaddon.unfix.org (Postfix) with ESMTPSA id 49BD535A539; Thu, 10 Jul 2008 22:07:40 +0200 (CEST)
Message-ID: <48766C09.4020102@spaghetti.zurich.ibm.com>
Date: Thu, 10 Jul 2008 22:07:37 +0200
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080421 Lightning/0.8 Thunderbird/2.0.0.14 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Kurt Erik Lindqvist <kurtis@kurtis.pp.se>
Subject: Re: problem dealing w/ ietf.org mail servers
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> <06595477BCEAFD54D608797C@p3.JCK.COM> <0E3112A0-B01B-40D7-AE82-6E1D9EAC94D6@kurtis.pp.se> <4873B4DC.90800@network-heretics.com> <92282F5B-9974-419D-AAC8-61B1D4DE29E3@kurtis.pp.se>
In-Reply-To: <92282F5B-9974-419D-AAC8-61B1D4DE29E3@kurtis.pp.se>
X-Enigmail-Version: 0.95.6
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV version 0.93.1, clamav-milter version 0.93.1 on abaddon.unfix.org
X-Virus-Status: Clean
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org, Dave Crocker <dcrocker@bbiw.net>, Keith Moore <moore@network-heretics.com>, Richard Shockey <richard@shockey.us>
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: multipart/mixed; boundary="===============0590513465=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Kurt Erik Lindqvist wrote:
> On 8 jul 2008, at 20.41, Keith Moore wrote:
[..]
>> I disagree that it doesn't work for servers.   (Or it would be better 
>> to say that I'd like to know why you think it doesn't work for servers.)

People have personal opinions, one likes this, the other likes that, 
maybe it works for you, maybe it works different for me.

> Well, when I change that broken NIC in my server, it will receive a new 
> address that needs to be reflected in the DNS.

Which is why EUI-64 is a great method on combination with RA to do 
autoconfiguration, but if somebody (for whatever reason they have) want 
to use those 64bits differently (eg using DHCP or static config) they 
should definitely do so, it is their network after all, and there is no 
meaning in those bits.

EUI-64/RA is just to make some cases (the dental office one for 
instance) really simply, but it is not a solution for everything else.
Pick and use what is useful...

BTW: Most OS's allow overriding of the MAC address, next to of course 
just configing an "automatic EUI-64 address" as a static one on an 
interface ;) Your network, your rules, your problem if you peep it up.

Greets,
  Jeroen

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