RE: [dhcwg] Agenda for dhc WG meeting in San Diego
"Bernie Volz \(volz\)" <volz@cisco.com> Sat, 04 November 2006 15:48 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GgNkj-0006RA-Ay; Sat, 04 Nov 2006 10:48:13 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GgNki-0006R5-LG for dhcwg@ietf.org; Sat, 04 Nov 2006 10:48:12 -0500
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GgNkh-0007Yv-BA for dhcwg@ietf.org; Sat, 04 Nov 2006 10:48:12 -0500
Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-1.cisco.com with ESMTP; 04 Nov 2006 07:48:11 -0800
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAB5ETEVAZnmf/2dsb2JhbAA
X-IronPort-AV: i="4.09,387,1157353200"; d="scan'208"; a="47855450:sNHT36903932"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id kA4FmAsS018730; Sat, 4 Nov 2006 10:48:10 -0500
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id kA4FmADM015302; Sat, 4 Nov 2006 10:48:10 -0500 (EST)
Received: from xmb-rtp-20a.amer.cisco.com ([64.102.31.15]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 4 Nov 2006 10:48:10 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [dhcwg] Agenda for dhc WG meeting in San Diego
Date: Sat, 04 Nov 2006 10:48:09 -0500
Message-ID: <8E296595B6471A4689555D5D725EBB21027A31AB@xmb-rtp-20a.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [dhcwg] Agenda for dhc WG meeting in San Diego
Thread-Index: Acb/pUbZhWB/ZGuYEduxqQARJOT6egAf9FYQ
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Ralph Droms (rdroms)" <rdroms@cisco.com>, "David W. Hankins" <David_Hankins@isc.org>, dhcwg@ietf.org
X-OriginalArrivalTime: 04 Nov 2006 15:48:10.0779 (UTC) FILETIME=[A14676B0:01C70028]
DKIM-Signature: a=rsa-sha1; q=dns; l=2811; t=1162655290; x=1163519290; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=volz@cisco.com; z=From:=22Bernie=20Volz=20\(volz\)=22=20<volz@cisco.com> |Subject:RE=3A=20[dhcwg]=20Agenda=20for=20dhc=20WG=20meeting=20in=20San=20Diego |To:=22Ralph=20Droms=20\(rdroms\)=22=20<rdroms@cisco.com>, =0A=20=20=20=20=20 =20=20=20=22David=20W.=20Hankins=22=20<David_Hankins@isc.org>, =20<dhcwg@iet f.org>; X=v=3Dcisco.com=3B=20h=3DcKtBvp4aoi4IQsTixBq7tt3nB+M=3D; b=KItNwepeiMF9pX7tCFnnfg4apwyhQpDFMTGnlsl7W/87UGSVCTFpPB4DoMl8Cdn6ROIV41e+ DubWv9VoqNCNdokUhDJGdS1HUF2zHvU0X66XPjmfnvS/uATT3mPm6t+N;
Authentication-Results: rtp-dkim-2.cisco.com; header.From=volz@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Cc:
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
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>
Errors-To: dhcwg-bounces@ietf.org
Personally, I think it should be INFORMATIONAL. This is documenting existing behavior, is it not? It is not developing a new standard (i.e., the DHC WG can't change how these options are used -- we can only help to improve the documentation of their existing usage). At least, that's my interpretation of Informational in http://www.ietf.org/rfc/rfc2026.txt: 4.2.2 Informational An "Informational" specification is published for the general information of the Internet community, and does not represent an Internet community consensus or recommendation. The Informational designation is intended to provide for the timely publication of a very broad range of responsible informational documents from many sources, subject only to editorial considerations and to verification that there has been adequate coordination with the standards process (see section 4.2.3). Specifications that have been prepared outside of the Internet community and are not incorporated into the Internet Standards Process by any of the provisions of section 10 may be published as Informational RFCs, with the permission of the owner and the concurrence of the RFC Editor. RFC 3942 is silent on the type of RFC needed to keep an existing use of an option in the old site-specific range. So, there is no impact there. I guess the DHC WG could ask "if these options had been defined through the normal DHC WG process for new options, would we have done anything sufficiently different"? If the consensus answer was NO, there would be no harm in a standards track document. But my answer to that question would actually be YES, as I'd see no need for option 208 "MAGIC" if these options had been developed through the normal process. For *FUTURE* new options that the PXELINUX folks want to use, if they do go through the DHC WG process to develop the options, those would then be standards track documents. - Bernie -----Original Message----- From: Ralph Droms (rdroms) Sent: Friday, November 03, 2006 7:08 PM To: David W. Hankins; dhcwg@ietf.org Subject: Re: [dhcwg] Agenda for dhc WG meeting in San Diego OK... - Ralph On 11/3/06 5:12 PM, "David W. Hankins" <David_Hankins@isc.org> wrote: > On Mon, Oct 30, 2006 at 01:32:02PM -0500, Ralph Droms wrote: >> draft-ietf-dhc-pxelinux-00, "PXELINUX Use of 'Site Local' Option Space" >> (Informational) > > I'm not sure if this should be Informational or Proposed Standard. > The draft does contain normative language. > > Perhaps that's one of the things we should talk about at the end of > my (very short) presentation. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Agenda for dhc WG meeting in San Diego Ralph Droms
- Re: [dhcwg] Agenda for dhc WG meeting in San Diego Ralph Droms
- Re: [dhcwg] Agenda for dhc WG meeting in San Diego David W. Hankins
- RE: [dhcwg] Agenda for dhc WG meeting in San Diego Bernie Volz (volz)
- Re: [dhcwg] Agenda for dhc WG meeting in San Diego David W. Hankins
- Re: [dhcwg] Agenda for dhc WG meeting in San Diego H. Peter Anvin