Re: successful termination? Or interest in resumption of the work?

[Geoff Huston <[e-mail]>]

On 03/04/2009, at 7:37 AM, Jari Arkko wrote:

> Folks,
>
> As you may have noticed, all three base Shim6 documents have now  
> been approved after extensive edits from IESG reviews. This is  
> obviously a very happy outcome even if it took a long time. Thank  
> you everyone who was involved in making this happen!
>
> Last week I when I met the chairs and lead authors I asked what they  
> believe should happen next. A lively discussion followed about the  
> status of the technology, the WG, and its few remaining WG  
> documents. But our main conclusion was that the working group  
> participants should tell us what they have in mind.
>
> Here's a couple of different alternatives:
>
> 1. Declare success and close the WG. The most important work now is  
> implementation, testing, and deployments. The WG is not needed at  
> this moment, and if it will later be needed, it is easy to create a  
> maintenance WG. Or if a new effort for some bigger new piece of  
> functionality is needed, the proper way to do that is through a BOF  
> anyway. Question: how many implementations exist? Which ones are  
> worked on actively? Is there any deployment or trial experience to  
> report?
>
> 2. Put the WG into sleep for a year or two, and return when there's  
> additional experience.
>
> 3. Work on the most important one(s) of the remaining WG documents  
> (locator-pair-selection, api, applicability). Which one? Is there  
> energy to do the work, including WG participants doing reviews,  
> commenting on issues, etc?
>
> 4. Do something else that is important for Shim6. What?
>
> We would like to move forward with this in a couple of weeks. The WG  
> will either be closed or rechartered. Let us know if you are  
> interested and if so, what you believe should be done.
>
>


 From my notes of that meeting with the AD I have:

There were the following drafts that are still WG documents at this  
stage:

- the outstanding applicability draft (draft-ietf-shim6- 
applicability-03.txt)

- the locator pair selection draft (draft-ietf-shim6-locator-pair- 
selection-04.txt)

- the API draft (draft-ietf-shim6-multihome-shim-api-07.txt)

There may be work on Illitsch's proposal to perform a faster algorithm  
in the failure detection / reachability area (he had a draft on this I  
recall)

There were areas about ULP / SHIM signalling to allow greater levels  
of control in an instance of a ULP and greater levels of feedback from  
the SHIM layer.

There appears to be interest in multipath TCP, andf the possible  
coupling of multipath TCP to Shim6

There was interest in proxy shim6 and a draft on the topic (draft- 
nordmark-shim6-esd-01.txt)

I must point out that the past two years has been spent largely  
waiting for the documents to clear the IESG, and the lack of work in  
this WG in the interim was due to a decision to await these core  
documents to be cleared through the IESG before picking up more work.

So if there is interst in picking up this work now, it would be good  
to hear from intersted individuals in response to Jari's call.


thanks,

   Geoff