
From brian.e.carpenter@gmail.com  Tue Mar  8 11:54:53 2011
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 BC0923A6959 for <shim6@core3.amsl.com>; Tue,  8 Mar 2011 11:54:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.699
X-Spam-Level: 
X-Spam-Status: No, score=-102.699 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 baa6rdgR10TF for <shim6@core3.amsl.com>; Tue,  8 Mar 2011 11:54:53 -0800 (PST)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id ADE703A6814 for <shim6@ietf.org>; Tue,  8 Mar 2011 11:54:52 -0800 (PST)
Received: by fxm15 with SMTP id 15so5940475fxm.31 for <shim6@ietf.org>; Tue, 08 Mar 2011 11:56:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=KepZ1mKUvro42fHex4EF00XlMgPbRoN4okj28YOJedg=; b=nWhCOpFM6r++YKx2KxRyxYexKrlESS85O6yZ+13zolU8ZYSlxds8EL7FQiN/jzxfKb +IQtMisL1oEftx8zMajn2Cbaw1JEEJRE8WRDyIDd/mhpk3LXqfBSOwcEoTz5l1O1HN40 Z3xep0wDCLx9RRZD3GGL+lKgfBxdg/Qh/47ng=
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=hylVX4ieMimrKG0ptnnI66zIimridtsSjkCkpjn0w6wX0GLvHKxhKYfc7KseyrLgqe r1uGZkIaTJyNLGcf/sItxwRWUySvrUeInCXBHEePdK209RWLlKqE+SUtgdkmRQ4ZEseZ OWLF9S3xex1HXPRHLsI6nAk0YwG2zD6Os82tM=
Received: by 10.223.127.210 with SMTP id h18mr4334700fas.46.1299614167481; Tue, 08 Mar 2011 11:56:07 -0800 (PST)
Received: from [192.168.2.167] (202-180-96-58.callplus.net.nz [202.180.96.58]) by mx.google.com with ESMTPS id j11sm536247faa.20.2011.03.08.11.56.02 (version=SSLv3 cipher=OTHER); Tue, 08 Mar 2011 11:56:06 -0800 (PST)
Message-ID: <4D7689CC.7060409@gmail.com>
Date: Wed, 09 Mar 2011 08:55:56 +1300
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: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <remi.despres@free.fr>
References: <20110228223003.13022.10464.idtracker@localhost> <845A4F08-46E7-48EE-B294-0C8368BAD1CB@cisco.com> <20110302072822.GA20321@serpens.de> <5AC61190-49B0-49B5-ACB1-1FA5082C0380@cisco.com> <20110302203006.GI23030@serpens.de> <4D6EB08E.9000109@gmail.com> <20110302214913.GG20321@serpens.de> <4D6EC293.90608@gmail.com> <20110303065132.GH20321@serpens.de> <4D6FF098.6010600@gmail.com> <A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr>
In-Reply-To: <A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: shim6-wg <shim6@ietf.org>, "S.P.Zeidler" <spz@serpens.de>
Subject: [shim6] Exit selection [New Version Notification - draft-mrw-nat66-08.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: Tue, 08 Mar 2011 19:54:53 -0000

Diverted from the v6ops list:

On 2011-03-09 06:22, R=C3=A9mi Despr=C3=A9s wrote:
> Le 3 mars 2011 =C3=A0 20:48, Brian E Carpenter a =C3=A9crit :
>> ...
>> Of course. PI has the cost of exploding the BGP4 table.
>> NPTv6 has the cost of destroying address transparency.
>>
>> Since SHIM6 has neither of these costs, are you surprised
>> that I prefer it?
>=20
> SHIM6 is a solution, but AFAIK it needs that hosts know:
> - their global addresses
> - means to force outgoing paths that go via the right CPE's (an ingress=
-filtering constraint)=20

This is well understood to be an issue for shim6.

How about rechartering the WG to resolve this?

The tail end of the charter says:

 Dec 2010  	Submit implementation report to IESG for publication as Infor=
mational RFC
 Dec 2010 	Submit applicability document to IESG for publication as Infor=
mational RFC
 Dec 2010 	Close or re-charter

Where is the implementation report, BTW? And when will the applicability
draft be ready for the IESG?

      Brian

> In a site using ULAs and having several links, a complement is therefor=
e needed.=20
> SAM is an approach for this (ref. draft-despres-softwire-sam-01 - sec. =
3.3), and AFAIK the only documented one so far.
> Would you agree on this?
>=20
> RD
>=20
>=20
>=20
>=20
>=20


