Re: Update of RFC 2606 based on the recent ICANN changes ?

John C Klensin <john-ietf@jck.com> Tue, 08 July 2008 20:21 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 5E11E3A6962; Tue, 8 Jul 2008 13:21:26 -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 11EDC3A69D2 for <ietf@core3.amsl.com>; Tue, 8 Jul 2008 13:21:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.452
X-Spam-Level:
X-Spam-Status: No, score=-2.452 tagged_above=-999 required=5 tests=[AWL=0.147, 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 9LkI4YeVbVvf for <ietf@core3.amsl.com>; Tue, 8 Jul 2008 13:21:24 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 13F9D3A6961 for <ietf@ietf.org>; Tue, 8 Jul 2008 13:21:24 -0700 (PDT)
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1KGJgn-000Ftk-9V; Tue, 08 Jul 2008 16:21:29 -0400
Date: Tue, 08 Jul 2008 16:21:28 -0400
From: John C Klensin <john-ietf@jck.com>
To: Bob Braden <braden@ISI.EDU>, Mark_Andrews@isc.org
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
Message-ID: <0732D45D45246DF2DB204267@p3.JCK.COM>
In-Reply-To: <200807081551.IAA15104@gra.isi.edu>
References: <200807081551.IAA15104@gra.isi.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Disposition: inline
Cc: 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 Tuesday, 08 July, 2008 08:51 -0700 Bob Braden
<braden@ISI.EDU> wrote:

>   *>  
>   *> > 	* was not even examined in the "requirements" review
>   *> > 	that led up to RFC 1123 and is not referenced there.
>   *> 
>   *> 	RFC 1123 -> RFC 952 -> RFC 921
>   *>  	
> 
> Your "->" arrows here apparently mean only "contains a
> reference to". This is not an explicit dependence relationship
> like "updates" or "obsoletes", and nothing can be imfered from
> "contains a reference to" except thaton Postel was
> academically thorough.

Indeed.  But the point was that those references do not exist,
despite that thoroughness and the rather comprehensive "what do
we need to say about the DNS" review that went into 1123.

If there had been a real intention to instantiate 952 or 921 as
"requirements" or the basis for them, I would have expected
either

	* Some discussion in 1123 that refers to or repeats the
	rules,  or 
	
	* At least a 'see also' style of reference in 1123, or

	* Some other relatively recent (compared to 1985)
	document that restates or refers to the rules in
	question.   As an example, those statements might
	reasonably have been picked up in, or referenced from,
	RFC 2181, but aren't there either.

and

	* A status in the RFC Index that is a little stronger
	than "Unknown" 

Those expectations are clearly just inferential, but I believe
that they strongly support my point that reaching back to 921 to
claim a requirement on how applications must (sic) behave today
is something of a stretch even if not altogether bogus.

    john


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