Re: mobility (and multicast...)
Paul Tsuchiya <tsuchiya@thumper.bellcore.com> Tue, 19 January 1993 15:15 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03029;
19 Jan 93 10:15 EST
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa03021;
19 Jan 93 10:15 EST
Received: from p.lanl.gov by CNRI.Reston.VA.US id aa09457; 19 Jan 93 10:17 EST
Received: from noc-gw.lanl.gov by p.lanl.gov (5.65/1.14)
id AA28871; Tue, 19 Jan 93 08:15:21 -0700
Received: by noc-gw.lanl.gov (4.1/SMI-4.1)
id AA26444; Tue, 19 Jan 93 08:14:12 MST
Return-Path: <tsuchiya@thumper.bellcore.com>
Received: from p.lanl.gov by noc-gw.lanl.gov (4.1/SMI-4.1)
id AA26440; Tue, 19 Jan 93 08:14:04 MST
Received: from thumper.bellcore.com by p.lanl.gov (5.65/1.14)
id AA28807; Tue, 19 Jan 93 08:14:03 -0700
Received: from chiya.bellcore.com by thumper.bellcore.com (4.1/4.7)
id <AA17790> for tuba@lanl.gov; Tue, 19 Jan 93 10:14:00 EST
Received: by chiya.bellcore.com (4.1/4.7)
id <AA13521> for tuba@lanl.gov; Tue, 19 Jan 93 10:13:58 EST
Date: Tue, 19 Jan 93 10:13:58 EST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Paul Tsuchiya <tsuchiya@thumper.bellcore.com>
Message-Id: <9301191513.AA13521@chiya.bellcore.com>
To: J.Crowcroft@cs.ucl.ac.uk, pip@thumper.bellcore.com, tuba@lanl.gov
Subject: Re: mobility (and multicast...)
> > 3. i believe mobility should be _integral_ in routers and not involve > more processes/servers etc....if hierarchical multicast addressing and > routeing are in place, i think something could evolve that is very > clean.... Hmmmmm. Next time I'm in London, we'll have to hash this out. I believe that mobility should be completely transparent to routers, and should be handled at the edges...... > > anyhow, sorry to cross post, just thinking out loud... as usual..... :-) PX
- mobility (and multicast...) Jon Crowcroft
- mobility (and multicast...) Jon Crowcroft
- Re: mobility (and multicast...) Paul Tsuchiya