From marcelo@it.uc3m.es  Tue Mar  8 13:35:44 2011
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 3E5A13A6767 for <shim6@core3.amsl.com>; Tue,  8 Mar 2011 13:35:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.539
X-Spam-Level: 
X-Spam-Status: No, score=-106.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 rsWRB5ZQ0KZR for <shim6@core3.amsl.com>; Tue,  8 Mar 2011 13:35:43 -0800 (PST)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by core3.amsl.com (Postfix) with ESMTP id 127603A63EC for <shim6@ietf.org>; Tue,  8 Mar 2011 13:35:43 -0800 (PST)
X-uc3m-safe: yes
Received: from marcelo-bagnulos-macbook-pro-2.local (3.31.18.95.dynamic.jazztel.es [95.18.31.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp03.uc3m.es (Postfix) with ESMTP id BBB3B87230D for <shim6@ietf.org>; Tue,  8 Mar 2011 22:36:55 +0100 (CET)
Message-ID: <4D76A175.7020809@it.uc3m.es>
Date: Tue, 08 Mar 2011 22:36:53 +0100
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; es-ES; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: shim6@ietf.org
References: <20110228223003.13022.10464.idtracker@localhost>	<845A4F08-46E7-48EE-B294-0C8368BAD1CB@cisco.com>	<20110302072822.GA20321@serpens.de>	<5AC61190-49B0-49B5-ACB1-1FA5082C0380@cisco.com>	<20110302203006.GI23030@serpens.de> <4D6EB08E.9000109@gmail.com>	<20110302214913.GG20321@serpens.de> <4D6EC293.90608@gmail.com>	<20110303065132.GH20321@serpens.de> <4D6FF098.6010600@gmail.com>	<A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr> <4D7689CC.7060409@gmail.com>
In-Reply-To: <4D7689CC.7060409@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-6.5.0.1024-18000.002
Subject: Re: [shim6] Exit selection [New Version Notification -	draft-mrw-nat66-08.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: Tue, 08 Mar 2011 21:35:44 -0000

El 08/03/11 20:55, Brian E Carpenter escribió:
>
> Where is the implementation report, BTW? And when will the applicability
> draft be ready for the IESG?
>

from the editors side, this is already the case.

>        Brian
>
>> In a site using ULAs and having several links, a complement is therefore needed.
>> SAM is an approach for this (ref. draft-despres-softwire-sam-01 - sec. 3.3), and AFAIK the only documented one so far.
>> Would you agree on this?
>>
>> RD
>>
>>
>>
>>
>>
> _______________________________________________
> shim6 mailing list
> shim6@ietf.org
> https://www.ietf.org/mailman/listinfo/shim6


From sebastien.barre@uclouvain.be  Tue Mar  8 13:55:06 2011
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 D2BB43A659B for <shim6@core3.amsl.com>; Tue,  8 Mar 2011 13:55:06 -0800 (PST)
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 ZGUwROjE8N89 for <shim6@core3.amsl.com>; Tue,  8 Mar 2011 13:55:05 -0800 (PST)
Received: from smtp1.sgsi.ucl.ac.be (smtp.sgsi.ucl.ac.be [130.104.5.67]) by core3.amsl.com (Postfix) with ESMTP id 9536E3A63C9 for <shim6@ietf.org>; Tue,  8 Mar 2011 13:55:05 -0800 (PST)
Received: from [192.168.1.103] (unknown [83.101.32.77]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: sbarre@smtp1.sgsi.ucl.ac.be) by smtp1.sgsi.ucl.ac.be (Postfix) with ESMTPSA id BF648E9853; Tue,  8 Mar 2011 22:56:15 +0100 (CET)
Message-ID: <4D76A5FF.2020704@uclouvain.be>
Date: Tue, 08 Mar 2011 22:56:15 +0100
From: =?UTF-8?B?U8OpYmFzdGllbiBCYXJyw6k=?= <sebastien.barre@uclouvain.be>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); nl; rv:1.9.2.14) Gecko/20110221 Lightning/1.0b2 Thunderbird/3.1.8
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <20110228223003.13022.10464.idtracker@localhost> <845A4F08-46E7-48EE-B294-0C8368BAD1CB@cisco.com> <20110302072822.GA20321@serpens.de> <5AC61190-49B0-49B5-ACB1-1FA5082C0380@cisco.com> <20110302203006.GI23030@serpens.de> <4D6EB08E.9000109@gmail.com> <20110302214913.GG20321@serpens.de> <4D6EC293.90608@gmail.com> <20110303065132.GH20321@serpens.de> <4D6FF098.6010600@gmail.com> <A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr> <4D7689CC.7060409@gmail.com>
In-Reply-To: <4D7689CC.7060409@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.97-exp at smtp-1.sipr-dc.ucl.ac.be
X-Virus-Status: Clean
Received-SPF: Pass (sender authenticated); receiver=; client-ip=83.101.32.77; helo=[192.168.1.103]
Received-SPF: Pass (sender authenticated); receiver=; client-ip=83.101.32.77; envelope-from=<sebastien.barre@uclouvain.be>
X-Sgsi-Spamcheck: SASL authenticated, 
X-SGSI-MailScanner-ID: BF648E9853.00000
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: sebastien.barre@uclouvain.be
X-SGSI-Spam-Status: No
Cc: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <remi.despres@free.fr>, shim6-wg <shim6@ietf.org>, "S.P.Zeidler" <spz@serpens.de>
Subject: Re: [shim6] Exit selection [New Version Notification -	draft-mrw-nat66-08.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: Tue, 08 Mar 2011 21:55:06 -0000

Hi,

Op 08-03-11 20:55, Brian E Carpenter schreef:
>
> Where is the implementation report, BTW?
I have proposed an implementation report a while ago, but received no 
comment about it (as far as I remember).
It is now an expired draft, but I can revive it if there is motivation 
from people to review it. It can still be downloaded from here: 
http://inl.info.ucl.ac.be/publications/shim6-implementation-report-linshim6

If anyone is interested in reviewing/commenting on it, I will be happy 
to apply the comments and do my best to improve it. We can also discuss 
in Prague as I will be there.

regards,

Sébastien.
> And when will the applicability
> draft be ready for the IESG?
>
>        Brian
>
>> In a site using ULAs and having several links, a complement is therefore needed.
>> SAM is an approach for this (ref. draft-despres-softwire-sam-01 - sec. 3.3), and AFAIK the only documented one so far.
>> Would you agree on this?
>>
>> RD
>>
>>
>>
>>
>>
> _______________________________________________
> shim6 mailing list
> shim6@ietf.org
> https://www.ietf.org/mailman/listinfo/shim6

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


From brian.e.carpenter@gmail.com  Tue Mar  8 16:04:52 2011
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 B98C13A67B8 for <shim6@core3.amsl.com>; Tue,  8 Mar 2011 16:04:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.224
X-Spam-Level: 
X-Spam-Status: No, score=-103.224 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 wahkJAlV+iqB for <shim6@core3.amsl.com>; Tue,  8 Mar 2011 16:04:51 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 29FF33A67AB for <shim6@ietf.org>; Tue,  8 Mar 2011 16:04:50 -0800 (PST)
Received: by vws6 with SMTP id 6so6137006vws.31 for <shim6@ietf.org>; Tue, 08 Mar 2011 16:06:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=DOOejW7MzLt7US12HUtvBPI/UcGtrOe5fnoS6zAkm+c=; b=q4RB73+QdEU/MgOKCppCssowY2YDG3n3yo6Q0EILB2WxDhDy75yi0YsRUwt6+KtkIE ki1zWH0f/ZFCu7S4Ky7Km6SyWuxgnXtRXoxiI3HEV4X359yH+LdgcylnZw367cNNnH4t I4XQ6uEaZge6IM19Ckz+81do7ChWmm93hKT8k=
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=BTAWHb2zB7KIFy1r6WEtl9khzCf5z0hQY+s39cxgGpOlgIT3WcN/G3+FF7in9QpJX7 HUeliVPpf/PoNinYCYWgpxCINDFNipd3CpOFR9vHNMhiEUZ/2GNS5px//8uqu1braDdr LeEVMbyfsDZysxQ3j4tTv16/hJjSuJgTZt1Uo=
Received: by 10.52.65.100 with SMTP id w4mr8607283vds.200.1299629162183; Tue, 08 Mar 2011 16:06:02 -0800 (PST)
Received: from [192.168.2.167] (202-180-96-58.callplus.net.nz [202.180.96.58]) by mx.google.com with ESMTPS id b6sm526269vci.24.2011.03.08.16.05.58 (version=SSLv3 cipher=OTHER); Tue, 08 Mar 2011 16:06:01 -0800 (PST)
Message-ID: <4D76C461.30506@gmail.com>
Date: Wed, 09 Mar 2011 13:05:53 +1300
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: =?UTF-8?B?U8OpYmFzdGllbiBCYXJyw6k=?= <sebastien.barre@uclouvain.be>
References: <20110228223003.13022.10464.idtracker@localhost> <845A4F08-46E7-48EE-B294-0C8368BAD1CB@cisco.com> <20110302072822.GA20321@serpens.de> <5AC61190-49B0-49B5-ACB1-1FA5082C0380@cisco.com> <20110302203006.GI23030@serpens.de> <4D6EB08E.9000109@gmail.com> <20110302214913.GG20321@serpens.de> <4D6EC293.90608@gmail.com> <20110303065132.GH20321@serpens.de> <4D6FF098.6010600@gmail.com> <A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr> <4D7689CC.7060409@gmail.com> <4D76A5FF.2020704@uclouvain.be>
In-Reply-To: <4D76A5FF.2020704@uclouvain.be>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: =?UTF-8?B?UsOpbWkgRGVzcHLDqXM=?= <remi.despres@free.fr>, shim6-wg <shim6@ietf.org>, "S.P.Zeidler" <spz@serpens.de>
Subject: Re: [shim6] Exit selection [New Version Notification -	draft-mrw-nat66-08.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: Wed, 09 Mar 2011 00:04:52 -0000

It's for the WG chairs to say, but I think we should pursue this
WG deliverable, *and* recharter to work on the exit selection
issue.

I remain optimistic about shim6. Its time may come in a few years
when the dust has settled from the IPv6 deployment panic. So we
should finish the job.

Regards
   Brian Carpenter

On 2011-03-09 10:56, S=C3=A9bastien Barr=C3=A9 wrote:
> Hi,
>=20
> Op 08-03-11 20:55, Brian E Carpenter schreef:
>>
>> Where is the implementation report, BTW?
> I have proposed an implementation report a while ago, but received no
> comment about it (as far as I remember).
> It is now an expired draft, but I can revive it if there is motivation
> from people to review it. It can still be downloaded from here:
> http://inl.info.ucl.ac.be/publications/shim6-implementation-report-lins=
him6
>=20
> If anyone is interested in reviewing/commenting on it, I will be happy
> to apply the comments and do my best to improve it. We can also discuss=

> in Prague as I will be there.
>=20
> regards,
>=20
> S=C3=A9bastien.
>> And when will the applicability
>> draft be ready for the IESG?
>>
>>        Brian
>>
>>> In a site using ULAs and having several links, a complement is
>>> therefore needed.
>>> SAM is an approach for this (ref. draft-despres-softwire-sam-01 -
>>> sec. 3.3), and AFAIK the only documented one so far.
>>> Would you agree on this?
>>>
>>> RD
>>>
>>>
>>>
>>>
>>>
>> _______________________________________________
>> shim6 mailing list
>> shim6@ietf.org
>> https://www.ietf.org/mailman/listinfo/shim6
>=20


From remi.despres@free.fr  Wed Mar  9 00:18:18 2011
Return-Path: <remi.despres@free.fr>
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 342DA3A6841 for <shim6@core3.amsl.com>; Wed,  9 Mar 2011 00:18:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.259
X-Spam-Level: 
X-Spam-Status: No, score=-1.259 tagged_above=-999 required=5 tests=[AWL=0.690,  BAYES_00=-2.599, HELO_EQ_FR=0.35, 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 zSR9hfMm8Wmz for <shim6@core3.amsl.com>; Wed,  9 Mar 2011 00:18:17 -0800 (PST)
Received: from smtp22.services.sfr.fr (smtp22.services.sfr.fr [93.17.128.12]) by core3.amsl.com (Postfix) with ESMTP id 13F103A6822 for <shim6@ietf.org>; Wed,  9 Mar 2011 00:18:17 -0800 (PST)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2213.sfr.fr (SMTP Server) with ESMTP id 7925D700008F; Wed,  9 Mar 2011 09:19:32 +0100 (CET)
Received: from [192.168.0.14] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2213.sfr.fr (SMTP Server) with ESMTP id E085A7000091; Wed,  9 Mar 2011 09:19:31 +0100 (CET)
X-SFR-UUID: 20110309081931919.E085A7000091@msfrf2213.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <4D76C461.30506@gmail.com>
Date: Wed, 9 Mar 2011 09:19:31 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C3AC5E50-1E3F-4381-A0A4-B5023EBA529B@free.fr>
References: <20110228223003.13022.10464.idtracker@localhost> <845A4F08-46E7-48EE-B294-0C8368BAD1CB@cisco.com> <20110302072822.GA20321@serpens.de> <5AC61190-49B0-49B5-ACB1-1FA5082C0380@cisco.com> <20110302203006.GI23030@serpens.de> <4D6EB08E.9000109@gmail.com> <20110302214913.GG20321@serpens.de> <4D6EC293.90608@gmail.com> <20110303065132.GH20321@serpens.de> <4D6FF098.6010600@gmail.com> <A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr> <4D7689CC.7060409@gmail.com> <4D76A5FF.2020704@uclouvain.be> <4D76C461.30506@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: shim6-wg <shim6@ietf.org>, "S.P.Zeidler" <spz@serpens.de>
Subject: Re: [shim6] Exit selection [New Version Notification -	draft-mrw-nat66-08.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: Wed, 09 Mar 2011 08:18:18 -0000

Le 9 mars 2011 =E0 01:05, Brian E Carpenter a =E9crit :

> It's for the WG chairs to say, but I think we should pursue this
> WG deliverable, *and* recharter to work on the exit selection
> issue.
>=20
> I remain optimistic about shim6. Its time may come in a few years
> when the dust has settled from the IPv6 deployment panic.

> So we
> should finish the job.

+1
IMHO, practical use of shim6 will become really interesting when the =
exit-selection problem is also completely solved.

RD


>=20
> Regards
>   Brian Carpenter
>=20
> On 2011-03-09 10:56, S=E9bastien Barr=E9 wrote:
>> Hi,
>>=20
>> Op 08-03-11 20:55, Brian E Carpenter schreef:
>>>=20
>>> Where is the implementation report, BTW?
>> I have proposed an implementation report a while ago, but received no
>> comment about it (as far as I remember).
>> It is now an expired draft, but I can revive it if there is =
motivation
>> from people to review it. It can still be downloaded from here:
>> =
http://inl.info.ucl.ac.be/publications/shim6-implementation-report-linshim=
6
>>=20
>> If anyone is interested in reviewing/commenting on it, I will be =
happy
>> to apply the comments and do my best to improve it. We can also =
discuss
>> in Prague as I will be there.
>>=20
>> regards,
>>=20
>> S=E9bastien.
>>> And when will the applicability
>>> draft be ready for the IESG?
>>>=20
>>>       Brian
>>>=20
>>>> In a site using ULAs and having several links, a complement is
>>>> therefore needed.
>>>> SAM is an approach for this (ref. draft-despres-softwire-sam-01 -
>>>> sec. 3.3), and AFAIK the only documented one so far.
>>>> Would you agree on this?
>>>>=20
>>>> RD
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>> _______________________________________________
>>> shim6 mailing list
>>> shim6@ietf.org
>>> https://www.ietf.org/mailman/listinfo/shim6
>>=20
>=20



From scott.brim@gmail.com  Fri Mar 11 11:12:16 2011
Return-Path: <scott.brim@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 6C7293A6C6E for <shim6@core3.amsl.com>; Fri, 11 Mar 2011 11:12:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.148
X-Spam-Level: 
X-Spam-Status: No, score=-103.148 tagged_above=-999 required=5 tests=[AWL=-0.450, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 wNWMC-UrOIsM for <shim6@core3.amsl.com>; Fri, 11 Mar 2011 11:12:15 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by core3.amsl.com (Postfix) with ESMTP id A61A23A6994 for <shim6@ietf.org>; Fri, 11 Mar 2011 11:12:15 -0800 (PST)
Received: by iyj8 with SMTP id 8so3593639iyj.31 for <shim6@ietf.org>; Fri, 11 Mar 2011 11:13:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=x4jQoyhuL320GDmMeevRPI3kBESHQUG5Sn24zPneYf8=; b=Ni71ZlJgUnwSLmP+d5sJgUZ5pYroQZOvtB+f1MC9C/1myQ45uOwqfX1Jl0bKX0Xnv/ Uv6Q8i2X/ZwllO8b6dTEqTN/BTnnSWJ0yXi+efvlsDg8IB+yhgJCZE2P3qrCfw+ssNR7 G++yfs4jsHrOR1FOB0rG9cyfc7pk8wVjz4AYA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=JR1qv+yb5CKag71tdnUVXKvVasSs4kBpC9KyoL8M2nOtsyHCcMAavH/9UiMFz91vXi sO0W/DAdlW0/konX8i0VpPAkdgmjsF8ooBqWS55WdohLqiwMibyLTn78oBdj7p5xEuB2 teETLhOEmMXUqbBbeFGQydTkiXeAy2mAQCo0c=
Received: by 10.42.134.135 with SMTP id l7mr11930701ict.234.1299870815091; Fri, 11 Mar 2011 11:13:35 -0800 (PST)
MIME-Version: 1.0
Received: by 10.42.114.81 with HTTP; Fri, 11 Mar 2011 11:13:15 -0800 (PST)
In-Reply-To: <C3AC5E50-1E3F-4381-A0A4-B5023EBA529B@free.fr>
References: <20110228223003.13022.10464.idtracker@localhost> <845A4F08-46E7-48EE-B294-0C8368BAD1CB@cisco.com> <20110302072822.GA20321@serpens.de> <5AC61190-49B0-49B5-ACB1-1FA5082C0380@cisco.com> <20110302203006.GI23030@serpens.de> <4D6EB08E.9000109@gmail.com> <20110302214913.GG20321@serpens.de> <4D6EC293.90608@gmail.com> <20110303065132.GH20321@serpens.de> <4D6FF098.6010600@gmail.com> <A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr> <4D7689CC.7060409@gmail.com> <4D76A5FF.2020704@uclouvain.be> <4D76C461.30506@gmail.com> <C3AC5E50-1E3F-4381-A0A4-B5023EBA529B@free.fr>
From: Scott W Brim <scott.brim@gmail.com>
Date: Fri, 11 Mar 2011 14:13:15 -0500
Message-ID: <AANLkTi=Yej0=a1q7GejBGBCjXJQrLA90J9+xpcimTuXr@mail.gmail.com>
To: =?ISO-8859-1?B?UultaSBEZXNwculz?= <remi.despres@free.fr>
Content-Type: multipart/alternative; boundary=90e6ba6e8a522ffd1d049e39c269
Cc: "S.P.Zeidler" <spz@serpens.de>, shim6-wg <shim6@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [shim6] Exit selection [New Version Notification - draft-mrw-nat66-08.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: Fri, 11 Mar 2011 19:12:16 -0000

--90e6ba6e8a522ffd1d049e39c269
Content-Type: text/plain; charset=ISO-8859-1

Shim6 itself cannot select an exit.  In all but trivial cases the network
has the intelligence and must be involved (e.g. the exit points).  Given
that one has to involve the network, then an exit selection mechanism is not
just for Shim6 but for anything that can take advantage of multiple src+dst
pairs, and it should not be Shim6-specific.  Therefore whatever needs doing,
I recommend that it not be done in Shim6 but somewhere more general --
IntArea WG looks like a good place.

Scott

--90e6ba6e8a522ffd1d049e39c269
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Shim6 itself cannot select an exit. =A0In all but trivial cases the network=
 has the intelligence and must be involved (e.g. the exit points). =A0Given=
 that one has to involve the network, then an exit selection mechanism is n=
ot just for Shim6 but for anything that can take advantage of multiple src+=
dst pairs, and it should not be Shim6-specific. =A0Therefore whatever needs=
 doing, I recommend that it not be done in Shim6 but somewhere more general=
 -- IntArea WG looks like a good place.<div>

<br></div><div>Scott</div>

--90e6ba6e8a522ffd1d049e39c269--

From brian.e.carpenter@gmail.com  Fri Mar 11 11:21:17 2011
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 3D7713A6C93 for <shim6@core3.amsl.com>; Fri, 11 Mar 2011 11:21:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.202
X-Spam-Level: 
X-Spam-Status: No, score=-103.202 tagged_above=-999 required=5 tests=[AWL=-0.203, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 sHO0yRLJQhNv for <shim6@core3.amsl.com>; Fri, 11 Mar 2011 11:21:16 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by core3.amsl.com (Postfix) with ESMTP id B6ED73A6C8F for <shim6@ietf.org>; Fri, 11 Mar 2011 11:21:15 -0800 (PST)
Received: by wwa36 with SMTP id 36so2498341wwa.13 for <shim6@ietf.org>; Fri, 11 Mar 2011 11:22:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=EVWPmWQq73M+Q9hhL+wyYtuEOkTRbMWp3H3HR8lBVtM=; b=qrHZt7pPxRSZVywhWMytazC9QKgBqVU1LJ4H/rLjjUtQQCtVJJ/sPyFyUJG3LL8qlK l0EeXXDJeWzWz5m8Kes4m0z1JlpmD++LHNTNCPRUE/7PCAzBO2kbs3TF7mPJdOEr4TaN 6chyGZtojTNf+luJbzdq0dnzd7ap3I+eixmNw=
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=f8TBvb7rYWRCkEGM5BuNPc6Gx1HD3TyFo2TpVPk7aFJ0tJNfUFByPC+hc24ZnAkMLs hbc38rnpic6OBaUkn3feb7fDJx8swpLybFcw1Fgn+YFYOSd96S9+2gHS5xxVKkmMngsa 9eBlJa2CuyEn2TyDLPpR5VfSSJV5f0bVoRZJ0=
Received: by 10.216.80.89 with SMTP id j67mr8482761wee.20.1299871354633; Fri, 11 Mar 2011 11:22:34 -0800 (PST)
Received: from [10.1.1.4] ([121.98.190.33]) by mx.google.com with ESMTPS id o19sm2344693wee.26.2011.03.11.11.22.29 (version=SSLv3 cipher=OTHER); Fri, 11 Mar 2011 11:22:33 -0800 (PST)
Message-ID: <4D7A7666.1040602@gmail.com>
Date: Sat, 12 Mar 2011 08:22:14 +1300
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: Scott W Brim <scott.brim@gmail.com>
References: <20110228223003.13022.10464.idtracker@localhost> <845A4F08-46E7-48EE-B294-0C8368BAD1CB@cisco.com> <20110302072822.GA20321@serpens.de> <5AC61190-49B0-49B5-ACB1-1FA5082C0380@cisco.com> <20110302203006.GI23030@serpens.de> <4D6EB08E.9000109@gmail.com> <20110302214913.GG20321@serpens.de> <4D6EC293.90608@gmail.com> <20110303065132.GH20321@serpens.de> <4D6FF098.6010600@gmail.com> <A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr> <4D7689CC.7060409@gmail.com> <4D76A5FF.2020704@uclouvain.be> <4D76C461.30506@gmail.com> <C3AC5E50-1E3F-4381-A0A4-B5023EBA529B@free.fr> <AANLkTi=Yej0=a1q7GejBGBCjXJQrLA90J9+xpcimTuXr@mail.gmail.com>
In-Reply-To: <AANLkTi=Yej0=a1q7GejBGBCjXJQrLA90J9+xpcimTuXr@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "S.P.Zeidler" <spz@serpens.de>, shim6-wg <shim6@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [shim6] Exit selection [New Version Notification - draft-mrw-nat66-08.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: Fri, 11 Mar 2011 19:21:17 -0000

Scott,

That may well be true, but shouldn't we work here to define the
requirements from the shim6 point of view?

I must go and read the MIF documents sometime. It could be they
have already defined sufficient requirements for shim6.

   Brian

On 2011-03-12 08:13, Scott W Brim wrote:
> Shim6 itself cannot select an exit.  In all but trivial cases the network
> has the intelligence and must be involved (e.g. the exit points).  Given
> that one has to involve the network, then an exit selection mechanism is not
> just for Shim6 but for anything that can take advantage of multiple src+dst
> pairs, and it should not be Shim6-specific.  Therefore whatever needs doing,
> I recommend that it not be done in Shim6 but somewhere more general --
> IntArea WG looks like a good place.
> 
> Scott
> 

From scott.brim@gmail.com  Fri Mar 11 12:06:59 2011
Return-Path: <scott.brim@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 B8A3A3A6944 for <shim6@core3.amsl.com>; Fri, 11 Mar 2011 12:06:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.566
X-Spam-Level: 
X-Spam-Status: No, score=-103.566 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 m4lAgBjVMmMs for <shim6@core3.amsl.com>; Fri, 11 Mar 2011 12:06:59 -0800 (PST)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id DBA913A68B1 for <shim6@ietf.org>; Fri, 11 Mar 2011 12:06:58 -0800 (PST)
Received: by iwl42 with SMTP id 42so3693807iwl.31 for <shim6@ietf.org>; Fri, 11 Mar 2011 12:08:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=HzSqe4H5daYx9K/3rZfOGxfwx9jJNgLiFnDA4U1ZB1k=; b=pspQH0EMl7gd5gamFlagiUvxjoqowEoh+mHkHAh0VfwVvmbGgLvLMWju4mp8cMzrgN TguzdunDTotfTkKmkUhALLIpyi14GDFbhwBBis6531Vr1gRXaXZS3KLmHTCQTD7Eshz1 Dj5AevfVaV3PrSIjJDwwh0EHA7c2jdY4UPKr0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=trvSBG0DTggt3Xe85PFl68F5c7x1/i9xuHd16bUc65SZqOx+F5OBrHY/vIIxq48wwz 2D0GEAM6yNLYZ/xvxIjJLtwXD+3DoDD3SDel1w5AGGok0kRwtRj/lLJIOLMrYehdPgH+ 9ifWgqNQwsDTm8+caTX7z+avZt4/fITn5zeUY=
Received: by 10.42.189.200 with SMTP id df8mr2830055icb.33.1299874098123; Fri, 11 Mar 2011 12:08:18 -0800 (PST)
MIME-Version: 1.0
Received: by 10.42.114.81 with HTTP; Fri, 11 Mar 2011 12:07:58 -0800 (PST)
In-Reply-To: <4D7A7666.1040602@gmail.com>
References: <20110228223003.13022.10464.idtracker@localhost> <845A4F08-46E7-48EE-B294-0C8368BAD1CB@cisco.com> <20110302072822.GA20321@serpens.de> <5AC61190-49B0-49B5-ACB1-1FA5082C0380@cisco.com> <20110302203006.GI23030@serpens.de> <4D6EB08E.9000109@gmail.com> <20110302214913.GG20321@serpens.de> <4D6EC293.90608@gmail.com> <20110303065132.GH20321@serpens.de> <4D6FF098.6010600@gmail.com> <A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr> <4D7689CC.7060409@gmail.com> <4D76A5FF.2020704@uclouvain.be> <4D76C461.30506@gmail.com> <C3AC5E50-1E3F-4381-A0A4-B5023EBA529B@free.fr> <AANLkTi=Yej0=a1q7GejBGBCjXJQrLA90J9+xpcimTuXr@mail.gmail.com> <4D7A7666.1040602@gmail.com>
From: Scott W Brim <scott.brim@gmail.com>
Date: Fri, 11 Mar 2011 15:07:58 -0500
Message-ID: <AANLkTim8_sfLBmjTVHXtZhi6t2ZvLwOEM-VJszXJmrKi@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=20cf303ea5eadf1255049e3a8539
Cc: "S.P.Zeidler" <spz@serpens.de>, shim6-wg <shim6@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [shim6] Exit selection [New Version Notification - draft-mrw-nat66-08.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: Fri, 11 Mar 2011 20:07:00 -0000

--20cf303ea5eadf1255049e3a8539
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Mar 11, 2011 at 14:22, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Scott,
>
> That may well be true, but shouldn't we work here to define the
> requirements from the shim6 point of view?
>

OK, sounds good.


> I must go and read the MIF documents sometime. It could be they
> have already defined sufficient requirements for shim6.


When you do, and you feel frustrated, please contribute :-)

--20cf303ea5eadf1255049e3a8539
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Fri, Mar 11, 2011 at 14:22, Brian E C=
arpenter <span dir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.co=
m">brian.e.carpenter@gmail.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex;">

Scott,<br>
<br>
That may well be true, but shouldn&#39;t we work here to define the<br>
requirements from the shim6 point of view?<br></blockquote><div><br></div><=
div>OK, sounds good.</div><div>=A0</div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I must go and read the MIF documents sometime. It could be they<br>
have already defined sufficient requirements for shim6.</blockquote><div><b=
r></div><div>When you do, and you feel frustrated, please contribute :-)</d=
iv></div>

--20cf303ea5eadf1255049e3a8539--

From remi.despres@free.fr  Sat Mar 12 08:31:41 2011
Return-Path: <remi.despres@free.fr>
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 15FC53A6A83 for <shim6@core3.amsl.com>; Sat, 12 Mar 2011 08:31:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.981
X-Spam-Level: 
X-Spam-Status: No, score=-0.981 tagged_above=-999 required=5 tests=[AWL=0.368,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_33=0.6, 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 EHKh9RC7+hjB for <shim6@core3.amsl.com>; Sat, 12 Mar 2011 08:31:39 -0800 (PST)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.21]) by core3.amsl.com (Postfix) with ESMTP id AF88E3A6A19 for <shim6@ietf.org>; Sat, 12 Mar 2011 08:31:39 -0800 (PST)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2313.sfr.fr (SMTP Server) with ESMTP id 7DE8B7000087; Sat, 12 Mar 2011 17:32:59 +0100 (CET)
Received: from [192.168.0.14] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2313.sfr.fr (SMTP Server) with ESMTP id CFF237000093; Sat, 12 Mar 2011 17:32:56 +0100 (CET)
X-SFR-UUID: 20110312163256851.CFF237000093@msfrf2313.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <AANLkTi=Yej0=a1q7GejBGBCjXJQrLA90J9+xpcimTuXr@mail.gmail.com>
Date: Sat, 12 Mar 2011 17:32:54 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D7244E10-B305-45F3-9395-1C8C701D7A08@free.fr>
References: <20110228223003.13022.10464.idtracker@localhost> <845A4F08-46E7-48EE-B294-0C8368BAD1CB@cisco.com> <20110302072822.GA20321@serpens.de> <5AC61190-49B0-49B5-ACB1-1FA5082C0380@cisco.com> <20110302203006.GI23030@serpens.de> <4D6EB08E.9000109@gmail.com> <20110302214913.GG20321@serpens.de> <4D6EC293.90608@gmail.com> <20110303065132.GH20321@serpens.de> <4D6FF098.6010600@gmail.com> <A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr> <4D7689CC.7060409@gmail.com> <4D76A5FF.2020704@uclouvain.be> <4D76C461.30506@gmail.com> <C3AC5E50-1E3F-4381-A0A4-B5023EBA529B@free.fr> <AANLkTi=Yej0=a1q7GejBGBCjXJQrLA90J9+xpcimTuXr@mail.gmail.com>
To: Scott W Brim <scott.brim@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: "S.P.Zeidler" <spz@serpens.de>, shim6-wg <shim6@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [shim6] Exit selection [New Version Notification - draft-mrw-nat66-08.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: Sat, 12 Mar 2011 16:31:41 -0000

Le 11 mars 2011 =E0 20:13, Scott W Brim a =E9crit :

> Shim6 itself cannot select an exit.  In all but trivial cases the =
network has the intelligence and must be involved (e.g. the exit =
points).  Given that one has to involve the network, then an exit =
selection mechanism is not just for Shim6 but for anything that can take =
advantage of multiple src+dst pairs, and it should not be =
Shim6-specific. =20

> Therefore whatever needs doing, I recommend that it not be done in =
Shim6 but somewhere more general -- IntArea WG looks like a good place.

+1

RD



From gih@apnic.net  Sun Mar 13 14:13:01 2011
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 793413A6BAF for <shim6@core3.amsl.com>; Sun, 13 Mar 2011 14:13:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.185
X-Spam-Level: 
X-Spam-Status: No, score=-101.185 tagged_above=-999 required=5 tests=[AWL=-0.180, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RELAY_IS_203=0.994, USER_IN_WHITELIST=-100]
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 bhPALlsm9OMW for <shim6@core3.amsl.com>; Sun, 13 Mar 2011 14:13:00 -0700 (PDT)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by core3.amsl.com (Postfix) with ESMTP id 0DFEA3A6BA8 for <shim6@ietf.org>; Sun, 13 Mar 2011 14:12:59 -0700 (PDT)
Received: from dhcp75.potaroo.net (eth143.act.adsl.internode.on.net [203.16.208.142]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 57CCDB66C9; Mon, 14 Mar 2011 07:14:19 +1000 (EST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <D7244E10-B305-45F3-9395-1C8C701D7A08@free.fr>
Date: Mon, 14 Mar 2011 08:14:14 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <733F86F7-54F7-4544-B139-5F534F143DA6@apnic.net>
References: <20110228223003.13022.10464.idtracker@localhost> <845A4F08-46E7-48EE-B294-0C8368BAD1CB@cisco.com> <20110302072822.GA20321@serpens.de> <5AC61190-49B0-49B5-ACB1-1FA5082C0380@cisco.com> <20110302203006.GI23030@serpens.de> <4D6EB08E.9000109@gmail.com> <20110302214913.GG20321@serpens.de> <4D6EC293.90608@gmail.com> <20110303065132.GH20321@serpens.de> <4D6FF098.6010600@gmail.com> <A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr> <4D7689CC.7060409@gmail.com> <4D76A5FF.2020704@uclouvain.be> <4D76C461.30506@gmail.com> <C3AC5E50-1E3F-4381-A0A4-B5023EBA529B@free.fr> <AANLkTi=Yej0=a1q7GejBGBCjXJQrLA90J9+xpcimTuXr@mail.gmail.com> <D7244E10-B305-45F3-9395-1C8C701D7A08@free.fr>
To: Scott Brim <scott.brim@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: shim6-wg <shim6@ietf.org>, "S.P.Zeidler" <spz@serpens.de>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [shim6] Exit selection [New Version Notification - draft-mrw-nat66-08.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: Sun, 13 Mar 2011 21:13:01 -0000

On 13/03/2011, at 3:32 AM, R=E9mi Despr=E9s wrote:

>=20
> Le 11 mars 2011 =E0 20:13, Scott W Brim a =E9crit :
>=20
>> Shim6 itself cannot select an exit.  In all but trivial cases the =
network has the intelligence and must be involved (e.g. the exit =
points).  Given that one has to involve the network, then an exit =
selection mechanism is not just for Shim6 but for anything that can take =
advantage of multiple src+dst pairs, and it should not be =
Shim6-specific. =20
>=20
>> Therefore whatever needs doing, I recommend that it not be done in =
Shim6 but somewhere more general -- IntArea WG looks like a good place.
>=20
> +1
>=20

wg co-chair hat OFF

I appreciate that in the context of the IETF saying "we should not do =
this" is invariably like standing in front of a bulldozer, and like the =
bulldozer, it rarely has any effect - but nevertheless I want to share =
with you a personal opinion that we should not do this! :-)
=20
I have two problems with this issue of "exit selection".=20

Firstly, I recall the demise of the site-local scoped address in IPv6. =
The compelling argument for me was one of inability of self-awareness of =
context. i.e. it was never clear where the edge of a site actually lay. =
So let me replay the same problem statement here - what is an "exit" and =
how does a packet know when it has gone through it? And how does a =
router "know" its the exit router and not an interior router? In the =
context of nested sites (e.g. workgroup, department, faculty) whats =
_the_ exit?

Secondly, its not just the problem of scope of a site here. Its also =
trying to clearly understand the nature of the problem and place that =
into juxtaposition with the various proposed "solutions." =46rom memory =
the various exit selection solutions proposed in the context of shim6 =
were all various forms of source-address based forwarding, and for me =
its getting the cart well and truly before the horse. Hop-by-hop =
stateless destination-based forwarding is an incredibly powerful =
architectural concept in packet networks, and any other forwarding =
mechanism tends to invoke copious quantities of complexity and state, =
and should only be contemplated as a last resort of the desperate rather =
than the first line solution. So why was exit selection an issue in =
shim6? Surely if routing is working, and shim6 does not assume broken =
routing, if a route to a destination is offered, then its a valid route. =
So why select exits that are not being offered by routing as being on =
the best path? =46rom my memory I believe it was because some folk  =
thought that a) unicast reverse route filtering would be prevalent in =
IPv6 and that b) clients could not negotiate filters with their =
provider.  But is a) true? and is b) really true? Frankly I'm pretty =
sceptical that this is the case and it concerns me that this is a case =
of over solving.

my 2c anyway

   Geoff



From sander@steffann.nl  Sun Mar 13 14:22:25 2011
Return-Path: <sander@steffann.nl>
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 3D85F3A6BA6 for <shim6@core3.amsl.com>; Sun, 13 Mar 2011 14:22:25 -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 4j8dWisxF50d for <shim6@core3.amsl.com>; Sun, 13 Mar 2011 14:22:24 -0700 (PDT)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by core3.amsl.com (Postfix) with ESMTP id DF56F3A6B80 for <shim6@ietf.org>; Sun, 13 Mar 2011 14:22:23 -0700 (PDT)
Received: from macpro.10ww.steffann.nl (unknown [IPv6:2001:610:6ce:1:224:36ff:feef:1d89]) by mail.sintact.nl (Postfix) with ESMTP id 5C7AF200A; Sun, 13 Mar 2011 22:23:44 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <733F86F7-54F7-4544-B139-5F534F143DA6@apnic.net>
Date: Sun, 13 Mar 2011 22:23:44 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E4E83F81-BEF1-41C0-97BF-08107901758F@steffann.nl>
References: <20110228223003.13022.10464.idtracker@localhost> <845A4F08-46E7-48EE-B294-0C8368BAD1CB@cisco.com> <20110302072822.GA20321@serpens.de> <5AC61190-49B0-49B5-ACB1-1FA5082C0380@cisco.com> <20110302203006.GI23030@serpens.de> <4D6EB08E.9000109@gmail.com> <20110302214913.GG20321@serpens.de> <4D6EC293.90608@gmail.com> <20110303065132.GH20321@serpens.de> <4D6FF098.6010600@gmail.com> <A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr> <4D7689CC.7060409@gmail.com> <4D76A5FF.2020704@uclouvain.be> <4D76C461.30506@gmail.com> <C3AC5E50-1E3F-4381-A0A4-B5023EBA529B@free.fr> <AANLkTi=Yej0=a1q7GejBGBCjXJQrLA90J9+xpcimTuXr@mail.gmail.com> <D7244E10-B305-45F3-9395-1C8C701D7A08@free.fr> <733F86F7-54F7-4544-B139-5F534F143DA6@apnic.net>
To: Geoff Huston <gih@apnic.net>
X-Mailer: Apple Mail (2.1082)
Cc: shim6-wg <shim6@ietf.org>
Subject: Re: [shim6] Exit selection [New Version Notification - draft-mrw-nat66-08.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: Sun, 13 Mar 2011 21:22:25 -0000

Hi Geoff,

> =46rom my memory I believe it was because some folk  thought that a) =
unicast reverse route filtering would be prevalent in IPv6 and that b) =
clients could not negotiate filters with their provider.  But is a) =
true? and is b) really true? Frankly I'm pretty sceptical that this is =
the case and it concerns me that this is a case of over solving.

=46rom my personal experience here in The Netherlands: a) yes, b) yes. =
At least for home users and small/medium sized businesses. A lot of them =
use cheap DSL based internet access, and they do uRPF for IPv4 and =
refuse to deploy an IPv6 service that can not do uRPF. And because the =
service is cheap, the ISP has no budget for b)...

