
From shim6-bounces@ietf.org  Mon Jun  1 08:11:41 2009
Return-Path: <shim6-bounces@ietf.org>
X-Original-To: shim6-archive-oY2iet1p@lists.ietf.org
Delivered-To: ietfarch-shim6-archive-oY2iet1p@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E34863A6DB6; Mon,  1 Jun 2009 08:11:41 -0700 (PDT)
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4BC3C3A6D05 for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 08:11:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WKIqATem-9IX for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 08:11:38 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [83.149.65.1]) by core3.amsl.com (Postfix) with ESMTP id 788B43A6DB6 for <shim6@ietf.org>; Mon,  1 Jun 2009 08:11:38 -0700 (PDT)
Received: from claw.it.uc3m.es (claw.it.uc3m.es [163.117.139.52]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n51FArgP027801 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <shim6@ietf.org>; Mon, 1 Jun 2009 17:10:54 +0200 (CEST) (envelope-from iljitsch@muada.com)
Message-Id: <594719CF-ABAC-44D8-9EDA-98D330670BBA@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: shim6@ietf.org
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 1 Jun 2009 17:11:12 +0200
X-Mailer: Apple Mail (2.935.3)
Subject: [shim6] shim6 over 6to4
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: shim6-bounces@ietf.org
Errors-To: shim6-bounces@ietf.org

Erik and I had a short discussion in San Francisco on using shim6 with  
an IPv6 identifier and IPv4 locators. A good way to do this would be  
by running shim6 over 6to4, as the HBA protects the 6to4 addresses  
like normal and the 6to4 address maps directly to an IPv4 address.

I don't remember the details, but I came up with a rather convoluted  
way to do this and then when I started to write it down all of the  
complexity didn't seem necessary: simply run shim6 over 6to4. The main  
issue getting the packets with the right 6to4 addresses to the right  
routers with the right IPv4 addresses (assuming the host doesn't have  
two IPv4 addresses). Other than that, maybe some RFC 3484 preference  
magic could be useful.

Would it make sense to write down how this should work as an  
informational document?
_______________________________________________
shim6 mailing list
shim6@ietf.org
https://www.ietf.org/mailman/listinfo/shim6

From iljitsch@muada.com  Mon Jun  1 08:11:41 2009
Return-Path: <iljitsch@muada.com>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4BC3C3A6D05 for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 08:11:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WKIqATem-9IX for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 08:11:38 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [83.149.65.1]) by core3.amsl.com (Postfix) with ESMTP id 788B43A6DB6 for <shim6@ietf.org>; Mon,  1 Jun 2009 08:11:38 -0700 (PDT)
Received: from claw.it.uc3m.es (claw.it.uc3m.es [163.117.139.52]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n51FArgP027801 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <shim6@ietf.org>; Mon, 1 Jun 2009 17:10:54 +0200 (CEST) (envelope-from iljitsch@muada.com)
Message-Id: <594719CF-ABAC-44D8-9EDA-98D330670BBA@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: shim6@ietf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 1 Jun 2009 17:11:12 +0200
X-Mailer: Apple Mail (2.935.3)
Subject: [shim6] shim6 over 6to4
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jun 2009 15:11:41 -0000

Erik and I had a short discussion in San Francisco on using shim6 with  
an IPv6 identifier and IPv4 locators. A good way to do this would be  
by running shim6 over 6to4, as the HBA protects the 6to4 addresses  
like normal and the 6to4 address maps directly to an IPv4 address.

I don't remember the details, but I came up with a rather convoluted  
way to do this and then when I started to write it down all of the  
complexity didn't seem necessary: simply run shim6 over 6to4. The main  
issue getting the packets with the right 6to4 addresses to the right  
routers with the right IPv4 addresses (assuming the host doesn't have  
two IPv4 addresses). Other than that, maybe some RFC 3484 preference  
magic could be useful.

Would it make sense to write down how this should work as an  
informational document?

From shim6-bounces@ietf.org  Mon Jun  1 08:24:34 2009
Return-Path: <shim6-bounces@ietf.org>
X-Original-To: shim6-archive-oY2iet1p@lists.ietf.org
Delivered-To: ietfarch-shim6-archive-oY2iet1p@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB1783A717D; Mon,  1 Jun 2009 08:24:34 -0700 (PDT)
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E6E3D3A7177 for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 08:24:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HuuZjPEIGVkj for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 08:24:33 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [83.149.65.1]) by core3.amsl.com (Postfix) with ESMTP id 2F2983A717D for <shim6@ietf.org>; Mon,  1 Jun 2009 08:24:32 -0700 (PDT)
Received: from claw.it.uc3m.es (claw.it.uc3m.es [163.117.139.52]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n51FNNbI027990 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <shim6@ietf.org>; Mon, 1 Jun 2009 17:23:47 +0200 (CEST) (envelope-from iljitsch@muada.com)
Message-Id: <343A4938-4791-44C8-AC59-214B079EBF1F@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: shim6@ietf.org
In-Reply-To: <49D9E7EE.6080506@piuha.net>
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 1 Jun 2009 17:24:11 +0200
References: <49D52210.1050008@piuha.net> <49D6653D.7080909@uclouvain.be> <49D66E42.6060607@piuha.net> <49D81049.1000407@gmail.com> <49D9E7EE.6080506@piuha.net>
X-Mailer: Apple Mail (2.935.3)
Subject: Re: [shim6] successful termination?
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: shim6-bounces@ietf.org
Errors-To: shim6-bounces@ietf.org

On 6 apr 2009, at 13:30, Jari Arkko wrote:

> You've sent a lot of good input. How do the people who have not said  
> anything yet feel? Please speak up!

Sorry for the delay.

I think it would be useful for the wg to hang around for a bit, it  
seems there is implementation activity and also IETF work that at  
least overlaps with shim6 somewhat, so having a mailinglist and the  
ability to easily have a slot during IETF meetings if the need arises  
could be helpful. If in another year or so nothing useful happens we  
can always call it quits then.

Other than that, we really need to fix the ingress filtering issue,  
either in this working group or elsewhere.

And see my next message.
_______________________________________________
shim6 mailing list
shim6@ietf.org
https://www.ietf.org/mailman/listinfo/shim6

From iljitsch@muada.com  Mon Jun  1 08:24:33 2009
Return-Path: <iljitsch@muada.com>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E6E3D3A7177 for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 08:24:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HuuZjPEIGVkj for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 08:24:33 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [83.149.65.1]) by core3.amsl.com (Postfix) with ESMTP id 2F2983A717D for <shim6@ietf.org>; Mon,  1 Jun 2009 08:24:32 -0700 (PDT)
Received: from claw.it.uc3m.es (claw.it.uc3m.es [163.117.139.52]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n51FNNbI027990 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <shim6@ietf.org>; Mon, 1 Jun 2009 17:23:47 +0200 (CEST) (envelope-from iljitsch@muada.com)
Message-Id: <343A4938-4791-44C8-AC59-214B079EBF1F@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: shim6@ietf.org
In-Reply-To: <49D9E7EE.6080506@piuha.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 1 Jun 2009 17:24:11 +0200
References: <49D52210.1050008@piuha.net> <49D6653D.7080909@uclouvain.be> <49D66E42.6060607@piuha.net> <49D81049.1000407@gmail.com> <49D9E7EE.6080506@piuha.net>
X-Mailer: Apple Mail (2.935.3)
Subject: Re: [shim6] successful termination?
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jun 2009 15:24:34 -0000

On 6 apr 2009, at 13:30, Jari Arkko wrote:

> You've sent a lot of good input. How do the people who have not said  
> anything yet feel? Please speak up!

Sorry for the delay.

I think it would be useful for the wg to hang around for a bit, it  
seems there is implementation activity and also IETF work that at  
least overlaps with shim6 somewhat, so having a mailinglist and the  
ability to easily have a slot during IETF meetings if the need arises  
could be helpful. If in another year or so nothing useful happens we  
can always call it quits then.

Other than that, we really need to fix the ingress filtering issue,  
either in this working group or elsewhere.

And see my next message.

From iljitsch@muada.com  Mon Jun  1 08:42:08 2009
Return-Path: <iljitsch@muada.com>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C0D83A6B34 for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 08:42:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xNjNlz8UkExG for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 08:42:07 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [83.149.65.1]) by core3.amsl.com (Postfix) with ESMTP id 331EF3A6A4F for <shim6@ietf.org>; Mon,  1 Jun 2009 08:42:07 -0700 (PDT)
Received: from claw.it.uc3m.es (claw.it.uc3m.es [163.117.139.52]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n51FNNbH027990 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 1 Jun 2009 17:23:24 +0200 (CEST) (envelope-from iljitsch@muada.com)
Message-Id: <92AE9AB7-6BD7-4BD0-AA03-B3354A4F7BF3@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Geoff Huston <gih@apnic.net>
In-Reply-To: <6B008DB7-D5CE-4AC9-A6DA-264BAF3B6B06@apnic.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 1 Jun 2009 17:23:43 +0200
References: <49D52210.1050008@piuha.net> <6B008DB7-D5CE-4AC9-A6DA-264BAF3B6B06@apnic.net>
X-Mailer: Apple Mail (2.935.3)
Cc: shim6@ietf.org
Subject: Re: [shim6] successful termination? Or interest in resumption of the work?
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jun 2009 15:42:08 -0000

On 2 apr 2009, at 23:37, Geoff Huston wrote:

> 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)

Really? I don't remember that... Must have been a long time ago. If  
anyone has a pointer, please let me know.

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

Right. We've applied for a multipath TCP BOF in Stockholm. https://www.ietf.org/mailman/listinfo/multipathtcp

There are now two drafts under discussion, one that does its own  
address management, and another written by me (co-developed with  
Marcelo) where the multipath changes are only made on the sender. As  
Marcelo explained some time ago, another way to go (which would be a  
natural extension of the one-ended approach) would be to make TCP  
multipath-capable and let shim6 (I guess I should say "Shim6" now)  
handle the addressing.

From shim6-bounces@ietf.org  Mon Jun  1 08:42:09 2009
Return-Path: <shim6-bounces@ietf.org>
X-Original-To: shim6-archive-oY2iet1p@lists.ietf.org
Delivered-To: ietfarch-shim6-archive-oY2iet1p@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 283F73A7143; Mon,  1 Jun 2009 08:42:09 -0700 (PDT)
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C0D83A6B34 for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 08:42:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xNjNlz8UkExG for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 08:42:07 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [83.149.65.1]) by core3.amsl.com (Postfix) with ESMTP id 331EF3A6A4F for <shim6@ietf.org>; Mon,  1 Jun 2009 08:42:07 -0700 (PDT)
Received: from claw.it.uc3m.es (claw.it.uc3m.es [163.117.139.52]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n51FNNbH027990 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 1 Jun 2009 17:23:24 +0200 (CEST) (envelope-from iljitsch@muada.com)
Message-Id: <92AE9AB7-6BD7-4BD0-AA03-B3354A4F7BF3@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Geoff Huston <gih@apnic.net>
In-Reply-To: <6B008DB7-D5CE-4AC9-A6DA-264BAF3B6B06@apnic.net>
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 1 Jun 2009 17:23:43 +0200
References: <49D52210.1050008@piuha.net> <6B008DB7-D5CE-4AC9-A6DA-264BAF3B6B06@apnic.net>
X-Mailer: Apple Mail (2.935.3)
Cc: shim6@ietf.org
Subject: Re: [shim6] successful termination? Or interest in resumption of the work?
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: shim6-bounces@ietf.org
Errors-To: shim6-bounces@ietf.org

On 2 apr 2009, at 23:37, Geoff Huston wrote:

> 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)

Really? I don't remember that... Must have been a long time ago. If  
anyone has a pointer, please let me know.

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

Right. We've applied for a multipath TCP BOF in Stockholm. https://www.ietf.org/mailman/listinfo/multipathtcp

There are now two drafts under discussion, one that does its own  
address management, and another written by me (co-developed with  
Marcelo) where the multipath changes are only made on the sender. As  
Marcelo explained some time ago, another way to go (which would be a  
natural extension of the one-ended approach) would be to make TCP  
multipath-capable and let shim6 (I guess I should say "Shim6" now)  
handle the addressing.
_______________________________________________
shim6 mailing list
shim6@ietf.org
https://www.ietf.org/mailman/listinfo/shim6

From brian.e.carpenter@gmail.com  Mon Jun  1 08:47:09 2009
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F2E8B3A6F33 for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 08:47:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4vwcSX73QLzL for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 08:47:08 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.238]) by core3.amsl.com (Postfix) with ESMTP id 25D653A6A4F for <shim6@ietf.org>; Mon,  1 Jun 2009 08:47:05 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id g37so2026636rvb.49 for <shim6@ietf.org>; Mon, 01 Jun 2009 08:47:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=XcfGkgJJOP5VvnzvFvkl3gpEpr7qjIiVYJFdbO2LL+w=; b=agEZen3OBJVbErruogUxrRHMakaOow5LMHUaXiuu2lOyX1g4Lpwc4sc2x4E75QcKEp R2e3AlLoSjPvMGU0OuROMeRDkgTrPMo+XkFhaz5W+SkrRoZT391WRbVGDDYhnCIsb7i1 UtxC2g05XhpxmVdlYFjHz2vzP27uioghXbD5E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=K3NfhA85+PEDh8L1ZmTEl/X2wNC2FJR8A2egHp4qXTLU7Zu4mLWeDA7n2tv2X06HJ5 eNr03tUzKTY6A6doeakArzLeVKyRvWt6jtUPg+kdtAbKhF/tqd9XmdBh8nduLwdLU2Vc ssW5xGcxq3D0Nu6EWbxux99gNDZYPHxzB3578=
Received: by 10.140.202.12 with SMTP id z12mr7014767rvf.183.1243871222351; Mon, 01 Jun 2009 08:47:02 -0700 (PDT)
Received: from ?192.168.1.65? (host81-157-94-1.range81-157.btcentralplus.com [81.157.94.1]) by mx.google.com with ESMTPS id f21sm15859386rvb.55.2009.06.01.08.47.00 (version=SSLv3 cipher=RC4-MD5); Mon, 01 Jun 2009 08:47:01 -0700 (PDT)
Message-ID: <4A23F7E7.3040903@gmail.com>
Date: Mon, 01 Jun 2009 16:46:47 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <594719CF-ABAC-44D8-9EDA-98D330670BBA@muada.com>
In-Reply-To: <594719CF-ABAC-44D8-9EDA-98D330670BBA@muada.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: shim6@ietf.org
Subject: Re: [shim6] shim6 over 6to4
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jun 2009 15:47:09 -0000

On 2009-06-01 16:11, Iljitsch van Beijnum wrote:
> Erik and I had a short discussion in San Francisco on using shim6 with
> an IPv6 identifier and IPv4 locators. A good way to do this would be by
> running shim6 over 6to4, as the HBA protects the 6to4 addresses like
> normal and the 6to4 address maps directly to an IPv4 address.

Can you state the goal of this? It only makes sense if there are at least
two IPv4 addresses for the destination site, right? Is that a common enough
case to matter? Most IPv4 multihoming is pure PI, surely?

> 
> I don't remember the details, but I came up with a rather convoluted way
> to do this and then when I started to write it down all of the
> complexity didn't seem necessary: simply run shim6 over 6to4. The main
> issue getting the packets with the right 6to4 addresses to the right
> routers with the right IPv4 addresses (assuming the host doesn't have
> two IPv4 addresses). 

Do you mean the site egress 6to4 routers at the source? There shouldn't be any
issue for the site ingress at the far end. IPv4 routing will do that.

> Other than that, maybe some RFC 3484 preference
> magic could be useful.

What about mixed scenarios, where there's a pure IPv6 path and 6to4 path
to choose between?

> 
> Would it make sense to write down how this should work as an
> informational document?

Maybe. But please clarify the goal first and maybe describe the scenario(s)
in more detail.

   Brian

