Re: problem dealing w/ ietf.org mail servers

Bill Manning <bmanning@ISI.EDU> Thu, 03 July 2008 22:05 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 0701F3A68E5; Thu, 3 Jul 2008 15:05:59 -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 B7D9F3A68E5 for <ietf@core3.amsl.com>; Thu, 3 Jul 2008 15:05:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.574
X-Spam-Level:
X-Spam-Status: No, score=-1.574 tagged_above=-999 required=5 tests=[AWL=1.025, 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 m6ABE-oapXC3 for <ietf@core3.amsl.com>; Thu, 3 Jul 2008 15:05:56 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 857B63A68A1 for <ietf@ietf.org>; Thu, 3 Jul 2008 15:05:56 -0700 (PDT)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m63M5PTs021360 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 3 Jul 2008 15:05:26 -0700 (PDT)
Received: (from bmanning@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id m63M5Ovn021348; Thu, 3 Jul 2008 15:05:24 -0700 (PDT)
Date: Thu, 03 Jul 2008 15:05:24 -0700
From: Bill Manning <bmanning@ISI.EDU>
To: Mark Andrews <Mark_Andrews@isc.org>
Subject: Re: problem dealing w/ ietf.org mail servers
Message-ID: <20080703220524.GB15341@boreas.isi.edu>
References: <486CDAE1.4040905@spaghetti.zurich.ibm.com> <200807032158.m63LvwqL047054@drugs.dv.isc.org>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <200807032158.m63LvwqL047054@drugs.dv.isc.org>
User-Agent: Mutt/1.4.2.2i
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@boreas.isi.edu
Cc: Richard Shockey <richard@shockey.us>, Dave Crocker <dcrocker@bbiw.net>, Jeroen Massar <jeroen@unfix.org>, ietf@ietf.org
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 Fri, Jul 04, 2008 at 07:57:58AM +1000, Mark Andrews wrote:
> 
> 	A mobile machine can register its current addresses in the
> 	DNS regardless much more easily than it can register its
> 	reverse PTR records.

	er... both are registering things in the DNS. manipulation
	of the farward map is occasionally easier than manipulation
	of the reverse map... which i think is what you are trying 
	to say.

	and it is often true that those who manage the forward DNS map
	are -NOT- the same folks that manage the reverse DNS map.


--bill

Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).

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