- Sander


From brian.e.carpenter@gmail.com  Sun Mar 13 15:31:10 2011
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 9AD013A69CA for <shim6@core3.amsl.com>; Sun, 13 Mar 2011 15:31:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.15
X-Spam-Level: 
X-Spam-Status: No, score=-103.15 tagged_above=-999 required=5 tests=[AWL=-0.151, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 C9d59GZqHT0z for <shim6@core3.amsl.com>; Sun, 13 Mar 2011 15:31:09 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by core3.amsl.com (Postfix) with ESMTP id 610AB3A6BCB for <shim6@ietf.org>; Sun, 13 Mar 2011 15:31:09 -0700 (PDT)
Received: by ywi6 with SMTP id 6so2424260ywi.31 for <shim6@ietf.org>; Sun, 13 Mar 2011 15:32:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=gJyHtZ9kF/pC1Oz9HUwUup41b44z7ep7dQAh/Ewwtmk=; b=GfP/XG/tYID0HLUbmhaTXDQ4dzd2z/rpAInsKMWXRTLJiGKVkUJv/hUSegPohaRZKF AHUv0gcVNVrBbT5MvZIDUsqqeQ1tGEuYS2vXpfDWo/pgcLkvNLkTIf1yYqJzJQR6gPcC pKUsFYMol5gboeduleISwdZqCasJgQZu+7Bhk=
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=bWHKqJmYrKJ7plfppIdRlHOPHRBHYEck7ks9uSSsQsPyn4INS2/PFuCD+c8eyp3+tg QExkdymFBS4QLmSdPh33j91cHg8wUopdEymoqd810xUqVdzNQ+HNRUu+otcTLpzi18y9 TcMxmpXkEVYOtvyx/Zu/M/pniTQhGLSP86m1A=
Received: by 10.91.34.26 with SMTP id m26mr2445171agj.140.1300055550560; Sun, 13 Mar 2011 15:32:30 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id u20sm5497338anu.34.2011.03.13.15.32.27 (version=SSLv3 cipher=OTHER); Sun, 13 Mar 2011 15:32:29 -0700 (PDT)
Message-ID: <4D7D45F9.6030409@gmail.com>
Date: Mon, 14 Mar 2011 11:32:25 +1300
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: Geoff Huston <gih@apnic.net>
References: <20110228223003.13022.10464.idtracker@localhost>	<845A4F08-46E7-48EE-B294-0C8368BAD1CB@cisco.com>	<20110302072822.GA20321@serpens.de>	<5AC61190-49B0-49B5-ACB1-1FA5082C0380@cisco.com>	<20110302203006.GI23030@serpens.de> <4D6EB08E.9000109@gmail.com>	<20110302214913.GG20321@serpens.de> <4D6EC293.90608@gmail.com>	<20110303065132.GH20321@serpens.de> <4D6FF098.6010600@gmail.com>	<A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr>	<4D7689CC.7060409@gmail.com> <4D76A5FF.2020704@uclouvain.be>	<4D76C461.30506@gmail.com>	<C3AC5E50-1E3F-4381-A0A4-B5023EBA529B@free.fr>	<AANLkTi=Yej0=a1q7GejBGBCjXJQrLA90J9+xpcimTuXr@mail.gmail.com>	<D7244E10-B305-45F3-9395-1C8C701D7A08@free.fr> <733F86F7-54F7-4544-B139-5F534F143DA6@apnic.net>
In-Reply-To: <733F86F7-54F7-4544-B139-5F534F143DA6@apnic.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "S.P.Zeidler" <spz@serpens.de>, shim6-wg <shim6@ietf.org>, Scott Brim <scott.brim@gmail.com>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [shim6] Exit selection [New Version Notification -	draft-mrw-nat66-08.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: Sun, 13 Mar 2011 22:31:11 -0000

On 2011-03-14 10:14, Geoff Huston wrote:
> On 13/03/2011, at 3:32 AM, R=C3=A9mi Despr=C3=A9s wrote:
>=20
>> Le 11 mars 2011 =C3=A0 20:13, Scott W Brim a =C3=A9crit :
>>=20
>>> Shim6 itself cannot select an exit.  In all but trivial
>>> cases the network has the intelligence and must be
>>> involved (e.g. the exit points).  Given that one has to
>>> involve the network, then an exit selection mechanism is
>>> not just for Shim6 but for anything that can take
>>> advantage of multiple src+dst pairs, and it should not be
>>> Shim6-specific. Therefore whatever needs doing, I
>>> recommend that it not be done in Shim6 but somewhere more
>>> general -- IntArea WG looks like a good place.
>> +1
>>=20
>=20
> wg co-chair hat OFF
>=20
> I appreciate that in the context of the IETF saying "we
> should not do this" is invariably like standing in front of a
> bulldozer, and like the bulldozer, it rarely has any effect -
> but nevertheless I want to share with you a personal opinion
> that we should not do this! :-)

If by "we" you mean the shim6 WG, I'm inclined to agree,
beyond documenting that this problem needs to be solved
generically for IPv6. I don't believe shim6 is really a
special case: once you have prefixes from and exits to several
different ISPs, you have a potential problem.

>=20
> I have two problems with this issue of "exit selection".
>=20
> Firstly, I recall the demise of the site-local scoped address
> in IPv6. The compelling argument for me was one of inability
> of self-awareness of context. i.e. it was never clear where
> the edge of a site actually lay. So let me replay the same
> problem statement here - what is an "exit" and how does a
> packet know when it has gone through it? And how does a
> router "know" its the exit router and not an interior router?
> In the context of nested sites (e.g. workgroup, department,
> faculty) whats _the_ exit?

The host and the departmental router cannot know the answer to
that question, I fear, without erecting some very complicated
machinery.

>=20
> Secondly, its not just the problem of scope of a site here.
> Its also trying to clearly understand the nature of the
> problem and place that into juxtaposition with the various
> proposed "solutions." From memory the various exit selection
> solutions proposed in the context of shim6 were all various
> forms of source-address based forwarding, and for me its
> getting the cart well and truly before the horse. Hop-by-hop
> stateless destination-based forwarding is an incredibly
> powerful architectural concept in packet networks, and any
> other forwarding mechanism tends to invoke copious quantities
> of complexity and state, and should only be contemplated as a
> last resort of the desperate rather than the first line
> solution.=20

I fully agree. That would be baroque, and despite having started
this conversation, I am not in favour of a host-based or even
departmental-router-based solution.

> So why was exit selection an issue in shim6? Surely
> if routing is working, and shim6 does not assume broken
> routing, if a route to a destination is offered, then its a
> valid route. So why select exits that are not being offered
> by routing as being on the best path? From my memory I
> believe it was because some folk  thought that a) unicast
> reverse route filtering would be prevalent in IPv6 and that
> b) clients could not negotiate filters with their provider.
> But is a) true? and is b) really true?=20

