RE: [Seamoby] CAR Discovery Requirements

"Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se> Fri, 11 January 2002 17:56 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 MAA23536 for <seamoby-archive@odin.ietf.org>; Fri, 11 Jan 2002 12:56:45 -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 MAA09208; Fri, 11 Jan 2002 12:45:50 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id MAA09177 for <seamoby@optimus.ietf.org>; Fri, 11 Jan 2002 12:45:47 -0500 (EST)
Received: from albatross-ext.wise.edt.ericsson.se (albatross-ext.wise.edt.ericsson.se [194.237.142.116]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23126 for <seamoby@ietf.org>; Fri, 11 Jan 2002 12:45:45 -0500 (EST)
Received: from esealnt461 (esealnt461.al.sw.ericsson.se [153.88.251.61]) by albatross.wise.edt.ericsson.se (8.11.0/8.11.0/WIREfire-1.3) with SMTP id g0BHjkJ13488 for <seamoby@ietf.org>; Fri, 11 Jan 2002 18:45:46 +0100 (MET)
Received: FROM esealnt742.al.sw.ericsson.se BY esealnt461 ; Fri Jan 11 18:45:29 2002 +0100
Received: by esealnt742.al.sw.ericsson.se with Internet Mail Service (5.5.2653.19) id <YHKCHD50>; Fri, 11 Jan 2002 18:36:50 +0100
Message-ID: <4DA6EA82906FD511BE2F00508BCF053801C4C1E6@Esealnt861.al.sw.ericsson.se>
From: "Hesham Soliman (ERA)" <hesham.soliman@era.ericsson.se>
To: 'Govind Krishnamurthi' <govs23@hotmail.com>
Cc: seamoby@ietf.org
Subject: RE: [Seamoby] CAR Discovery Requirements
Date: Fri, 11 Jan 2002 18:45:27 +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

Hi Govind, 

Sure you could use CAR without any mobility 
management, but I think that it is reasonable
to assume that CAR will also be very useful for 
MNs. If you agree with that, then it would sense
to make sure that it certainly works smoothly
with existing solutions, that will most likely
be around for a long time. 

Again, I' not suggesting we integrate CAR into
MIP, just make sure they work well together.

Hesham

  > -----Original Message-----
  > From: Govind Krishnamurthi [mailto:govs23@hotmail.com]
  > Sent: Friday, January 11, 2002 5:49 PM
  > To: hesham.soliman@era.ericsson.se
  > Subject: RE: [Seamoby] CAR Discovery Requirements
  > 
  > 
  > Hello Hesham,
  > Just for clarification. Is there an inherent assumption in your
  > statement that CAR discovery will need assistance from 
  > mobility management 
  > protocols. My understanding is that in Seamoby we don't
  > restrict only to MIP. Also by making it independent of 
  > mobility management 
  > protocols  we clearly don't affect any of the features of 
  > the underlying 
  > mobility management protocol is that not? Or am I missing 
  > something here.
  > -Govind.
  > 
  > 
  > 
  > >
  > >Phil,
  > >
  > >   > We seem to dance around in abstract space a lot in this WG.
  > >
  > >=> Really ! :)
  > >
  > >   >  Isn't it time
  > >   > to get down to brass tacks?  MIP has an implied
  > >   > architecture and it is not
  > >   > going away.  Neither are many of the MANET protocols.  What
  >    > ever happened
  > >   > to the "running code" idea anyway?  I don't see why 
  > we have to be so
  > >   > very vague (which is occuring strictly to be pedantic about
  > >   > requirement-
  > >   > speak).  There is an old adage that states if its not
  > >   > "testable" its not
  > >   > a requirement.
  > >
  > >=> I agree, we should have clear and 'easy to test'
  > >requirements. I was only explaining in generic terms
  > >that requirements should not mandate solutions. In  this
  > >particular case, all I care about is that no optimisations
  > >or features of existing MIP/MANET stuff is lost.
  > >I don't care how it's done.
  > >
  > >Hesham
  > >
  > >
  > >_______________________________________________
  > >Seamoby mailing list
  > >Seamoby@ietf.org
  > >https://www1.ietf.org/mailman/listinfo/seamoby
  > 
  > 
  > 
  > 
  > _________________________________________________________________
  > MSN Photos is the easiest way to share and print your photos: 
  > http://photos.msn.com/support/worldwide.aspx
  > 

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