RE: [Seamoby] CAR Discovery Requirements

Phillip Neumiller <PNeumiller@meshnetworks.com> Fri, 11 January 2002 18:34 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 NAA24873 for <seamoby-archive@odin.ietf.org>; Fri, 11 Jan 2002 13:34:38 -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 NAA10734; Fri, 11 Jan 2002 13:23:24 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA10703 for <seamoby@optimus.ietf.org>; Fri, 11 Jan 2002 13:23:22 -0500 (EST)
Received: from meshpdc.meshnetworks.com ([205.245.27.196]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24531 for <seamoby@ietf.org>; Fri, 11 Jan 2002 13:23:19 -0500 (EST)
Received: by meshpdc.meshnetworks.com with Internet Mail Service (5.5.2653.19) id <Z720RRBR>; Fri, 11 Jan 2002 13:23:14 -0500
Message-ID: <0DF9FBC42474A24CA50F7A27FB08E048616682@meshpdc.meshnetworks.com>
From: Phillip Neumiller <PNeumiller@meshnetworks.com>
To: "'Trossen Dirk (NRC/Boston)'" <Dirk.Trossen@nokia.com>, "'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>
Subject: RE: [Seamoby] CAR Discovery Requirements
Date: Fri, 11 Jan 2002 13:23:12 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
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

Hi Dirk,

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?

Thanks,

Phil
> 
****************************************************************************
This e-mail is intended only for the addressee named above and may contain
confidential, proprietary or privileged information. If you are not the
named addressee or the person responsible for delivering the message to the
named addressee, please inform us promptly by reply e-mail, then delete the
e-mail and destroy any printed copy. The contents should not be disclosed to
anyone and no copies should be made. We take reasonable precautions to
ensure that our emails are virus free. However we accept no responsibility
for any virus transmitted by us and recommend that you subject any incoming
e-mail to your own virus checking procedures. 

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