Well, it seems from other responses that both are real problems,
but not specific to shim6. draft-v6ops-multihoming-without-nat66
talks about this, and at first sight, a valid approach for
the problems described in that draft would work just fine for
shim6 too. Maybe shim6 people should read that draft carefully.

    Brian

> Frankly I'm pretty
> sceptical that this is the case and it concerns me that this
> is a case of over solving.
>=20
> my 2c anyway
>=20
> Geoff
>=20
>=20
> _______________________________________________ shim6 mailing
> list shim6@ietf.org=20
> https://www.ietf.org/mailman/listinfo/shim6
>=20


From gih@apnic.net  Sun Mar 13 15:57:04 2011
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 1EF8D3A690A for <shim6@core3.amsl.com>; Sun, 13 Mar 2011 15:57:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.455
X-Spam-Level: 
X-Spam-Status: No, score=-101.455 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RELAY_IS_203=0.994, USER_IN_WHITELIST=-100]
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 X6ykAqUpI60H for <shim6@core3.amsl.com>; Sun, 13 Mar 2011 15:57:03 -0700 (PDT)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by core3.amsl.com (Postfix) with ESMTP id 9A40F3A68AB for <shim6@ietf.org>; Sun, 13 Mar 2011 15:57:02 -0700 (PDT)
Received: from dhcp76.potaroo.net (eth143.act.adsl.internode.on.net [203.16.208.142]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id DECC1B6735; Mon, 14 Mar 2011 08:58:23 +1000 (EST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <E4E83F81-BEF1-41C0-97BF-08107901758F@steffann.nl>
Date: Mon, 14 Mar 2011 09:58:17 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B96B5E8F-1752-421A-BB80-C5EE4A05DD8B@apnic.net>
References: <20110228223003.13022.10464.idtracker@localhost> <845A4F08-46E7-48EE-B294-0C8368BAD1CB@cisco.com> <20110302072822.GA20321@serpens.de> <5AC61190-49B0-49B5-ACB1-1FA5082C0380@cisco.com> <20110302203006.GI23030@serpens.de> <4D6EB08E.9000109@gmail.com> <20110302214913.GG20321@serpens.de> <4D6EC293.90608@gmail.com> <20110303065132.GH20321@serpens.de> <4D6FF098.6010600@gmail.com> <A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr> <4D7689CC.7060409@gmail.com> <4D76A5FF.2020704@uclouvain.be> <4D76C461.30506@gmail.com> <C3AC5E50-1E3F-4381-A0A4-B5023EBA529B@free.fr> <AANLkTi=Yej0=a1q7GejBGBCjXJQrLA90J9+xpcimTuXr@mail.gmail.com> <D7244E10-B305-45F3-9395-1C8C701D7A08@free.fr> <733F86F7-54F7-4544-B139-5F534F143DA6@apnic.net> <E4E83F81-BEF1-41C0-97BF-08107901758F@steffann.nl>
To: Sander Steffann <sander@steffann.nl>
X-Mailer: Apple Mail (2.1082)
Cc: shim6-wg <shim6@ietf.org>
Subject: Re: [shim6] Exit selection [New Version Notification - draft-mrw-nat66-08.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: Sun, 13 Mar 2011 22:57:04 -0000

On 14/03/2011, at 8:23 AM, Sander Steffann wrote:

> Hi Geoff,
>=20
>> =46rom my memory I believe it was because some folk  thought that a) =
unicast reverse route filtering would be prevalent in IPv6 and that b) =
clients could not negotiate filters with their provider.  But is a) =
true? and is b) really true? Frankly I'm pretty sceptical that this is =
the case and it concerns me that this is a case of over solving.
>=20
> =46rom my personal experience here in The Netherlands: a) yes, b) yes. =
At least for home users and small/medium sized businesses. A lot of them =
use cheap DSL based internet access, and they do uRPF for IPv4 and =
refuse to deploy an IPv6 service that can not do uRPF. And because the =
service is cheap, the ISP has no budget for b)...
>=20

