IETF Logo Mail Archive

RE: [Seamoby] CAR Discovery Requirements

"Trossen Dirk (NRC/Boston)" <Dirk.Trossen@nokia.com> Fri, 11 January 2002 18:30 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 NAA24744 for <seamoby-archive@odin.ietf.org>; Fri, 11 Jan 2002 13:30:46 -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 NAA10570; Fri, 11 Jan 2002 13:18:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA10536 for <seamoby@optimus.ietf.org>; Fri, 11 Jan 2002 13:18:29 -0500 (EST)
Received: from mgw-dax1.ext.nokia.com (mgw-dax1.ext.nokia.com [63.78.179.216]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24347 for <seamoby@ietf.org>; Fri, 11 Jan 2002 13:18:26 -0500 (EST)
Received: from davir01nok.americas.nokia.com (davir01nok.americas.nokia.com [172.18.242.84]) by mgw-dax1.ext.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0BIIcQ27441 for <seamoby@ietf.org>; Fri, 11 Jan 2002 12:18:38 -0600 (CST)
Received: from daebh001.NOE.Nokia.com (unverified) by davir01nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id <T5861e4ba8bac12f254079@davir01nok.americas.nokia.com>; Fri, 11 Jan 2002 12:18:21 -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:18:21 -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:18:20 -0500
Message-ID: <DC504E9C3384054C8506D3E6BB012460382DD5@bsebe001.NOE.Nokia.com>
Thread-Topic: [Seamoby] CAR Discovery Requirements
Thread-Index: AcGayl6wRCPKYQa9Edar0gAIx6S5QwAAWosA
From: "Trossen Dirk (NRC/Boston)" <Dirk.Trossen@nokia.com>
To: "'ext Hesham Soliman (ERA)'" <hesham.soliman@era.ericsson.se>, Phillip Neumiller <PNeumiller@meshnetworks.com>, Govind Krishnamurthi <govs23@hotmail.com>, seamoby@ietf.org
Cc: "Krishnamurthi Govind (NRC/Boston)" <Govind.Krishnamurthi@nokia.com>
X-OriginalArrivalTime: 11 Jan 2002 18:18:21.0260 (UTC) FILETIME=[59BC40C0:01C19ACC]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id NAA10537
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 Hesham,

maybe you should outline what you mean by 'accomodating features'.

Being compatible to existing mobility management solution means to
me not to break mobility management when introducing a specific
solution.

Accomodating features means to me to use specific features whereever
possible. 

These are two different things. The first one should be clear, I simply
don't like the second one since it restricts the solution space. That's 
where the discussion started by Phil's proposal to make specific methods

mandatory in any solution.

Regards,



Dirk

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

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