From shim6-bounces@ietf.org  Mon Jun  1 08:47:10 2009
Return-Path: <shim6-bounces@ietf.org>
X-Original-To: shim6-archive-oY2iet1p@lists.ietf.org
Delivered-To: ietfarch-shim6-archive-oY2iet1p@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D4633A7159; Mon,  1 Jun 2009 08:47:10 -0700 (PDT)
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F2E8B3A6F33 for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 08:47:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4vwcSX73QLzL for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 08:47:08 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.238]) by core3.amsl.com (Postfix) with ESMTP id 25D653A6A4F for <shim6@ietf.org>; Mon,  1 Jun 2009 08:47:05 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id g37so2026636rvb.49 for <shim6@ietf.org>; Mon, 01 Jun 2009 08:47:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=XcfGkgJJOP5VvnzvFvkl3gpEpr7qjIiVYJFdbO2LL+w=; b=agEZen3OBJVbErruogUxrRHMakaOow5LMHUaXiuu2lOyX1g4Lpwc4sc2x4E75QcKEp R2e3AlLoSjPvMGU0OuROMeRDkgTrPMo+XkFhaz5W+SkrRoZT391WRbVGDDYhnCIsb7i1 UtxC2g05XhpxmVdlYFjHz2vzP27uioghXbD5E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=K3NfhA85+PEDh8L1ZmTEl/X2wNC2FJR8A2egHp4qXTLU7Zu4mLWeDA7n2tv2X06HJ5 eNr03tUzKTY6A6doeakArzLeVKyRvWt6jtUPg+kdtAbKhF/tqd9XmdBh8nduLwdLU2Vc ssW5xGcxq3D0Nu6EWbxux99gNDZYPHxzB3578=
Received: by 10.140.202.12 with SMTP id z12mr7014767rvf.183.1243871222351; Mon, 01 Jun 2009 08:47:02 -0700 (PDT)
Received: from ?192.168.1.65? (host81-157-94-1.range81-157.btcentralplus.com [81.157.94.1]) by mx.google.com with ESMTPS id f21sm15859386rvb.55.2009.06.01.08.47.00 (version=SSLv3 cipher=RC4-MD5); Mon, 01 Jun 2009 08:47:01 -0700 (PDT)
Message-ID: <4A23F7E7.3040903@gmail.com>
Date: Mon, 01 Jun 2009 16:46:47 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Iljitsch van Beijnum <iljitsch@muada.com>
References: <594719CF-ABAC-44D8-9EDA-98D330670BBA@muada.com>
In-Reply-To: <594719CF-ABAC-44D8-9EDA-98D330670BBA@muada.com>
Cc: shim6@ietf.org
Subject: Re: [shim6] shim6 over 6to4
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: shim6-bounces@ietf.org
Errors-To: shim6-bounces@ietf.org

On 2009-06-01 16:11, Iljitsch van Beijnum wrote:
> Erik and I had a short discussion in San Francisco on using shim6 with
> an IPv6 identifier and IPv4 locators. A good way to do this would be by
> running shim6 over 6to4, as the HBA protects the 6to4 addresses like
> normal and the 6to4 address maps directly to an IPv4 address.

Can you state the goal of this? It only makes sense if there are at least
two IPv4 addresses for the destination site, right? Is that a common enough
case to matter? Most IPv4 multihoming is pure PI, surely?

> 
> I don't remember the details, but I came up with a rather convoluted way
> to do this and then when I started to write it down all of the
> complexity didn't seem necessary: simply run shim6 over 6to4. The main
> issue getting the packets with the right 6to4 addresses to the right
> routers with the right IPv4 addresses (assuming the host doesn't have
> two IPv4 addresses). 

Do you mean the site egress 6to4 routers at the source? There shouldn't be any
issue for the site ingress at the far end. IPv4 routing will do that.

> Other than that, maybe some RFC 3484 preference
> magic could be useful.

What about mixed scenarios, where there's a pure IPv6 path and 6to4 path
to choose between?

> 
> Would it make sense to write down how this should work as an
> informational document?

Maybe. But please clarify the goal first and maybe describe the scenario(s)
in more detail.

   Brian
_______________________________________________
shim6 mailing list
shim6@ietf.org
https://www.ietf.org/mailman/listinfo/shim6

From shim6-bounces@ietf.org  Mon Jun  1 09:02:50 2009
Return-Path: <shim6-bounces@ietf.org>
X-Original-To: shim6-archive-oy2iet1p@lists.ietf.org
Delivered-To: ietfarch-shim6-archive-oY2iet1p@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7BB7C28C25E for <shim6-archive-oy2iet1p@lists.ietf.org>; Mon,  1 Jun 2009 09:02:50 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: You have been unsubscribed from the shim6 mailing list
From: shim6-bounces@ietf.org
To: shim6-archive-oy2iet1p@lists.ietf.org
Message-ID: <mailman.0.1243872169.14495.shim6@ietf.org>
Date: Mon, 01 Jun 2009 09:02:49 -0700
Precedence: bulk
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
X-List-Administrivia: yes
Sender: shim6-bounces@ietf.org
Errors-To: shim6-bounces@ietf.org


