RE: RE: [dhcwg] dhc WG last call on draft-ietf-dhc-rapid-commit-opt-05

"Steve Gonczi" <steve@relicore.com> Thu, 15 July 2004 18:50 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13127; Thu, 15 Jul 2004 14:50:21 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BlBA9-0008DP-HC; Thu, 15 Jul 2004 14:40:57 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BlB5o-0007Of-Mg for dhcwg@megatron.ietf.org; Thu, 15 Jul 2004 14:36:28 -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 OAA11818 for <dhcwg@ietf.org>; Thu, 15 Jul 2004 14:36:26 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BlB5n-00058a-9g for dhcwg@ietf.org; Thu, 15 Jul 2004 14:36:27 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BlB4r-0004l5-00 for dhcwg@ietf.org; Thu, 15 Jul 2004 14:35:30 -0400
Received: from ftp.relicore.com ([4.36.57.198]) by ietf-mx with esmtp (Exim 4.12) id 1BlB3p-00044p-00 for dhcwg@ietf.org; Thu, 15 Jul 2004 14:34:25 -0400
Received: from STEVEPC ([192.168.0.222]) by ftp.relicore.com (8.12.9/8.12.9) with SMTP id i6FI74AZ013340; Thu, 15 Jul 2004 14:07:04 -0400 (EDT)
From: "Steve Gonczi" <steve@relicore.com>
To: "Bernie Volz" <volz@cisco.com>
Subject: RE: RE: [dhcwg] dhc WG last call on draft-ietf-dhc-rapid-commit-opt-05
Date: Thu, 15 Jul 2004 14:31:50 -0400
Message-ID: <BFELJLKGHEJOPOPGJBKKKEIDCJAA.steve@relicore.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
In-Reply-To: <000501c46a23$a85fd970$18fc7044@amer.cisco.com>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,HTML_50_60, HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60
Cc: dhcwg@ietf.org
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>
Content-Type: multipart/mixed; boundary="===============1652102067=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

MessageHi Bernie,

My thinking was exactly as you outline it below. (the DHCPREQUEST
would have the rapid commit option...)

In any case, the point is moot, as I have come around to seeing
the beauty of using initial short leases.

I presume that the intent is to get the client IP-enabled as fast as
possible,
whilst the cost of the almost immediate renewal is not relevant.

I did post a note of supporting the advancement of this draft as-is.

/sG


  -----Original Message-----
  From: Bernie Volz [mailto:volz@cisco.com]
  Sent: Thursday, July 15, 2004 12:25 AM
  To: 'Steve Gonczi'
  Cc: dhcwg@ietf.org
  Subject: RE: RE: [dhcwg] dhc WG last call on
draft-ietf-dhc-rapid-commit-opt-05


  >Would not get retransmitted,  and I did not propose
  >an ACK/ NAK.

  Well, you didn't propose the ACK/NAK but the server will send that back in
response to DHCPREQUEST. Or, are you also suggesting that more is changed to
include the "Rapid Commit" in the DHCPREQUEST such that the server knows not
to send the ACK (or NAK)?

  Again, if you want to do this use short lease times for the Rapid Commit
and give the client a full length lease when it renews.

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