Re: [dhcwg] dhcpv6-24: Elapsed Time option
Ted Lemon <Ted.Lemon@nominum.com> Thu, 09 May 2002 18:24 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03893 for <dhcwg-archive@odin.ietf.org>; Thu, 9 May 2002 14:24:32 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id OAA15437 for dhcwg-archive@odin.ietf.org; Thu, 9 May 2002 14:24:41 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA15248; Thu, 9 May 2002 14:22:25 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id OAA15219 for <dhcwg@optimus.ietf.org>; Thu, 9 May 2002 14:22:23 -0400 (EDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA03672 for <dhcwg@ietf.org>; Thu, 9 May 2002 14:22:13 -0400 (EDT)
Received: from green.bisbee.fugue.com (dsl-64-193-175-153.telocity.com [64.193.175.153]) by toccata.fugue.com (8.11.3/8.6.11) with ESMTP id g49ILIS13650; Thu, 9 May 2002 11:21:18 -0700 (PDT)
Received: from tongpanyi (localhost [127.0.0.1]) by green.bisbee.fugue.com (8.10.2/8.6.11) with ESMTP id g49IMJ602271; Thu, 9 May 2002 13:22:19 -0500 (CDT)
Date: Thu, 09 May 2002 13:22:19 -0500
Subject: Re: [dhcwg] dhcpv6-24: Elapsed Time option
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Mime-Version: 1.0 (Apple Message framework v481)
Cc: 'Thomas Narten' <narten@us.ibm.com>, dhcwg@ietf.org
To: "Bernie Volz (EUD)" <Bernie.Volz@am1.ericsson.se>
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <66F66129A77AD411B76200508B65AC69B4D3E5@EAMBUNT705>
Message-Id: <B2A7514D-6379-11D6-A5AB-00039367340A@nominum.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.481)
Content-Transfer-Encoding: 7bit
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
Content-Transfer-Encoding: 7bit
If relays aren't using the time to decide to which server to relay, it's safe for servers to use it, because they're the end recipients of it. The only problem that comes in is when the relay might censor some messages to some servers at different times based on how long the client has been trying to send the message. So I think this field is useful as long as relays don't use it to decide to which server a message is sent. _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] dhcpv6-24: Elapsed Time option Thomas Narten
- RE: [dhcwg] dhcpv6-24: Elapsed Time option Bernie Volz (EUD)
- Re: [dhcwg] dhcpv6-24: Elapsed Time option Ted Lemon
- RE: [dhcwg] dhcpv6-24: Elapsed Time option Bernie Volz (EUD)
- Re: [dhcwg] dhcpv6-24: Elapsed Time option Ted Lemon
- RE: [dhcwg] dhcpv6-24: Elapsed Time option Bernie Volz (EUD)
- RE: [dhcwg] dhcpv6-24: Elapsed Time option Bernie Volz (EUD)
- Re: [dhcwg] dhcpv6-24: Elapsed Time option Ted Lemon
- RE: [dhcwg] dhcpv6-24: Elapsed Time option Bernie Volz (EUD)
- Re: [dhcwg] dhcpv6-24: Elapsed Time option Ted Lemon
- Re: [dhcwg] dhcpv6-24: Elapsed Time option Ted Lemon
- Re: [dhcwg] dhcpv6-24: Elapsed Time option Ted Lemon
- RE: [dhcwg] dhcpv6-24: Elapsed Time option Vijayabhaskar A K