IETF Logo Mail Archive

Re: [Seamoby] CAR Discovery Requirements

"James Kempf" <kempf@docomolabs-usa.com> Tue, 12 March 2002 20:42 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 PAA06263 for <seamoby-archive@odin.ietf.org>; Tue, 12 Mar 2002 15:42:43 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA09285; Tue, 12 Mar 2002 15:28:59 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA09239 for <seamoby@optimus.ietf.org>; Tue, 12 Mar 2002 15:28:56 -0500 (EST)
Received: from fridge.docomolabs-usa.com (fridge.docomolabs-usa.com [216.98.102.228]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05694 for <seamoby@ietf.org>; Tue, 12 Mar 2002 15:28:53 -0500 (EST)
Received: from T23KEMPF (dhcp126.docomolabs-usa.com [172.21.96.126]) by fridge.docomolabs-usa.com (8.11.3/8.11.3) with SMTP id g2CKSLI29270; Tue, 12 Mar 2002 12:28:21 -0800 (PST)
Message-ID: <020b01c1ca04$39d70f80$7e6015ac@T23KEMPF>
From: James Kempf <kempf@docomolabs-usa.com>
To: Dirk.Trossen@nokia.com, seamoby@ietf.org
References: <DC504E9C3384054C8506D3E6BB012460382FE0@bsebe001.NOE.Nokia.com>
Subject: Re: [Seamoby] CAR Discovery Requirements
Date: Tue, 12 Mar 2002 12:26:44 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 7bit
Sender: seamoby-admin@ietf.org
Errors-To: seamoby-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Context Transfer, Handoff Candidate Discovery, and Dormant Mode Host Alerting <seamoby.ietf.org>
X-BeenThere: seamoby@ietf.org
Content-Transfer-Encoding: 7bit

Dirk,

</wg-chair-hat-off>

> "3.xx Providing MN's requirement for Determination of CARs
> 
> The fundamental task of CAR discovery is to determine candidate
> access routers (from the set of GAARs) that meet MN's requirements,
> if known at the time of handoff. A CAR discovery protocol MUST 
> determine a set of CARs that meet MN's requirements. For this, 
> a CAR discovery protocol MUST provide means for the MN to express 
> these requirements."
> 

I think this is confusing two issues:

    - Distribution of routing reachability and capability information.

    - Expression of MN requirements or rights.

The second issue may require, for example, AAA, or it 
may be implemented using an AAA protocol.

I think it would make more sense to keep these issues separate.

</wg-chair-hat-on>

            jak





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

v2.35.0 | Report a Bug | By Email | System Status