wg co-chair hat still off

It may be (is?) heretical in the context of this wg, but at the low end =
of the market that is highly cost and process constrained, as the =
subject line refers, NAT66 is an obvious approach that does not try and =
jump through the trapeze hoops of trying to do hop-by-hop forwarding =
based on source address in a general manner..

:-)

  Geoff





From brian.e.carpenter@gmail.com  Sun Mar 13 16:15:21 2011
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 4DF3B3A690A for <shim6@core3.amsl.com>; Sun, 13 Mar 2011 16:15:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.448
X-Spam-Level: 
X-Spam-Status: No, score=-103.448 tagged_above=-999 required=5 tests=[AWL=0.151, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 lEwtNol3oSwH for <shim6@core3.amsl.com>; Sun, 13 Mar 2011 16:15:20 -0700 (PDT)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by core3.amsl.com (Postfix) with ESMTP id 7AE183A68AB for <shim6@ietf.org>; Sun, 13 Mar 2011 16:15:20 -0700 (PDT)
Received: by qyk29 with SMTP id 29so896508qyk.10 for <shim6@ietf.org>; Sun, 13 Mar 2011 16:16:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=UO06FDeFw2yQdjtP9yPJeC0wUB+HGPopg56TYHu78do=; b=FlzqRvxjR2x2qbNXZvBCSZ2oYjGH02Grngoxj9BPAAGFnLPvr5V3YnHIcoi/5z3GOV ciTL8QO8O8fmtZ55qPEEE8QfEmjzIapO5inse0k7wmy/R3s8H2wlilotfAXh9TBbj4Sg A/RDHL3IqeA/uy3O4I4cITBqIKh2dU/rjdcZA=
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=S2sxWgRv0UevA9ckn+ErRU+LU/CSnXQ+FiklNDIOwxG2U4NuHz4cqTEFyK6EnmMRqh SAijxHmd3TP41cCUcEc+spkd5AriJeCVhnTce+twhQ6Un15NMeOejZdvyFACceQgU/Ip GR+DK9FzI9YD5pk5Wr/2g0YDiUdCza8g1xaK0=
Received: by 10.224.188.8 with SMTP id cy8mr10550352qab.85.1300058202948; Sun, 13 Mar 2011 16:16:42 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id s10sm5021231qco.23.2011.03.13.16.16.40 (version=SSLv3 cipher=OTHER); Sun, 13 Mar 2011 16:16:42 -0700 (PDT)
Message-ID: <4D7D5057.2090100@gmail.com>
Date: Mon, 14 Mar 2011 12:16:39 +1300
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: Geoff Huston <gih@apnic.net>
References: <20110228223003.13022.10464.idtracker@localhost>	<845A4F08-46E7-48EE-B294-0C8368BAD1CB@cisco.com>	<20110302072822.GA20321@serpens.de>	<5AC61190-49B0-49B5-ACB1-1FA5082C0380@cisco.com>	<20110302203006.GI23030@serpens.de> <4D6EB08E.9000109@gmail.com>	<20110302214913.GG20321@serpens.de> <4D6EC293.90608@gmail.com>	<20110303065132.GH20321@serpens.de> <4D6FF098.6010600@gmail.com>	<A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr>	<4D7689CC.7060409@gmail.com> <4D76A5FF.2020704@uclouvain.be>	<4D76C461.30506@gmail.com>	<C3AC5E50-1E3F-4381-A0A4-B5023EBA529B@free.fr>	<AANLkTi=Yej0=a1q7GejBGBCjXJQrLA90J9+xpcimTuXr@mail.gmail.com>	<D7244E10-B305-45F3-9395-1C8C701D7A08@free.fr>	<733F86F7-54F7-4544-B139-5F534F143DA6@apnic.net>	<E4E83F81-BEF1-41C0-97BF-08107901758F@steffann.nl> <B96B5E8F-1752-421A-BB80-C5EE4A05DD8B@apnic.net>
In-Reply-To: <B96B5E8F-1752-421A-BB80-C5EE4A05DD8B@apnic.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: shim6-wg <shim6@ietf.org>
Subject: Re: [shim6] Exit selection [New Version Notification -	draft-mrw-nat66-08.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: Sun, 13 Mar 2011 23:15:21 -0000

On 2011-03-14 11:58, Geoff Huston wrote:
> On 14/03/2011, at 8:23 AM, Sander Steffann wrote:
> 
>> Hi Geoff,
>>
>>> From my memory I believe it was because some folk  thought that a) unicast reverse route filtering would be prevalent in IPv6 and that b) clients could not negotiate filters with their provider.  But is a) true? and is b) really true? Frankly I'm pretty sceptical that this is the case and it concerns me that this is a case of over solving.
>> From my personal experience here in The Netherlands: a) yes, b) yes. At least for home users and small/medium sized businesses. A lot of them use cheap DSL based internet access, and they do uRPF for IPv4 and refuse to deploy an IPv6 service that can not do uRPF. And because the service is cheap, the ISP has no budget for b)...
>>
> 
> wg co-chair hat still off
> 
> It may be (is?) heretical in the context of this wg, but at the low end of the market that is highly cost and process constrained, as the subject line refers, NAT66 is an obvious approach that does not try and jump through the trapeze hoops of trying to do hop-by-hop forwarding based on source address in a general manner..

