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

"Steve Gonczi" <steve@relicore.com> Tue, 13 July 2004 18:56 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 OAA03615; Tue, 13 Jul 2004 14:56:20 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkSLr-0004E6-IS; Tue, 13 Jul 2004 14:50:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkSEn-00021g-5y for dhcwg@megatron.ietf.org; Tue, 13 Jul 2004 14:42:45 -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 OAA02961 for <dhcwg@ietf.org>; Tue, 13 Jul 2004 14:42:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BkSEl-00012H-SY for dhcwg@ietf.org; Tue, 13 Jul 2004 14:42:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BkSDo-0000ha-00 for dhcwg@ietf.org; Tue, 13 Jul 2004 14:41:44 -0400
Received: from ftp.relicore.com ([4.36.57.198]) by ietf-mx with esmtp (Exim 4.12) id 1BkSCw-00004S-00 for dhcwg@ietf.org; Tue, 13 Jul 2004 14:40:51 -0400
Received: from STEVEPC ([192.168.0.222]) by ftp.relicore.com (8.12.9/8.12.9) with SMTP id i6DIFTAZ022697; Tue, 13 Jul 2004 14:15:29 -0400 (EDT)
From: "Steve Gonczi" <steve@relicore.com>
To: "Bernie Volz" <volz@cisco.com>
Subject: RE: [dhcwg] dhc WG last call on draft-ietf-dhc-rapid-commit-opt-05
Date: Tue, 13 Jul 2004 14:40:12 -0400
Message-ID: <BFELJLKGHEJOPOPGJBKKOEHFCJAA.steve@relicore.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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: <001401c468cf$fcb11840$0bfe7044@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.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
Content-Transfer-Encoding: 7bit

Kudos to Samsung for the new IPR statement...

How do the authors feel about the following tweak 
to the protocol:

When the Rapid commit client decides to accept an address
sent via a Rapid Commit ack, it should send out a DHCPREQUEST
(perhaps with the rapid commit option), 
similar to the classic DHC protocol. 

The sole purpose of this message is to notify any servers that 
offered addresses to release those addresses not selected.

IMHO this is inexpensive to do, and solves the address 
tie-up issue.

Cheers,

Steve Gonczi


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