Re: PI space under IPv6

by the details i meant silly stuff such as how the protocols
actually work to support this.

Isn't that the point of the discussion. I thought it starts with definitions:
- what should bear a name
- what should have an adress
- what is the address hierarchy or does it need a hierarchy
- what are communication requirements
Answering the above gives guidelines for protocols?

Building protocols bottom up may be practical. But than what is the top goal?

Thanks,

Peter


--- Randy Bush <[email protected]> wrote:

> >> great idea.  would you mind fleshing out the details a bit?
> > 
> > I did on ram and as it is evolving here is more:
> > NAMES
> > - A large standard name space in a format similar to IPv6. Current proxies: MAC,
> > EUI-64, RFID, UPC
> > - Names identify functional entities, e.g. a chip or an application
> > - IANA governs name format and distribution
> > - End users manage name meanings within the standard format
> > - Names are distributed to end user via their tax agencies
> > 
> > ADDRESSES
> > - LAN Routing = current including PI
> > - WAN Routing = global hierarchical network with Access Points every 10sq miles
> > - End users connect to AP via wire, fiber, or wireless
> > - Various ISPs support different parts of the hierarchy
> > - ISPs charge end users for the total traffic from a given name
> > - IANA governs address distribution
> > - Addresses are distributed via IR to ISP
> 
> by the details i meant silly stuff such as how the protocols
> actually work to support this.
> 
> randy
> 
> 



 
____________________________________________________________________________________
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives.
http://tools.search.yahoo.com/toolbar/features/mail/
_______________________________________________
global-v6 mailing list
[email protected]
http://mailman.apnic.net/mailman/listinfo/global-v6