If you mean NPTv6, yes, it's heresy but it will no doubt get its
share of the market. I see shim6 and multihoming-without-nat as
part of the longer term future for medium scale enterprise sites.

   Brian

From gih@apnic.net  Sun Mar 13 16:20:53 2011
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 F01553A6A49 for <shim6@core3.amsl.com>; Sun, 13 Mar 2011 16:20:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.176
X-Spam-Level: 
X-Spam-Status: No, score=-101.176 tagged_above=-999 required=5 tests=[AWL=-0.171, BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RELAY_IS_203=0.994, USER_IN_WHITELIST=-100]
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 n8WD+ZLccdSW for <shim6@core3.amsl.com>; Sun, 13 Mar 2011 16:20:52 -0700 (PDT)
Received: from asmtp.apnic.net (asmtp.apnic.net [IPv6:2001:dc0:2001:11::199]) by core3.amsl.com (Postfix) with ESMTP id 689303A68AB for <shim6@ietf.org>; Sun, 13 Mar 2011 16:20:50 -0700 (PDT)
Received: from dhcp76.potaroo.net (eth143.act.adsl.internode.on.net [203.16.208.142]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by asmtp.apnic.net (Postfix) with ESMTP id 017C6B6735; Mon, 14 Mar 2011 09:22:09 +1000 (EST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <4D7D45F9.6030409@gmail.com>
Date: Mon, 14 Mar 2011 10:22:03 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <9F3421E0-A591-4C06-A11A-01A7F2CB6279@apnic.net>
References: <20110228223003.13022.10464.idtracker@localhost>	<845A4F08-46E7-48EE-B294-0C8368BAD1CB@cisco.com>	<20110302072822.GA20321@serpens.de>	<5AC61190-49B0-49B5-ACB1-1FA5082C0380@cisco.com>	<20110302203006.GI23030@serpens.de> <4D6EB08E.9000109@gmail.com>	<20110302214913.GG20321@serpens.de> <4D6EC293.90608@gmail.com>	<20110303065132.GH20321@serpens.de> <4D6FF098.6010600@gmail.com>	<A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr>	<4D7689CC.7060409@gmail.com> <4D76A5FF.2020704@uclouvain.be>	<4D76C461.30506@gmail.com>	<C3AC5E50-1E3F-4381-A0A4-B5023EBA529B@free.fr>	<AANLkTi=Yej0=a1q7GejBGBCjXJQrLA90J9+xpcimTuXr@mail.gmail.com>	<D7244E10-B305-45F3-9395-1C8C701D7A08@free.fr> <733F86F7-54F7-4544-B139-5F534F143DA6@apnic.net> <4D7D45F9.6030409@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: "S.P.Zeidler" <spz@serpens.de>, shim6-wg <shim6@ietf.org>, Scott Brim <scott.brim@gmail.com>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [shim6] Exit selection [New Version Notification -	draft-mrw-nat66-08.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: Sun, 13 Mar 2011 23:20:53 -0000

On 14/03/2011, at 9:32 AM, Brian E Carpenter wrote:

> On 2011-03-14 10:14, Geoff Huston wrote:
>> On 13/03/2011, at 3:32 AM, R=E9mi Despr=E9s wrote:
>>=20
>>> Le 11 mars 2011 =E0 20:13, Scott W Brim a =E9crit :
>>>=20
>>>> Shim6 itself cannot select an exit.  In all but trivial
>>>> cases the network has the intelligence and must be
>>>> involved (e.g. the exit points).  Given that one has to
>>>> involve the network, then an exit selection mechanism is
>>>> not just for Shim6 but for anything that can take
>>>> advantage of multiple src+dst pairs, and it should not be
>>>> Shim6-specific. Therefore whatever needs doing, I
>>>> recommend that it not be done in Shim6 but somewhere more
>>>> general -- IntArea WG looks like a good place.
>>> +1
>>>=20
>>=20
>> wg co-chair hat OFF
>>=20
>> I appreciate that in the context of the IETF saying "we
>> should not do this" is invariably like standing in front of a
>> bulldozer, and like the bulldozer, it rarely has any effect -
>> but nevertheless I want to share with you a personal opinion
>> that we should not do this! :-)
>=20
> If by "we" you mean the shim6 WG, I'm inclined to agree,
> beyond documenting that this problem needs to be solved
> generically for IPv6.


As might be evident from my positing I'm of the view that this is
a case of "nothing to see here, move along" and therefore I personally=20=

disagree that this "problem" needs to be solved. (but I also appreciate
that in the IETF this never works and the IETF is often more
obsessed with the rathole than the larger landscape.  :-)




> I don't believe shim6 is really a
> special case: once you have prefixes from and exits to several
> different ISPs, you have a potential problem.
>=20


>>=20
>> I have two problems with this issue of "exit selection".
>>=20
>> Firstly, I recall the demise of the site-local scoped address
>> in IPv6. The compelling argument for me was one of inability
>> of self-awareness of context. i.e. it was never clear where
>> the edge of a site actually lay. So let me replay the same
>> problem statement here - what is an "exit" and how does a
>> packet know when it has gone through it? And how does a
>> router "know" its the exit router and not an interior router?
>> In the context of nested sites (e.g. workgroup, department,
>> faculty) whats _the_ exit?
>=20
> The host and the departmental router cannot know the answer to
> that question, I fear, without erecting some very complicated
> machinery.
>=20

That's my understanding of the situation!


>>=20
>> Secondly, its not just the problem of scope of a site here.
>> Its also trying to clearly understand the nature of the
>> problem and place that into juxtaposition with the various
>> proposed "solutions." =46rom memory the various exit selection
>> solutions proposed in the context of shim6 were all various
>> forms of source-address based forwarding, and for me its
>> getting the cart well and truly before the horse. Hop-by-hop
>> stateless destination-based forwarding is an incredibly
>> powerful architectural concept in packet networks, and any
>> other forwarding mechanism tends to invoke copious quantities
>> of complexity and state, and should only be contemplated as a
>> last resort of the desperate rather than the first line
>> solution.=20
>=20
> I fully agree. That would be baroque, and despite having started
> this conversation, I am not in favour of a host-based or even
> departmental-router-based solution.
>=20
>> So why was exit selection an issue in shim6? Surely
>> if routing is working, and shim6 does not assume broken
>> routing, if a route to a destination is offered, then its a
>> valid route. So why select exits that are not being offered
>> by routing as being on the best path? =46rom my memory I
>> believe it was because some folk  thought that a) unicast
>> reverse route filtering would be prevalent in IPv6 and that
>> b) clients could not negotiate filters with their provider.
>> But is a) true? and is b) really true?=20
>=20
> Well, it seems from other responses that both are real problems,
> but not specific to shim6. draft-v6ops-multihoming-without-nat66
> talks about this, and at first sight, a valid approach for
> the problems described in that draft would work just fine for
> shim6 too. Maybe shim6 people should read that draft carefully.

indeed,

  Geoff


