
From iljitsch@muada.com  Mon Jul  6 13:48:04 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 3F98E3A6DD1 for <shim6@core3.amsl.com>; Mon,  6 Jul 2009 13:48:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.445
X-Spam-Level: 
X-Spam-Status: No, score=-6.445 tagged_above=-999 required=5 tests=[AWL=0.154,  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 dZDQv4ycDVMN for <shim6@core3.amsl.com>; Mon,  6 Jul 2009 13:48:03 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [83.149.65.1]) by core3.amsl.com (Postfix) with ESMTP id 2100C3A6DD2 for <shim6@ietf.org>; Mon,  6 Jul 2009 13:48:02 -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 n66KlMpo053687 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <shim6@ietf.org>; Mon, 6 Jul 2009 22:47:23 +0200 (CEST) (envelope-from iljitsch@muada.com)
Message-Id: <67E3E1F0-6126-4859-AF85-FAFA6B2CCDE8@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, 6 Jul 2009 22:47:19 +0200
References: <20090706204013.00AE13A6DAF@core3.amsl.com>
X-Mailer: Apple Mail (2.935.3)
Subject: [shim6] Fwd: New Version Notification for draft-van-beijnum-shim6-shim6to4-00
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, 06 Jul 2009 20:48:04 -0000

Hi,

At the last IETF meeting Erik and me had a short discussion about  
(ab)using 6to4 for making shim6 compatible with IPv4. Unfortunately I  
have since forgotton our discussion, which had some fairly intricate  
ideas although it only took 10 minutes, but I wrote down how to make  
6to4 and shim6 work together, which is all fairly obvious. If anyone  
has any better ideas or cool optimizations, let me know.

Iljitsch

http://www.ietf.org/internet-drafts/draft-van-beijnum-shim6-shim6to4-00.txt

Begin forwarded message:

> From: IETF I-D Submission Tool <idsubmission@ietf.org>
> Date: 6 juli 2009 22:40:12 GMT+02:00
> To: iljitsch@muada.com
> Subject: New Version Notification for draft-van-beijnum-shim6- 
> shim6to4-00
>
>
> A new version of I-D, draft-van-beijnum-shim6-shim6to4-00.txt has  
> been successfuly submitted by Iljitsch van Beijnum and posted to the  
> IETF repository.
>
> Filename:	 draft-van-beijnum-shim6-shim6to4
> Revision:	 00
> Title:		 Shim6 with IPv4 locators through 6to4
> Creation_date:	 2009-07-06
> WG ID:		 Independent Submission
> Number_of_pages: 6
>
> Abstract:
> A limitation of Shim6 is that it only works with IPv6.  With 6to4, it
> is possible for hosts that only have IPv4 connectivity to still enjoy
> Shim6's multihoming benefits.
>
>
>
> The IETF Secretariat.
>


From root@core3.amsl.com  Tue Jul  7 14:15:02 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 266E53A688C; Tue,  7 Jul 2009 14:15:02 -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: <20090707211502.266E53A688C@core3.amsl.com>
Date: Tue,  7 Jul 2009 14:15:02 -0700 (PDT)
Cc: shim6@ietf.org
Subject: [shim6] WG Action: RECHARTER: Site Multihoming by IPv6 Intermediation (shim6)
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, 07 Jul 2009 21:15:02 -0000

The Site Multihoming by IPv6 Intermediation (shim6) working group in the
Internet Area of the IETF has been rechartered.  For additional
information, please contact the Area Directors or the working group
Chairs.

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

From iljitsch@muada.com  Mon Jul 13 13:35:07 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 11B1028C495 for <shim6@core3.amsl.com>; Mon, 13 Jul 2009 13:35:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.464
X-Spam-Level: 
X-Spam-Status: No, score=-6.464 tagged_above=-999 required=5 tests=[AWL=0.135,  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 QFyPS--R1MCv for <shim6@core3.amsl.com>; Mon, 13 Jul 2009 13:35:06 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [83.149.65.1]) by core3.amsl.com (Postfix) with ESMTP id 3B46828C6AD for <shim6@ietf.org>; Mon, 13 Jul 2009 13:33:55 -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 n6DKXIQd033271 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 13 Jul 2009 22:33:19 +0200 (CEST) (envelope-from iljitsch@muada.com)
Message-Id: <73447B6F-F90C-4033-BD34-A0090BAE080E@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <4A5A0010.6050101@gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Mon, 13 Jul 2009 22:33:19 +0200
References: <20090706204501.EC6E33A6DA1@core3.amsl.com> <4A5A0010.6050101@gmail.com>
X-Mailer: Apple Mail (2.935.3)
Cc: shim6@ietf.org
Subject: Re: [shim6] I-D Action:draft-van-beijnum-shim6-shim6to4-00.txt
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, 13 Jul 2009 20:35:07 -0000

On 12 jul 2009, at 17:24, Brian E Carpenter wrote:

> I think this works.

Excellent. I submitted a new version based on your comments:

http://www.ietf.org/internet-drafts/draft-van-beijnum-shim6-shim6to4-01.txt

