[AG-TECH] Mapping IP addresses to Venues

[Tony Rimovsky]

Bill will smack me for this, but this is essentially the same
functionality that SDR provides.

Venues has the potential to be an example of a new paradigm for
dynamic address/port assignment via http instead of SAP.  What Ivan is
describing sounds wonderful.



On Fri, Mar 22, 2002 at 01:05:25AM -0600, Ivan Judson wrote:
> 
> I think what this conversation leads to is the requirement that address
> allocation have a well defined interface.  We need to define it now, and
> use it to shield ourselves from the coming wave of new technology
> that might tempt us into implementing new functionality that gives us
> greater freedom (why does that sound so good? :-).
> 
> One scheme involves not binding data to addresses permanently, but rather
> allocating addresses on a "as needed" basis.  Venues persist, the stuff in
> them persist, but the paths for data between peers are created when there
> are peers and destroyed when peers are not present.
> 
> Then a virtual network layer (we don't care how it does it, just that it
> does it well) provides connectivity among peers.  This leads to some very
> interesting possibilities for network solutions to things like bridging,
> asymmetric network paths, multicast issues, etc.
> 
> --Ivan
> 
> 
> On Thu, 21 Mar 2002, Robert Olson wrote:
> 
> > At 08:31 PM 3/21/2002 -0800, Jay Beavers wrote:
> > >An example would be the deployment of AG nodes for virtual classrooms 
> > >throughout a major state university system.  This could add up to hundreds 
> > >of venues in use simultaneously fairly easily.
> > 
> > Each school with an AS number has 256 GLOP addresses at its disposal; that 
> > alone will probably suit their needs for some time, if carefully allocated.
> > 
> > Tho we gotta wonder what's up with 225/4 thru 231/4 and 234/4 thru 238/4... 
> > marked "reserved" in rfc 3171.No lack of addresses in there.. :-)
> > 
> > --bob