From fred@cisco.com  Sun Mar 13 18:08:23 2011
Return-Path: <fred@cisco.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 D29B43A68F3 for <shim6@core3.amsl.com>; Sun, 13 Mar 2011 18:08:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.399
X-Spam-Level: 
X-Spam-Status: No, score=-109.399 tagged_above=-999 required=5 tests=[AWL=1.200, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 8+4FaiaTFsap for <shim6@core3.amsl.com>; Sun, 13 Mar 2011 18:08:22 -0700 (PDT)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 8912E3A6BDE for <shim6@ietf.org>; Sun, 13 Mar 2011 18:08:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=407; q=dns/txt; s=iport; t=1300064985; x=1301274585; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=qv3uGj+/4SPG5XIqJnTvIpIsJQx3ltQlBSgXOgERM9E=; b=M+QAV2/VwfMvGYCidKpOB+4yAMciB9usnhC4MCGMz12cUEThIhpq+I4e ckdIzmecI3017sscSRhI0px0oNXK0KwHI106iU+0CTaXKPQb+I339kfvL EkjMiKo70GH8i/Xw7pnbF3udAGVrQR2TvUnCw3exF2BGy1G5ZcX3Crn4n c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAAMIfU2tJV2b/2dsb2JhbACmD3elGZpwhWIEhSuHJ4NO
X-IronPort-AV: E=Sophos;i="4.62,312,1297036800"; d="scan'208";a="224881946"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rtp-iport-1.cisco.com with ESMTP; 14 Mar 2011 01:09:44 +0000
Received: from stealth-10-32-244-219.cisco.com (stealth-10-32-244-219.cisco.com [10.32.244.219]) by rcdn-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id p2E19dQ2008572;  Mon, 14 Mar 2011 01:09:44 GMT
Received: from [127.0.0.1] by stealth-10-32-244-219.cisco.com (PGP Universal service); Sun, 13 Mar 2011 18:09:44 -0700
X-PGP-Universal: processed; by stealth-10-32-244-219.cisco.com on Sun, 13 Mar 2011 18:09:44 -0700
Mime-Version: 1.0 (Apple Message framework v1082)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4D7D5057.2090100@gmail.com>
Date: Sun, 13 Mar 2011 18:09:26 -0700
Message-Id: <D6B510C2-A97C-4F0A-BAF8-2FF836673FCC@cisco.com>
References: <20110228223003.13022.10464.idtracker@localhost>	<845A4F08-46E7-48EE-B294-0C8368BAD1CB@cisco.com>	<20110302072822.GA20321@serpens.de>	<5AC61190-49B0-49B5-ACB1-1FA5082C0380@cisco.com>	<20110302203006.GI23030@serpens.de> <4D6EB08E.9000109@gmail.com>	<20110302214913.GG20321@serpens.de> <4D6EC293.90608@gmail.com>	<20110303065132.GH20321@serpens.de> <4D6FF098.6010600@gmail.com>	<A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr>	<4D7689CC.7060409@gmail.com> <4D76A5FF.2020704@uclouvain.be>	<4D76C461.30506@gmail.com>	<C3AC5E50-1E3F-4381-A0A4-B5023EBA529B@free.fr>	<AANLkTi=Yej0=a1q7GejBGBCjXJQrLA90J9+xpcimTuXr@mail.gmail.com>	<D7244E10-B305-45F3-9395-1C8C701D7A08@free.fr>	<733F86F7-54F7-4544-B139-5F534F143DA6@apnic.net>	<E4E83F81-BEF1-41C0-97BF-08107901758F@steffann.nl> <B96B5E8F-1752-421A-BB80-C5EE4A05DD8B@apnic.net> <4D7D5057.2090100@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1082)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: shim6-wg <shim6@ietf.org>
Subject: Re: [shim6] Exit selection [New Version Notification -	draft-mrw-nat66-08.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, 14 Mar 2011 01:08:24 -0000

On Mar 13, 2011, at 4:16 PM, Brian E Carpenter wrote:

> If you mean NPTv6, yes, it's heresy but it will no doubt get its share =
of the market. I see shim6 and multihoming-without-nat as part of the =
longer term future for medium scale enterprise sites.

Very possibly, if you can get enterprise networks to deploy it. At this =
point, it is largely DOA. What do you think the reason might be?=

From brian.e.carpenter@gmail.com  Sun Mar 13 20:23:24 2011
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 39E413A6A85 for <shim6@core3.amsl.com>; Sun, 13 Mar 2011 20:23:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.448
X-Spam-Level: 
X-Spam-Status: No, score=-103.448 tagged_above=-999 required=5 tests=[AWL=0.151, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 UsOOBn4j2Ysg for <shim6@core3.amsl.com>; Sun, 13 Mar 2011 20:23:23 -0700 (PDT)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by core3.amsl.com (Postfix) with ESMTP id 4CD8C3A6AB4 for <shim6@ietf.org>; Sun, 13 Mar 2011 20:23:23 -0700 (PDT)
Received: by qwg5 with SMTP id 5so1232285qwg.31 for <shim6@ietf.org>; Sun, 13 Mar 2011 20:24:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:organization:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=KMU76ZUY9s8jfqDbOCGjdf+HasaGEJnMRu5oftob7Fw=; b=TTQAL6IvaZixCH30h10ZVXdFeYdN0WxY4wfWSquSUymWduFgocYi0SA/Jz+uKjKCbn lhGkCj0gOAqMNrLfu18JCYKRqEsKKdvCWOQwT7OHsXj6OLjCK203RIUIam1MkmaTB5sx ZDFbiYDmARkzH9ICKwVwxL659xXwpSU9+04Ew=
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=l5NMxDnuCqGOeCJ/zXAnQlRDzAAgUapNayZeRPUBfnRE3CpYUlum80yZ/RVhDKIPsb ZKVg1fhUb0SkC9z6joE58ZLRs00IG8QGApTTdNMJnWeGYaMg0JHS2uQRGJJnxKef2EBK U6Ii0gTWlcJ4pwP3Lf0KRPBNTBwGBTAtkMhwk=
Received: by 10.224.180.141 with SMTP id bu13mr10425661qab.346.1300073085994;  Sun, 13 Mar 2011 20:24:45 -0700 (PDT)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz [130.216.38.124]) by mx.google.com with ESMTPS id l17sm5190608qck.8.2011.03.13.20.24.43 (version=SSLv3 cipher=OTHER); Sun, 13 Mar 2011 20:24:45 -0700 (PDT)
Message-ID: <4D7D8A79.8020309@gmail.com>
Date: Mon, 14 Mar 2011 16:24:41 +1300
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: Fred Baker <fred@cisco.com>
References: <20110228223003.13022.10464.idtracker@localhost>	<845A4F08-46E7-48EE-B294-0C8368BAD1CB@cisco.com>	<20110302072822.GA20321@serpens.de>	<5AC61190-49B0-49B5-ACB1-1FA5082C0380@cisco.com>	<20110302203006.GI23030@serpens.de> <4D6EB08E.9000109@gmail.com>	<20110302214913.GG20321@serpens.de> <4D6EC293.90608@gmail.com>	<20110303065132.GH20321@serpens.de> <4D6FF098.6010600@gmail.com>	<A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr>	<4D7689CC.7060409@gmail.com> <4D76A5FF.2020704@uclouvain.be>	<4D76C461.30506@gmail.com>	<C3AC5E50-1E3F-4381-A0A4-B5023EBA529B@free.fr>	<AANLkTi=Yej0=a1q7GejBGBCjXJQrLA90J9+xpcimTuXr@mail.gmail.com>	<D7244E10-B305-45F3-9395-1C8C701D7A08@free.fr>	<733F86F7-54F7-4544-B139-5F534F143DA6@apnic.net>	<E4E83F81-BEF1-41C0-97BF-08107901758F@steffann.nl> <B96B5E8F-1752-421A-BB80-C5EE4A05DD8B@apnic.net> <4D7D5057.2090100@gmail.com> <D6B510C2-A97C-4F0A-BAF8-2FF836673FCC@cisco.com>
In-Reply-To: <D6B510C2-A97C-4F0A-BAF8-2FF836673FCC@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: shim6-wg <shim6@ietf.org>
Subject: Re: [shim6] Exit selection [New Version Notification -	draft-mrw-nat66-08.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, 14 Mar 2011 03:23:24 -0000

On 2011-03-14 14:09, Fred Baker wrote:
> On Mar 13, 2011, at 4:16 PM, Brian E Carpenter wrote:
> 
>> If you mean NPTv6, yes, it's heresy but it will no doubt get its share of the market. I see shim6 and multihoming-without-nat as part of the longer term future for medium scale enterprise sites.
> 
> Very possibly, if you can get enterprise networks to deploy it. At this point, it is largely DOA. What do you think the reason might be?

IMHO:

Firstly, because it isn't in Windows.

Secondly, because it was explicitly badmouthed by various operators a couple
of years ago, in my opinion because they didn't really understand it and
were just getting to grips with the immediate problems of deploying v6
at all.

Thirdly, because we really don't need it yet. We don't need it for
early adopters of v6 and we don't need it for very large enterprises
who can perfectly well use PI/BGP4. We also don't need it for
SOHO users, who manage well enough behind NAT44 and will manage well
enough behind NPTv6.

We'll find out in a few years whether we need shim6 for the medium
size enterprises who will discover that they want address transparency.

Oh, and we'd better make IPv6 renumbering work too. BOF in Prague.

   Brian

From remi.despres@free.fr  Mon Mar 14 02:31:38 2011
Return-Path: <remi.despres@free.fr>
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 53CB13A6C5E for <shim6@core3.amsl.com>; Mon, 14 Mar 2011 02:31:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.158
X-Spam-Level: 
X-Spam-Status: No, score=0.158 tagged_above=-999 required=5 tests=[AWL=-0.793,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_33=0.6, MANGLED_PAIN=2.3, 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 CPlP6dGmTkag for <shim6@core3.amsl.com>; Mon, 14 Mar 2011 02:31:37 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.81]) by core3.amsl.com (Postfix) with ESMTP id BA1EF3A6AEE for <shim6@ietf.org>; Mon, 14 Mar 2011 02:31:29 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2419.sfr.fr (SMTP Server) with ESMTP id CB2807000094; Mon, 14 Mar 2011 10:32:52 +0100 (CET)
Received: from [192.168.0.14] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2419.sfr.fr (SMTP Server) with ESMTP id 2AC7D7000092; Mon, 14 Mar 2011 10:32:52 +0100 (CET)
X-SFR-UUID: 20110314093252175.2AC7D7000092@msfrf2419.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <733F86F7-54F7-4544-B139-5F534F143DA6@apnic.net>
Date: Mon, 14 Mar 2011 10:32:51 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2CA07AD5-8FFE-4E21-A7DE-E3116082252A@free.fr>
References: <20110228223003.13022.10464.idtracker@localhost> <845A4F08-46E7-48EE-B294-0C8368BAD1CB@cisco.com> <20110302072822.GA20321@serpens.de> <5AC61190-49B0-49B5-ACB1-1FA5082C0380@cisco.com> <20110302203006.GI23030@serpens.de> <4D6EB08E.9000109@gmail.com> <20110302214913.GG20321@serpens.de> <4D6EC293.90608@gmail.com> <20110303065132.GH20321@serpens.de> <4D6FF098.6010600@gmail.com> <A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr> <4D7689CC.7060409@gmail.com> <4D76A5FF.2020704@uclouvain.be> <4D76C461.30506@gmail.com> <C3AC5E50-1E3F-4381-A0A4-B5023EBA529B@free.fr> <AANLkTi=Yej0=a1q7GejBGBCjXJQrLA90J9+xpcimTuXr@mail.gmail.com> <D7244E10-B305-45F3-9395-1C8C701D7A08@free.fr> <733F86F7-54F7-4544-B139-5F534F143DA6@apnic.net>
To: Geoff Huston <gih@apnic.net>
X-Mailer: Apple Mail (2.1082)
Cc: "S.P.Zeidler" <spz@serpens.de>, shim6-wg <shim6@ietf.org>, Scott Brim <scott.brim@gmail.com>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [shim6] Exit selection
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, 14 Mar 2011 09:31:38 -0000

Le 13 mars 2011 =E0 22:14, Geoff Huston a =E9crit :

> On 13/03/2011, at 3:32 AM, R=E9mi Despr=E9s wrote:
>=20
>>=20
>> Le 11 mars 2011 =E0 20:13, Scott W Brim a =E9crit :
>>=20
>>> Shim6 itself cannot select an exit.  In all but trivial cases the =
network has the intelligence and must be involved (e.g. the exit =
points).  Given that one has to involve the network, then an exit =
selection mechanism is not just for Shim6 but for anything that can take =
advantage of multiple src+dst pairs, and it should not be =
Shim6-specific. =20
>>=20
>>> Therefore whatever needs doing, I recommend that it not be done in =
Shim6 but somewhere more general -- IntArea WG looks like a good place.
>>=20
>> +1
>>=20
>=20
> wg co-chair hat OFF
>=20
> I appreciate that in the context of the IETF saying "we should not do =
this" is invariably like standing in front of a bulldozer, and like the =
bulldozer, it rarely has any effect - but nevertheless I want to share =
with you a personal opinion that we should not do this! :-)