From shinta@sfc.wide.ad.jp  Tue Jul 14 23:17:45 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 9069D3A689E for <shim6@core3.amsl.com>; Tue, 14 Jul 2009 23:17:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.669
X-Spam-Level: *
X-Spam-Status: No, score=1.669 tagged_above=-999 required=5 tests=[AWL=0.765,  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 9a0nJQpWxl3D for <shim6@core3.amsl.com>; Tue, 14 Jul 2009 23:17:44 -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 AFA983A6860 for <shim6@ietf.org>; Tue, 14 Jul 2009 23:17:44 -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 DBB394C0BC; Wed, 15 Jul 2009 15:15:42 +0900 (JST)
Message-ID: <4A5D71F5.2010604@sfc.wide.ad.jp>
Date: Wed, 15 Jul 2009 15:06:45 +0900
From: Shinta Sugimoto <shinta@sfc.wide.ad.jp>
User-Agent: Thunderbird 2.0.0.6 (X11/20070809)
MIME-Version: 1.0
To: Kurt Lindqvist <kurtis@kurtis.pp.se>, Geoff Huston <gih@apnic.net>
Content-Type: text/plain; charset=ISO-2022-JP
Content-Transfer-Encoding: 7bit
Cc: shim6@ietf.org
Subject: [shim6] status and plan of draft-ietf-shim6-multihome-shim-api
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, 15 Jul 2009 06:17:45 -0000

Dear SHIM6 WG chairs, and all,

Representing the co-authors of the draft, let me explain the status and
plan of the multihome shim API draft.

The latest version of the draft can be found at the following URL:
http://tools.ietf.org/id/draft-ietf-shim6-multihome-shim-api-09.txt

The document as it stands (09) is not ready for WGLC and there are some
remaining issues:

- We need to figure out which socket options are valid for which types
(i.e., connected/unconnected) of sockets. Some of the socket options
such as SHIM_ASSOCIATED are not valid for unconnected sockets. We have
not done sanity check for all the socket options yet. So the sanity
check and providing descriptions about error handling (e.g., what errno
should be returned when application makes an false attempt) shall be
done.

- We are not aware of any implementation of the socket API extensions so
far. I understand that implementation report would be valuable to see if
the document defines enough details.  We are going to ask HIP/SHIM6
implementers to implement some of the socket options that relate to
locator management, and some of us (co-authors) are also planning to
implement those on Linux and BSD platforms.  In anycase, we hope we can
present at least one implementation to show feasibility of the API
before going for the WGLC and IESG review.

- We need feedbacks from application programmers. We have not succeeded
to receive feedbacks, but we will try by solicitating comments on the
ietf apps-discuss ML.

When it comes to timeline, we aim to go for WGLC before the Hiroshima
IETF meeting.  So, we are planning to complete the remaining issues by
mid October, and we think 2.5 months for the above tasks are doable.

Regards,
Shinta

From iljitsch@muada.com  Tue Jul 28 07:01:36 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 E06A23A6F41 for <shim6@core3.amsl.com>; Tue, 28 Jul 2009 07:01:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.214
X-Spam-Level: 
X-Spam-Status: No, score=-6.214 tagged_above=-999 required=5 tests=[AWL=-0.215, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, 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 wzawSA30Li-9 for <shim6@core3.amsl.com>; Tue, 28 Jul 2009 07:01:36 -0700 (PDT)
Received: from sequoia.muada.com (sequoia.muada.com [83.149.65.1]) by core3.amsl.com (Postfix) with ESMTP id C9F603A6F43 for <shim6@ietf.org>; Tue, 28 Jul 2009 07:01:35 -0700 (PDT)
Received: from dhcp-55f3.meeting.ietf.org (dhcp-55f3.meeting.ietf.org [130.129.85.243] (may be forged)) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id n6SE0tcM076723 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 28 Jul 2009 16:00:56 +0200 (CEST) (envelope-from iljitsch@muada.com)
Message-Id: <495C8CA9-5146-48E8-A3FE-3063D6A9ED2F@muada.com>
From: Iljitsch van Beijnum <iljitsch@muada.com>
To: IPv6 Operations <v6ops@ops.ietf.org>, 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: Tue, 28 Jul 2009 16:01:11 +0200
X-Mailer: Apple Mail (2.935.3)
Subject: [shim6] about draft-ietf-v6ops-cpe-simple-security-07
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, 28 Jul 2009 14:01:37 -0000

[to v6ops and shim6, prune as necessary]

    R11: Filter state records for generic upper-layer transport  
protocols
    MUST NOT be deleted or recycled until an idle timer not less than  
two
    minutes has expired without having forwarded a packet matching the
    state in some configurable amount of time.  By DEFAULT, the idle
    timer for such state records is five minutes.

That seems rather short: new transports would now have to send  
keepalives every 1.75 minutes. I'd say that a timeout MUST be at least  
11 minutes and preferably 124 minutes, like TCP.

If the timers for unknown transports are compatible with those needed  
for SCTP and DCCP then implementers can forego handling those  
explicitly but they'll still work.

3.2.4.  6to4 Tunnels

    Typical dual-stack IPv4/IPv6 residential gateways use private IPv4
    address ranges and network address/port translation on a single IPv4
    address assigned by the service provider.  The use of private
    addresses prevents interior hosts from using 6to4 [RFC3068] tunnels.

Usually the private addresses are on the inside and a public on the  
outside (which will presumably start to change as IPv4 depletes but  
will never completely go away) so 6to4 can work just fine in those  
cases.

    The use of Level 3 Multihoming Shim
    Protocol for IPv6 (SHIM6) [I-D.ietf-shim6-proto] as a site multi-
    homing solution is not generally compatible with IPv6 simple
    security.

(Now RFC 5533.) Why? Assuming that there are two CPEs with each an ISP  
link and advertising separate address ranges, then if the host sends  
normal packets over CPE A and then when the ISP connected to CPE A  
fails, the host can send protocol 140 signaling and encapsulated data  
packets to CPE B. This should work. An optimization would be to allow  
incoming protocol 140 whenever there is communication between an  
internal and external host already, whatever the type. (Without that,  
the shim6 signaling fails when the first host initiates it and only  
succeeds if the second host initiates it soon enough after.)
