[Seamoby] RE: CAR Discovery Draft

"Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se> Mon, 14 January 2002 16:15 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 LAA05510 for <seamoby-archive@odin.ietf.org>; Mon, 14 Jan 2002 11:15:25 -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 KAA11458; Mon, 14 Jan 2002 10:56:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA11430 for <seamoby@optimus.ietf.org>; Mon, 14 Jan 2002 10:56:05 -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 KAA04903 for <seamoby@ietf.org>; Mon, 14 Jan 2002 10:56:02 -0500 (EST)
Received: from esealnt409.al.sw.ericsson.se (ESEALNT409.al.sw.ericsson.se [153.88.251.32]) by penguin.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0EFu3K16704 for <seamoby@ietf.org>; Mon, 14 Jan 2002 16:56:03 +0100 (MET)
Received: FROM esealnt400.al.sw.ericsson.se BY esealnt409.al.sw.ericsson.se ; Mon Jan 14 16:56:02 2002 +0100
Received: by esealnt400 with Internet Mail Service (5.5.2653.19) id <Z1HX2FJ1>; Mon, 14 Jan 2002 16:55:46 +0100
Message-ID: <4DA6EA82906FD511BE2F00508BCF053801C4C1F1@Esealnt861.al.sw.ericsson.se>
From: "Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se>
To: 'James Kempf' <kempf@docomolabs-usa.com>, "Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se>, "'Trossen Dirk (NRC/Boston)'" <Dirk.Trossen@nokia.com>, Govind Krishnamurthi <govs23@hotmail.com>, seamoby@ietf.org
Date: Mon, 14 Jan 2002 16:55:39 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
Subject: [Seamoby] RE: CAR Discovery Draft
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

James,

  > It certainly would have been helpful if you had posted your comments
  > during the Last Call period.
  > Last Call expired Jan. 4 on this document. I don't believe 
  > comments sent
  > in after
  > Last Call necessarily need to be accommodated, but, if 
  > these are simple
  > editorial changes that can be
  >  resolved in the next day or two, then I think we can 
  > accommodate them.
  > However, I do not want to get into a
  >  long discussion about requirements prior to releasing the problem
  > statement. 

=> The requirements discussion is seaprate from my 
comments on the problem statement. I would have liked
to send them earlier too, but as I said it's a very 
common holiday period. Perhaps something to think about
with future last calls.

  > 
  > > => To me the following text from the draft suggests
  > > that the AR knows ALL GAARs. I think that's unrealistic.
  > >
  > >   4.1 Anticipated CAR Discovery
  > >
  > >    In this approach, an AR currently serving the MN identifies all
  > CARs
  > >    for the MN's handoff, at some point prior to handoff.
  > >
  > 
  > How about:
  > 
  >     In this approach, an AR currently serving the MN 
  > identifies some set
  > of
  >     suitable CARs for the MN's handoff, at some point prior 
  > to handoff.

=> Fine with me
  > 
  > If this text is unsatisfactory, please feel free to propose an
  > alternative.
  > 
  > > => anticipation should not be associated with the
  > > case where the MN does not signal, you can have
  > > anticipation when the MN signals also. Therefore
  > > associating 'anticipation' with a certain model
  > > where the MN does not signal, does not seem right.
  > >
  > > I'm referring to the title of ch 4.1
  > >
  > 
  > One of the problems with not having a consistent set
  > of terminology for wireless networking in the IETF
  > is that it becomes difficult to find a word that describes
  > the concept you are trying to get at without impinging
  > on what somebody else thinks a particular word
  > means. I believe this is the case here. The "anticipated"
  > here has nothing to do with "anticipated handover."
  > Here, the AR is anticipating the need for CARs
  > by performing discovery prior to the MN needing
  > them. 

=> Then it should be explicitly stated that the 
anticipation is 'AR-based'. Simply saying 
'anticipation' in isolation and not mentioning
this term in ch 4.2 is misleading because it associates
'anticipation' with a certain mechanism.

  > Perhaps another word would be suitable? Please
  > feel free to suggest one. Perhaps "router based"?

=> Exactly, I think 'access router- based' is more
appropriate. 

Hesham

  > 
  >             jak
  > 

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