IETF Logo Mail Archive

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

"Steve Gonczi" <steve@relicore.com> Wed, 14 July 2004 19:33 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 PAA10282; Wed, 14 Jul 2004 15:33:16 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkpI9-0002t2-My; Wed, 14 Jul 2004 15:19:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkpFx-00024h-4b for dhcwg@megatron.ietf.org; Wed, 14 Jul 2004 15:17:29 -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 PAA08649 for <dhcwg@ietf.org>; Wed, 14 Jul 2004 15:17:27 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BkpFv-0004Fb-UM for dhcwg@ietf.org; Wed, 14 Jul 2004 15:17:28 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BkpEz-0003uw-00 for dhcwg@ietf.org; Wed, 14 Jul 2004 15:16:30 -0400
Received: from ftp.relicore.com ([4.36.57.198]) by ietf-mx with esmtp (Exim 4.12) id 1BkpE1-0003JK-00 for dhcwg@ietf.org; Wed, 14 Jul 2004 15:15:29 -0400
Received: from STEVEPC ([192.168.0.222]) by ftp.relicore.com (8.12.9/8.12.9) with SMTP id i6EIo7AZ025042; Wed, 14 Jul 2004 14:50:07 -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: Wed, 14 Jul 2004 15:14:52 -0400
Message-ID: <BFELJLKGHEJOPOPGJBKKMEHLCJAA.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: <000c01c4699c$81c34810$4bfeba44@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="===============1305774646=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

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

Merely a best effort DHCPREQUEST,  to give any server
that committed and address (but was not selected by the client)
a chance to clean up.

This DHCPREQUEST is not intended for the server that offered
the accepted ( and committed) address.

That server does not need to do anything further.

BTW this is exactly how plain DHCP works today.
Any server that did offer an address, and sees the DHCPREQUEST
for a different address, just releases  the address and there is no further
action required. Neither does DHCP provide any assurance that
any (not selected) server does see the DHCPREQUEST.



regards,

/sG

  -----Original Message-----
  From: Bernie Volz [mailto:volz@cisco.com]
  Sent: Wednesday, July 14, 2004 8:17 AM
  To: 'Steve Gonczi'; soohong.park@samsung.com
  Cc: dhcwg@ietf.org
  Subject: RE: RE: [dhcwg] dhc WG last call on
draft-ietf-dhc-rapid-commit-opt-05


  This likely isn't as a cut and dry as you assume. Does the DHCPREQUEST get
retransmitted until it is ACKed? What happens if it isn't ACKed? What
happens if it is NAK?

  - Berni

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

v2.23.0 | Report a Bug | By Email