[Seamoby] RE: Differences in Requirements between AR and MN CAR discovery

"Trossen Dirk (NRC/Boston)" <Dirk.Trossen@nokia.com> Tue, 15 January 2002 18:25 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 NAA08296 for <seamoby-archive@odin.ietf.org>; Tue, 15 Jan 2002 13:25:36 -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 NAA16646; Tue, 15 Jan 2002 13:14:52 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA16615 for <seamoby@optimus.ietf.org>; Tue, 15 Jan 2002 13:14:48 -0500 (EST)
Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07820 for <seamoby@ietf.org>; Tue, 15 Jan 2002 13:14:45 -0500 (EST)
Received: from esvir02nok.ntc.nokia.com (esvir02nokt.ntc.nokia.com [172.21.143.34]) by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0FIEl905630 for <seamoby@ietf.org>; Tue, 15 Jan 2002 20:14:48 +0200 (EET)
Received: from esebh002.NOE.Nokia.com (unverified) by esvir02nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id <T58783252efac158f22078@esvir02nok.ntc.nokia.com>; Tue, 15 Jan 2002 20:14:46 +0200
Received: from daebh002.NOE.Nokia.com ([172.18.242.232]) by esebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.3779); Tue, 15 Jan 2002 20:14:45 +0200
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966); Tue, 15 Jan 2002 12:14:19 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Date: Tue, 15 Jan 2002 13:14:18 -0500
Message-ID: <DC504E9C3384054C8506D3E6BB012460382DFE@bsebe001.NOE.Nokia.com>
Thread-Topic: Differences in Requirements between AR and MN CAR discovery
Thread-Index: AcGd7is5K3fRMAnhEdar0gAIx6S5QwAARQVQ
From: "Trossen Dirk (NRC/Boston)" <Dirk.Trossen@nokia.com>
To: 'ext James Kempf' <kempf@docomolabs-usa.com>, "ext Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se>, Govind Krishnamurthi <govs23@hotmail.com>, seamoby@ietf.org
X-OriginalArrivalTime: 15 Jan 2002 18:14:19.0075 (UTC) FILETIME=[7308C130:01C19DF0]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id NAA16616
Subject: [Seamoby] RE: Differences in Requirements between AR and MN CAR discovery
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 James,

> I understand, but I believe that Hesham, and perhaps some others, do
> think that
> there will be different requirements based on whether the MN or
> the ARs are doing the discovery.

With all due respect, James, but believing in differences won't
lead to any definition of requirements. I'm not saying that there
is no difference but I want to see it.

> 
> I agree that we need to have a clearer understanding of what the
> differences in requirements are. Perhaps those who think
> that there should be a difference can post specific requirements
> that they believe do differ (and please post under the above
> subject, so I can keep track of the thread). If we don't get a well
> articulated list of such requirements by the end of the requirements
> development
> period, then I think we can be justified in not separating them.

Thanks, that's exactly my point. All comments regarding separation
merely asked for separation without giving ANY concrete example.
But that's what I asked for. If we get a list of requirements that
indeed contains items that demand for a separation, we have to do 
this. But for that, we first need these items. I'm simply kind
of confused why we discuss first the grouping of information, i.e.,
requirements, before we actually have the information that justify
this specific grouping. Maybe, another grouping would make much
more sense actually. I'd like to discuss this at the end not before.

So please, everybody who 'believes' that this separation makes
sense, send the specific requirement(s) to the list. We'll keep
track of them and present (hopefully) an appropriate ordered/
separated/grouped list of them at the end of the discussion. 
Right now, we're still at the list that was presented in SLC 
(with some proposals to change MUSTs and SHOULDs).

Regards,



Dirk

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