RE: [Seamoby] CAR Discovery Requirements

"Trossen Dirk (NRC/Boston)" <Dirk.Trossen@nokia.com> Fri, 11 January 2002 18:48 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 NAA25335 for <seamoby-archive@odin.ietf.org>; Fri, 11 Jan 2002 13:48:01 -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 NAA11478; Fri, 11 Jan 2002 13:35:42 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA11446 for <seamoby@optimus.ietf.org>; Fri, 11 Jan 2002 13:35:40 -0500 (EST)
Received: from mgw-dax2.ext.nokia.com (mgw-dax2.ext.nokia.com [63.78.179.217]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24973 for <seamoby@ietf.org>; Fri, 11 Jan 2002 13:35:38 -0500 (EST)
Received: from davir02nok.americas.nokia.com (davir02nok.americas.nokia.com [172.18.242.85]) by mgw-dax2.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0BIb8Q24583 for <seamoby@ietf.org>; Fri, 11 Jan 2002 12:37:08 -0600 (CST)
Received: from daebh001.NOE.Nokia.com (unverified) by davir02nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5861f48f0dac12f2550ef@davir02nok.americas.nokia.com>; Fri, 11 Jan 2002 12:35:39 -0600
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966); Fri, 11 Jan 2002 12:35:39 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
Subject: RE: [Seamoby] CAR Discovery Requirements
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Fri, 11 Jan 2002 13:35:38 -0500
Message-ID: <DC504E9C3384054C8506D3E6BB01246008D55E@bsebe001.NOE.Nokia.com>
Thread-Topic: [Seamoby] CAR Discovery Requirements
Thread-Index: AcGazQsZ48zmlga7EdaxMgAIx6TWeAAABa2w
From: "Trossen Dirk (NRC/Boston)" <Dirk.Trossen@nokia.com>
To: 'ext Phillip Neumiller' <PNeumiller@meshnetworks.com>, "ext Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se>, Govind Krishnamurthi <govs23@hotmail.com>, seamoby@ietf.org
Cc: "Krishnamurthi Govind (NRC/Boston)" <Govind.Krishnamurthi@nokia.com>
X-OriginalArrivalTime: 11 Jan 2002 18:35:39.0289 (UTC) FILETIME=[C472E890:01C19ACE]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id NAA11447
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: 8bit

Hi Phil,

> Perhaps we can compromise here and say that some particular set of 
> specific methods MUST be supported as a minimum and not restrict at
> all what goes on beyond this.  Lets be honest with ourselves here,
> this protocol will be used by MIP and MANET protocols as their 
> primary customers.  If not, then what customer does this requirement
> serve?  Maybe I am dense on this, but I just don't get why we can't
> specify the existance of an interface here?
> 
Maybe, there is some misunderstanding on my side what this interface
is about. 

Let's assume a final CAR discovery solution (however it'll work)
that provides the current AR with a set of GAARs and its associated
capabilities. Do you want to make the necessity mandatory to define
an interface to access this information for any (maybe mobility
management
dependend) subsequent actions, such as a policy server-based TAR
selection 
for the fast handover case?

Regards,


Dirk

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