Re: [dhcwg] Response to IESG comments on draft-ietf-dhc-isnsoption-08.txt
Ralph Droms <rdroms@cisco.com> Thu, 28 August 2003 08:25 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 EAA16206 for <dhcwg-archive@odin.ietf.org>; Thu, 28 Aug 2003 04:25:08 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19sCqf-0003Uc-7m for dhcwg-archive@odin.ietf.org; Wed, 27 Aug 2003 22:49:33 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7S2nLut013420 for dhcwg-archive@odin.ietf.org; Wed, 27 Aug 2003 22:49:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19sA3I-0007zR-Vw for dhcwg-web-archive@optimus.ietf.org; Wed, 27 Aug 2003 19:50:13 -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 TAA19893 for <dhcwg-web-archive@ietf.org>; Wed, 27 Aug 2003 19:50:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19sA3E-0003MS-00 for dhcwg-web-archive@ietf.org; Wed, 27 Aug 2003 19:50:08 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19sA3D-0003MP-00 for dhcwg-web-archive@ietf.org; Wed, 27 Aug 2003 19:50:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19s4vt-00017p-7f; Wed, 27 Aug 2003 14:22:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19ry8l-0006w6-B3 for dhcwg@optimus.ietf.org; Wed, 27 Aug 2003 07:07:03 -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 HAA16477 for <dhcwg@ietf.org>; Wed, 27 Aug 2003 07:06:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ry8h-0003NN-00 for dhcwg@ietf.org; Wed, 27 Aug 2003 07:06:59 -0400
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 19ry8g-0003MX-00 for dhcwg@ietf.org; Wed, 27 Aug 2003 07:06:58 -0400
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h7RB5sVr002977; Wed, 27 Aug 2003 04:05:54 -0700 (PDT)
Received: from rdroms-w2k01.cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id ABW25170; Wed, 27 Aug 2003 07:05:41 -0400 (EDT)
Message-Id: <4.3.2.7.2.20030827060625.0464f580@localhost>
X-Sender: rdroms@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 27 Aug 2003 06:09:21 -0400
To: Charles Monia <cmonia@NishanSystems.com>
From: Ralph Droms <rdroms@cisco.com>
Subject: Re: [dhcwg] Response to IESG comments on draft-ietf-dhc-isnsoption-08.txt
Cc: "Thomas Narten (E-mail)" <narten@us.ibm.com>, "DHCP (E-mail)" <dhcwg@ietf.org>, "Ips (E-mail)" <ips@ece.cmu.edu>, "David Black (E-mail)" <Black_David@emc.com>, "Elizabeth Rodriguez (E-mail)" <ElizabethRodriguez@ieee.org>, "Allison Mankin (E-mail)" <mankin@isi.edu>, Charles Monia <cmonia@NishanSystems.com>, Joshua Tseng <jtseng@NishanSystems.com>, Kevin Gibbons <kgibbons@NishanSystems.com>
In-Reply-To: <B300BD9620BCD411A366009027C21D9BE86ED4@ariel.nishansystems .com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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>
Note that, because there are no implementations of RFC 3118 today, and no plans by any important vendors to implement RFC 3118 in the future, making RFC 3118 authentication mandatory will effectively disallo any use of this option. Perhaps we can modify this requirement to something like "use of RFC 3118 is mandatory if it is available in the client and server". - Ralph At 03:37 PM 8/19/2003 -0700, Charles Monia wrote: > > "Steven M. Bellovin" <smb@research.att.com> writes: > > > Is 3118 mandatory-to-implement or not? I have a hard time > > understanding why it should be optional. > >We will revise the spec to make implementation of RFC 3118 mandatory. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Response to IESG comments on draft-ietf-d… Charles Monia
- Re: [dhcwg] Response to IESG comments on draft-ie… Ralph Droms