[dhcwg] Leasequery protocol issue
Ralph Droms <rdroms@cisco.com> Wed, 07 April 2004 04:35 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09460 for <dhcwg-archive@odin.ietf.org>; Wed, 7 Apr 2004 00:35:47 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BB4mX-0000KV-Cr for dhcwg-archive@odin.ietf.org; Wed, 07 Apr 2004 00:35:21 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i374ZLwl001258 for dhcwg-archive@odin.ietf.org; Wed, 7 Apr 2004 00:35:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BB4mX-0000KC-8z for dhcwg-web-archive@optimus.ietf.org; Wed, 07 Apr 2004 00:35:21 -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 AAA09382 for <dhcwg-web-archive@ietf.org>; Wed, 7 Apr 2004 00:35:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BB4mU-0006Ma-00 for dhcwg-web-archive@ietf.org; Wed, 07 Apr 2004 00:35:18 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BB3vn-00078j-00 for dhcwg-web-archive@ietf.org; Tue, 06 Apr 2004 23:40:52 -0400
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1BB2kc-0000i5-01 for dhcwg-web-archive@ietf.org; Tue, 06 Apr 2004 22:25:14 -0400
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org) by mx2.foretec.com with esmtp (Exim 4.24) id 1BB2gK-0004WG-Bv for dhcwg-web-archive@ietf.org; Tue, 06 Apr 2004 22:20:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BB2ff-0001wN-Co; Tue, 06 Apr 2004 22:20:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BB2fJ-0001qW-4N for dhcwg@optimus.ietf.org; Tue, 06 Apr 2004 22:19: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 WAA27974 for <dhcwg@ietf.org>; Tue, 6 Apr 2004 22:19:40 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1BB2fF-00006p-00 for dhcwg@ietf.org; Tue, 06 Apr 2004 22:19:42 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BB2Bt-0003J7-00 for dhcwg@ietf.org; Tue, 06 Apr 2004 21:49:22 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1BB1GE-0004Gl-00 for dhcwg@ietf.org; Tue, 06 Apr 2004 20:49:46 -0400
Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 06 Apr 2004 16:58:08 +0000
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i370nDKl014185 for <dhcwg@ietf.org>; Tue, 6 Apr 2004 17:49:15 -0700 (PDT)
Received: from rdroms-w2k01.cisco.com (che-vpn-cluster-1-83.cisco.com [10.86.240.83]) by flask.cisco.com (Mirapoint Messaging Server MOS 3.3.6-GR) with ESMTP id AHK37488; Tue, 6 Apr 2004 20:49:12 -0400 (EDT)
Message-Id: <4.3.2.7.2.20040406204605.02c44d40@flask.cisco.com>
X-Sender: rdroms@flask.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 06 Apr 2004 20:47:23 -0400
To: dhcwg@ietf.org
From: Ralph Droms <rdroms@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Subject: [dhcwg] Leasequery protocol issue
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
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>
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
Thomas Narten: Discuss: I wonder if the following is a possible protocol issue: Assume a client is connected to access concentrator A, and obtains a lease. Client moves to concentrator B, and obtains a second lease. B looses state, and issues lease query. Server will return two addresses. How does B know which addresses (and location info) applies to it (i.e, B) rather than A? Is there info in the protocol messages that allows B to determine which address is its? E.g., does the relay-agent info include such an identification in it? _______________________________________________ dhcwg mailing list dhcwg@ietf.org https://www1.ietf.org/mailman/listinfo/dhcwg
- [dhcwg] Leasequery protocol issue Ralph Droms
- Re: [dhcwg] Leasequery protocol issue Kim Kinnear