IETF Logo Mail Archive

Re: [dhcwg] AD review of draft-ietf-dhc-unused-optioncodes-03.txt

Robert Elz <kre@munnari.OZ.AU> Wed, 09 July 2003 07:47 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22544; Wed, 9 Jul 2003 03:47:39 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19a9fI-0006UF-QT; Wed, 09 Jul 2003 03:47:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19a9eJ-0006Sq-Rl for dhcwg@optimus.ietf.org; Wed, 09 Jul 2003 03:45:59 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22515 for <dhcwg@ietf.org>; Wed, 9 Jul 2003 03:45:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19a9eH-0004jD-00 for dhcwg@ietf.org; Wed, 09 Jul 2003 03:45:57 -0400
Received: from ratree.psu.ac.th ([202.12.73.3]) by ietf-mx with esmtp (Exim 4.12) id 19a9e4-0004j4-00 for dhcwg@ietf.org; Wed, 09 Jul 2003 03:45:45 -0400
Received: from delta.cs.mu.OZ.AU (delta.coe.psu.ac.th [172.30.0.98]) by ratree.psu.ac.th (8.11.6/8.11.6) with ESMTP id h697iti03516; Wed, 9 Jul 2003 14:44:56 +0700 (ICT)
Received: from munnari.OZ.AU (localhost [127.0.0.1]) by delta.cs.mu.OZ.AU (8.11.6/8.11.6) with ESMTP id h68LLKD09251; Wed, 9 Jul 2003 04:21:20 +0700 (ICT)
From: Robert Elz <kre@munnari.OZ.AU>
To: Ralph Droms <rdroms@cisco.com>
cc: Thomas Narten <narten@us.ibm.com>, dhcwg@ietf.org
Subject: Re: [dhcwg] AD review of draft-ietf-dhc-unused-optioncodes-03.txt
In-Reply-To: <4.3.2.7.2.20030708143215.0494eb90@funnel.cisco.com>
References: <4.3.2.7.2.20030708143215.0494eb90@funnel.cisco.com> <Message from rdroms@cisco.com of "Fri, 27 Jun 2003 16:42:42 EDT." <4.3.2.7.2.20030627163720.00ba6290@funnel.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 09 Jul 2003 04:21:20 +0700
Message-ID: <21139.1057699280@munnari.OZ.AU>
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>

    Date:        Tue, 08 Jul 2003 14:37:05 -0400
    From:        Ralph Droms <rdroms@cisco.com>
    Message-ID:  <4.3.2.7.2.20030708143215.0494eb90@funnel.cisco.com>

  | Well, perhaps I've written this doc to be sufficiently self-contained
  | to avoid normative references.

It is hard to imagine how you could have done it any other way.

Thomas is quite correct here, this doc needs none.

It would need one, if there was a protocol for deleting unused
DHCP option codes, and you wanted to say "The unused DHCP option
protocol [RFC9876] is to be used to delete option 666".

Then without reading that RFC you wouldn't know what to do, so that's
a normative reference.

"Normative" does not mean "important", the split isn't between the
references that you consider to be really on point. or useful for
the reader - only those for which the document makes no sense without
an earlier doc.

And yes, that does mean that a normative reference must be published as
an RFC (or in some equivalent fixed form, an IS would be OK, as would
a journal article describing an algorithm - an I-D or web page is not)
before the doc making the reference can be published.

kre


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email