RE: [Seamoby] CAR Discovery Requirements

"Trossen Dirk (NRC/Boston)" <Dirk.Trossen@nokia.com> Mon, 14 January 2002 17:20 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 MAA07880 for <seamoby-archive@odin.ietf.org>; Mon, 14 Jan 2002 12:20:07 -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 LAA13630; Mon, 14 Jan 2002 11:58: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 LAA13599 for <seamoby@optimus.ietf.org>; Mon, 14 Jan 2002 11:58: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 LAA06713 for <seamoby@ietf.org>; Mon, 14 Jan 2002 11:58:25 -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 g0EGwdQ17873 for <seamoby@ietf.org>; Mon, 14 Jan 2002 10:58:39 -0600 (CST)
Received: from daebh002.NOE.Nokia.com (unverified) by davir01nok.americas.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id <T58710ea700ac12f254079@davir01nok.americas.nokia.com>; Mon, 14 Jan 2002 10:58:27 -0600
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.2966); Mon, 14 Jan 2002 10:57:42 -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: Mon, 14 Jan 2002 11:57:41 -0500
Message-ID: <DC504E9C3384054C8506D3E6BB012460382DE1@bsebe001.NOE.Nokia.com>
Thread-Topic: [Seamoby] CAR Discovery Requirements
Thread-Index: AcGdG8ZiwAzO4gkNEdaJYAAIx6TWpQAADOWg
From: "Trossen Dirk (NRC/Boston)" <Dirk.Trossen@nokia.com>
To: 'ext John Schnizlein' <jschnizl@cisco.com>, Govind Krishnamurthi <govs23@hotmail.com>
Cc: seamoby@ietf.org
X-OriginalArrivalTime: 14 Jan 2002 16:57:42.0270 (UTC) FILETIME=[94B639E0:01C19D1C]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id LAA13600
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 John,

I'm kind of confused by your comment. Are you questioning
the inter-domain handoff or the discovery? Why do I have to
resolve which users are subscribers of which domains if I want
to discover ARs in my proximity?

We're discussing CAR discovery. I don't see your policy
interactions, inter-domain roaming, and billing problems in this
context. However, it is certainly an issue for the actual selection of
the
target AR, but TAR selection is not within the scope of the
CAR discovery protocol.

Regards,



Dirk
> -----Original Message-----
> From: ext John Schnizlein [mailto:jschnizl@cisco.com]
> Sent: Monday, January 14, 2002 11:47 AM
> To: Govind Krishnamurthi
> Cc: seamoby@ietf.org
> Subject: Re: [Seamoby] CAR Discovery Requirements
> 
> 
> At 12:50 PM 1/10/2002, Govind Krishnamurthi wrote:
> >...
> >6. Protocol applicability ? SHOULD (?) 
> >(show of hands indicated that this item should be changed to a MUST) 
> >support inter-domain as well as Intra-domain scope
> 
> Inter-domain discovery of access routers (which seems implied by what
> might otherwise seem an innocuous protocol design feature) is 
> problematic.
> 
> It would require resolving which users are subscribers of 
> which domains,
> or complex inter-domain roaming and billing reciprocity. 
> 
> While it seems reasonable to avoid locking mobile stations 
> into a single
> domain, the policy interactions of requiring multiple-domain discovery
> would make the task much more difficult at the start.
> 
> Please reconsider even the SHOULD for this item, much less 
> moving toward
> MUST.
> 
> John
> 
> 
> _______________________________________________
> Seamoby mailing list
> Seamoby@ietf.org
> https://www1.ietf.org/mailman/listinfo/seamoby
> 

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