From iljitsch@muada.com  Mon Jun  1 09:06:38 2009
Return-Path: <iljitsch@muada.com>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 538F43A6A3C for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 09:06:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iLEQTAgrudEA for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 09:06:37 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [83.149.65.1]) by core3.amsl.com (Postfix) with ESMTP id 610A93A6893 for <shim6@ietf.org>; Mon,  1 Jun 2009 09:06:37 -0700 (PDT)
Received: from claw.it.uc3m.es (claw.it.uc3m.es [163.117.139.52]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n51G5vrU028310 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 1 Jun 2009 18:05:58 +0200 (CEST) (envelope-from iljitsch@muada.com)
Message-Id: <B1C8A31F-2232-4DC5-A938-822E5BD924A7@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <4A23F7E7.3040903@gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 1 Jun 2009 18:06:16 +0200
References: <594719CF-ABAC-44D8-9EDA-98D330670BBA@muada.com> <4A23F7E7.3040903@gmail.com>
X-Mailer: Apple Mail (2.935.3)
Cc: shim6@ietf.org
Subject: Re: [shim6] shim6 over 6to4
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jun 2009 16:06:38 -0000

On 1 jun 2009, at 17:46, Brian E Carpenter wrote:

> Can you state the goal of this? It only makes sense if there are at  
> least
> two IPv4 addresses for the destination site, right? Is that a common  
> enough
> case to matter? Most IPv4 multihoming is pure PI, surely?

Basically, any and all shim6 cases where there is no regular IPv6  
available.

In particular, the "basement multihoming" case would make sense here,  
where a user has two broadband connections that each provide an IPv4  
address and connectivity.

The interesting aspact of 6to4 is that it could be used by hosts that  
want multihoming, but not necessarily care about IPv6. If both sides  
do 6to4 the only penalty is some header overhead. But in the case  
where a host uses 6to4 and the other side native connectivity, there  
could be reduced performance.

From gih@apnic.net  Mon Jun  1 13:41:10 2009
Return-Path: <gih@apnic.net>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 91CFC3A688C for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 13:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8PZcLI-KolXl for <shim6@core3.amsl.com>; Mon,  1 Jun 2009 13:41:09 -0700 (PDT)
Received: from asmtp.apnic.net (oregano.apnic.net [IPv6:2001:dc0:2001:a:4608::60]) by core3.amsl.com (Postfix) with ESMTP id 8957A3A6A39 for <shim6@ietf.org>; Mon,  1 Jun 2009 13:41:09 -0700 (PDT)
Received: from [IPv6:2001:dc0:2001:10:217:f2ff:fec9:1b10] (unknown [IPv6:2001:dc0:2001:10:217:f2ff:fec9:1b10]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id A2116110066; Tue,  2 Jun 2009 06:41:03 +1000 (EST)
Message-Id: <B4D7BA1F-4507-4142-AD34-FD102E314981@apnic.net>
From: Geoff Huston <gih@apnic.net>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <594719CF-ABAC-44D8-9EDA-98D330670BBA@muada.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Tue, 2 Jun 2009 06:41:02 +1000
References: <594719CF-ABAC-44D8-9EDA-98D330670BBA@muada.com>
X-Mailer: Apple Mail (2.935.3)
Cc: shim6@ietf.org
Subject: Re: [shim6] shim6 over 6to4
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jun 2009 20:41:10 -0000

On 02/06/2009, at 1:11 AM, Iljitsch van Beijnum wrote:

> Erik and I had a short discussion in San Francisco on using shim6  
> with an IPv6 identifier and IPv4 locators. A good way to do this  
> would be by running shim6 over 6to4, as the HBA protects the 6to4  
> addresses like normal and the 6to4 address maps directly to an IPv4  
> address.
>
> I don't remember the details, but I came up with a rather convoluted  
> way to do this and then when I started to write it down all of the  
> complexity didn't seem necessary: simply run shim6 over 6to4. The  
> main issue getting the packets with the right 6to4 addresses to the  
> right routers with the right IPv4 addresses (assuming the host  
> doesn't have two IPv4 addresses). Other than that, maybe some RFC  
> 3484 preference magic could be useful.
>
> Would it make sense to write down how this should work as an  
> informational document?


yes, that makes sense to me - tyhe write up may well resolve some of  
the questions I have in reading this brief description


  Geoff



From shinta@sfc.wide.ad.jp  Tue Jun  2 19:35:04 2009
Return-Path: <shinta@sfc.wide.ad.jp>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 50D5A3A6768 for <shim6@core3.amsl.com>; Tue,  2 Jun 2009 19:35:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.904
X-Spam-Level: 
X-Spam-Status: No, score=0.904 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zO7m42OHVv2Y for <shim6@core3.amsl.com>; Tue,  2 Jun 2009 19:35:03 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (mail.sfc.wide.ad.jp [203.178.142.146]) by core3.amsl.com (Postfix) with ESMTP id E3A023A6BDE for <shim6@ietf.org>; Tue,  2 Jun 2009 19:34:54 -0700 (PDT)
Received: from localhost.localdomain (unknown [IPv6:2001:380:633:2:20b:cdff:fefb:2a8]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 45F5A4C0BD; Wed,  3 Jun 2009 11:34:48 +0900 (JST)
Message-ID: <4A25DFAC.6020305@sfc.wide.ad.jp>
Date: Wed, 03 Jun 2009 11:27:56 +0900
From: Shinta Sugimoto <shinta@sfc.wide.ad.jp>
User-Agent: Thunderbird 2.0.0.6 (X11/20070809)
MIME-Version: 1.0
To: Varjonen Samu <samu.varjonen@hiit.fi>
References: <4A1E5122.6000709@hiit.fi>
In-Reply-To: <4A1E5122.6000709@hiit.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: shim6@ietf.org
Subject: Re: [shim6] Comments on the draft-ietf-shim6-multihome-shim-api-08
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2009 02:35:04 -0000

Hello Samu,

Thank you very much for reviewing the multihome shim API draft.
Please find my comments inline:

Varjonen Samu wrote:
> Hi,
> 
> Some comments on the draft-ietf-shim6-multihome-shim-api-08.
> 
> Section 1. Introduction. I would prefer "network layer" instead of 
> "IP-layer" (2 instances in introduction and 1 in fig. 1).

Ok, will change "IP-layer" to "network layer".

> Shim is explained as a sub-layer in network layer and is referred as 
> "shim sub-layer" and "shim layer" through out the document. I would just 
> use one form uniformly through out the document. Sub-layer one would be 
> my choice and it would rule out any ambiguity from the text as some 
> parts talked about shim like it would have been its own layer.

Ok, I will keep it consistent throughout the document.
I agree that "shim sub-layer" would be more suitable term.

> 
> Section 1. Introduction (second paragraph) tells that locator changes 
> should be hidden from upper layer protocols. In general this is true but 
> how about protocols/applications based on location awareness?

We believe that some applications may want to be aware of locators that 
are used to send or receive IP packets, and that's one of the reasons 
why we wrote this API document.

The second paragraph intends to explain the meaning of the shim layer in 
a general sense by addressing the problem of IP address change under the 
multihomed environment.  The IP address which is considered as a 
communication endpoint from the upper layer protocol (i.e., identifier) 
should be kept unaltered during the session lifetime, while the IP 
address used for routing packets (i.e., locators) may be changed.  And 
the sentence you referred are talking about the former, the need for 
having a stable communication endpoint.  I will rephrase the text to 
avoid confusion.

> Section 4. Requirements. To me it looks like the requirements is missing 
> one important case. Application may want to set used addresses 
> (SHIM_LOC_*_RECVs and SHIM_LOC_*_SENDs). The current version looks like 
> applications only need to obtain the information from shim sub-layer.

I don't think I am following you hear.  Could you elaborate more about 
SHIM_LOC_*_RECVs and SHIM_LOC_*_SENDs?  What do you mean by "used 
addresses"?

> Section 5. Socket Options...
> In descriptions on most options that have "o" in get and set just say 
> "request" (get) or "inform" (set) or "specify" (set) while it is 
> possible to get and set the information. I think this should be "Get or 
> set the option" for all "get and settable" in this list. Same goes for 
> the sections 5.*. Some of them start "can be set" and then later in 
> example it is mentioned that it can also be obtained.

Ok.  Let me do sanity check of Section 5, and I will try to keep 
consistency.

> Section 5.4 has double specify in the first sentence.

Noted.

> In sections 7.2 and 7.3 the explanations of reserved fields, in my 
> opinion, should be unified to say "Must be initialized to zero and must 
> be ignored by the receiver"

Ok.

> The document left me puzzled on the situation if I deferrer the ctx 
> setup and start off with plain IP and then upgrade to shim. Does the 
> shim handshake start simultaneously with the plain IP communication or 
> after some timer or can the implementor trigger it (with SHIM_DONTSHIM 
> set to 1 in the middle of the communication?) and can I turn shim off 
> during the communications? To my knowledge shim6 does not have any close 
> procedures, so to me it looks like I would have to abandon the ctx for 
> garbage collection by closing the socket.

In the case of deferred context setup, the way to initiate SHIM6 context
establishment is an implementation specific issue, I think.  I mean,
implementation can choose any strategy about when (or under what 
circumstance) a context establishment shall be initiated.

With regard to the SHIM_DONTSHIM socket option, we have not discussed 
much (among co-authors, I mean) about how the SHIM6 stack should react 
when the SHIM_DONTSHIM was set during the communication (and the session 
is already shimmed).  In my opinion, the SHIM6 stack must immediately 
teardown the context when the application requests to NOT apply SHIM6 
during the communication.  I think you are right that there is no close 
(teardown) negotiation specified in the SHIM6 protocol spec, and I 
wonder how the peer would know the need for tearing down the SHIM6 
context.  Suppose applications APP1 and APP2 are running on hosts H1 and 
H2.  The session was automatically SHIMmed and eventually APP1 requests 
the SHIM layer to not apply SHIM6 for the session.  Then tearing down 
the SHIM6 context can be done on H1, but not on H2.  The consequence is 
that H2 would keep sending SHIMmed packets to the H1.  Unless H1 
preserves the established context, it has no clue to demultiplex the 
SHIMmed packets.  I may be missing something, but I think your question 
is valid.  Let me discuss this issue with co-authors.

Thanks again for your comments.

Regards,
Shinta

> BR,
> Samu Varjonen
> _______________________________________________
> shim6 mailing list
> shim6@ietf.org
> https://www.ietf.org/mailman/listinfo/shim6
> 


From jari.arkko@piuha.net  Wed Jun  3 09:48:29 2009
Return-Path: <jari.arkko@piuha.net>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 43A3628C171 for <shim6@core3.amsl.com>; Wed,  3 Jun 2009 09:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.29
X-Spam-Level: 
X-Spam-Status: No, score=-2.29 tagged_above=-999 required=5 tests=[AWL=0.309,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8zUjGCkFXS1s for <shim6@core3.amsl.com>; Wed,  3 Jun 2009 09:48:28 -0700 (PDT)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 8C3F628C15D for <shim6@ietf.org>; Wed,  3 Jun 2009 09:48:27 -0700 (PDT)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id C6814198712 for <shim6@ietf.org>; Wed,  3 Jun 2009 19:48:27 +0300 (EEST)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 6B033198665 for <shim6@ietf.org>; Wed,  3 Jun 2009 19:48:27 +0300 (EEST)
Message-ID: <4A26A959.7060104@piuha.net>
Date: Wed, 03 Jun 2009 19:48:25 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: shim6@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: [shim6] next steps for the shim6 wg
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Jun 2009 16:48:29 -0000

Hi,

I have finally found time to go through various pieces of input and come 
up with a suggested way forward.

I do think it would be useful to continue. But we need to make a careful 
selection for what the group should be looking at, because I'm not 
convinced that the amount of people and energy available for this is too 
big. And to be quite frank, while I get a lot of suggestions for further 
work, I have also gotten (privately) a fair number of suggestions that 
this would be a good time to close the WG. So I think we need to show 
some concrete and achievable steps in the charter.

My suggested new charter text is below -- please comment & suggest 
alternative content if needed.

The starting point for this proposal was that we have the following 
possible work:

1. implementation, testing, and deployment reports
2. API specification
3. applicability draft
4. firewall implications document
5. shim6 and 6to4 interactions; an informational document
6. network-based address pair selection preferences (i.e., provider control)
7. proxy shim6 specification
8. multipath-tcp and shim6 interactions
9. locator selection in general
10. dealing with ingress filtering issues

I believe the most useful output at this stage would be 1. Item 2 is 
fairly far along, and I have commitments from the authors to complete 
this work.

I think completing 3 would be useful as well, though I suspect it is 
going to take quite a bit of work. For instance, in the last two years 
we got quite a bit of feedback, and we also tweaked the specifications 
on a number of areas. Items 4 and 5 are small, and I think they could be 
tackled under the applicability document. Perhaps that would also 
provide some new energy to completing the applicability document.

Item 6, provider control, is interesting. But is there energy behind 
doing something?

Proxy Shim6, item 7, is a fairly big effort. It might be better dealt 
with in a group or a BOF of its own. I'm not in principle against doing 
this, however. The IETF seems to be taking on all the main approaches 
discussed in the RRG, so why not this too... but the main criteria for 
us to adopt any of these efforts has been the existence of a sufficient 
community interested in doing the work, implementing, and discussing it 
in the WG. Does this exist for Proxy Shim6? Are there implementations? 
AFAICT, there is no big enough community behind this.

The work on multipath TCP related to item 8 deserves its own working 
group, and in my opinion, should be focused on a very specific solution 
on the TCP layer and avoid any avoidable interaction with other 
components. I do believe Shim6 has a lot to give to the multipath TCP 
effort, but suspect the most useful input for that effort happens 
through re-use of concepts and algorithms. I hope the WG participants go 
to the BOF (or eventual WG) and provide input so that multipath TCP gets 
constructed correctly.

Address selection issues (item 9) are more fundamental than just about 
Shim6, and I would rather see them addressed in 6MAN, as a part of the 
current address selection improvement efforts. If that effort has not 
yet taken all Shim6 related requirements, it should. Ingress filtering 
issues (item 10) would be a high priority item, but its not clear to me 
that we have a solution that the community likes.

Given all this, my suggestion would be to do items 1 through 5 and leave 
the rest for later. This is what the charter below contains. I'm 
hesitating a bit on items 6 and 10 though. Thoughts?

Jari

----------------------

Site Multihoming by IPv6 Intermediation (shim6)

Last Modified: 2009-06-03

Additional information is available at tools.ietf.org/wg/shim6

Chair(s):
Kurt Lindqvist <kurtis@kurtis.pp.se>
Geoff Huston <gih@apnic.net>

Internet Area Director(s):
Ralph Droms <rdroms@cisco.com>
Jari Arkko <jari.arkko@piuha.net>

Internet Area Advisor:
Jari Arkko <jari.arkko@piuha.net>

Technical Advisor(s):
Thomas Narten <narten@us.ibm.com>

Mailing Lists:
General Discussion: shim6@psg.com
To Subscribe: shim6-request@psg.com
Archive: http://ops.ietf.org/lists/shim6/

Description of Working Group:

Earlier efforts in this working group completed the Shim6 protocol
specification, documented in RFCs 5533 through 5535. This protocol is
a layer 3 shim for providing locator agility with failover
capabilities for IPv6 nodes. Hosts that employ Shim6 use multiple IPv6
address prefixes and setup state with peer hosts. This state can later
be used to failover to a different set of locators, should the
original locators stop working.

The Shim6 approach has a number of advantages, such as enabling small
sites to be multihomed without requiring a provider independent IPv6
address prefix for the site. But the approach has also been
criticized, e.g., for the operational impacts that the use of multiple
prefixes causes. At this time there is no clear view on how well Shim6
works in practice. Implementation and deployment in select networks is
needed to determine its true characteristics.

The Shim6 working group is chartered to track the implementation and
testing or deployment efforts. The group is also expected to shepherd
to completion a few remaining informational documents that complement
the existing protocol specifications.

The specific work items of the group are:

o  Write an implementation and/or deployment experience report.

o  Specify socket API extensions. This API enables interactions between
   applications and the Shim6 layer for advanced locator management,
   and access to information about failure detection and path
   exploration. It also enables some applications to turn Shim6 off.

o  Complete the work on the applicability draft. This draft explains
   in detail in which types of networks Shim6 is applicable, and
   what its advantages and disadvantages are. The draft will also
   explain how firewalls are impacted by the use of Shim6. Finally,
   the draft will also explain how Shim6 can be used in situations
   where native IPv6 connectivity is not available, such as using
   Shim6 over 6to4.

The group will also work in co-operation with the 6MAN working group
as they continue their efforts in improving IPv6 address selection
mechanisms.

The group shall not work on extensions to the Shim6 protocol itself at
this time. However, new work items can be added through rechartering
as others get completed.

Goals and Milestones:

Sep 2009  Next revision of the API document
Nov 2009  First WG draft on an implementation report
Jan 2010  Submit API document to IESG for publication as Informational RFC
Jan 2010  Next revision of the applicability document
Dec 2010  Submit implementation report to IESG for publication as 
Informational RFC
Dec 2010  Submit applicability document to IESG for publication as 
Informational RFC
Dec 2010  Close or re-charter


From brian.e.carpenter@gmail.com  Thu Jun  4 00:07:46 2009
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1620C28C233 for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:07:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2sRrowM+FT3o for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:07:44 -0700 (PDT)
Received: from mail-px0-f187.google.com (mail-px0-f187.google.com [209.85.216.187]) by core3.amsl.com (Postfix) with ESMTP id B5F653A6904 for <shim6@ietf.org>; Thu,  4 Jun 2009 00:07:44 -0700 (PDT)
Received: by pxi17 with SMTP id 17so503161pxi.29 for <shim6@ietf.org>; Thu, 04 Jun 2009 00:07:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ba84ppYYOOXELo87cLuYiaWkjr0lVyBZzxhqi5loDN4=; b=DdlqKz2d/zrv/GbRmpSy5BcfC5MXELmiYkg7gfyJr2+jQtS8S1/efpMjLYgyH4xSlv xShjY9OV2zh88HydqGQw5ZBgtwB03s/qfRHbe3wkQdeaWVCBECCd+CwCYyMB0etYlghy ttqAJuLOZg+8bMT4NlXkLf6zHDLQXD8ig6kAU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=H3NA9h/cZVu+B9Cri2ClC25XurqbBV0YohgCjdnDaveKt6J3PapPytvhH8VLHxtfu3 x5a5hxzh+MQbLeMFACdF8kbTFBqTcrhozVCiND7mmVkED9JqbkJ+Iq+3I76e9URRvs67 qvykLYH9QW55GawBZko/Bq0bDaNgHPECqSUYU=
Received: by 10.114.110.9 with SMTP id i9mr3070983wac.76.1244099264667; Thu, 04 Jun 2009 00:07:44 -0700 (PDT)
Received: from ?192.168.1.65? (host81-152-6-167.range81-152.btcentralplus.com [81.152.6.167]) by mx.google.com with ESMTPS id b39sm25140000rvf.5.2009.06.04.00.07.41 (version=SSLv3 cipher=RC4-MD5); Thu, 04 Jun 2009 00:07:43 -0700 (PDT)
Message-ID: <4A2772B6.2020404@gmail.com>
Date: Thu, 04 Jun 2009 08:07:34 +0100
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <4A26A959.7060104@piuha.net>
In-Reply-To: <4A26A959.7060104@piuha.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: shim6@ietf.org
Subject: Re: [shim6] next steps for the shim6 wg
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2009 07:07:46 -0000

Hi Jari,

I think this is very reasonable, as long as "leave the rest for later"
is not intended to prevent people producing non-WG drafts if they have
the energy to do so, or for the locator selection issues being
folded into more general work elsewhere.

    Brian

On 2009-06-03 17:48, Jari Arkko wrote:
> Hi,
> 
> I have finally found time to go through various pieces of input and come
> up with a suggested way forward.
> 
> I do think it would be useful to continue. But we need to make a careful
> selection for what the group should be looking at, because I'm not
> convinced that the amount of people and energy available for this is too
> big. And to be quite frank, while I get a lot of suggestions for further
> work, I have also gotten (privately) a fair number of suggestions that
> this would be a good time to close the WG. So I think we need to show
> some concrete and achievable steps in the charter.
> 
> My suggested new charter text is below -- please comment & suggest
> alternative content if needed.
> 
> The starting point for this proposal was that we have the following
> possible work:
> 
> 1. implementation, testing, and deployment reports
> 2. API specification
> 3. applicability draft
> 4. firewall implications document
> 5. shim6 and 6to4 interactions; an informational document
> 6. network-based address pair selection preferences (i.e., provider
> control)
> 7. proxy shim6 specification
> 8. multipath-tcp and shim6 interactions
> 9. locator selection in general
> 10. dealing with ingress filtering issues
> 
> I believe the most useful output at this stage would be 1. Item 2 is
> fairly far along, and I have commitments from the authors to complete
> this work.
> 
> I think completing 3 would be useful as well, though I suspect it is
> going to take quite a bit of work. For instance, in the last two years
> we got quite a bit of feedback, and we also tweaked the specifications
> on a number of areas. Items 4 and 5 are small, and I think they could be
> tackled under the applicability document. Perhaps that would also
> provide some new energy to completing the applicability document.
> 
> Item 6, provider control, is interesting. But is there energy behind
> doing something?
> 
> Proxy Shim6, item 7, is a fairly big effort. It might be better dealt
> with in a group or a BOF of its own. I'm not in principle against doing
> this, however. The IETF seems to be taking on all the main approaches
> discussed in the RRG, so why not this too... but the main criteria for
> us to adopt any of these efforts has been the existence of a sufficient
> community interested in doing the work, implementing, and discussing it
> in the WG. Does this exist for Proxy Shim6? Are there implementations?
> AFAICT, there is no big enough community behind this.
> 
> The work on multipath TCP related to item 8 deserves its own working
> group, and in my opinion, should be focused on a very specific solution
> on the TCP layer and avoid any avoidable interaction with other
> components. I do believe Shim6 has a lot to give to the multipath TCP
> effort, but suspect the most useful input for that effort happens
> through re-use of concepts and algorithms. I hope the WG participants go
> to the BOF (or eventual WG) and provide input so that multipath TCP gets
> constructed correctly.
> 
> Address selection issues (item 9) are more fundamental than just about
> Shim6, and I would rather see them addressed in 6MAN, as a part of the
> current address selection improvement efforts. If that effort has not
> yet taken all Shim6 related requirements, it should. Ingress filtering
> issues (item 10) would be a high priority item, but its not clear to me
> that we have a solution that the community likes.
> 
> Given all this, my suggestion would be to do items 1 through 5 and leave
> the rest for later. This is what the charter below contains. I'm
> hesitating a bit on items 6 and 10 though. Thoughts?
> 
> Jari
> 
> ----------------------
> 
> Site Multihoming by IPv6 Intermediation (shim6)
> 
> Last Modified: 2009-06-03
> 
> Additional information is available at tools.ietf.org/wg/shim6
> 
> Chair(s):
> Kurt Lindqvist <kurtis@kurtis.pp.se>
> Geoff Huston <gih@apnic.net>
> 
> Internet Area Director(s):
> Ralph Droms <rdroms@cisco.com>
> Jari Arkko <jari.arkko@piuha.net>
> 
> Internet Area Advisor:
> Jari Arkko <jari.arkko@piuha.net>
> 
> Technical Advisor(s):
> Thomas Narten <narten@us.ibm.com>
> 
> Mailing Lists:
> General Discussion: shim6@psg.com
> To Subscribe: shim6-request@psg.com
> Archive: http://ops.ietf.org/lists/shim6/
> 
> Description of Working Group:
> 
> Earlier efforts in this working group completed the Shim6 protocol
> specification, documented in RFCs 5533 through 5535. This protocol is
> a layer 3 shim for providing locator agility with failover
> capabilities for IPv6 nodes. Hosts that employ Shim6 use multiple IPv6
> address prefixes and setup state with peer hosts. This state can later
> be used to failover to a different set of locators, should the
> original locators stop working.
> 
> The Shim6 approach has a number of advantages, such as enabling small
> sites to be multihomed without requiring a provider independent IPv6
> address prefix for the site. But the approach has also been
> criticized, e.g., for the operational impacts that the use of multiple
> prefixes causes. At this time there is no clear view on how well Shim6
> works in practice. Implementation and deployment in select networks is
> needed to determine its true characteristics.
> 
> The Shim6 working group is chartered to track the implementation and
> testing or deployment efforts. The group is also expected to shepherd
> to completion a few remaining informational documents that complement
> the existing protocol specifications.
> 
> The specific work items of the group are:
> 
> o  Write an implementation and/or deployment experience report.
> 
> o  Specify socket API extensions. This API enables interactions between
>   applications and the Shim6 layer for advanced locator management,
>   and access to information about failure detection and path
>   exploration. It also enables some applications to turn Shim6 off.
> 
> o  Complete the work on the applicability draft. This draft explains
>   in detail in which types of networks Shim6 is applicable, and
>   what its advantages and disadvantages are. The draft will also
>   explain how firewalls are impacted by the use of Shim6. Finally,
>   the draft will also explain how Shim6 can be used in situations
>   where native IPv6 connectivity is not available, such as using
>   Shim6 over 6to4.
> 
> The group will also work in co-operation with the 6MAN working group
> as they continue their efforts in improving IPv6 address selection
> mechanisms.
> 
> The group shall not work on extensions to the Shim6 protocol itself at
> this time. However, new work items can be added through rechartering
> as others get completed.
> 
> Goals and Milestones:
> 
> Sep 2009  Next revision of the API document
> Nov 2009  First WG draft on an implementation report
> Jan 2010  Submit API document to IESG for publication as Informational RFC
> Jan 2010  Next revision of the applicability document
> Dec 2010  Submit implementation report to IESG for publication as
> Informational RFC
> Dec 2010  Submit applicability document to IESG for publication as
> Informational RFC
> Dec 2010  Close or re-charter
> 
> _______________________________________________
> shim6 mailing list
> shim6@ietf.org
> https://www.ietf.org/mailman/listinfo/shim6
> 

From marcelo@it.uc3m.es  Thu Jun  4 00:26:22 2009
Return-Path: <marcelo@it.uc3m.es>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B33F33A6D89 for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:26:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J+lEFmxdLXX3 for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:26:11 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by core3.amsl.com (Postfix) with ESMTP id 75DE93A7084 for <shim6@ietf.org>; Thu,  4 Jun 2009 00:26:04 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (unknown [141.39.21.152]) by smtp03.uc3m.es (Postfix) with ESMTP id 4A22B72D79A; Thu,  4 Jun 2009 09:26:04 +0200 (CEST)
Message-ID: <4A27770C.6040503@it.uc3m.es>
Date: Thu, 04 Jun 2009 09:26:04 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <4A26A959.7060104@piuha.net> <4A2772B6.2020404@gmail.com>
In-Reply-To: <4A2772B6.2020404@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.6.0.1016-16682.004
Cc: shim6@ietf.org
Subject: Re: [shim6] next steps for the shim6 wg
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2009 07:26:23 -0000

Exactly!
this was my reading of the proposed charter as well, and i think it is 
the correct approach at this point

Regards, marcelo


Brian E Carpenter escribió:
> Hi Jari,
>
> I think this is very reasonable, as long as "leave the rest for later"
> is not intended to prevent people producing non-WG drafts if they have
> the energy to do so, or for the locator selection issues being
> folded into more general work elsewhere.
>
>     Brian
>
> On 2009-06-03 17:48, Jari Arkko wrote:
>   
>> Hi,
>>
>> I have finally found time to go through various pieces of input and come
>> up with a suggested way forward.
>>
>> I do think it would be useful to continue. But we need to make a careful
>> selection for what the group should be looking at, because I'm not
>> convinced that the amount of people and energy available for this is too
>> big. And to be quite frank, while I get a lot of suggestions for further
>> work, I have also gotten (privately) a fair number of suggestions that
>> this would be a good time to close the WG. So I think we need to show
>> some concrete and achievable steps in the charter.
>>
>> My suggested new charter text is below -- please comment & suggest
>> alternative content if needed.
>>
>> The starting point for this proposal was that we have the following
>> possible work:
>>
>> 1. implementation, testing, and deployment reports
>> 2. API specification
>> 3. applicability draft
>> 4. firewall implications document
>> 5. shim6 and 6to4 interactions; an informational document
>> 6. network-based address pair selection preferences (i.e., provider
>> control)
>> 7. proxy shim6 specification
>> 8. multipath-tcp and shim6 interactions
>> 9. locator selection in general
>> 10. dealing with ingress filtering issues
>>
>> I believe the most useful output at this stage would be 1. Item 2 is
>> fairly far along, and I have commitments from the authors to complete
>> this work.
>>
>> I think completing 3 would be useful as well, though I suspect it is
>> going to take quite a bit of work. For instance, in the last two years
>> we got quite a bit of feedback, and we also tweaked the specifications
>> on a number of areas. Items 4 and 5 are small, and I think they could be
>> tackled under the applicability document. Perhaps that would also
>> provide some new energy to completing the applicability document.
>>
>> Item 6, provider control, is interesting. But is there energy behind
>> doing something?
>>
>> Proxy Shim6, item 7, is a fairly big effort. It might be better dealt
>> with in a group or a BOF of its own. I'm not in principle against doing
>> this, however. The IETF seems to be taking on all the main approaches
>> discussed in the RRG, so why not this too... but the main criteria for
>> us to adopt any of these efforts has been the existence of a sufficient
>> community interested in doing the work, implementing, and discussing it
>> in the WG. Does this exist for Proxy Shim6? Are there implementations?
>> AFAICT, there is no big enough community behind this.
>>
>> The work on multipath TCP related to item 8 deserves its own working
>> group, and in my opinion, should be focused on a very specific solution
>> on the TCP layer and avoid any avoidable interaction with other
>> components. I do believe Shim6 has a lot to give to the multipath TCP
>> effort, but suspect the most useful input for that effort happens
>> through re-use of concepts and algorithms. I hope the WG participants go
>> to the BOF (or eventual WG) and provide input so that multipath TCP gets
>> constructed correctly.
>>
>> Address selection issues (item 9) are more fundamental than just about
>> Shim6, and I would rather see them addressed in 6MAN, as a part of the
>> current address selection improvement efforts. If that effort has not
>> yet taken all Shim6 related requirements, it should. Ingress filtering
>> issues (item 10) would be a high priority item, but its not clear to me
>> that we have a solution that the community likes.
>>
>> Given all this, my suggestion would be to do items 1 through 5 and leave
>> the rest for later. This is what the charter below contains. I'm
>> hesitating a bit on items 6 and 10 though. Thoughts?
>>
>> Jari
>>
>> ----------------------
>>
>> Site Multihoming by IPv6 Intermediation (shim6)
>>
>> Last Modified: 2009-06-03
>>
>> Additional information is available at tools.ietf.org/wg/shim6
>>
>> Chair(s):
>> Kurt Lindqvist <kurtis@kurtis.pp.se>
>> Geoff Huston <gih@apnic.net>
>>
>> Internet Area Director(s):
>> Ralph Droms <rdroms@cisco.com>
>> Jari Arkko <jari.arkko@piuha.net>
>>
>> Internet Area Advisor:
>> Jari Arkko <jari.arkko@piuha.net>
>>
>> Technical Advisor(s):
>> Thomas Narten <narten@us.ibm.com>
>>
>> Mailing Lists:
>> General Discussion: shim6@psg.com
>> To Subscribe: shim6-request@psg.com
>> Archive: http://ops.ietf.org/lists/shim6/
>>
>> Description of Working Group:
>>
>> Earlier efforts in this working group completed the Shim6 protocol
>> specification, documented in RFCs 5533 through 5535. This protocol is
>> a layer 3 shim for providing locator agility with failover
>> capabilities for IPv6 nodes. Hosts that employ Shim6 use multiple IPv6
>> address prefixes and setup state with peer hosts. This state can later
>> be used to failover to a different set of locators, should the
>> original locators stop working.
>>
>> The Shim6 approach has a number of advantages, such as enabling small
>> sites to be multihomed without requiring a provider independent IPv6
>> address prefix for the site. But the approach has also been
>> criticized, e.g., for the operational impacts that the use of multiple
>> prefixes causes. At this time there is no clear view on how well Shim6
>> works in practice. Implementation and deployment in select networks is
>> needed to determine its true characteristics.
>>
>> The Shim6 working group is chartered to track the implementation and
>> testing or deployment efforts. The group is also expected to shepherd
>> to completion a few remaining informational documents that complement
>> the existing protocol specifications.
>>
>> The specific work items of the group are:
>>
>> o  Write an implementation and/or deployment experience report.
>>
>> o  Specify socket API extensions. This API enables interactions between
>>   applications and the Shim6 layer for advanced locator management,
>>   and access to information about failure detection and path
>>   exploration. It also enables some applications to turn Shim6 off.
>>
>> o  Complete the work on the applicability draft. This draft explains
>>   in detail in which types of networks Shim6 is applicable, and
>>   what its advantages and disadvantages are. The draft will also
>>   explain how firewalls are impacted by the use of Shim6. Finally,
>>   the draft will also explain how Shim6 can be used in situations
>>   where native IPv6 connectivity is not available, such as using
>>   Shim6 over 6to4.
>>
>> The group will also work in co-operation with the 6MAN working group
>> as they continue their efforts in improving IPv6 address selection
>> mechanisms.
>>
>> The group shall not work on extensions to the Shim6 protocol itself at
>> this time. However, new work items can be added through rechartering
>> as others get completed.
>>
>> Goals and Milestones:
>>
>> Sep 2009  Next revision of the API document
>> Nov 2009  First WG draft on an implementation report
>> Jan 2010  Submit API document to IESG for publication as Informational RFC
>> Jan 2010  Next revision of the applicability document
>> Dec 2010  Submit implementation report to IESG for publication as
>> Informational RFC
>> Dec 2010  Submit applicability document to IESG for publication as
>> Informational RFC
>> Dec 2010  Close or re-charter
>>
>> _______________________________________________
>> shim6 mailing list
>> shim6@ietf.org
>> https://www.ietf.org/mailman/listinfo/shim6
>>
>>     
> _______________________________________________
> shim6 mailing list
> shim6@ietf.org
> https://www.ietf.org/mailman/listinfo/shim6
>
>   


From pekkas@netcore.fi  Thu Jun  4 00:28:20 2009
Return-Path: <pekkas@netcore.fi>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5333C3A7080 for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hkEGfMvnO80q for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:28:18 -0700 (PDT)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1]) by core3.amsl.com (Postfix) with ESMTP id C1FF23A6C83 for <shim6@ietf.org>; Thu,  4 Jun 2009 00:28:17 -0700 (PDT)
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.13.8/8.13.8) with ESMTP id n547SBL3004357 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Jun 2009 10:28:11 +0300
Received: from localhost (pekkas@localhost) by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id n547SBeq004354; Thu, 4 Jun 2009 10:28:11 +0300
Date: Thu, 4 Jun 2009 10:28:11 +0300 (EEST)
From: Pekka Savola <pekkas@netcore.fi>
To: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <4A26A959.7060104@piuha.net>
Message-ID: <alpine.LRH.2.00.0906041023540.4154@netcore.fi>
References: <4A26A959.7060104@piuha.net>
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Virus-Scanned: clamav-milter 0.95.1 at otso.netcore.fi
X-Virus-Status: Clean
Cc: shim6@ietf.org
Subject: Re: [shim6] next steps for the shim6 wg
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2009 07:28:20 -0000

On Wed, 3 Jun 2009, Jari Arkko wrote:
> I do think it would be useful to continue. But we need to make a careful 
> selection for what the group should be looking at, because I'm not convinced 
> that the amount of people and energy available for this is too big. And to be 
> quite frank, while I get a lot of suggestions for further work, I have also 
> gotten (privately) a fair number of suggestions that this would be a good 
> time to close the WG. So I think we need to show some concrete and achievable 
> steps in the charter.
>
> My suggested new charter text is below -- please comment & suggest 
> alternative content if needed.

I share your concerns.  If the WG is to continue, I think the outline 
you suggest is reasonable and could achieve the objectives.

> The starting point for this proposal was that we have the following possible 
> work:
>
> 1. implementation, testing, and deployment reports
> 2. API specification
> 3. applicability draft
> 4. firewall implications document
> 5. shim6 and 6to4 interactions; an informational document
> 6. network-based address pair selection preferences (i.e., provider control)
> 7. proxy shim6 specification
> 8. multipath-tcp and shim6 interactions
> 9. locator selection in general
> 10. dealing with ingress filtering issues
>
> I believe the most useful output at this stage would be 1. Item 2 is fairly 
> far along, and I have commitments from the authors to complete this work.
>
> I think completing 3 would be useful as well, though I suspect it is going to 
> take quite a bit of work. For instance, in the last two years we got quite a 
> bit of feedback, and we also tweaked the specifications on a number of areas. 
> Items 4 and 5 are small, and I think they could be tackled under the 
> applicability document. Perhaps that would also provide some new energy to 
> completing the applicability document.
>
> Item 6, provider control, is interesting. But is there energy behind doing 
> something?
>
> Proxy Shim6, item 7, is a fairly big effort. It might be better dealt with in 
> a group or a BOF of its own. I'm not in principle against doing this, 
> however. The IETF seems to be taking on all the main approaches discussed in 
> the RRG, so why not this too... but the main criteria for us to adopt any of 
> these efforts has been the existence of a sufficient community interested in 
> doing the work, implementing, and discussing it in the WG. Does this exist 
> for Proxy Shim6? Are there implementations? AFAICT, there is no big enough 
> community behind this.
>
> The work on multipath TCP related to item 8 deserves its own working group, 
> and in my opinion, should be focused on a very specific solution on the TCP 
> layer and avoid any avoidable interaction with other components. I do believe 
> Shim6 has a lot to give to the multipath TCP effort, but suspect the most 
> useful input for that effort happens through re-use of concepts and 
> algorithms. I hope the WG participants go to the BOF (or eventual WG) and 
> provide input so that multipath TCP gets constructed correctly.
>
> Address selection issues (item 9) are more fundamental than just about Shim6, 
> and I would rather see them addressed in 6MAN, as a part of the current 
> address selection improvement efforts. If that effort has not yet taken all 
> Shim6 related requirements, it should. Ingress filtering issues (item 10) 
> would be a high priority item, but its not clear to me that we have a 
> solution that the community likes.
>
> Given all this, my suggestion would be to do items 1 through 5 and leave the 
> rest for later. This is what the charter below contains. I'm hesitating a bit 
> on items 6 and 10 though. Thoughts?
>
> Jari
>
> ----------------------
>
> Site Multihoming by IPv6 Intermediation (shim6)
>
> Last Modified: 2009-06-03
>
> Additional information is available at tools.ietf.org/wg/shim6
>
> Chair(s):
> Kurt Lindqvist <kurtis@kurtis.pp.se>
> Geoff Huston <gih@apnic.net>
>
> Internet Area Director(s):
> Ralph Droms <rdroms@cisco.com>
> Jari Arkko <jari.arkko@piuha.net>
>
> Internet Area Advisor:
> Jari Arkko <jari.arkko@piuha.net>
>
> Technical Advisor(s):
> Thomas Narten <narten@us.ibm.com>
>
> Mailing Lists:
> General Discussion: shim6@psg.com
> To Subscribe: shim6-request@psg.com
> Archive: http://ops.ietf.org/lists/shim6/
>
> Description of Working Group:
>
> Earlier efforts in this working group completed the Shim6 protocol
> specification, documented in RFCs 5533 through 5535. This protocol is
> a layer 3 shim for providing locator agility with failover
> capabilities for IPv6 nodes. Hosts that employ Shim6 use multiple IPv6
> address prefixes and setup state with peer hosts. This state can later
> be used to failover to a different set of locators, should the
> original locators stop working.
>
> The Shim6 approach has a number of advantages, such as enabling small
> sites to be multihomed without requiring a provider independent IPv6
> address prefix for the site. But the approach has also been
> criticized, e.g., for the operational impacts that the use of multiple
> prefixes causes. At this time there is no clear view on how well Shim6
> works in practice. Implementation and deployment in select networks is
> needed to determine its true characteristics.
>
> The Shim6 working group is chartered to track the implementation and
> testing or deployment efforts. The group is also expected to shepherd
> to completion a few remaining informational documents that complement
> the existing protocol specifications.
>
> The specific work items of the group are:
>
> o  Write an implementation and/or deployment experience report.
>
> o  Specify socket API extensions. This API enables interactions between
>   applications and the Shim6 layer for advanced locator management,
>   and access to information about failure detection and path
>   exploration. It also enables some applications to turn Shim6 off.
>
> o  Complete the work on the applicability draft. This draft explains
>   in detail in which types of networks Shim6 is applicable, and
>   what its advantages and disadvantages are. The draft will also
>   explain how firewalls are impacted by the use of Shim6. Finally,
>   the draft will also explain how Shim6 can be used in situations
>   where native IPv6 connectivity is not available, such as using
>   Shim6 over 6to4.
>
> The group will also work in co-operation with the 6MAN working group
> as they continue their efforts in improving IPv6 address selection
> mechanisms.
>
> The group shall not work on extensions to the Shim6 protocol itself at
> this time. However, new work items can be added through rechartering
> as others get completed.
>
> Goals and Milestones:
>
> Sep 2009  Next revision of the API document
> Nov 2009  First WG draft on an implementation report
> Jan 2010  Submit API document to IESG for publication as Informational RFC
> Jan 2010  Next revision of the applicability document
> Dec 2010  Submit implementation report to IESG for publication as 
> Informational RFC
> Dec 2010  Submit applicability document to IESG for publication as 
> Informational RFC
> Dec 2010  Close or re-charter
>
> _______________________________________________
> shim6 mailing list
> shim6@ietf.org
> https://www.ietf.org/mailman/listinfo/shim6
>
>

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

From jari.arkko@piuha.net  Thu Jun  4 00:28:29 2009
Return-Path: <jari.arkko@piuha.net>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E51523A67B1 for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:28:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.33
X-Spam-Level: 
X-Spam-Status: No, score=-2.33 tagged_above=-999 required=5 tests=[AWL=0.269,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GwQNQdFiGbkq for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:28:28 -0700 (PDT)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id F35093A7088 for <shim6@ietf.org>; Thu,  4 Jun 2009 00:28:27 -0700 (PDT)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id 0C31A19871D; Thu,  4 Jun 2009 10:28:28 +0300 (EEST)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id BE3EC198699; Thu,  4 Jun 2009 10:28:27 +0300 (EEST)
Message-ID: <4A277799.8050204@piuha.net>
Date: Thu, 04 Jun 2009 10:28:25 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <4A26A959.7060104@piuha.net> <4A2772B6.2020404@gmail.com>
In-Reply-To: <4A2772B6.2020404@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: shim6@ietf.org
Subject: Re: [shim6] next steps for the shim6 wg
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2009 07:28:30 -0000

Brian,

> I think this is very reasonable

Thanks.

> as long as "leave the rest for later"
> is not intended to prevent people producing non-WG drafts if they have
> the energy to do so

Of course not. Also, if there truly is good drafts and energy to do 
something additional, I'm always happy to AD sponsor RFCs. Or, if the 
existence of good work becomes obvious, we can add things to the charter.

> or for the locator selection issues being
> folded into more general work elsewhere.
>   

My preference is for the locator selection work in 6MAN to be 
sufficiently general that it takes into account requirements from Shim6 
and possibly some other things as well.

Jari

>     Brian
>
> On 2009-06-03 17:48, Jari Arkko wrote:
>   
>> Hi,
>>
>> I have finally found time to go through various pieces of input and come
>> up with a suggested way forward.
>>
>> I do think it would be useful to continue. But we need to make a careful
>> selection for what the group should be looking at, because I'm not
>> convinced that the amount of people and energy available for this is too
>> big. And to be quite frank, while I get a lot of suggestions for further
>> work, I have also gotten (privately) a fair number of suggestions that
>> this would be a good time to close the WG. So I think we need to show
>> some concrete and achievable steps in the charter.
>>
>> My suggested new charter text is below -- please comment & suggest
>> alternative content if needed.
>>
>> The starting point for this proposal was that we have the following
>> possible work:
>>
>> 1. implementation, testing, and deployment reports
>> 2. API specification
>> 3. applicability draft
>> 4. firewall implications document
>> 5. shim6 and 6to4 interactions; an informational document
>> 6. network-based address pair selection preferences (i.e., provider
>> control)
>> 7. proxy shim6 specification
>> 8. multipath-tcp and shim6 interactions
>> 9. locator selection in general
>> 10. dealing with ingress filtering issues
>>
>> I believe the most useful output at this stage would be 1. Item 2 is
>> fairly far along, and I have commitments from the authors to complete
>> this work.
>>
>> I think completing 3 would be useful as well, though I suspect it is
>> going to take quite a bit of work. For instance, in the last two years
>> we got quite a bit of feedback, and we also tweaked the specifications
>> on a number of areas. Items 4 and 5 are small, and I think they could be
>> tackled under the applicability document. Perhaps that would also
>> provide some new energy to completing the applicability document.
>>
>> Item 6, provider control, is interesting. But is there energy behind
>> doing something?
>>
>> Proxy Shim6, item 7, is a fairly big effort. It might be better dealt
>> with in a group or a BOF of its own. I'm not in principle against doing
>> this, however. The IETF seems to be taking on all the main approaches
>> discussed in the RRG, so why not this too... but the main criteria for
>> us to adopt any of these efforts has been the existence of a sufficient
>> community interested in doing the work, implementing, and discussing it
>> in the WG. Does this exist for Proxy Shim6? Are there implementations?
>> AFAICT, there is no big enough community behind this.
>>
>> The work on multipath TCP related to item 8 deserves its own working
>> group, and in my opinion, should be focused on a very specific solution
>> on the TCP layer and avoid any avoidable interaction with other
>> components. I do believe Shim6 has a lot to give to the multipath TCP
>> effort, but suspect the most useful input for that effort happens
>> through re-use of concepts and algorithms. I hope the WG participants go
>> to the BOF (or eventual WG) and provide input so that multipath TCP gets
>> constructed correctly.
>>
>> Address selection issues (item 9) are more fundamental than just about
>> Shim6, and I would rather see them addressed in 6MAN, as a part of the
>> current address selection improvement efforts. If that effort has not
>> yet taken all Shim6 related requirements, it should. Ingress filtering
>> issues (item 10) would be a high priority item, but its not clear to me
>> that we have a solution that the community likes.
>>
>> Given all this, my suggestion would be to do items 1 through 5 and leave
>> the rest for later. This is what the charter below contains. I'm
>> hesitating a bit on items 6 and 10 though. Thoughts?
>>
>> Jari
>>
>> ----------------------
>>
>> Site Multihoming by IPv6 Intermediation (shim6)
>>
>> Last Modified: 2009-06-03
>>
>> Additional information is available at tools.ietf.org/wg/shim6
>>
>> Chair(s):
>> Kurt Lindqvist <kurtis@kurtis.pp.se>
>> Geoff Huston <gih@apnic.net>
>>
>> Internet Area Director(s):
>> Ralph Droms <rdroms@cisco.com>
>> Jari Arkko <jari.arkko@piuha.net>
>>
>> Internet Area Advisor:
>> Jari Arkko <jari.arkko@piuha.net>
>>
>> Technical Advisor(s):
>> Thomas Narten <narten@us.ibm.com>
>>
>> Mailing Lists:
>> General Discussion: shim6@psg.com
>> To Subscribe: shim6-request@psg.com
>> Archive: http://ops.ietf.org/lists/shim6/
>>
>> Description of Working Group:
>>
>> Earlier efforts in this working group completed the Shim6 protocol
>> specification, documented in RFCs 5533 through 5535. This protocol is
>> a layer 3 shim for providing locator agility with failover
>> capabilities for IPv6 nodes. Hosts that employ Shim6 use multiple IPv6
>> address prefixes and setup state with peer hosts. This state can later
>> be used to failover to a different set of locators, should the
>> original locators stop working.
>>
>> The Shim6 approach has a number of advantages, such as enabling small
>> sites to be multihomed without requiring a provider independent IPv6
>> address prefix for the site. But the approach has also been
>> criticized, e.g., for the operational impacts that the use of multiple
>> prefixes causes. At this time there is no clear view on how well Shim6
>> works in practice. Implementation and deployment in select networks is
>> needed to determine its true characteristics.
>>
>> The Shim6 working group is chartered to track the implementation and
>> testing or deployment efforts. The group is also expected to shepherd
>> to completion a few remaining informational documents that complement
>> the existing protocol specifications.
>>
>> The specific work items of the group are:
>>
>> o  Write an implementation and/or deployment experience report.
>>
>> o  Specify socket API extensions. This API enables interactions between
>>   applications and the Shim6 layer for advanced locator management,
>>   and access to information about failure detection and path
>>   exploration. It also enables some applications to turn Shim6 off.
>>
>> o  Complete the work on the applicability draft. This draft explains
>>   in detail in which types of networks Shim6 is applicable, and
>>   what its advantages and disadvantages are. The draft will also
>>   explain how firewalls are impacted by the use of Shim6. Finally,
>>   the draft will also explain how Shim6 can be used in situations
>>   where native IPv6 connectivity is not available, such as using
>>   Shim6 over 6to4.
>>
>> The group will also work in co-operation with the 6MAN working group
>> as they continue their efforts in improving IPv6 address selection
>> mechanisms.
>>
>> The group shall not work on extensions to the Shim6 protocol itself at
>> this time. However, new work items can be added through rechartering
>> as others get completed.
>>
>> Goals and Milestones:
>>
>> Sep 2009  Next revision of the API document
>> Nov 2009  First WG draft on an implementation report
>> Jan 2010  Submit API document to IESG for publication as Informational RFC
>> Jan 2010  Next revision of the applicability document
>> Dec 2010  Submit implementation report to IESG for publication as
>> Informational RFC
>> Dec 2010  Submit applicability document to IESG for publication as
>> Informational RFC
>> Dec 2010  Close or re-charter
>>
>> _______________________________________________
>> shim6 mailing list
>> shim6@ietf.org
>> https://www.ietf.org/mailman/listinfo/shim6
>>
>>     
>
>
>   


From gih@apnic.net  Thu Jun  4 00:40:10 2009
Return-Path: <gih@apnic.net>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 38E353A68D9 for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:40:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id APmNgbCPufVg for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:40:09 -0700 (PDT)
Received: from asmtp.apnic.net (oregano.apnic.net [IPv6:2001:dc0:2001:a:4608::60]) by core3.amsl.com (Postfix) with ESMTP id D49093A6A29 for <shim6@ietf.org>; Thu,  4 Jun 2009 00:40:07 -0700 (PDT)
Received: from [IPv6:2001:dc0:2001:10:217:f2ff:fec9:1b10] (unknown [IPv6:2001:dc0:2001:10:217:f2ff:fec9:1b10]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 59BE0110061; Thu,  4 Jun 2009 17:40:07 +1000 (EST)
Message-Id: <687F04C5-5D29-4060-A877-912E710D1A37@apnic.net>
From: Geoff Huston <gih@apnic.net>
To: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <4A26A959.7060104@piuha.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Thu, 4 Jun 2009 17:40:06 +1000
References: <4A26A959.7060104@piuha.net>
X-Mailer: Apple Mail (2.935.3)
Cc: shim6@ietf.org
Subject: Re: [shim6] next steps for the shim6 wg
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2009 07:40:10 -0000

This looks reasonable to me.

The usual caveat applies, though - there needs to be interest to  
actually do this work. Right now there is a single API draft in the  
works, but nothing current in the other proposed areas.

This would imply that the first objective of the chairs under this  
charter would be to see what interest there is to actually do this work.

thanks,

    Geoff




On 04/06/2009, at 2:48 AM, Jari Arkko wrote:

> Hi,
>
> I have finally found time to go through various pieces of input and  
> come up with a suggested way forward.
>
> I do think it would be useful to continue. But we need to make a  
> careful selection for what the group should be looking at, because  
> I'm not convinced that the amount of people and energy available for  
> this is too big. And to be quite frank, while I get a lot of  
> suggestions for further work, I have also gotten (privately) a fair  
> number of suggestions that this would be a good time to close the  
> WG. So I think we need to show some concrete and achievable steps in  
> the charter.
>
> My suggested new charter text is below -- please comment & suggest  
> alternative content if needed.
>
> The starting point for this proposal was that we have the following  
> possible work:
>
> 1. implementation, testing, and deployment reports
> 2. API specification
> 3. applicability draft
> 4. firewall implications document
> 5. shim6 and 6to4 interactions; an informational document
> 6. network-based address pair selection preferences (i.e., provider  
> control)
> 7. proxy shim6 specification
> 8. multipath-tcp and shim6 interactions
> 9. locator selection in general
> 10. dealing with ingress filtering issues
>
> I believe the most useful output at this stage would be 1. Item 2 is  
> fairly far along, and I have commitments from the authors to  
> complete this work.
>
> I think completing 3 would be useful as well, though I suspect it is  
> going to take quite a bit of work. For instance, in the last two  
> years we got quite a bit of feedback, and we also tweaked the  
> specifications on a number of areas. Items 4 and 5 are small, and I  
> think they could be tackled under the applicability document.  
> Perhaps that would also provide some new energy to completing the  
> applicability document.
>
> Item 6, provider control, is interesting. But is there energy behind  
> doing something?
>
> Proxy Shim6, item 7, is a fairly big effort. It might be better  
> dealt with in a group or a BOF of its own. I'm not in principle  
> against doing this, however. The IETF seems to be taking on all the  
> main approaches discussed in the RRG, so why not this too... but the  
> main criteria for us to adopt any of these efforts has been the  
> existence of a sufficient community interested in doing the work,  
> implementing, and discussing it in the WG. Does this exist for Proxy  
> Shim6? Are there implementations? AFAICT, there is no big enough  
> community behind this.
>
> The work on multipath TCP related to item 8 deserves its own working  
> group, and in my opinion, should be focused on a very specific  
> solution on the TCP layer and avoid any avoidable interaction with  
> other components. I do believe Shim6 has a lot to give to the  
> multipath TCP effort, but suspect the most useful input for that  
> effort happens through re-use of concepts and algorithms. I hope the  
> WG participants go to the BOF (or eventual WG) and provide input so  
> that multipath TCP gets constructed correctly.
>
> Address selection issues (item 9) are more fundamental than just  
> about Shim6, and I would rather see them addressed in 6MAN, as a  
> part of the current address selection improvement efforts. If that  
> effort has not yet taken all Shim6 related requirements, it should.  
> Ingress filtering issues (item 10) would be a high priority item,  
> but its not clear to me that we have a solution that the community  
> likes.
>
> Given all this, my suggestion would be to do items 1 through 5 and  
> leave the rest for later. This is what the charter below contains.  
> I'm hesitating a bit on items 6 and 10 though. Thoughts?
>
> Jari
>
> ----------------------
>
> Site Multihoming by IPv6 Intermediation (shim6)
>
> Last Modified: 2009-06-03
>
> Additional information is available at tools.ietf.org/wg/shim6
>
> Chair(s):
> Kurt Lindqvist <kurtis@kurtis.pp.se>
> Geoff Huston <gih@apnic.net>
>
> Internet Area Director(s):
> Ralph Droms <rdroms@cisco.com>
> Jari Arkko <jari.arkko@piuha.net>
>
> Internet Area Advisor:
> Jari Arkko <jari.arkko@piuha.net>
>
> Technical Advisor(s):
> Thomas Narten <narten@us.ibm.com>
>
> Mailing Lists:
> General Discussion: shim6@psg.com
> To Subscribe: shim6-request@psg.com
> Archive: http://ops.ietf.org/lists/shim6/
>
> Description of Working Group:
>
> Earlier efforts in this working group completed the Shim6 protocol
> specification, documented in RFCs 5533 through 5535. This protocol is
> a layer 3 shim for providing locator agility with failover
> capabilities for IPv6 nodes. Hosts that employ Shim6 use multiple IPv6
> address prefixes and setup state with peer hosts. This state can later
> be used to failover to a different set of locators, should the
> original locators stop working.
>
> The Shim6 approach has a number of advantages, such as enabling small
> sites to be multihomed without requiring a provider independent IPv6
> address prefix for the site. But the approach has also been
> criticized, e.g., for the operational impacts that the use of multiple
> prefixes causes. At this time there is no clear view on how well Shim6
> works in practice. Implementation and deployment in select networks is
> needed to determine its true characteristics.
>
> The Shim6 working group is chartered to track the implementation and
> testing or deployment efforts. The group is also expected to shepherd
> to completion a few remaining informational documents that complement
> the existing protocol specifications.
>
> The specific work items of the group are:
>
> o  Write an implementation and/or deployment experience report.
>
> o  Specify socket API extensions. This API enables interactions  
> between
>  applications and the Shim6 layer for advanced locator management,
>  and access to information about failure detection and path
>  exploration. It also enables some applications to turn Shim6 off.
>
> o  Complete the work on the applicability draft. This draft explains
>  in detail in which types of networks Shim6 is applicable, and
>  what its advantages and disadvantages are. The draft will also
>  explain how firewalls are impacted by the use of Shim6. Finally,
>  the draft will also explain how Shim6 can be used in situations
>  where native IPv6 connectivity is not available, such as using
>  Shim6 over 6to4.
>
> The group will also work in co-operation with the 6MAN working group
> as they continue their efforts in improving IPv6 address selection
> mechanisms.
>
> The group shall not work on extensions to the Shim6 protocol itself at
> this time. However, new work items can be added through rechartering
> as others get completed.
>
> Goals and Milestones:
>
> Sep 2009  Next revision of the API document
> Nov 2009  First WG draft on an implementation report
> Jan 2010  Submit API document to IESG for publication as  
> Informational RFC
> Jan 2010  Next revision of the applicability document
> Dec 2010  Submit implementation report to IESG for publication as  
> Informational RFC
> Dec 2010  Submit applicability document to IESG for publication as  
> Informational RFC
> Dec 2010  Close or re-charter
>
> _______________________________________________
> shim6 mailing list
> shim6@ietf.org
> https://www.ietf.org/mailman/listinfo/shim6


From olivier.bonaventure@uclouvain.be  Thu Jun  4 00:54:28 2009
Return-Path: <olivier.bonaventure@uclouvain.be>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1DAAE3A6904 for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:54:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.297
X-Spam-Level: 
X-Spam-Status: No, score=-6.297 tagged_above=-999 required=5 tests=[AWL=0.302,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o4fwDYU7x2Fw for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:54:27 -0700 (PDT)
Received: from smtp3.sgsi.ucl.ac.be (smtpout.sgsi.ucl.ac.be [130.104.5.77]) by core3.amsl.com (Postfix) with ESMTP id F10B43A67B1 for <shim6@ietf.org>; Thu,  4 Jun 2009 00:54:26 -0700 (PDT)
Received: from mbpobo.local (ip-83-134-254-6.dsl.scarlet.be [83.134.254.6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: obonaventure@smtp3.sgsi.ucl.ac.be) by smtp3.sgsi.ucl.ac.be (Postfix) with ESMTPSA id 7C5991C57A8; Thu,  4 Jun 2009 09:54:10 +0200 (CEST)
X-DKIM: Sendmail DKIM Filter v2.8.2 smtp3.sgsi.ucl.ac.be 7C5991C57A8
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1244102050; bh=ZJ4lHUV66544Xcy4/L32ZwUfcNCj0HMJ40mAtQz4Zss=; h=Message-ID:Date:From:Reply-To:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=uz1pd3xQaOt7b8M7gsJDD9borVw2hfSxvg1MnmLCXt5C3vDNN8MtGNsIKL4rrBaNi exd36WH0OBeQXsjM8JIRiz77DAW2yCYkUdY6fqFIGyxBBE5cUdiVt5wfzNsmp6QUhB 4Ug//BjQndpQ5u9Flsjm8pAJFfslkV/Pr01g+FIE=
Message-ID: <4A277DA1.2010502@uclouvain.be>
Date: Thu, 04 Jun 2009 09:54:09 +0200
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: Geoff Huston <gih@apnic.net>
References: <4A26A959.7060104@piuha.net> <687F04C5-5D29-4060-A877-912E710D1A37@apnic.net>
In-Reply-To: <687F04C5-5D29-4060-A877-912E710D1A37@apnic.net>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.95.1
X-Virus-Status: Clean
X-Sgsi-Spamcheck: SASL authenticated, 
X-SGSI-MailScanner-ID: 7C5991C57A8.00000
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: olivier.bonaventure@uclouvain.be
X-SGSI-Spam-Status: No
Cc: shim6@ietf.org
Subject: Re: [shim6] next steps for the shim6 wg
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Olivier.Bonaventure@uclouvain.be
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2009 07:54:28 -0000

Geoff,

> This looks reasonable to me.
> 
> The usual caveat applies, though - there needs to be interest to
> actually do this work. Right now there is a single API draft in the
> works, but nothing current in the other proposed areas.

...

> 
> On 04/06/2009, at 2:48 AM, Jari Arkko wrote:

...

>> The starting point for this proposal was that we have the following
>> possible work:
>>
>> 1. implementation, testing, and deployment reports

For this, Sébastien Barré wrote a detailed implementation report that
describes his choices in implementing shim6 in the Linux kernel

http://tools.ietf.org/html/draft-barre-shim6-impl-02

Sébastien's implementation is freely available and can be used for
testing and deployment efforts. We would be happy to collaborate with
such efforts. Same for interoperability testing with other mature
implementations.


Olivier

-- 
http://inl.info.ucl.ac.be , UCLouvain, Belgium


From jari.arkko@piuha.net  Thu Jun  4 00:55:51 2009
Return-Path: <jari.arkko@piuha.net>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B5C903A6B22 for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:55:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.37
X-Spam-Level: 
X-Spam-Status: No, score=-2.37 tagged_above=-999 required=5 tests=[AWL=0.229,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ys51N2iGd8Fb for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:55:51 -0700 (PDT)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id CCA853A67B1 for <shim6@ietf.org>; Thu,  4 Jun 2009 00:55:50 -0700 (PDT)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id E537B19878A; Thu,  4 Jun 2009 10:55:51 +0300 (EEST)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id A9D5C198665; Thu,  4 Jun 2009 10:55:51 +0300 (EEST)
Message-ID: <4A277E05.6090103@piuha.net>
Date: Thu, 04 Jun 2009 10:55:49 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: Olivier.Bonaventure@uclouvain.be
References: <4A26A959.7060104@piuha.net> <687F04C5-5D29-4060-A877-912E710D1A37@apnic.net> <4A277DA1.2010502@uclouvain.be>
In-Reply-To: <4A277DA1.2010502@uclouvain.be>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: shim6@ietf.org
Subject: Re: [shim6] next steps for the shim6 wg
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2009 07:55:51 -0000

Is Sebastien interested in completing the implementation report as an 
RFC, or as a part of an RFC?

Jari


From olivier.bonaventure@uclouvain.be  Thu Jun  4 00:57:16 2009
Return-Path: <olivier.bonaventure@uclouvain.be>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4AFEE3A6D0F for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:57:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.358
X-Spam-Level: 
X-Spam-Status: No, score=-6.358 tagged_above=-999 required=5 tests=[AWL=0.241,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SASvwGRRPZm4 for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:57:15 -0700 (PDT)
Received: from smtp2.sgsi.ucl.ac.be (smtpout.sgsi.ucl.ac.be [130.104.5.77]) by core3.amsl.com (Postfix) with ESMTP id 6D9B83A6A57 for <shim6@ietf.org>; Thu,  4 Jun 2009 00:57:15 -0700 (PDT)
Received: from mbpobo.local (ip-83-134-254-6.dsl.scarlet.be [83.134.254.6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: obonaventure@smtp2.sgsi.ucl.ac.be) by smtp2.sgsi.ucl.ac.be (Postfix) with ESMTPSA id 323F4EB3E8; Thu,  4 Jun 2009 09:57:08 +0200 (CEST)
X-DKIM: Sendmail DKIM Filter v2.8.2 smtp2.sgsi.ucl.ac.be 323F4EB3E8
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1244102228; bh=QboFZiXLKPejLZjY1GVeTzfD1BeS3s+92MpEs1GU7/4=; h=Message-ID:Date:From:Reply-To:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=RaE0g/Ttt/342BHI8sQnEiWKtMaOagRo4L2+fsJVcQZZRUoqq3J0ga/jIiIip5zXr LhpcFw+JJaJ8VoIq8FlMNYJ1DvvY8AcSYVJ/T8dznFJi2TRQ2akSV8EqFmsW80woJE iYra9a//qOgwptf4AXgvYexsUHmEjtQp1iXkcLxU=
Message-ID: <4A277E53.50506@uclouvain.be>
Date: Thu, 04 Jun 2009 09:57:07 +0200
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <4A26A959.7060104@piuha.net> <687F04C5-5D29-4060-A877-912E710D1A37@apnic.net> <4A277DA1.2010502@uclouvain.be> <4A277E05.6090103@piuha.net>
In-Reply-To: <4A277E05.6090103@piuha.net>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: clamav-milter 0.95.1
X-Virus-Status: Clean
X-Sgsi-Spamcheck: SASL authenticated, 
X-SGSI-MailScanner-ID: 323F4EB3E8.00000
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: olivier.bonaventure@uclouvain.be
X-SGSI-Spam-Status: No
Cc: shim6@ietf.org
Subject: Re: [shim6] next steps for the shim6 wg
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Olivier.Bonaventure@uclouvain.be
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2009 07:57:16 -0000

Jari,
> Is Sebastien interested in completing the implementation report as an
> RFC, or as a part of an RFC?

Yes, of course


Olivier


-- 
http://inl.info.ucl.ac.be , UCLouvain, Belgium

From marcelo@it.uc3m.es  Thu Jun  4 00:57:32 2009
Return-Path: <marcelo@it.uc3m.es>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 696813A6C42 for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:57:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WoOJbjcUsNxA for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:57:31 -0700 (PDT)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) by core3.amsl.com (Postfix) with ESMTP id B66CB3A6A57 for <shim6@ietf.org>; Thu,  4 Jun 2009 00:57:30 -0700 (PDT)
Received: from marcelo-bagnulos-macbook-pro.local (unknown [141.39.21.152]) by smtp01.uc3m.es (Postfix) with ESMTP id 4D7F5B48E6D; Thu,  4 Jun 2009 09:57:31 +0200 (CEST)
Message-ID: <4A277E6B.3020906@it.uc3m.es>
Date: Thu, 04 Jun 2009 09:57:31 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: Geoff Huston <gih@apnic.net>
References: <4A26A959.7060104@piuha.net> <687F04C5-5D29-4060-A877-912E710D1A37@apnic.net>
In-Reply-To: <687F04C5-5D29-4060-A877-912E710D1A37@apnic.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.6.0.1016-16682.004
Cc: shim6@ietf.org
Subject: Re: [shim6] next steps for the shim6 wg
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2009 07:57:32 -0000

Hi,

we do have an applicability draft already as well that i can update.

Regards, marcelo


Geoff Huston escribió:
> This looks reasonable to me.
>
> The usual caveat applies, though - there needs to be interest to 
> actually do this work. Right now there is a single API draft in the 
> works, but nothing current in the other proposed areas.
>
> This would imply that the first objective of the chairs under this 
> charter would be to see what interest there is to actually do this work.
>
> thanks,
>
>    Geoff
>
>
>
>
> On 04/06/2009, at 2:48 AM, Jari Arkko wrote:
>
>> Hi,
>>
>> I have finally found time to go through various pieces of input and 
>> come up with a suggested way forward.
>>
>> I do think it would be useful to continue. But we need to make a 
>> careful selection for what the group should be looking at, because 
>> I'm not convinced that the amount of people and energy available for 
>> this is too big. And to be quite frank, while I get a lot of 
>> suggestions for further work, I have also gotten (privately) a fair 
>> number of suggestions that this would be a good time to close the WG. 
>> So I think we need to show some concrete and achievable steps in the 
>> charter.
>>
>> My suggested new charter text is below -- please comment & suggest 
>> alternative content if needed.
>>
>> The starting point for this proposal was that we have the following 
>> possible work:
>>
>> 1. implementation, testing, and deployment reports
>> 2. API specification
>> 3. applicability draft
>> 4. firewall implications document
>> 5. shim6 and 6to4 interactions; an informational document
>> 6. network-based address pair selection preferences (i.e., provider 
>> control)
>> 7. proxy shim6 specification
>> 8. multipath-tcp and shim6 interactions
>> 9. locator selection in general
>> 10. dealing with ingress filtering issues
>>
>> I believe the most useful output at this stage would be 1. Item 2 is 
>> fairly far along, and I have commitments from the authors to complete 
>> this work.
>>
>> I think completing 3 would be useful as well, though I suspect it is 
>> going to take quite a bit of work. For instance, in the last two 
>> years we got quite a bit of feedback, and we also tweaked the 
>> specifications on a number of areas. Items 4 and 5 are small, and I 
>> think they could be tackled under the applicability document. Perhaps 
>> that would also provide some new energy to completing the 
>> applicability document.
>>
>> Item 6, provider control, is interesting. But is there energy behind 
>> doing something?
>>
>> Proxy Shim6, item 7, is a fairly big effort. It might be better dealt 
>> with in a group or a BOF of its own. I'm not in principle against 
>> doing this, however. The IETF seems to be taking on all the main 
>> approaches discussed in the RRG, so why not this too... but the main 
>> criteria for us to adopt any of these efforts has been the existence 
>> of a sufficient community interested in doing the work, implementing, 
>> and discussing it in the WG. Does this exist for Proxy Shim6? Are 
>> there implementations? AFAICT, there is no big enough community 
>> behind this.
>>
>> The work on multipath TCP related to item 8 deserves its own working 
>> group, and in my opinion, should be focused on a very specific 
>> solution on the TCP layer and avoid any avoidable interaction with 
>> other components. I do believe Shim6 has a lot to give to the 
>> multipath TCP effort, but suspect the most useful input for that 
>> effort happens through re-use of concepts and algorithms. I hope the 
>> WG participants go to the BOF (or eventual WG) and provide input so 
>> that multipath TCP gets constructed correctly.
>>
>> Address selection issues (item 9) are more fundamental than just 
>> about Shim6, and I would rather see them addressed in 6MAN, as a part 
>> of the current address selection improvement efforts. If that effort 
>> has not yet taken all Shim6 related requirements, it should. Ingress 
>> filtering issues (item 10) would be a high priority item, but its not 
>> clear to me that we have a solution that the community likes.
>>
>> Given all this, my suggestion would be to do items 1 through 5 and 
>> leave the rest for later. This is what the charter below contains. 
>> I'm hesitating a bit on items 6 and 10 though. Thoughts?
>>
>> Jari
>>
>> ----------------------
>>
>> Site Multihoming by IPv6 Intermediation (shim6)
>>
>> Last Modified: 2009-06-03
>>
>> Additional information is available at tools.ietf.org/wg/shim6
>>
>> Chair(s):
>> Kurt Lindqvist <kurtis@kurtis.pp.se>
>> Geoff Huston <gih@apnic.net>
>>
>> Internet Area Director(s):
>> Ralph Droms <rdroms@cisco.com>
>> Jari Arkko <jari.arkko@piuha.net>
>>
>> Internet Area Advisor:
>> Jari Arkko <jari.arkko@piuha.net>
>>
>> Technical Advisor(s):
>> Thomas Narten <narten@us.ibm.com>
>>
>> Mailing Lists:
>> General Discussion: shim6@psg.com
>> To Subscribe: shim6-request@psg.com
>> Archive: http://ops.ietf.org/lists/shim6/
>>
>> Description of Working Group:
>>
>> Earlier efforts in this working group completed the Shim6 protocol
>> specification, documented in RFCs 5533 through 5535. This protocol is
>> a layer 3 shim for providing locator agility with failover
>> capabilities for IPv6 nodes. Hosts that employ Shim6 use multiple IPv6
>> address prefixes and setup state with peer hosts. This state can later
>> be used to failover to a different set of locators, should the
>> original locators stop working.
>>
>> The Shim6 approach has a number of advantages, such as enabling small
>> sites to be multihomed without requiring a provider independent IPv6
>> address prefix for the site. But the approach has also been
>> criticized, e.g., for the operational impacts that the use of multiple
>> prefixes causes. At this time there is no clear view on how well Shim6
>> works in practice. Implementation and deployment in select networks is
>> needed to determine its true characteristics.
>>
>> The Shim6 working group is chartered to track the implementation and
>> testing or deployment efforts. The group is also expected to shepherd
>> to completion a few remaining informational documents that complement
>> the existing protocol specifications.
>>
>> The specific work items of the group are:
>>
>> o  Write an implementation and/or deployment experience report.
>>
>> o  Specify socket API extensions. This API enables interactions between
>>  applications and the Shim6 layer for advanced locator management,
>>  and access to information about failure detection and path
>>  exploration. It also enables some applications to turn Shim6 off.
>>
>> o  Complete the work on the applicability draft. This draft explains
>>  in detail in which types of networks Shim6 is applicable, and
>>  what its advantages and disadvantages are. The draft will also
>>  explain how firewalls are impacted by the use of Shim6. Finally,
>>  the draft will also explain how Shim6 can be used in situations
>>  where native IPv6 connectivity is not available, such as using
>>  Shim6 over 6to4.
>>
>> The group will also work in co-operation with the 6MAN working group
>> as they continue their efforts in improving IPv6 address selection
>> mechanisms.
>>
>> The group shall not work on extensions to the Shim6 protocol itself at
>> this time. However, new work items can be added through rechartering
>> as others get completed.
>>
>> Goals and Milestones:
>>
>> Sep 2009  Next revision of the API document
>> Nov 2009  First WG draft on an implementation report
>> Jan 2010  Submit API document to IESG for publication as 
>> Informational RFC
>> Jan 2010  Next revision of the applicability document
>> Dec 2010  Submit implementation report to IESG for publication as 
>> Informational RFC
>> Dec 2010  Submit applicability document to IESG for publication as 
>> Informational RFC
>> Dec 2010  Close or re-charter
>>
>> _______________________________________________
>> shim6 mailing list
>> shim6@ietf.org
>> https://www.ietf.org/mailman/listinfo/shim6
>
> _______________________________________________
> shim6 mailing list
> shim6@ietf.org
> https://www.ietf.org/mailman/listinfo/shim6
>


From sebastien.barre@uclouvain.be  Fri Jun  5 03:03:17 2009
Return-Path: <sebastien.barre@uclouvain.be>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3CE433A6940 for <shim6@core3.amsl.com>; Fri,  5 Jun 2009 03:03:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Level: 
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHpaXUSCbuO5 for <shim6@core3.amsl.com>; Fri,  5 Jun 2009 03:03:16 -0700 (PDT)
Received: from smtp2.sgsi.ucl.ac.be (smtpout.sgsi.ucl.ac.be [130.104.5.77]) by core3.amsl.com (Postfix) with ESMTP id 2B3EF3A68DA for <shim6@ietf.org>; Fri,  5 Jun 2009 03:03:16 -0700 (PDT)
Received: from [141.39.21.135] (unknown [141.39.21.135]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: sbarre@smtp2.sgsi.ucl.ac.be) by smtp2.sgsi.ucl.ac.be (Postfix) with ESMTPSA id 165A6EB571; Fri,  5 Jun 2009 12:01:12 +0200 (CEST)
Message-ID: <4A28ECE6.1070605@uclouvain.be>
Date: Fri, 05 Jun 2009 12:01:10 +0200
From: =?ISO-8859-1?Q?S=E9bastien_Barr=E9?= <sebastien.barre@uclouvain.be>
User-Agent: Thunderbird 2.0.0.21 (X11/20090409)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <4A26A959.7060104@piuha.net> <687F04C5-5D29-4060-A877-912E710D1A37@apnic.net> <4A277DA1.2010502@uclouvain.be> <4A277E05.6090103@piuha.net> <4A277E53.50506@uclouvain.be>
In-Reply-To: <4A277E53.50506@uclouvain.be>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.95.1
X-Virus-Status: Clean
X-Sgsi-Spamcheck: SASL authenticated, 
X-SGSI-MailScanner-ID: 165A6EB571.00000
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: sebastien.barre@uclouvain.be
X-SGSI-Spam-Status: No
Cc: shim6@ietf.org, Olivier.Bonaventure@uclouvain.be
Subject: Re: [shim6] next steps for the shim6 wg
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Jun 2009 10:03:17 -0000

Hi,

As explained by Olivier. I can use my current implementation report 
draft as a starting point for this work.
Currently the structure of the impl report is to list in details Shim6 
features, and check which of them are implemented in the latest LinShim6 
version.

Based on comments on this mailing list, I can update the format so that 
it fits better with a "standard" implementation report. If other mature 
implementations are available, they can be added to the draft. Beside 
LinShim6 which I authored, I only know about the Boeing implementation, 
which does not support the security stuff, though (HBA/CGA).

regards,

Sébastien.

Olivier Bonaventure a écrit :
> Jari,
>   
>> Is Sebastien interested in completing the implementation report as an
>> RFC, or as a part of an RFC?
>>     
>
> Yes, of course
>
>
> Olivier
>
>
>   

-- 
Sébastien Barré
Researcher,
CSE department, UCLouvain, Belgium
http://inl.info.ucl.ac.be/sbarre


From jari.arkko@piuha.net  Fri Jun  5 03:13:26 2009
Return-Path: <jari.arkko@piuha.net>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C1EF93A6C06 for <shim6@core3.amsl.com>; Fri,  5 Jun 2009 03:13:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.268
X-Spam-Level: 
X-Spam-Status: No, score=-2.268 tagged_above=-999 required=5 tests=[AWL=0.031,  BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9GwxEEBPgoyS for <shim6@core3.amsl.com>; Fri,  5 Jun 2009 03:13:26 -0700 (PDT)
Received: from smtp.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id E37A03A6C21 for <shim6@ietf.org>; Fri,  5 Jun 2009 03:13:25 -0700 (PDT)
Received: from smtp.piuha.net (localhost [127.0.0.1]) by smtp.piuha.net (Postfix) with ESMTP id 57C00198710; Fri,  5 Jun 2009 13:13:28 +0300 (EEST)
Received: from [127.0.0.1] (unknown [IPv6:2001:14b8:400::130]) by smtp.piuha.net (Postfix) with ESMTP id 0D24A19870C; Fri,  5 Jun 2009 13:13:28 +0300 (EEST)
Message-ID: <4A28EFC4.7000901@piuha.net>
Date: Fri, 05 Jun 2009 13:13:24 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.21 (X11/20090318)
MIME-Version: 1.0
To: =?ISO-8859-1?Q?S=E9bastien_Barr=E9?= <sebastien.barre@uclouvain.be>
References: <4A26A959.7060104@piuha.net> <687F04C5-5D29-4060-A877-912E710D1A37@apnic.net> <4A277DA1.2010502@uclouvain.be> <4A277E05.6090103@piuha.net> <4A277E53.50506@uclouvain.be> <4A28ECE6.1070605@uclouvain.be>
In-Reply-To: <4A28ECE6.1070605@uclouvain.be>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: ClamAV using ClamSMTP
Cc: shim6@ietf.org, Olivier.Bonaventure@uclouvain.be
Subject: Re: [shim6] next steps for the shim6 wg
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Jun 2009 10:13:26 -0000

Sébastien,

This all sounds good. It would also be great if you could add 
"experience" type information, e.g., comment on things that were not 
easy to implement, point out bugs that were found in the specifications, 
indicate problems that you've had when turning Shim6 on for test 
traffic, etc. In other words, data that would help us improve the 
specifications later. Or information that helps people to determine how 
easy or hard Shim6 in general is to implement and use.

Jari


From olivier.bonaventure@uclouvain.be  Thu Jun  4 00:49:07 2009
Return-Path: <olivier.bonaventure@uclouvain.be>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4E6E13A6C4C for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:49:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.197
X-Spam-Level: 
X-Spam-Status: No, score=-6.197 tagged_above=-999 required=5 tests=[AWL=0.402,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nobvE-5GAK7s for <shim6@core3.amsl.com>; Thu,  4 Jun 2009 00:49:06 -0700 (PDT)
Received: from smtp1.sgsi.ucl.ac.be (smtpout.sgsi.ucl.ac.be [130.104.5.77]) by core3.amsl.com (Postfix) with ESMTP id 6A45328C273 for <shim6@ietf.org>; Thu,  4 Jun 2009 00:48:59 -0700 (PDT)
Received: from mbpobo.local (ip-83-134-254-6.dsl.scarlet.be [83.134.254.6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: obonaventure@smtp1.sgsi.ucl.ac.be) by smtp1.sgsi.ucl.ac.be (Postfix) with ESMTPSA id E4559E8908; Thu,  4 Jun 2009 09:48:41 +0200 (CEST)
X-DKIM: Sendmail DKIM Filter v2.8.2 smtp1.sgsi.ucl.ac.be E4559E8908
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1244101722; bh=ZJ4lHUV66544Xcy4/L32ZwUfcNCj0HMJ40mAtQz4Zss=; h=Message-ID:Date:From:Reply-To:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=YT/SFY4sFMimMxt0z/nHfxhJJrVxIH9DuOkfJGlU7vZdW2ahvZ74B99iX+ZkXOrOd uaxiqobTQA+lsq6RrHGpSwkWkoMBuYoaZ+rOvMzPB16nb1Wzzg9mTPaG24TP4WoHwT SOk3n62E0dRHRm+PTfI4ctpFo25Re9KfhV6Owjpg=
Message-ID: <4A277C57.4060106@uclouvain.be>
Date: Thu, 04 Jun 2009 09:48:39 +0200
From: Olivier Bonaventure <Olivier.Bonaventure@uclouvain.be>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: Geoff Huston <gih@apnic.net>
References: <4A26A959.7060104@piuha.net> <687F04C5-5D29-4060-A877-912E710D1A37@apnic.net>
In-Reply-To: <687F04C5-5D29-4060-A877-912E710D1A37@apnic.net>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.95.1
X-Virus-Status: Clean
X-Sgsi-Spamcheck: SASL authenticated, 
X-SGSI-MailScanner-ID: E4559E8908.00000
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: olivier.bonaventure@uclouvain.be
X-SGSI-Spam-Status: No
X-Mailman-Approved-At: Fri, 05 Jun 2009 17:28:27 -0700
Cc: shim6@ietf.org
Subject: Re: [shim6] next steps for the shim6 wg
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Olivier.Bonaventure@uclouvain.be
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2009 07:49:07 -0000

Geoff,

> This looks reasonable to me.
> 
> The usual caveat applies, though - there needs to be interest to
> actually do this work. Right now there is a single API draft in the
> works, but nothing current in the other proposed areas.

...

> 
> On 04/06/2009, at 2:48 AM, Jari Arkko wrote:

...

>> The starting point for this proposal was that we have the following
>> possible work:
>>
>> 1. implementation, testing, and deployment reports

For this, Sébastien Barré wrote a detailed implementation report that
describes his choices in implementing shim6 in the Linux kernel

http://tools.ietf.org/html/draft-barre-shim6-impl-02

Sébastien's implementation is freely available and can be used for
testing and deployment efforts. We would be happy to collaborate with
such efforts. Same for interoperability testing with other mature
implementations.


Olivier

-- 
http://inl.info.ucl.ac.be , UCLouvain, Belgium

From thomas.r.henderson@boeing.com  Mon Jun  8 08:26:31 2009
Return-Path: <thomas.r.henderson@boeing.com>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 597363A6D9C for <shim6@core3.amsl.com>; Mon,  8 Jun 2009 08:26:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Level: 
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XpbXGsnwKgFX for <shim6@core3.amsl.com>; Mon,  8 Jun 2009 08:26:29 -0700 (PDT)
Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by core3.amsl.com (Postfix) with ESMTP id 10DFA3A6D26 for <shim6@ietf.org>; Mon,  8 Jun 2009 08:26:29 -0700 (PDT)
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n58FQKNh023076 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Jun 2009 08:26:22 -0700 (PDT)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n58FQK9F000041; Mon, 8 Jun 2009 08:26:20 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n58FQJnq000008; Mon, 8 Jun 2009 08:26:19 -0700 (PDT)
Received: from XCH-NW-5V1.nw.nos.boeing.com ([130.247.55.44]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959);  Mon, 8 Jun 2009 08:26:09 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 8 Jun 2009 08:26:09 -0700
Message-ID: <77F357662F8BFA4CA7074B0410171B6D07B0C2FD@XCH-NW-5V1.nw.nos.boeing.com>
In-Reply-To: <4A28ECE6.1070605@uclouvain.be>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [shim6] next steps for the shim6 wg
Thread-Index: AcnlxN0qzNHuOU3GRXWc6ilbQJVhCgCh5mnw
References: <4A26A959.7060104@piuha.net><687F04C5-5D29-4060-A877-912E710D1A37@apnic.net><4A277DA1.2010502@uclouvain.be> <4A277E05.6090103@piuha.net><4A277E53.50506@uclouvain.be> <4A28ECE6.1070605@uclouvain.be>
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: =?iso-8859-1?Q?S=E9bastien_Barr=E9?= <sebastien.barre@uclouvain.be>, "Jari Arkko" <jari.arkko@piuha.net>
X-OriginalArrivalTime: 08 Jun 2009 15:26:09.0925 (UTC) FILETIME=[732D6350:01C9E84D]
Cc: shim6@ietf.org, Olivier.Bonaventure@uclouvain.be
Subject: Re: [shim6] next steps for the shim6 wg
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jun 2009 15:26:31 -0000

=20

> -----Original Message-----
> From: S=E9bastien Barr=E9 [mailto:sebastien.barre@uclouvain.be]=20
> Sent: Friday, June 05, 2009 3:01 AM
> To: Jari Arkko
> Cc: shim6@ietf.org; Olivier.Bonaventure@uclouvain.be
> Subject: Re: [shim6] next steps for the shim6 wg
>=20
> Hi,
>=20
> As explained by Olivier. I can use my current implementation report=20
> draft as a starting point for this work.
> Currently the structure of the impl report is to list in=20
> details Shim6=20
> features, and check which of them are implemented in the=20
> latest LinShim6=20
> version.
>=20
> Based on comments on this mailing list, I can update the=20
> format so that=20
> it fits better with a "standard" implementation report. If=20
> other mature=20
> implementations are available, they can be added to the draft. Beside=20
> LinShim6 which I authored, I only know about the Boeing=20
> implementation,=20
> which does not support the security stuff, though (HBA/CGA).
>=20
> regards,
>=20
> S=E9bastien.
>=20

Hi, we've previously published our shim6 documentation at this site:
http://www.openhip.org/docs/shim6.html
and code here:
http://sourceforge.net/project/showfiles.php?group_id=3D132288
in case this information can be of any use to the implementation report. =
=20
We haven't been actively working on shim6 for over a year, though.=20
Sebastien is right that we did not implement HBA/CGA but rather focused
on the multihoming and REAP behavior and how it might tie into HIP.

Regards,
Tom


From samu.varjonen@hiit.fi  Tue Jun  9 02:11:20 2009
Return-Path: <samu.varjonen@hiit.fi>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 83A0B28C0FC for <shim6@core3.amsl.com>; Tue,  9 Jun 2009 02:11:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ARHMXbmPPDdl for <shim6@core3.amsl.com>; Tue,  9 Jun 2009 02:11:19 -0700 (PDT)
Received: from creon.otaverkko.fi (creon.otaverkko.fi [212.68.0.5]) by core3.amsl.com (Postfix) with ESMTP id A211B28C15E for <shim6@ietf.org>; Tue,  9 Jun 2009 02:11:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by creon.otaverkko.fi (Postfix) with ESMTP id E67CD21AF39; Tue,  9 Jun 2009 12:11:24 +0300 (EEST)
Received: from creon.otaverkko.fi ([127.0.0.1]) by localhost (creon.otaverkko.fi [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15786-05; Tue,  9 Jun 2009 12:11:18 +0300 (EEST)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by creon.otaverkko.fi (Postfix) with ESMTP id C7A2821AF3A; Tue,  9 Jun 2009 12:11:18 +0300 (EEST)
Received: from [128.214.114.26] (midian.pc.hiit.fi [128.214.114.26]) by argo.otaverkko.fi (Postfix) with ESMTP id BF5DB25ED06; Tue,  9 Jun 2009 12:11:18 +0300 (EEST)
Message-ID: <4A2E2736.1060905@hiit.fi>
Date: Tue, 09 Jun 2009 12:11:18 +0300
From: Varjonen Samu <samu.varjonen@hiit.fi>
User-Agent: Thunderbird 2.0.0.21 (X11/20090409)
MIME-Version: 1.0
To: Shinta Sugimoto <shinta@sfc.wide.ad.jp>
References: <4A1E5122.6000709@hiit.fi> <4A25DFAC.6020305@sfc.wide.ad.jp>
In-Reply-To: <4A25DFAC.6020305@sfc.wide.ad.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at otaverkko.fi
Cc: shim6@ietf.org
Subject: Re: [shim6] Comments on the draft-ietf-shim6-multihome-shim-api-08
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Jun 2009 09:11:20 -0000

Hi,

Left out the OK parts and left the unclear parts.

Shinta Sugimoto wrote:

>> Section 4. Requirements. To me it looks like the requirements is 
>> missing one important case. Application may want to set used addresses 
>> (SHIM_LOC_*_RECVs and SHIM_LOC_*_SENDs). The current version looks 
>> like applications only need to obtain the information from shim 
>> sub-layer.
> 
> I don't think I am following you hear.  Could you elaborate more about 
> SHIM_LOC_*_RECVs and SHIM_LOC_*_SENDs?  What do you mean by "used 
> addresses"?
> 

Well if we forget about the SHIM_LOC_*_RECVs and SHIM_LOC_*_SENDs for 
now. I meant that for me it looked like the requirements did not include 
the possibility for the application to tell to the shim sub-layer that 
use this address as the src when sending. This actually is covered by 
RFC 5014 and simple bind(). There is nothing shim specific that would 
differ from 5014, I guess?

BR,
Samu Varjonen

From shinta@sfc.wide.ad.jp  Tue Jun  9 19:24:06 2009
Return-Path: <shinta@sfc.wide.ad.jp>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 867EC3A685D for <shim6@core3.amsl.com>; Tue,  9 Jun 2009 19:24:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.904
X-Spam-Level: 
X-Spam-Status: No, score=0.904 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RELAY_IS_203=0.994]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J+3wh8tbLQP2 for <shim6@core3.amsl.com>; Tue,  9 Jun 2009 19:24:05 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (mail.sfc.wide.ad.jp [203.178.142.146]) by core3.amsl.com (Postfix) with ESMTP id AB2DE3A6830 for <shim6@ietf.org>; Tue,  9 Jun 2009 19:24:05 -0700 (PDT)
Received: from localhost.localdomain (unknown [IPv6:2001:380:633:2:20b:cdff:fefb:2a8]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 565074C09E; Wed, 10 Jun 2009 11:24:07 +0900 (JST)
Message-ID: <4A2F1797.2060908@sfc.wide.ad.jp>
Date: Wed, 10 Jun 2009 11:16:55 +0900
From: Shinta Sugimoto <shinta@sfc.wide.ad.jp>
User-Agent: Thunderbird 2.0.0.6 (X11/20070809)
MIME-Version: 1.0
To: Varjonen Samu <samu.varjonen@hiit.fi>
References: <4A1E5122.6000709@hiit.fi> <4A25DFAC.6020305@sfc.wide.ad.jp> <4A2E2736.1060905@hiit.fi>
In-Reply-To: <4A2E2736.1060905@hiit.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: shim6@ietf.org
Subject: Re: [shim6] Comments on the draft-ietf-shim6-multihome-shim-api-08
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jun 2009 02:24:06 -0000

Varjonen Samu wrote:
> Hi,
> 
> Left out the OK parts and left the unclear parts.
> 
> Shinta Sugimoto wrote:
> 
>>> Section 4. Requirements. To me it looks like the requirements is 
>>> missing one important case. Application may want to set used 
>>> addresses (SHIM_LOC_*_RECVs and SHIM_LOC_*_SENDs). The current 
>>> version looks like applications only need to obtain the information 
>>> from shim sub-layer.
>>
>> I don't think I am following you hear.  Could you elaborate more about 
>> SHIM_LOC_*_RECVs and SHIM_LOC_*_SENDs?  What do you mean by "used 
>> addresses"?
>>
> 
> Well if we forget about the SHIM_LOC_*_RECVs and SHIM_LOC_*_SENDs for 
> now. I meant that for me it looked like the requirements did not include 
> the possibility for the application to tell to the shim sub-layer that 
> use this address as the src when sending. This actually is covered by 
> RFC 5014 and simple bind(). There is nothing shim specific that would 
> differ from 5014, I guess?

Hi Samu,

I think now I understand what you are talking about.
Actually the API provides a tool for applications to specify src/dst 
locators as you mentioned.  Src/dst locator selection can be made by 
application using SHIM_LOC_LOCAL_SEND and SHIM_LOC_PEER_SEND.  See 
section 5.9 and 5.10 for details.  On the other hand, I notice (thanks 
to your comments) that the current document does not clearly address 
requirements from applications about the src/dst locator selection.  Let 
us revise Section 4 (Requirements) accordingly.

Please note that our API is dealing with locator selection and not 
identifier selection.  The socket options that I mentioned above allows 
applications to specify source and/or destination locator when sending 
IP packets.  The reason why we only focus on the locator selection is 
that we believe identifier selection can/should be made by the existing 
mechanism (e.g., RFC 3484, RFC 5014).  In general, application may or 
may not specify its source address when initiating a session.  In the 
former case, application explicitly specifies the source address by 
using the bind() system call as you mentioned.  In the latter case, the 
kernel selects the source address as per RFC 3484.  In any case, the IP 
address selected (either by app or kernel) can be considered as an 
identifier in the ID/Locator context.  It is because the IP address is 
regarded as an communication endpoint to the upper layer protocols.  And 
we do not intend to make any changes to the existing src/dst address 
selection mechanisms.

Hope this helps.

Regards,
Shinta

From samu.varjonen@hiit.fi  Tue Jun  9 23:30:02 2009
Return-Path: <samu.varjonen@hiit.fi>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A08D3A6CC6 for <shim6@core3.amsl.com>; Tue,  9 Jun 2009 23:30:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d75riH2xgHdy for <shim6@core3.amsl.com>; Tue,  9 Jun 2009 23:29:55 -0700 (PDT)
Received: from creon.otaverkko.fi (creon.otaverkko.fi [212.68.0.5]) by core3.amsl.com (Postfix) with ESMTP id 14B773A6C9D for <shim6@ietf.org>; Tue,  9 Jun 2009 23:29:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by creon.otaverkko.fi (Postfix) with ESMTP id 0EE4A21AF43; Wed, 10 Jun 2009 09:30:00 +0300 (EEST)
Received: from creon.otaverkko.fi ([127.0.0.1]) by localhost (creon.otaverkko.fi [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13151-01; Wed, 10 Jun 2009 09:29:55 +0300 (EEST)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by creon.otaverkko.fi (Postfix) with ESMTP id 6EB4021AF3F; Wed, 10 Jun 2009 09:29:55 +0300 (EEST)
Received: from [192.168.1.11] (cs181123046.pp.htv.fi [82.181.123.46]) by argo.otaverkko.fi (Postfix) with ESMTP id 6103925ED06; Wed, 10 Jun 2009 09:29:55 +0300 (EEST)
Message-ID: <4A2F52DE.6090207@hiit.fi>
Date: Wed, 10 Jun 2009 09:29:50 +0300
From: Samu Varjonen <samu.varjonen@hiit.fi>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Shinta Sugimoto <shinta@sfc.wide.ad.jp>
References: <4A1E5122.6000709@hiit.fi> <4A25DFAC.6020305@sfc.wide.ad.jp> <4A2E2736.1060905@hiit.fi> <4A2F1797.2060908@sfc.wide.ad.jp>
In-Reply-To: <4A2F1797.2060908@sfc.wide.ad.jp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: amavisd-new at otaverkko.fi
Cc: shim6@ietf.org
Subject: Re: [shim6] Comments on the draft-ietf-shim6-multihome-shim-api-08
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Jun 2009 06:30:02 -0000

Shinta Sugimoto kirjoitti:
> Varjonen Samu wrote:
>> Hi,
>>
>> Left out the OK parts and left the unclear parts.
>>
>> Shinta Sugimoto wrote:
>>
>>>> Section 4. Requirements. To me it looks like the requirements is 
>>>> missing one important case. Application may want to set used 
>>>> addresses (SHIM_LOC_*_RECVs and SHIM_LOC_*_SENDs). The current 
>>>> version looks like applications only need to obtain the information 
>>>> from shim sub-layer.
>>>
>>> I don't think I am following you hear.  Could you elaborate more 
>>> about SHIM_LOC_*_RECVs and SHIM_LOC_*_SENDs?  What do you mean by 
>>> "used addresses"?
>>>
>>
>> Well if we forget about the SHIM_LOC_*_RECVs and SHIM_LOC_*_SENDs for 
>> now. I meant that for me it looked like the requirements did not 
>> include the possibility for the application to tell to the shim 
>> sub-layer that use this address as the src when sending. This actually 
>> is covered by RFC 5014 and simple bind(). There is nothing shim 
>> specific that would differ from 5014, I guess?
> 
> Hi Samu,
> 
> I think now I understand what you are talking about.
> Actually the API provides a tool for applications to specify src/dst 
> locators as you mentioned.  Src/dst locator selection can be made by 
> application using SHIM_LOC_LOCAL_SEND and SHIM_LOC_PEER_SEND.  See 
> section 5.9 and 5.10 for details.  On the other hand, I notice (thanks 
> to your comments) that the current document does not clearly address 
> requirements from applications about the src/dst locator selection.  Let 
> us revise Section 4 (Requirements) accordingly.
> 
> Please note that our API is dealing with locator selection and not 
> identifier selection.  The socket options that I mentioned above allows 
> applications to specify source and/or destination locator when sending 
> IP packets.  The reason why we only focus on the locator selection is 
> that we believe identifier selection can/should be made by the existing 
> mechanism (e.g., RFC 3484, RFC 5014).  In general, application may or 
> may not specify its source address when initiating a session.  In the 
> former case, application explicitly specifies the source address by 
> using the bind() system call as you mentioned.  In the latter case, the 
> kernel selects the source address as per RFC 3484.  In any case, the IP 
> address selected (either by app or kernel) can be considered as an 
> identifier in the ID/Locator context.  It is because the IP address is 
> regarded as an communication endpoint to the upper layer protocols.  And 
> we do not intend to make any changes to the existing src/dst address 
> selection mechanisms.
> 

Identifiers, that was the thing that was nagging me with the bind. 
Thanks for reminding :)

> Hope this helps.
> 
> Regards,
> Shinta


-- 
BR,
Samu

"Programmer is an organism that changes caffeine into code"

From iljitsch@muada.com  Sat Jun 20 04:04:12 2009
Return-Path: <iljitsch@muada.com>
X-Original-To: shim6@core3.amsl.com
Delivered-To: shim6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4962E3A6A44 for <shim6@core3.amsl.com>; Sat, 20 Jun 2009 04:04:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.247
X-Spam-Level: 
X-Spam-Status: No, score=-5.247 tagged_above=-999 required=5 tests=[AWL=-0.867, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, TVD_SPACE_RATIO=2.219]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vX8OiAZ1PcAb for <shim6@core3.amsl.com>; Sat, 20 Jun 2009 04:04:11 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [83.149.65.1]) by core3.amsl.com (Postfix) with ESMTP id 405043A6809 for <shim6@ietf.org>; Sat, 20 Jun 2009 04:04:10 -0700 (PDT)
Received: from [192.168.2.4] (static-167-138-7-89.ipcom.comunitel.net [89.7.138.167] (may be forged)) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n5KB4OxA022157 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <shim6@ietf.org>; Sat, 20 Jun 2009 13:04:25 +0200 (CEST) (envelope-from iljitsch@muada.com)
Message-Id: <26E73667-5B41-43E3-9D8E-80E03EC82753@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: shim6@ietf.org
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Sat, 20 Jun 2009 13:03:51 +0200
X-Mailer: Apple Mail (2.935.3)
Subject: [shim6] Tada
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Jun 2009 11:04:12 -0000

http://www.ibiblio.org/pub/multimedia/pc-sounds/tada.wav

http://tools.ietf.org/rfc/rfc5533.txt
http://tools.ietf.org/rfc/rfc5534.txt
http://tools.ietf.org/rfc/rfc5535.txt

From root@core3.amsl.com  Tue Jun 23 13:30:01 2009
Return-Path: <root@core3.amsl.com>
X-Original-To: shim6@ietf.org
Delivered-To: shim6@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id 887EC3A6C63; Tue, 23 Jun 2009 13:30:00 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: ietf-announce@ietf.org
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20090623203001.887EC3A6C63@core3.amsl.com>
Date: Tue, 23 Jun 2009 13:30:01 -0700 (PDT)
Cc: shim6@ietf.org
Subject: [shim6] WG Review: Recharter of Site Multihoming by IPv6 Intermediation (shim6)
X-BeenThere: shim6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: iesg@ietf.org
List-Id: SHIM6 Working Group Mailing List <shim6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/shim6>
List-Post: <mailto:shim6@ietf.org>
List-Help: <mailto:shim6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shim6>, <mailto:shim6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jun 2009 20:30:01 -0000

A modified charter has been submitted for the Site Multihoming by IPv6
Intermediation (shim6) working group in the Internet Area of the IETF. 
The IESG has not made any determination as yet.  The modified charter is
provided below for informational purposes only.  Please send your comments
to the IESG mailing list (iesg@ietf.org) by Tuesday, June 30, 2009.

Site Multihoming by IPv6 Intermediation (shim6)
===============================================

Last Modified: 2009-06-17

Current Status: Active Working Group 

Additional information is available at tools.ietf.org/wg/shim6

Chair(s):
Kurt Lindqvist <kurtis@kurtis.pp.se>
Geoff Huston <gih@apnic.net>

Internet Area Director(s):
Ralph Droms <rdroms@cisco.com>
Jari Arkko <jari.arkko@piuha.net>

Internet Area Advisor:
Jari Arkko <jari.arkko@piuha.net>

Technical Advisor(s):
Thomas Narten <narten@us.ibm.com>

Mailing Lists:
General Discussion: shim6@ietf.org
To Subscribe: https://www.ietf.org/mailman/listinfo/shim6
Archive: http://www.ietf.org/mail-archive/web/shim6/current/maillist.html

Description of Working Group:

Earlier efforts in this working group completed the Shim6 protocol
specification, documented in RFCs 5533 through 5535. This protocol is
a layer 3 shim for providing locator agility with failover
capabilities for IPv6 nodes. Hosts that employ Shim6 use multiple IPv6
address prefixes and setup state with peer hosts. This state can later
be used to failover to a different set of locators, should the
original locators stop working.

The Shim6 approach has a number of advantages, such as enabling small
sites to be multihomed without requiring a provider independent IPv6
address prefix for the site. But the approach has also been
criticized, e.g., for the operational impacts that the use of multiple
prefixes causes. At this time there is no clear view on how well Shim6
works in practice. Implementation and deployment in select networks is
needed to determine its true characteristics.

The Shim6 working group is chartered to track the implementation and
testing or deployment efforts. The group is also expected to shepherd
to completion a few remaining informational documents that complement
the existing protocol specifications.

The specific work items of the group are:

o Write an implementation and/or deployment experience report.

o Specify socket API extensions. This API enables interactions between
applications and the Shim6 layer for advanced locator management,
and access to information about failure detection and path
exploration. It also enables some applications to turn Shim6 off.

o Complete the work on the applicability draft. This draft explains
in detail in which types of networks Shim6 is applicable, and
what its advantages and disadvantages are. The draft will also
explain how firewalls are impacted by the use of Shim6. Finally,
the draft will also explain how Shim6 can be used in situations
where native IPv6 connectivity is not available, such as using
Shim6 over 6to4.

The group will also work in co-operation with the 6MAN working group
as they continue their efforts in improving IPv6 address selection
mechanisms.

The group shall not work on extensions to the Shim6 protocol itself at
this time. However, new work items can be added through rechartering
as others get completed.

Goals and Milestones:

Sep 2009 Next revision of the API document
Nov 2009 First WG draft on an implementation report
Jan 2010 Submit API document to IESG for publication as Informational RFC
Jan 2010 Next revision of the applicability document
Dec 2010 Submit implementation report to IESG for publication as
Informational RFC
Dec 2010 Submit applicability document to IESG for publication as
Informational RFC
Dec 2010 Close or re-charter
