RE: [Seamoby] CAR Discovery Requirements

"Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se> Mon, 14 January 2002 17:24 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 MAA08143 for <seamoby-archive@odin.ietf.org>; Mon, 14 Jan 2002 12:24:29 -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 MAA14498; Mon, 14 Jan 2002 12:00:54 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA14462 for <seamoby@optimus.ietf.org>; Mon, 14 Jan 2002 12:00:51 -0500 (EST)
Received: from penguin-ext.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06860 for <seamoby@ietf.org>; Mon, 14 Jan 2002 12:00:47 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61]) by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0EH0nK26526 for <seamoby@ietf.org>; Mon, 14 Jan 2002 18:00:49 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt461 ; Mon Jan 14 18:00:32 2002 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19) id <YHKCJ1DA>; Mon, 14 Jan 2002 17:51:50 +0100
Message-ID: <4DA6EA82906FD511BE2F00508BCF053801C4C1F6@Esealnt861.al.sw.ericsson.se>
From: "Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se>
To: 'John Schnizlein' <jschnizl@cisco.com>, Govind Krishnamurthi <govs23@hotmail.com>
Cc: seamoby@ietf.org
Subject: RE: [Seamoby] CAR Discovery Requirements
Date: Mon, 14 Jan 2002 18:00:28 +0100
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

>...
  > >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. 

=> This is exactly why I urge you (this wg) to clearly 
explain which protocol you are talking about. AR - AR or
AR MN ???
Clearly AR - MN lis an obvious way to discover all routers 
that the MN can hear. Inter/intra domain issues are 
not relevant. 

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. 

  > 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.

=> Certainly. But there is an easy way of doing that:
Let the MN decide.

Hesham

  > _______________________________________________
  > 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