Re: [dhcwg] Lifetime option (draft-ietf-dhc-lifetime-00.txt)
Thomas Narten <narten@us.ibm.com> Fri, 02 July 2004 15:11 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 LAA12434; Fri, 2 Jul 2004 11:11:54 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BgPM1-00030h-Hh; Fri, 02 Jul 2004 10:49:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BgPBE-0007w5-5t for dhcwg@megatron.ietf.org; Fri, 02 Jul 2004 10:38:20 -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 KAA09309 for <dhcwg@ietf.org>; Fri, 2 Jul 2004 10:38:17 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BgPBD-0000Kw-Dz for dhcwg@ietf.org; Fri, 02 Jul 2004 10:38:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BgPAB-00000p-00 for dhcwg@ietf.org; Fri, 02 Jul 2004 10:37:16 -0400
Received: from e5.ny.us.ibm.com ([32.97.182.105]) by ietf-mx with esmtp (Exim 4.12) id 1BgP9G-0007D3-00 for dhcwg@ietf.org; Fri, 02 Jul 2004 10:36:18 -0400
Received: from northrelay04.pok.ibm.com (northrelay04.pok.ibm.com [9.56.224.206]) by e5.ny.us.ibm.com (8.12.10/8.12.2) with ESMTP id i62EZjDk453410; Fri, 2 Jul 2004 10:35:46 -0400
Received: from rotala.raleigh.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by northrelay04.pok.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i62EaaV0018754; Fri, 2 Jul 2004 10:36:36 -0400
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.12.8/8.12.5) with ESMTP id i62EaJc2022890; Fri, 2 Jul 2004 10:36:19 -0400
Received: from rotala.raleigh.ibm.com (narten@localhost) by rotala.raleigh.ibm.com (8.12.8/8.12.8/Submit) with ESMTP id i62EaIAk022886; Fri, 2 Jul 2004 10:36:19 -0400
Message-Id: <200407021436.i62EaIAk022886@rotala.raleigh.ibm.com>
To: Stig Venaas <Stig.Venaas@uninett.no>
Subject: Re: [dhcwg] Lifetime option (draft-ietf-dhc-lifetime-00.txt)
In-Reply-To: Message from Stig.Venaas@uninett.no of "Tue, 29 Jun 2004 13:14:25 +0200." <20040629111425.GA14068@sverresborg.uninett.no>
Date: Fri, 02 Jul 2004 10:36:18 -0400
From: Thomas Narten <narten@us.ibm.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=AWL 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>
Sender: dhcwg-bounces@ietf.org
Errors-To: dhcwg-bounces@ietf.org
Personally, I think that if one is trying to contact a DHC server, and none respond, there should be a generic algorithm used for retries. I.e., the case for this option should not be any different (for say) the case where one first boots, and no DHC server responds, or when one fails to renew an address after an address expires. I.e., isn't there already a generic retranmission with backoff and some upper limit? Why not just do the same? Is there a need for multiple different algorithms? Thomas _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Lifetime option (draft-ietf-dhc-lifetime-… Stig Venaas
- Re: [dhcwg] Lifetime option (draft-ietf-dhc-lifet… Thomas Narten
- Re: [dhcwg] Lifetime option (draft-ietf-dhc-lifet… Stig Venaas