Consider: RIRs refuse to grant ASNs to dual-homed leaves. Transit providers _must_ cooperate with each other. Hopefully they coalesce joint ASNs and space responsibly before sending such merrily along to the global table. Voici, non-portable ASNs and "minimum height to ride" requirements for a portable, personal ASN. This really isn't much more restrictive than today's policies, and changing an ASN is easy for small leaves. The biggest pitfall I see: Imagine having to renumber when _any_ upstream changes. I propose that this is reasonable for > /24, where such is the status quo. For <= /24 non-PI space, one could use non-coop space from a specific upstream -- again, the status quo. On a related note: Someone pointed out off-list that the "coop ASN" approach requires creating a new ASN when one changes providers. Yes, but this still uses no more ASNs (unused ones are returned, right?) than if each leaf registered its own portable ASN. Eddy -- Everquick Internet - http://www.everquick.net/ A division of Brotsman & Dreger, Inc. - http://www.brotsman.com/ Bandwidth, consulting, e-commerce, hosting, and network building Phone: +1 785 865 5885 Lawrence and [inter]national Phone: +1 316 794 8922 Wichita ________________________________________________________________________ DO NOT send mail to the following addresses: davidc@brics.com -*- jfconmaapaq@intc.net -*- sam@everquick.net Sending mail to spambait addresses is a great way to get blocked. Ditto for broken OOO autoresponders and foolish AV software backscatter.