Welcome to the page of fearless IPv6 multihoming solutions developers
"mulsixhomers"
ipv6mh
Last modified:
The ipv6mh list has concluded. The list will remain active
for the time being but no new subscriptions are accepted. An offspring of this
list is
http://arneill-py.sacramento.ca.us/mhap/ (pardon the dust); ipv6mh members
are not automatically signed up for the MHAP list.
Charter:
- Develop IPv6 multihoming solutions that can be deployed in a reasonable
amount of time (before aggregation is broken). No IPv6 multihoming, no IPv6.
-
Solution spaces: solutions will not be restricted to site
multihoming. Host solutions, mobile solutions and others will be
considered.
- Develop a common framework that will integrate and bind all solutions together.
- Avoid solutions that break the aggregation or push people to become pTLAs/LIRs
for the sole purpose of having their prefix advertised in the Global Routing
Table.
- It is not out of scope to discuss long-term solutions that require major undertakings (such as replacing BGP), but the focus should be on extracting out of these solutions the ideas that could be re-used for solutions that have a shorter time-to-market.
Rules:
- Anybody can subscribe or unsubscribe by sending email to the webmaster.
Subscribe.
Subscription is subject to the webmaster and the list's approval, and is cancelable at any time without a reason.
- Post to the list with (ipv6mh) at the beginning of the subject line.
- Working documents might not have a boilerplate. This list or authors might allow
their
work to be implemented as a vendor proprietary solution.
- Political correctness is optional. "Complete crap" is a valid assessment of a
solution or idea.
- It is ok to qualify something as crap. It is not ok not to give a rationale for it.
- No idea is too stupid to be discussed.
- There are no specific requirements
for the quality of solutions. Requirement documents are to be used as a baseline
only, and some of the requirements may be ignored for some solution spaces. The
idea is to find out what we can actually deliver, not what we wish we could
deliver. A bad solution is better than no solution at all.
-This list is not affiliated to the IETF.
Chairs:
Michel Py
Iljitsch van Beijnum
To-do list:
| What |
Start |
End |
Status |
| - Write charter and rules. |
February 2002 |
July 2002 |
Complete |
| - Grow membership. |
February 2002 |
|
In progress |
|
-
Agenda for February-March, 2003 |
February 2003 |
|
In progress |
| - Begin to write common framework. |
February 2003 |
|
In progress |
| - Lobby vendors. |
|
|
Not started |
Links:
|
M |
Author / Editor is member of the List |
|
W |
Working document for the List. |
Framework:
Geographical data:
These files are .dbf. The data source is the United Nations statistics
division's "Capital cities and cities of 100,000 and more inhabitants"
(no longer available on the UN's web site). The
tables format is documented in "Data tables structure").
Router solutions:
Host solutions:
Presentations:
Drafts from the dark side:
Long term solutions:
The mulsixhomer's reading list:
Misc. and expired drafts:
Sites of interest:
6bone
Cisco's IPv6 page
Tom Lohdan's IPv6 Info/Links
BGPexpert.com
Bob Moskowitz' HIP page
Email:
