[ppml] "Recommended Practices" procedure

Hi Michel-

If work on 8+8 truly stopped completely and nobody is looking at it at all, then I'm curious why it still comes up in conversation as one of the possible fixes (given improvement).  However, that said, I do hear Shim 6 mentioned much more and how this one might be the best chance at creating a solution.  I don't believe that Shim 6 has been disbanded yet.   

I believe working on improving shim 6 or resurrecting others and improving them would be done because "some of us care" (I'm sure I can hear some laughter out there, but I care).  I know its tiresome to keep discussing and work on, however I believe supporting both sides of the coin.  One being we want to multihome and two being we need to keep the routing tables healthy. 

I'm an optimist

-----Original Message-----
From: Michel Py [mailto:michel at]
Sent: Thursday, April 27, 2006 3:14 PM
To: Azinger, Marla
Cc: ppml at
Subject: RE: [ppml] "Recommended Practices" procedure

> Marla Azinger wrote:
> This is yet another reason why I am pushing for a document that
> supports more specifics to be routed so that we may use the
> technology that exists.  Hopefully this would only be a short
> term solution.  I would hope this would motivate the Shim 6 or
> 8+8 groups to work faster towards a solution for multihoming.

As far as I know work on GSE (descendant of 8+8) has stopped in 1997. I
stopped working on MHAP (unrelated but somehow similar) in 2003. Unless
you have specific information that I am unaware of, as of today I don't
see why anybody would resurrect either.

> Jason Schiller wrote:
> I think IPv6 needs an architectural approach to solving PI and and
> multi-homing. If we could completely seperate locator and ID with
> something like 8+8/GSE, have DNS only reflect the ID, and have the
> network map one or more routing goops to a site (Yes I know this
> needs some protocol), and use only the low order bits for TCP
> session termination and firewall filters.  Then we have solved both
> the provider independant and multi-homing problem.

The IETF has decided that shim6 was the way to go. Unless you suggest
that ARIN (or someone else) gets in the business of designing protocols,
I'm interested in knowing where you think you can find such an animal.