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

"Steve Gonczi" <steve@relicore.com> Wed, 14 July 2004 04:03 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 AAA09814; Wed, 14 Jul 2004 00:03:49 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkaHw-00055W-Gg; Tue, 13 Jul 2004 23:18:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkWzz-0007YB-Bs for dhcwg@megatron.ietf.org; Tue, 13 Jul 2004 19:47:47 -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 TAA09922 for <dhcwg@ietf.org>; Tue, 13 Jul 2004 19:47:41 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BkWzv-0000tL-H6 for dhcwg@ietf.org; Tue, 13 Jul 2004 19:47:43 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BkWuN-0007DB-00 for dhcwg@ietf.org; Tue, 13 Jul 2004 19:42:01 -0400
Received: from ftp.relicore.com ([4.36.57.198]) by ietf-mx with esmtp (Exim 4.12) id 1BkWnq-0005U5-00 for dhcwg@ietf.org; Tue, 13 Jul 2004 19:35:14 -0400
Received: from STEVEPC ([192.168.0.222]) by ftp.relicore.com (8.12.9/8.12.9) with SMTP id i6DNA1AZ023293; Tue, 13 Jul 2004 19:10:01 -0400 (EDT)
From: "Steve Gonczi" <steve@relicore.com>
To: <soohong.park@samsung.com>
Subject: RE: RE: [dhcwg] dhc WG last call on draft-ietf-dhc-rapid-commit-opt-05
Date: Tue, 13 Jul 2004 19:34:44 -0400
Message-ID: <BFELJLKGHEJOPOPGJBKKCEHHCJAA.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: <0I0T009E88TSB3@ms3.samsung.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.1 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="===============0672991952=="
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org

Samsung Enterprise Portal mySingleHi Daniel,

I have to admit I am not entirely clear on what you meant,
although I suspect you disagree with my suggestion.

Let me try to make my case:

For the cost of sending out one extra message by the Rapid Commit
client (which BTW does not cause any significant delay)
you could eliminate the entire 3.2 section from your protocol.

To recap:

1)  The "no multiple servers" restriction
2)  or "must have enough addresses" restriction
3)  or "use short lease times" restriction

Why would you not want to do this?


/sG
  -----Original Message-----
  From: PARK SOO HONG [mailto:soohong.park@samsung.com]
  Sent: Tuesday, July 13, 2004 5:54 PM
  To: Steve Gonczi; soohong.park@samsung.com
  Cc: Bernie Volz; dhcwg@ietf.org
  Subject: Re: RE: [dhcwg] dhc WG last call on
draft-ietf-dhc-rapid-commit-opt-05


  Hi Steve, thanks your comments and see my comment inline



  >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.




  I'd keep the original sentence since to sync the operation of DHCPv6,

  also make sure this option is for *RAPID COMMIT*.







  Regards



  Daniel (Soohong Daniel Park)

  Mobile Platform Laboratory. SAMSUNG Electronics


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