> I have two problems with this issue of "exit selection".=20
>=20
> Firstly, I recall the demise of the site-local scoped address in IPv6. =
The compelling argument for me was one of inability of self-awareness of =
context. i.e. it was never clear where the edge of a site actually lay. =
So let me replay the same problem statement here - what is an "exit" and =
how does a packet know when it has gone through it?

The problem that needs a solution (be it called "exit selection" or =
otherwise) is that of a domain where:
- several global PA prefixes are assigned to several independent border =
nodes
- routing is done across several links in an address family other than =
global IPv6 (e.g. with ULA's to avoid renumbering in case of a change in =
the set of PA prefixes)
- some hosts need e2e address transparency (e.g. for SHIM6)

> And how does a router "know" its the exit router and not an interior =
router? In the context of nested sites (e.g. workgroup, department, =
faculty) whats _the_ exit?

Let "border node" replace "exit router" as name of a node that is =
assigned a PA on upstream network and that also deals with the local =
address family. =20
Now:
- e2e transparency can be preserved by encapsulating of e2e packets in =
locally routable packets.
- in addition to its local address, a SHIM6 host must know its =
(multiple) global addresses=20
- if it also knows, for each PA appearing at the head of its global =
addresses, the local address of the border node to be used when =
transmitting with this PA in its source addresses, it can address =
encapsulating packets to the right border node using this address.

This is the approach I tried to introduce with SAM for multihoming =
(draft-despres-softwire-sam-01 sec 3.3), but, as SAM was presented as a =
generic tool, it was found to have too large a scope.=20
Its applications have then progressed under different names:
- 4rd for stateless IPv4 across IPv6
- 6a44 for native IPv6 across NAT44-CPE's

Its application to global IPv6 across ULA's didn't receive a name yet =
because it didn't catch much attention so far.=20
Let me propose "Geetalad" for Generic E2E Transparency Across Local =
Addressing Domains.

What about a bar bof in Prague?

=20
> Secondly, its not just the problem of scope of a site here. Its also =
trying to clearly understand the nature of the problem and place that =
into juxtaposition with the various proposed "solutions." =46rom memory =
the various exit selection solutions proposed in the context of shim6 =
were all various forms of source-address based forwarding, and for me =
its getting the cart well and truly before the horse.

> Hop-by-hop stateless destination-based forwarding is an incredibly =
powerful architectural concept in packet networks, and any other =
forwarding mechanism tends to invoke copious quantities of complexity =
and state, and should only be contemplated as a last resort of the =
desperate rather than the first line solution.

Full agreement that routing within the domain has to remain as is, =
hop-by-hop stateless (this is the case with SAM/Geetalad).=20


> So why was exit selection an issue in shim6? Surely if routing is =
working, and shim6 does not assume broken routing, if a route to a =
destination is offered, then its a valid route. So why select exits that =
are not being offered by routing as being on the best path?

> =46rom my memory I believe it was because some folk  thought that a) =
unicast reverse route filtering would be prevalent in IPv6 and that b) =
clients could not negotiate filters with their provider. =20

> But is a) true?

I am not sure about what is actually done by various providers, but the =
fact is that ingress filtering is necessary to avoid source address =
spoofing.
It is therefore an elementary security tool.


> and is b) really true?

Even if possible, negotiating filters would be an operational burden, =
both for providers and for customers.
If the border node that has been assigned a PA is always traversed by =
packets leaving the domain with this PA in source addresses, there is no =
need for it.


> Frankly I'm pretty sceptical that this is the case and it concerns me =
that this is a case of over solving.

A solution that combines multihoming, local addressing independence, and =
shim6, is IMHO worth having, especially if it is stateless and =
straightforward.


> my 2c anyway

Thanks for your 2c.
I hope you will be interested in mine.

Regards,
RD




From remi.despres@free.fr  Mon Mar 14 02:41:08 2011
Return-Path: <remi.despres@free.fr>
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 211F23A6C5E for <shim6@core3.amsl.com>; Mon, 14 Mar 2011 02:41:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.969
X-Spam-Level: 
X-Spam-Status: No, score=-0.969 tagged_above=-999 required=5 tests=[AWL=0.380,  BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_33=0.6, 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 qGF-QSKDSM2J for <shim6@core3.amsl.com>; Mon, 14 Mar 2011 02:41:07 -0700 (PDT)
Received: from smtp24.services.sfr.fr (smtp24.services.sfr.fr [93.17.128.81]) by core3.amsl.com (Postfix) with ESMTP id BC0B33A6C5D for <shim6@ietf.org>; Mon, 14 Mar 2011 02:41:06 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2419.sfr.fr (SMTP Server) with ESMTP id 8014F7000098; Mon, 14 Mar 2011 10:42:29 +0100 (CET)
Received: from [192.168.0.14] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2419.sfr.fr (SMTP Server) with ESMTP id 1C4017000093; Mon, 14 Mar 2011 10:42:29 +0100 (CET)
X-SFR-UUID: 20110314094229115.1C4017000093@msfrf2419.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?R=E9mi_Despr=E9s?= <remi.despres@free.fr>
In-Reply-To: <4D7D45F9.6030409@gmail.com>
Date: Mon, 14 Mar 2011 10:42:28 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B969BD68-8D9C-43EC-B24F-DEF60B19DD4C@free.fr>
References: <20110228223003.13022.10464.idtracker@localhost>	<845A4F08-46E7-48EE-B294-0C8368BAD1CB@cisco.com>	<20110302072822.GA20321@serpens.de>	<5AC61190-49B0-49B5-ACB1-1FA5082C0380@cisco.com>	<20110302203006.GI23030@serpens.de> <4D6EB08E.9000109@gmail.com>	<20110302214913.GG20321@serpens.de> <4D6EC293.90608@gmail.com>	<20110303065132.GH20321@serpens.de> <4D6FF098.6010600@gmail.com>	<A3C0405F-F5E1-4911-A67B-CB3FCD153B29@free.fr>	<4D7689CC.7060409@gmail.com> <4D76A5FF.2020704@uclouvain.be>	<4D76C461.30506@gmail.com>	<C3AC5E50-1E3F-4381-A0A4-B5023EBA529B@free.fr>	<AANLkTi=Yej0=a1q7GejBGBCjXJQrLA90J9+xpcimTuXr@mail.gmail.com>	<D7244E10-B305-45F3-9395-1C8C701D7A08@free.fr> <733F86F7-54F7-4544-B139-5F534F143DA6@apnic.net> <4D7D45F9.6030409@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1082)
Cc: Scott Brim <scott.brim@gmail.com>, shim6-wg <shim6@ietf.org>, "S.P.Zeidler" <spz@serpens.de>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [shim6] Exit selection [New Version Notification -	draft-mrw-nat66-08.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, 14 Mar 2011 09:41:08 -0000

Le 13 mars 2011 =E0 23:32, Brian E Carpenter a =E9crit :

> On 2011-03-14 10:14, Geoff Huston wrote:
>> On 13/03/2011, at 3:32 AM, R=E9mi Despr=E9s wrote:
>>=20
>>> Le 11 mars 2011 =E0 20:13, Scott W Brim a =E9crit :
>>>=20
>>>> Shim6 itself cannot select an exit.  In all but trivial
>>>> cases the network has the intelligence and must be
>>>> involved (e.g. the exit points).  Given that one has to
>>>> involve the network, then an exit selection mechanism is
>>>> not just for Shim6 but for anything that can take
>>>> advantage of multiple src+dst pairs, and it should not be
>>>> Shim6-specific. Therefore whatever needs doing, I
>>>> recommend that it not be done in Shim6 but somewhere more
>>>> general -- IntArea WG looks like a good place.
>>> +1
>>>=20
>>=20
>> wg co-chair hat OFF
>>=20
>> I appreciate that in the context of the IETF saying "we
>> should not do this" is invariably like standing in front of a
>> bulldozer, and like the bulldozer, it rarely has any effect -
>> but nevertheless I want to share with you a personal opinion
>> that we should not do this! :-)
>=20
> If by "we" you mean the shim6 WG, I'm inclined to agree,
> beyond documenting that this problem needs to be solved
> generically for IPv6. I don't believe shim6 is really a
> special case: once you have prefixes from and exits to several
> different ISPs, you have a potential problem.
>=20
>>=20
>> I have two problems with this issue of "exit selection".
>>=20
>> Firstly, I recall the demise of the site-local scoped address
>> in IPv6. The compelling argument for me was one of inability
>> of self-awareness of context. i.e. it was never clear where
>> the edge of a site actually lay. So let me replay the same
>> problem statement here - what is an "exit" and how does a
>> packet know when it has gone through it? And how does a
>> router "know" its the exit router and not an interior router?
>> In the context of nested sites (e.g. workgroup, department,
>> faculty) whats _the_ exit?
>=20
> The host and the departmental router cannot know the answer to
> that question, I fear, without erecting some very complicated
> machinery.

Complicated, not that I know if its involving hosts is accepted (see =
below)
=20

>> Secondly, its not just the problem of scope of a site here.
>> Its also trying to clearly understand the nature of the
>> problem and place that into juxtaposition with the various
>> proposed "solutions." =46rom memory the various exit selection
>> solutions proposed in the context of shim6 were all various
>> forms of source-address based forwarding, and for me its
>> getting the cart well and truly before the horse. Hop-by-hop
>> stateless destination-based forwarding is an incredibly
>> powerful architectural concept in packet networks, and any
>> other forwarding mechanism tends to invoke copious quantities
>> of complexity and state, and should only be contemplated as a
>> last resort of the desperate rather than the first line
>> solution.=20
>=20
> I fully agree. That would be baroque, and despite having started
> this conversation, I am not in favour of a host-based or even
> departmental-router-based solution.

Well, if host based is the only complete solution, it shouldn't IMHO be =
taboo.=20

>=20
>> So why was exit selection an issue in shim6? Surely
>> if routing is working, and shim6 does not assume broken
>> routing, if a route to a destination is offered, then its a
>> valid route. So why select exits that are not being offered
>> by routing as being on the best path? =46rom my memory I
>> believe it was because some folk  thought that a) unicast
>> reverse route filtering would be prevalent in IPv6 and that
>> b) clients could not negotiate filters with their provider.
>> But is a) true? and is b) really true?=20
>=20
> Well, it seems from other responses that both are real problems,
> but not specific to shim6. draft-v6ops-multihoming-without-nat66
> talks about this, and at first sight, a valid approach for
> the problems described in that draft would work just fine for
> shim6 too. Maybe shim6 people should read that draft carefully.

I agree that it is a valid approach.
However, AFAIK, it doesn't deal with ULA's:
- it assumes that hosts have their global IPv6 addresses
- it doesn't say how global addresses would traverse domains in which =
ULA's are used.
In this respect, the SAM approach is complementary.

RD



>=20
>    Brian
>=20
>> Frankly I'm pretty
>> sceptical that this is the case and it concerns me that this
>> is a case of over solving.
>>=20
>> my 2c anyway
>>=20
>> Geoff
>>=20
>>=20
>> _______________________________________________ shim6 mailing
>> list shim6@ietf.org=20
>> https://www.ietf.org/mailman/listinfo/shim6
>>=20
>=20
> _______________________________________________
> shim6 mailing list
> shim6@ietf.org
> https://www.ietf.org/mailman/listinfo/shim6


