Re: [Seamoby] CAR Discovery Requirements

John Schnizlein <jschnizl@cisco.com> Mon, 14 January 2002 17:11 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 MAA07456 for <seamoby-archive@odin.ietf.org>; Mon, 14 Jan 2002 12:11:34 -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 LAA13334; Mon, 14 Jan 2002 11:48:33 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA13302 for <seamoby@optimus.ietf.org>; Mon, 14 Jan 2002 11:48:31 -0500 (EST)
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06383 for <seamoby@ietf.org>; Mon, 14 Jan 2002 11:48:28 -0500 (EST)
Received: from JSCHNIZL-W2K1.cisco.com (rtp-vpn2-595.cisco.com [10.82.242.83]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id IAA04519; Mon, 14 Jan 2002 08:47:59 -0800 (PST)
Message-Id: <4.3.2.7.2.20020114113728.03782008@diablo.cisco.com>
X-Sender: jschnizl@diablo.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 14 Jan 2002 11:46:55 -0500
To: Govind Krishnamurthi <govs23@hotmail.com>
From: John Schnizlein <jschnizl@cisco.com>
Subject: Re: [Seamoby] CAR Discovery Requirements
Cc: seamoby@ietf.org
In-Reply-To: <F150wHUFPDyCEYWKnCk0001f8e5@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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

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