RE: [Seamoby] CAR Discovery Requirements

John Schnizlein <jschnizl@cisco.com> Mon, 14 January 2002 17:49 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 MAA09269 for <seamoby-archive@odin.ietf.org>; Mon, 14 Jan 2002 12:49:03 -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 MAA15760; Mon, 14 Jan 2002 12:30:27 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA15711 for <seamoby@optimus.ietf.org>; Mon, 14 Jan 2002 12:30:25 -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 MAA08425 for <seamoby@ietf.org>; Mon, 14 Jan 2002 12:30:21 -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 JAA19420; Mon, 14 Jan 2002 09:29:46 -0800 (PST)
Message-Id: <4.3.2.7.2.20020114120320.037d6358@diablo.cisco.com>
X-Sender: jschnizl@diablo.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 14 Jan 2002 12:28:42 -0500
To: "Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se>
From: John Schnizlein <jschnizl@cisco.com>
Subject: RE: [Seamoby] CAR Discovery Requirements
Cc: Govind Krishnamurthi <govs23@hotmail.com>, seamoby@ietf.org
In-Reply-To: <4DA6EA82906FD511BE2F00508BCF053801C4C1F6@Esealnt861.al.sw. ericsson.se>
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:00 PM 1/14/2002, Hesham Soliman (ERA) wrote:
>>...
>  > >6. Protocol applicability ? SHOULD (?)
>  > 
>  > Inter-domain discovery of access routers is problematic.
>
>AR - AR or AR MN ???

This is a good question.

>Clearly AR - MN lis an obvious way to discover all routers that 
>the MN can hear. Inter/intra domain issues are not relevant. 

If the WG goes that way, the resulting protocol would be usable
only by operators who allow access to any mobile node (MN). But 
normal business arrangements might require a pre-existing 
relationship between the subscriber (MN) before service providers 
are willing to be discovered. Remember the implication that the
AR would be willing to accept an operating context for the MN from
some other provider.

The issue is potentially even more problematic for AR - AR. Would the
operator of an access service willingly include another operator's
routers to be neighbors, encouraging the possibility that the MN
would switch into/out-of service from a different provider?
We know that telephone companies try to avoid this.

>So please make it clear which part of the protocol
>you're referring to. We should not always assume 
>that we're discussing the AR - AR case. 
>
>...
>Let the MN decide.

This is a good answer. But then the MN would need to get the sort of
information it needs to make a reasonable decision. This might include
pricing information, or information regarding the which providers
share access reciprocity agreements. Are we ready for all this?

John


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