
From nobody Tue Jan  6 03:14:11 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 162C61A9142; Tue,  6 Jan 2015 03:14:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id az34e5YA3pjp; Tue,  6 Jan 2015 03:14:06 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CFEA1A1BEC; Tue,  6 Jan 2015 03:14:06 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id A9360629F; Tue,  6 Jan 2015 03:14:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version; s=selector1; bh=6q0cDvaWTd1Hm6QleC/jFhGybTU =; b=NIHLZL9KwuqCJPqrVmBTVMIOKfRyy4ebA0CFnQPtDAL6SQasLudTEgHUIFO fPRFWScLdCoqOb5tNJdrRLbB16VNbckQfWsCrLcO2mRq9I8C0+Zhnz31U9a2PvrS h7dTypd2duqOmplpA8MXSf5CfLAuDujfepCc5n1Nb2AItZ98=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version; q=dns; s=selector1; b=aROOllMnCL9equwxrNIu1 K/du+mXHl3Bp2+H2qJwcvNN3N6V+WyG4IE0IjSiWKpuHG1lcbhwD5WYogK+9Hp0T I586eZUb9PDjrdRuUIghFs1jlRZHs0R8sqszsLZoyfxUSa6nFx/iX+jo7F1kcTmj c8vvMIioqCfNXRUMUW6pas=
Received: from gomlefisk.localdomain (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 52A7A617B; Tue,  6 Jan 2015 03:14:05 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 070DD3C1994E; Tue,  6 Jan 2015 12:14:15 +0100 (CET)
From: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: 6MAN cross-wg review: draft-ietf-l2tpext-keyed-ipv6-tunnel-01
Date: Tue, 6 Jan 2015 12:14:14 +0100
Message-Id: <232077E7-7135-41E8-B0DB-C786F8C410CA@employees.org>
To: 6man WG <ipv6@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2064\))
X-Mailer: Apple Mail (2.2064)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/OUruEkjxyS-37ZpoHSe5w2qBOvI
Cc: l2tpext@ietf.org, l2tpext-chairs@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2015 11:14:08 -0000

Hi,

The chairs of l2tpext have asked for a 6man review of:

Title: Keyed IPv6 Tunnel
https://tools.ietf.org/html/draft-ietf-l2tpext-keyed-ipv6-tunnel-01

Can we get a couple of volunteers please? As well as any other comments =
to the lists are welcome of course.
Please keep l2tpext@ietf.org in CC.

Best regards,
Ole


From nobody Tue Jan  6 07:26:34 2015
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9F251A00E1; Tue,  6 Jan 2015 07:26:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o0kqJrfF93gY; Tue,  6 Jan 2015 07:26:16 -0800 (PST)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56D5D1A00A8; Tue,  6 Jan 2015 07:26:16 -0800 (PST)
Received: by mail-pa0-f51.google.com with SMTP id ey11so31343221pad.10; Tue, 06 Jan 2015 07:26:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=JHZRPpvMVNRCAbo7XYtpu0uZBKGGRJkRfRyVtpsxGuY=; b=y4gixdctYoa1bqWmm4IjyneJsYUnZ2mepeCXlihMaNWcDs8UYlqbsr1KJPWMrKxX/q 9HBOGU/gBjon1mC70KQe+9N/hjeEAa8YEP37jUCtIR4gxdH1vwq9GblkWYYNAC8nHvfW Z0Y2GMpuFbn4PXK+ONaTSLjwno2f+fjrc3KX/Aa/Z/59yV3pDHgW/m/ckFEmw/7z/dVT ZtUnA7RdJO2bw7GdcrwIXAlxAJykOwbkSQAH5Vm57LGeSbPMQHmMthPTm8i9iegxc+tu clG0n+WnZSINwXbEMcOMuIxEds170JTCx90TulEHM19VYbxvWDAKiHxlLKdHSc04zj/K YG3Q==
X-Received: by 10.70.89.129 with SMTP id bo1mr160246583pdb.23.1420557975552; Tue, 06 Jan 2015 07:26:15 -0800 (PST)
Received: from [10.82.101.41] (rtp-isp-nat1.cisco.com. [64.102.254.33]) by mx.google.com with ESMTPSA id wi15sm57689798pac.21.2015.01.06.07.26.13 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 06 Jan 2015 07:26:14 -0800 (PST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: [6lo] [Roll] call for consensus for the RPL RPI / RH3 compression
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <23FC8FE6-C41D-4627-99FC-DA51FE5777B8@cisco.com>
Date: Tue, 6 Jan 2015 09:33:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <97A18603-2934-481E-8859-711B00FB359F@gmail.com>
References: <E045AECD98228444A58C61C200AE1BD848AC2314@xmb-rcd-x01.cisco.com>,  <CE9445B8-BA8E-4112-B892-6BCDED74D8DC@gmail.com> <23FC8FE6-C41D-4627-99FC-DA51FE5777B8@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/eWU9eKdD9SPCqQ9-vRjMLWqKeKY
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "6lo-chairs@tools.ietf.org" <6lo-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>, "6lo@ietf.org WG" <6lo@ietf.org>, "int-ads@tools.ietf.org" <int-ads@tools.ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2015 15:26:20 -0000

(Adding 6man because of architecture issues)

On Jan 6, 2015, at 1:22 AM 1/6/15, Pascal Thubert (pthubert) =
<pthubert@cisco.com> wrote:

> Hello Ralph=20
>=20
> You certainly got it all right.
>=20
> To your question we started through the NHC and found that path less =
efficient than Laurent's initial suggestion to place all the LLN routing =
artifacts in a different header/dispatch whatever the correct term is =
for that object.
>=20
> One additional concern that doesn't show in your mail is the need for =
IP encapsulation when the artifacts are added by a router on the way or =
must be removed at LLN egress. By leaving the original IPv6 packet =
intact we simplify that matter and optimize the overall result by =
providing an improved compression for the outter header.

Yeah, I noticed the issue of IP encap hasn't been addressed (if I recall =
correctly) in draft-thubert-6lo-rpl-nhc...

But ... in my opinion, moving the LLN artifacts to the header/dispatch =
in the way defined in draft-thubert-6lo-routing-dispatch raises, =
implicitly, an important architectural issue: is the information in the =
dispatch header compressed IPv6 headers or headers for an independent, =
sub-IP protocol?

My understanding is that the IETF has made an architectural decision to =
do all the mesh network forwarding and routing in IPv6, so as to reuse =
as much as possible existing technology and associated infrastructure =
such as OAM.  If the dispatch header does not contain compressed IPv6 =
headers, per se, then this architectural question would lead me to =
investigate the completeness of the new protocol and the impacts of the =
new protocol on IPv6 and network operations. =20

>=20
> The new proposal also reopens the dispatch space (1/3 of the total) =
that is used is mesh under for mesh header, so it can also be use AND =
extended as TLV in route over.

There are both architectural and pragmatic issues in the design of the =
RPL-in-dispatch protocol.

The upcoming bakeoff might be a way to stimulate some running code that =
would check out all the potential impacts of moving the RPL information =
to a sub-IP protocol.

- Ralph

>=20
> Makes sense?
>=20
> Pascal
>=20
>> Le 5 janv. 2015 =E0 23:29, Ralph Droms <rdroms.ietf@gmail.com> a =
=E9crit :
>>=20
>> Do I have it right that:
>>=20
>> 1) draft-thubert-roll-flow-label-02 compresses RPL RPI but not RH3
>> 2) draft-thubert-6lo-rpl-nhc-02 compresses RPL RPI and might be =
extended to compress RH3
>> 3) draft-thubert-6lo-routing-dispatch-01 compresses both RPL RPI and =
RH3
>>=20
>> In discussion during the IETF-91 6lo working group meeting, a concern =
was raised about further consumption of NHC codepoints beyond what is =
defined in draft-thubert-6lo-rpl-nhc-02 for a future RH3 compression =
scheme.
>>=20
>> Pascal, Carsten - as you have devised a mechanism for RH3 compression =
in draft-thubert-6lo-routing-dispatch-01, would you be able to retrofit =
a version of that mechanism into draft-thubert-6lo-rpl-nhc-02?  This =
extension to NHC compression would provide an explicit proposal for =
evaluation of RPL header compression in NHC.
>>=20
>> - Ralph
>>=20
>> _______________________________________________
>> Roll mailing list
>> Roll@ietf.org
>> https://www.ietf.org/mailman/listinfo/roll
>=20
> _______________________________________________
> 6lo mailing list
> 6lo@ietf.org
> https://www.ietf.org/mailman/listinfo/6lo


From nobody Tue Jan  6 07:31:11 2015
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5BE81A0211; Tue,  6 Jan 2015 07:31:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8tXwRTcY0kLk; Tue,  6 Jan 2015 07:31:02 -0800 (PST)
Received: from mail-qg0-x233.google.com (mail-qg0-x233.google.com [IPv6:2607:f8b0:400d:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A784D1A00DB; Tue,  6 Jan 2015 07:30:56 -0800 (PST)
Received: by mail-qg0-f51.google.com with SMTP id i50so16517624qgf.24; Tue, 06 Jan 2015 07:30:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc:reply-to :content-transfer-encoding:message-id:references:to; bh=D79qegj4l2no82i5Hq2/nlbBOzYMBDxby9wBXBYgI3Y=; b=Tf+gjgL7ZCJpE1e0+Q4DdlSX+BFBN8VYBS++31Y7VmTabXYMD6vPZUry2JjEA8V4Hp x++LUPbGTz5Jupqv9aLt27Rn+MLC1GaIv3uvPaOV/WwKHfD1U1eDf459Gy6mXQXBHiWM jKRWVBGOy9S+XcRp2yCy/vrTPZ9djP+h6b3gzcs1U5/9XZbz1u7PJHQ3iJgb8ikVee64 X2d2JJ585FX0REbOOm3M/rKb1JCvKdQd4KGM709SJqRO7I0iH+HUDxPVNlDVzZsVYqsu RyxwiPA9UZ/oUumuYErZSsrLyFSlrfRlsMcy5OlG2IRbDMDJybJc5+O3Y+aOY0eRaV+R e6Gw==
X-Received: by 10.140.28.200 with SMTP id 66mr130317171qgz.16.1420558255516; Tue, 06 Jan 2015 07:30:55 -0800 (PST)
Received: from [10.82.101.41] (rtp-isp-nat-pool1-1.cisco.com. [64.102.254.34]) by mx.google.com with ESMTPSA id 77sm53566540qgx.43.2015.01.06.07.30.54 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 06 Jan 2015 07:30:55 -0800 (PST)
Subject: Re: [Roll] call for consensus for the RPL RPI / RH3 compression
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <000701d02815$f43df5f0$dcb9e1d0$@olddog.co.uk>
Date: Tue, 6 Jan 2015 10:30:39 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3FFF5CDE-5C65-4AC1-AAAB-A6CBCE2BC087@gmail.com>
References: <E045AECD98228444A58C61C200AE1BD848AC2314@xmb-rcd-x01.cisco.com> <184B78CA-953E-45AB-B00C-B3A12CFE4605@tzi.org> <E045AECD98228444A58C61C200AE1BD848AC7D04@xmb-rcd-x01.cisco.com> <54942758.6090705@innovationslab.net> <E045AECD98228444A58C61C200AE1BD848AC86C5@xmb-rcd-x01.cisco.com> <549440F0.8040407@innovationslab.net> <5C9D8B2D-8779-450A-B558-D35323BA18FE@tzi.org> <12622.1420055894@sandelman.ca> <000701d02815$f43df5f0$dcb9e1d0$@olddog.co.uk>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/oMJHfCjc9QuGHJ4R1mITvVgGAe8
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6lo-chairs@tools.ietf.org, 6man WG <ipv6@ietf.org>, rtg-ads@tools.ietf.org, "6lo@ietf.org WG" <6lo@ietf.org>, int-ads@tools.ietf.org, 6tisch@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2015 15:31:05 -0000

On Jan 4, 2015, at 6:59 AM 1/4/15, Adrian Farrel <adrian@olddog.co.uk> =
wrote:

> Michael,
>=20
> Thanks for continuing to try to wrangle this situation.

Agreeing - thanks.

> [...]
>> Please: how do we proceed?
>=20
> Consensus can sometimes be hard-won and slow. It is one of the things =
that makes people claim the IETF is slow. On the other hand, the =
alternative to consensus is, erm, no consensus.
>=20
> In agreeing consensus, however, we may need to declare minority =
opinions "in the rough" [RFC7282] if there is a body of opinion that one =
way of doing things is preferred and if the drawbacks of that approach =
are clearly recognised and accepted.

Yes, and, in this particular case, there are at least 4 working groups =
involved, which will make determining and declaring consensus even more =
difficult.


>=20
> I see the plugfest as an important way of reaching consensus on this =
issue. That is, if the plugfest shows that a particular approach is =
functional and not harmful it provides a strong case for documenting and =
standardising the mechanism.

Another outcome of the plugfest would be to assess the quality of the =
existing drafts (can an implementation be built from just the text in =
the draft) and the impact of the new mechanisms on other parts of the =
IPv6 suite as well as network operation.

>=20
> Beyond that it may be most helpful to note the objections to the =
"preferred" approach and to write text that explains the concerns and =
how they are mitigated (for example, not sending traffic out of admin =
domains without applying some magic policy).

I don't know that we have enough detail and discussion, yet, to have =
determined a "preferred" approach.=20

- Ralph
=20
>=20
> Adrian
>=20
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll


From nobody Tue Jan  6 08:08:15 2015
Return-Path: <pthubert@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D1541A0072; Tue,  6 Jan 2015 08:08:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JFOe2WYWX1AJ; Tue,  6 Jan 2015 08:08:00 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 656C21A005D; Tue,  6 Jan 2015 08:08:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2501; q=dns/txt; s=iport; t=1420560481; x=1421770081; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=mK4wrhCNBjKl+J9FMlVdN4GNuObTJ0HGLPsfQksxBMs=; b=ZkiK9HnX0vhJ3tGIWwg31BFWYyyan5sH3bbwNoyoHkC00kP0L4R5Itpx GUfY8kVUV1t4X2pUG2p+NegQjEIMkZ3usmk6YnSblBftgox2/Yfm0blkp Lx/WElFxZVrhOvZP8Vf1RnhQX45ZY3Tp3WlLwVyTgcSmMk7xPVZHubMeB s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnUFABQHrFStJV2b/2dsb2JhbABcgwZSWATEG4IbCoUpSgKBDhYBAQEBAX2EDQEBAwEBAQEaUQsFCwIBCA4UJCEGCyUCBA4FCIgQAwkIDb4ODYNOAQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSNToFSJzEHgxaBEwWJJ4R5hzGNQ4VaIoNub4EDQn4BAQE
X-IronPort-AV: E=Sophos;i="5.07,708,1413244800"; d="scan'208";a="384759607"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-3.cisco.com with ESMTP; 06 Jan 2015 16:08:00 +0000
Received: from xhc-aln-x01.cisco.com (xhc-aln-x01.cisco.com [173.36.12.75]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t06G7xPZ006736 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 6 Jan 2015 16:07:59 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.179]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0195.001; Tue, 6 Jan 2015 10:07:59 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Ralph Droms <rdroms.ietf@gmail.com>, "Routing Over Low power and Lossy networks" <roll@ietf.org>
Subject: RE: [6tisch] [6lo] [Roll] call for consensus for the RPL RPI / RH3 compression
Thread-Topic: [6tisch] [6lo] [Roll] call for consensus for the RPL RPI / RH3 compression
Thread-Index: AQHQKcUicqdmXylOn02aReH7B74uTpyzP7vQ
Date: Tue, 6 Jan 2015 16:07:58 +0000
Deferred-Delivery: Tue, 6 Jan 2015 16:07:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD848B0D992@xmb-rcd-x01.cisco.com>
References: <E045AECD98228444A58C61C200AE1BD848AC2314@xmb-rcd-x01.cisco.com>,  <CE9445B8-BA8E-4112-B892-6BCDED74D8DC@gmail.com> <23FC8FE6-C41D-4627-99FC-DA51FE5777B8@cisco.com> <97A18603-2934-481E-8859-711B00FB359F@gmail.com>
In-Reply-To: <97A18603-2934-481E-8859-711B00FB359F@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.49.80.18]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/RhU3PpPzSyl0QDMWwdOAi1pL25o
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "6lo-chairs@tools.ietf.org" <6lo-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>, "6lo@ietf.org WG" <6lo@ietf.org>, "int-ads@tools.ietf.org" <int-ads@tools.ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2015 16:08:03 -0000

Hello Ralph:

> Yeah, I noticed the issue of IP encap hasn't been addressed (if I recall =
correctly)
> in draft-thubert-6lo-rpl-nhc...

[PT] Yes, by design. The NHC draft has a more pragmatic and limited scope.=
=20
It covers the compression of the RPL option.=20
Whatever is used for IP in IP compression and RH3 is unchanged by that draf=
t.

> But ... in my opinion, moving the LLN artifacts to the header/dispatch in=
 the way
> defined in draft-thubert-6lo-routing-dispatch raises, implicitly, an impo=
rtant
> architectural issue: is the information in the dispatch header compressed=
 IPv6
> headers or headers for an independent, sub-IP protocol?

[PT] That would not be the goal, Ralph.=20

The idea is that there is a biunivocal correspondence between the compresse=
d and the uncompressed format.
The outter header with the RPL option and the RH3 (whichever are needed) wo=
uld be placed in the new dispatch.=20
But the 6LoWPAN expansion would result in the packet as it stands today.

Makes sense?

Pascal
> >
> >> Le 5 janv. 2015 =E0 23:29, Ralph Droms <rdroms.ietf@gmail.com> a =E9cr=
it :
> >>
> >> Do I have it right that:
> >>
> >> 1) draft-thubert-roll-flow-label-02 compresses RPL RPI but not RH3
> >> 2) draft-thubert-6lo-rpl-nhc-02 compresses RPL RPI and might be extend=
ed to
> compress RH3
> >> 3) draft-thubert-6lo-routing-dispatch-01 compresses both RPL RPI and R=
H3
> >>
> >> In discussion during the IETF-91 6lo working group meeting, a concern =
was
> raised about further consumption of NHC codepoints beyond what is defined=
 in
> draft-thubert-6lo-rpl-nhc-02 for a future RH3 compression scheme.
> >>
> >> Pascal, Carsten - as you have devised a mechanism for RH3 compression =
in
> draft-thubert-6lo-routing-dispatch-01, would you be able to retrofit a ve=
rsion of
> that mechanism into draft-thubert-6lo-rpl-nhc-02?  This extension to NHC
> compression would provide an explicit proposal for evaluation of RPL head=
er
> compression in NHC.
> >>
> >> - Ralph
> >>
> >> _______________________________________________
> >> Roll mailing list
> >> Roll@ietf.org
> >> https://www.ietf.org/mailman/listinfo/roll
> >
> > _______________________________________________
> > 6lo mailing list
> > 6lo@ietf.org
> > https://www.ietf.org/mailman/listinfo/6lo
>=20
> _______________________________________________
> 6tisch mailing list
> 6tisch@ietf.org
> https://www.ietf.org/mailman/listinfo/6tisch


From nobody Tue Jan  6 09:02:02 2015
Return-Path: <mcr@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D40B1A1A25; Tue,  6 Jan 2015 09:01:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EOtdsv0dgEEu; Tue,  6 Jan 2015 09:01:56 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E66D1A1A09; Tue,  6 Jan 2015 09:01:56 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id CB97D20098; Tue,  6 Jan 2015 12:07:14 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id E92BB637FE; Tue,  6 Jan 2015 12:01:54 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id D7802637EA; Tue,  6 Jan 2015 12:01:54 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Subject: Re: [6tisch] [6lo] [Roll] call for consensus for the RPL RPI / RH3 compression
In-Reply-To: <97A18603-2934-481E-8859-711B00FB359F@gmail.com>
References: <E045AECD98228444A58C61C200AE1BD848AC2314@xmb-rcd-x01.cisco.com>,  <CE9445B8-BA8E-4112-B892-6BCDED74D8DC@gmail.com> <23FC8FE6-C41D-4627-99FC-DA51FE5777B8@cisco.com> <97A18603-2934-481E-8859-711B00FB359F@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 06 Jan 2015 12:01:54 -0500
Message-ID: <29592.1420563714@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/Pwt9qBScZazcF6IYNibau22F0X8
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "6lo-chairs@tools.ietf.org" <6lo-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, "6lo@ietf.org WG" <6lo@ietf.org>, "int-ads@tools.ietf.org" <int-ads@tools.ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2015 17:01:58 -0000

--=-=-=
Content-Type: text/plain


Ralph Droms <rdroms.ietf@gmail.com> wrote:
    > But ... in my opinion, moving the LLN artifacts to the header/dispatch
    > in the way defined in draft-thubert-6lo-routing-dispatch raises,
    > implicitly, an important architectural issue: is the information in the
    > dispatch header compressed IPv6 headers or headers for an independent,
    > sub-IP protocol?

My answer is that a sub-IP protocol can encapsulate arbitrary layer-3 packets.
In particular, one can have overlapping IP addressing contexts, and there is
no implicit l3-routing assumed between sub-IP protocols.
In the LLN case, the l3-layer is constrained; the additional "tag" (the RPL
Instance ID) is used to select a particular QoS much like the DSCP can do.
Routing between instanceIDs is assumed; but potentially not every node has
the specific routes that permits it to do that.

    > My understanding is that the IETF has made an architectural decision to
    > do all the mesh network forwarding and routing in IPv6, so as to reuse
    > as much as possible existing technology and associated infrastructure
    > such as OAM.  If the dispatch header does not contain compressed IPv6
    > headers, per se, then this architectural question would lead me to
    > investigate the completeness of the new protocol and the impacts of the
    > new protocol on IPv6 and network operations.

I think that all of the HC methods *can* be implemented as Bump-in-the-Stack
activities; and in particular the loop LLN->ethernet->LLN should be
lossless(%). (ethernet->LLN->ethernet is both out of scope [the LLN is never
a transit network], and also potentially lossy as some generality of 6553 and
6554 may sacrificed.

(%)-lossless definition assumes flow label is always zero.

A think that concerns me is that I think that most constrained devices will
not implement HC as a bump in the stack, but will uncompress the headers
directly into internal control structures, and may have loose the ability to
process uncompressed 6553/6554 headers.

One could view this as a vestigal appendix-like thing that evolved away.
This could be regarded as good: less unused/untested code that will get
exploited.   This could be regarded as bad: as frame sizes in LLN radios grow
(802.15.4g, I'm told, has much larger frames) some systems might have no
6lowpan layer, and interoperation opportunities might become difficult.

(I picked the appendix on purpose: some say that it was used to digest
grasses/cellulose. If we had a useful appendix, humans might never starve...)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVKwU/4CLcPvd0N1lAQJwJAgAiXGfFH0Nai5lmxoLoi8+QCLZXkbfwPzS
PLxKQE0gxQuftKPm95vBSBV5sU0deLNMv0PhtL5agLiXkRVB601grTrohE3xjqeD
khW7da/pURiL4BKIs+eRQaaKH33nJ3XUHDd02MCJsFNKPWGTYZ8YmKiM6q7HtFEN
wdr3IRFtcl/3/0dqA/VzhePG5xrfftLKGb/+Zs2IhSfW2eKFoKY7JFMnEuYg9T9R
mhTQPMdzpMzjt1huBHVS3mB+GzTofGO27iCiLsk22i5wz64N0jR1rcWhjGjhkuEQ
alHAjbpow0+it8BPXesaqG6jfT9P43ZNCX8uG1Gj4r1NFDFsBgTkwg==
=YlTl
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Jan  6 11:40:55 2015
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3CBE1A1B34; Tue,  6 Jan 2015 11:40:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BnetIxXrzfaz; Tue,  6 Jan 2015 11:40:44 -0800 (PST)
Received: from mail-qa0-x229.google.com (mail-qa0-x229.google.com [IPv6:2607:f8b0:400d:c00::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B500C1A1AA8; Tue,  6 Jan 2015 11:40:44 -0800 (PST)
Received: by mail-qa0-f41.google.com with SMTP id s7so17003756qap.14; Tue, 06 Jan 2015 11:40:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=c2dSJTgsnSvMeCXfCDkHqCTAory24XN31jK8ud/2cE4=; b=RnhbWBvj3DQX/ax97jVeuG4l6yqj56AYDJm4J++99EwMACwgNcXSsnjX6vDNz35fbX hzuQNlb421KKnm6nlcIEaDlNeZ/Rv3Kev54JIBAHQV11pD1NgymnwY23M7Adh1MKcOg2 QymSmOwbnwC/U+b/3BppS+468z3sjCmPR/CagTrJ/SSsdJMT2FPDbE2W/psu7pfedb57 +sQeHobsJLRgGxNv65RbUN5a3t3tKmt0VXxhFHm5w8YNNskpqN2JhkyMHQP56wz4CPhf m5P1HcFwPxiSkjEeZ18m9qcJqJadWK1QBCXxLNfaqg0Bqvm+N9edjUiEm3tIX+usOdkS JGIA==
X-Received: by 10.224.147.197 with SMTP id m5mr124300241qav.51.1420573243883;  Tue, 06 Jan 2015 11:40:43 -0800 (PST)
Received: from [10.82.101.41] (rtp-isp-nat1.cisco.com. [64.102.254.33]) by mx.google.com with ESMTPSA id 91sm17422815qgf.1.2015.01.06.11.40.42 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 06 Jan 2015 11:40:43 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: [6tisch] [6lo] [Roll] call for consensus for the RPL RPI / RH3 compression
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <29592.1420563714@sandelman.ca>
Date: Tue, 6 Jan 2015 14:40:41 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4A5D805B-B73E-49E9-952E-8A4683E20C24@gmail.com>
References: <E045AECD98228444A58C61C200AE1BD848AC2314@xmb-rcd-x01.cisco.com>,  <CE9445B8-BA8E-4112-B892-6BCDED74D8DC@gmail.com> <23FC8FE6-C41D-4627-99FC-DA51FE5777B8@cisco.com> <97A18603-2934-481E-8859-711B00FB359F@gmail.com> <29592.1420563714@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/nEgYjRlBAjYdmej3qg1xiOyYVf4
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "6lo-chairs@tools.ietf.org" <6lo-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>, Routing Over Low power and Lossy networks <roll@ietf.org>, "6lo@ietf.org WG" <6lo@ietf.org>, "int-ads@tools.ietf.org" <int-ads@tools.ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2015 19:40:47 -0000

On Jan 6, 2015, at 12:01 PM 1/6/15, Michael Richardson =
<mcr+ietf@sandelman.ca> wrote:

>=20
> Ralph Droms <rdroms.ietf@gmail.com> wrote:
>> But ... in my opinion, moving the LLN artifacts to the =
header/dispatch
>> in the way defined in draft-thubert-6lo-routing-dispatch raises,
>> implicitly, an important architectural issue: is the information in =
the
>> dispatch header compressed IPv6 headers or headers for an =
independent,
>> sub-IP protocol?
>=20
> My answer is that a sub-IP protocol can encapsulate arbitrary layer-3 =
packets.
> In particular, one can have overlapping IP addressing contexts,

"addressing contexts"?

> and there is
> no implicit l3-routing assumed between sub-IP protocols.

OK.

> In the LLN case, the l3-layer is constrained; the additional "tag" =
(the RPL
> Instance ID) is used to select a particular QoS much like the DSCP can =
do.
> Routing between instanceIDs is assumed;

..instanceIDs covering intersecting sets of nodes; i.e., some nodes are =
part of multiple instances?

> but potentially not every node has
> the specific routes that permits it to do that.

Not sure how that relates to a sub-IP protocol for carrying source =
routes and RPL tags?

>=20
>> My understanding is that the IETF has made an architectural decision =
to
>> do all the mesh network forwarding and routing in IPv6, so as to =
reuse
>> as much as possible existing technology and associated infrastructure
>> such as OAM.  If the dispatch header does not contain compressed IPv6
>> headers, per se, then this architectural question would lead me to
>> investigate the completeness of the new protocol and the impacts of =
the
>> new protocol on IPv6 and network operations.
>=20
> I think that all of the HC methods *can* be implemented as =
Bump-in-the-Stack
> activities;

That statement gets to part of my question about =
draft-thubert-6lo-routing-dispatch: in the abstract, is =
draft-thubert-6lo-routing-dispatch intended to provide a mechanism =
through which the original RPI, RH3 and IP-in-IP headers can be =
reconstructed before sending the resulting IPv6 datagram up to the IPv6 =
stack?  At the risk of being overly concerned with the details, I really =
mean "reconstruct the header" as opposed to "carry information that can =
be used to perform the same function".

> and in particular the loop LLN->ethernet->LLN should be
> lossless(%).

...where both LLNs and ethernet are part of the same RPL instance?

> (ethernet->LLN->ethernet is both out of scope [the LLN is never
> a transit network], and also potentially lossy as some generality of =
6553 and
> 6554 may sacrificed.
>=20
> (%)-lossless definition assumes flow label is always zero.
>=20
> A think that concerns me is that I think that most constrained devices =
will
> not implement HC as a bump in the stack, but will uncompress the =
headers
> directly into internal control structures, and may have loose the =
ability to
> process uncompressed 6553/6554 headers.

Yeah.  We already see a side-effect of this form of implementation in =
the desire for compression techniques that do not result in expansion =
during transit, because such expansion can require re-fragmentation of a =
datagram that might otherwise be forwarded in place without explicitly =
uncompressing to the full IPv6 representation.

>=20
> One could view this as a vestigal appendix-like thing that evolved =
away.
> This could be regarded as good: less unused/untested code that will =
get
> exploited.  This could be regarded as bad: as frame sizes in LLN =
radios grow
> (802.15.4g, I'm told, has much larger frames) some systems might have =
no
> 6lowpan layer, and interoperation opportunities might become =
difficult.

I think there are also important issues to think about the interaction =
between a sub-IP protocol and the rest of the IPv6 protocol.  If the =
abstraction is that the sub-IP bits reconstruct into IPv6 headers, we =
may have less collateral damage to worry about.  Documents defining that =
behavior will beed to be careful to show the details and that the =
conversions are lossless.

- Ralph

>=20
> (I picked the appendix on purpose: some say that it was used to digest
> grasses/cellulose. If we had a useful appendix, humans might never =
starve...)
>=20
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -=3D IPv6 IoT consulting =3D-
>=20
>=20
>=20


From nobody Tue Jan  6 15:13:38 2015
Return-Path: <mcr@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1633B1A01CB; Tue,  6 Jan 2015 15:13:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lDJLgH6ySPKD; Tue,  6 Jan 2015 15:13:32 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B925A1A016A; Tue,  6 Jan 2015 15:13:32 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 0351320098; Tue,  6 Jan 2015 18:18:52 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 585E0637FE; Tue,  6 Jan 2015 18:13:31 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 3D87A63745; Tue,  6 Jan 2015 18:13:31 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [6tisch] [6lo] [Roll] call for consensus for the RPL RPI / RH3 compression
In-Reply-To: <4A5D805B-B73E-49E9-952E-8A4683E20C24@gmail.com>
References: <E045AECD98228444A58C61C200AE1BD848AC2314@xmb-rcd-x01.cisco.com>,  <CE9445B8-BA8E-4112-B892-6BCDED74D8DC@gmail.com> <23FC8FE6-C41D-4627-99FC-DA51FE5777B8@cisco.com> <97A18603-2934-481E-8859-711B00FB359F@gmail.com> <29592.1420563714@sandelman.ca> <4A5D805B-B73E-49E9-952E-8A4683E20C24@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 06 Jan 2015 18:13:31 -0500
Message-ID: <11092.1420586011@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/BMsQTfOmoGCfiLcXtLw0x4k0eTo
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "6lo-chairs@tools.ietf.org" <6lo-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>, Routing Over Low power and Lossy networks <roll@ietf.org>, "6lo@ietf.org WG" <6lo@ietf.org>, "int-ads@tools.ietf.org" <int-ads@tools.ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2015 23:13:36 -0000

--=-=-=
Content-Type: text/plain


Ralph Droms <rdroms.ietf@gmail.com> wrote:
    >> Ralph Droms <rdroms.ietf@gmail.com> wrote:
    >>> But ... in my opinion, moving the LLN artifacts to the header/dispatch
    >>> in the way defined in draft-thubert-6lo-routing-dispatch raises,
    >>> implicitly, an important architectural issue: is the information in the
    >>> dispatch header compressed IPv6 headers or headers for an independent,
    >>> sub-IP protocol?
    >>
    >> My answer is that a sub-IP protocol can encapsulate arbitrary layer-3 packets.
    >> In particular, one can have overlapping IP addressing contexts,

    > "addressing contexts"?

It's a meaningless and ambiguous term, particularly in IPv6.  Perhaps there
is a better one in some BEHAVE document.
What I mean is that you can run ten different 10.0.0.0/8 RFC1918 networks
simultaneously on the same link using one of the sub-IP protocols...

    >> In the LLN case, the l3-layer is constrained; the additional "tag" (the RPL
    >> Instance ID) is used to select a particular QoS much like the DSCP can do.
    >> Routing between instanceIDs is assumed;

    > ..instanceIDs covering intersecting sets of nodes; i.e., some nodes are
    > part of multiple instances?

Correct, any node could be part of multiple DODAGs which have been optimized
differently.  Whether those nodes will route traffic along a shorter path
than going to (respective) DODAG roots, and then out again is really outside
of our scope, let's just agree that it is a reasonable.
(Consider a powered light bulb router that participates in both the light
control DODAG, and also the TV remote control DODAG)

    >> but potentially not every node has
    >> the specific routes that permits it to do that.

    > Not sure how that relates to a sub-IP protocol for carrying source routes and RPL tags?

I guess it depends upon what you mean by "sub-IP".
I think that we are speaking about it in the former IETF AREA sense; things
which are below IP, which have a layering distinction from IP, and which
can simultaenously carry a multitude of layer-3 protocols.  MPLS for
instance.

Are you considering 6lowpan HC to be a sub-IP protocol?
Is PPP a sub-IP protocol?
Is PPP VJ compression a sub-IP protocol?

    >>> My understanding is that the IETF has made an architectural decision to
    >>> do all the mesh network forwarding and routing in IPv6, so as to reuse
    >>> as much as possible existing technology and associated infrastructure
    >>> such as OAM.  If the dispatch header does not contain compressed IPv6
    >>> headers, per se, then this architectural question would lead me to
    >>> investigate the completeness of the new protocol and the impacts of the
    >>> new protocol on IPv6 and network operations.
    >>
    >> I think that all of the HC methods *can* be implemented as Bump-in-the-Stack
    >> activities;

    > That statement gets to part of my question about
    > draft-thubert-6lo-routing-dispatch: in the abstract, is
    > draft-thubert-6lo-routing-dispatch intended to provide a mechanism
    > through which the original RPI, RH3 and IP-in-IP headers can be
    > reconstructed before sending the resulting IPv6 datagram up to the IPv6
    > stack?  At the risk of being overly concerned with the details, I
    > really mean "reconstruct the header" as opposed to "carry information
    > that can be used to perform the same function".

I think that this is the intent, and I see this as a good thing.

    >> and in particular the loop LLN->ethernet->LLN should be
    >> lossless(%).

    > ...where both LLNs and ethernet are part of the same RPL instance?

Yes, exactly: ethernet bridge of LLN between metal floors or other radio
opaque barriers.

    >> A think that concerns me is that I think that most constrained devices will
    >> not implement HC as a bump in the stack, but will uncompress the headers
    >> directly into internal control structures, and may have loose the ability to
    >> process uncompressed 6553/6554 headers.

    > Yeah.  We already see a side-effect of this form of implementation in
    > the desire for compression techniques that do not result in expansion
    > during transit, because such expansion can require re-fragmentation of
    > a datagram that might otherwise be forwarded in place without
    > explicitly uncompressing to the full IPv6 representation.

    >> One could view this as a vestigal appendix-like thing that evolved away.
    >> This could be regarded as good: less unused/untested code that will get
    >> exploited.  This could be regarded as bad: as frame sizes in LLN radios grow
    >> (802.15.4g, I'm told, has much larger frames) some systems might have no
    >> 6lowpan layer, and interoperation opportunities might become difficult.

    > I think there are also important issues to think about the interaction
    > between a sub-IP protocol and the rest of the IPv6 protocol.  If the
    > abstraction is that the sub-IP bits reconstruct into IPv6 headers, we
    > may have less collateral damage to worry about.  Documents defining
    > that behavior will beed to be careful to show the details and that the
    > conversions are lossless.

I agree completely.
One of the concerns I realized with rpl-flow-label was that it created an
alternative to 6553 which was not equivalent.  It's better actually, even on
Ethernet-like media.  It's also easier to implement in ASICs and current
protocol stacks because filters which match the flow label area available
already.  As such, if we go the rpl-flow-label way, we should probably
obsolete 6553 since we have present way to negotiate or announce what
should be used for a given network.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVKxsG4CLcPvd0N1lAQIk7AgAuY6dxr+5HGmVA1uNASiYVKR74Lj8zpSk
ZUqCAu2GJ3si2hk1ha2bXEc6V003hcq9rdM3dKbmg3vTxNKDUfmHpSBYj2neJDIH
Y/jfMRJNKYLIqbemuLag0ouazAXAftCkfcM2az04IQffbq5KOXHA2hi6J+6Ritn0
vH0lxt63F5CF5m8Kt4paQz2avxJVnVTSfT+4ASL56A6IrsCihLbXApXFsASTKRK6
Clg5UNeybQVQrYqRIDZaIlygaXFeFeQelf4X+7zLalbvSmHyB9HWZznXZLTMIqgZ
zE7cYQuOJf7dqKPnssRPs9OqV3nXF6O/QwGmEv1/S8qqbpn6vgPrUw==
=acVE
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Jan  6 15:20:26 2015
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECF811A01F4; Tue,  6 Jan 2015 15:20:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O0kAurEnHKqI; Tue,  6 Jan 2015 15:20:19 -0800 (PST)
Received: from mail-ie0-x232.google.com (mail-ie0-x232.google.com [IPv6:2607:f8b0:4001:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B6CF1A016B; Tue,  6 Jan 2015 15:20:19 -0800 (PST)
Received: by mail-ie0-f178.google.com with SMTP id vy18so738237iec.9; Tue, 06 Jan 2015 15:20:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=xqEaaGjF/c1yCvBEK86ctCZ1s/VIliMCMIUpOzy4BPc=; b=Gcv9Ds5/LXXILbX0SiIRMTNEuN470aLLiSMEMt1CU5NWe1/5afRejsDQFrLJNVYgUG gFeD4tgu+8lwwc0TepL61lVCI05MZAFcsZyBb9eYIIpUZkb1jLW8eDX0gzruDC5dopOQ 65Boaxapo4EHxttvp1NPaLEuC9dnp841R4xlO2o1HkWH4qeaqj2WXjJbGISQl4EVI5nE EtGNBDY/+CLRfCbdAgLAktyiu8zfxbe16atIJKabiUmyX2/dF3J0Ws/wHIZFfvxpjvHR jAM0QT4yd6B2kBGAltHbbWSy307oPdPQpJMyklE+r5dDC7UocbvesJ1nMijKBKsU85eH 6JRA==
X-Received: by 10.107.46.28 with SMTP id i28mr88501557ioo.73.1420586417690; Tue, 06 Jan 2015 15:20:17 -0800 (PST)
Received: from [192.168.0.101] (dsl-173-206-8-163.tor.primus.ca. [173.206.8.163]) by mx.google.com with ESMTPSA id qr1sm5644925igb.18.2015.01.06.15.20.16 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Jan 2015 15:20:17 -0800 (PST)
Message-ID: <54AC6DA6.1050707@gmail.com>
Date: Tue, 06 Jan 2015 18:20:06 -0500
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Michael Richardson <mcr+ietf@sandelman.ca>,  Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [6tisch] [6lo] [Roll] call for consensus for the RPL RPI / RH3 compression
References: <E045AECD98228444A58C61C200AE1BD848AC2314@xmb-rcd-x01.cisco.com>,  <CE9445B8-BA8E-4112-B892-6BCDED74D8DC@gmail.com> <23FC8FE6-C41D-4627-99FC-DA51FE5777B8@cisco.com> <97A18603-2934-481E-8859-711B00FB359F@gmail.com> <29592.1420563714@sandelman.ca> <4A5D805B-B73E-49E9-952E-8A4683E20C24@gmail.com> <11092.1420586011@sandelman.ca>
In-Reply-To: <11092.1420586011@sandelman.ca>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/1MtolTnRL47z-cLzmk0Q1LuaKoQ
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "6lo-chairs@tools.ietf.org" <6lo-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>, Routing Over Low power and Lossy networks <roll@ietf.org>, "6lo@ietf.org WG" <6lo@ietf.org>, "int-ads@tools.ietf.org" <int-ads@tools.ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Jan 2015 23:20:22 -0000

On 06/01/2015 6:13 PM, Michael Richardson wrote:
>
> Ralph Droms <rdroms.ietf@gmail.com> wrote:
>      >> Ralph Droms <rdroms.ietf@gmail.com> wrote:
>      >>> But ... in my opinion, moving the LLN artifacts to the header/dispatch
>      >>> in the way defined in draft-thubert-6lo-routing-dispatch raises,
>      >>> implicitly, an important architectural issue: is the information in the
>      >>> dispatch header compressed IPv6 headers or headers for an independent,
>      >>> sub-IP protocol?
>      >>
>      >> My answer is that a sub-IP protocol can encapsulate arbitrary layer-3 packets.
>      >> In particular, one can have overlapping IP addressing contexts,
>
>      > "addressing contexts"?
>
> It's a meaningless and ambiguous term, particularly in IPv6.  Perhaps there
> is a better one in some BEHAVE document.
> What I mean is that you can run ten different 10.0.0.0/8 RFC1918 networks
> simultaneously on the same link using one of the sub-IP protocols...

[PTT] The Behave term is "address domain". Initial definition in RFC 
2663, repeated in subsequent documents.
....


From nobody Tue Jan  6 16:19:06 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCE2C1A8790 for <ipv6@ietfa.amsl.com>; Tue,  6 Jan 2015 16:19:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CN2NRq_s4Tdi for <ipv6@ietfa.amsl.com>; Tue,  6 Jan 2015 16:18:59 -0800 (PST)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E98A71A87A8 for <ipv6@ietf.org>; Tue,  6 Jan 2015 16:18:58 -0800 (PST)
Received: by mail-pa0-f42.google.com with SMTP id et14so1074112pad.1 for <ipv6@ietf.org>; Tue, 06 Jan 2015 16:18:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=FOY7kl+CodqQYh/ZBg1graxcRJk3uwhz4thZLQmuuWY=; b=jdWcPhuWTQGdmdPvjuyftxXQalakDQE5lNRl1KjBssflWaT80Cr381wmvi556L9K0v jnuNjU7bkj3x4xXCflAyd+wsr8A1kjQ9qFx9rK6X1lxs6mXox6aQ3LijqM6RJbViOwMy 4v2ytt0AJJIN2pnNf90A/zI5E5UoMfPf+m3kmJsyN+cGFfVh3qYVj9AHerBWm29eAubl J9Olq+9RpYTAMnEzYAC/OU1UxUq9Nn+bHlOQ4iXQrSia6Rcyj42l6diwj0MZ5YUmgPqb o0jvFHwgv8YZmnJlfVZ6SgaGNPEsSBlqKMPt9Fs1JHqgRVKd+zTLqXHh6ox+Sq5cfJbD 6Zsg==
X-Received: by 10.68.182.1 with SMTP id ea1mr121803pbc.11.1420589938155; Tue, 06 Jan 2015 16:18:58 -0800 (PST)
Received: from ?IPv6:2001:df0:0:2006:c0da:ac17:5f6d:8e76? ([2001:df0:0:2006:c0da:ac17:5f6d:8e76]) by mx.google.com with ESMTPSA id fs1sm47216pdb.16.2015.01.06.16.18.55 for <ipv6@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Jan 2015 16:18:57 -0800 (PST)
Message-ID: <54AC7B84.8000902@gmail.com>
Date: Wed, 07 Jan 2015 13:19:16 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: 6man <ipv6@ietf.org>
Subject: Re: I-D Action: draft-sarikaya-6man-sadr-overview-03.txt
References: <20141208171247.21096.35754.idtracker@ietfa.amsl.com>
In-Reply-To: <20141208171247.21096.35754.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/uHEMhQo7uTGHd6XOSDK4ksclT-w
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jan 2015 00:19:03 -0000

Hi,

One general comment is that I think the title of the draft
is a little misleading, because it doesn't emphasise the
host aspect. This is clumsy but might be clearer:

"Source Address Dependent Routing and Source Address Selection for IPv6 Hosts"

I think the discussion in Section 5 "What Needs to be Done"
is getting closer to what we need to say, but is not quite
there yet. I think it would be better formulated in two
parts:

#1. Scenarios solved by Rule 5.5 in [RFC6724], and what needs
to be done for that to work (mainly, as I understand it, that
hosts SHOULD register which next-hop router announced each
prefix).

#2. Scenarios *not* solved by that, and exactly what information
hosts need for correct SA selection in that case.

Also, I think it's probably not made clear enough that SADR
SHOULD be supported by routers throughout a site that has
multiple exits. I guess Fred's draft implies that, but doesn't
say it in so many words.

(I don't want to comment on details of draft-sarikaya-6man-next-hop-ra
or draft-sarikaya-dhc-dhcpv6-raoptions-sadr until point #2 above
is settled.)

Regards
   Brian

On 09/12/2014 06:12, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>         Title           : Overview of Source Address Dependent Routing
>         Author          : Behcet Sarikaya
> 	Filename        : draft-sarikaya-6man-sadr-overview-03.txt
> 	Pages           : 14
> 	Date            : 2014-12-08
> 
> Abstract:
>    This document presents an overview of source address dependent
>    routing from the host perspective.  Multihomed hosts and hosts with
>    multiple interfaces are considered.  Different architectures are
>    introduced and with their help, why source address selection and next
>    hop resolution in view of source address dependent routing is needed
>    is explained.  The document concludes with a discussion on the
>    standardization work that is needed.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-sarikaya-6man-sadr-overview/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-sarikaya-6man-sadr-overview-03
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-sarikaya-6man-sadr-overview-03
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 


From nobody Wed Jan  7 04:30:55 2015
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6F381A89FD for <ipv6@ietfa.amsl.com>; Wed,  7 Jan 2015 04:30:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x2qyz_ckTrxr for <ipv6@ietfa.amsl.com>; Wed,  7 Jan 2015 04:30:51 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B66A31A89FB for <6man@ietf.org>; Wed,  7 Jan 2015 04:30:51 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 970EBA3; Wed,  7 Jan 2015 13:30:49 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1420633849; bh=GCpUAlPa7r3WYnoXAO8ZbIlF+eek+rAIWLaC0smRq2Q=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=RoCb45BsfRrD/L9upEBuxtbqtB7PZKNaoUU7PfLTfAj+CfHy6gQU30voivXf9Ujz+ 6+R410qc7eGnzbtKywuOIf+k5slGhApxVbBL0vMdTq1R0yG36+ze6ssYsLbtAjNq4V yy70Kx539SQZ9Ax4rgGU8rb7PYsdg2yF3MUC6WzU=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 90DEEA2; Wed,  7 Jan 2015 13:30:49 +0100 (CET)
Date: Wed, 7 Jan 2015 13:30:49 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: Transmission and Processing of IPv6 Options (draft-gont-6man-ipv6-opt-transmit-00.txt)
In-Reply-To: <54945AFE.20106@gont.com.ar>
Message-ID: <alpine.DEB.2.02.1501071324110.22729@uplift.swm.pp.se>
References: <54945AFE.20106@gont.com.ar>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/cmZlEPkVeoEM8mx8Uv5lcUNbRbs
Cc: "6man@ietf.org" <6man@ietf.org>, draft-gont-6man-ipv6-opt-transmit@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jan 2015 12:30:54 -0000

On Fri, 19 Dec 2014, Fernando Gont wrote:

> We're planning to publish a rev soon... So we'd like to hear your 
> comments such that they can be addressed in the next rev....

I like this document and I think it fills a gap.

Comments:

2.2.

When it says "Drop (and log)", I propose that instead it should say "Drop 
(and potentially log)". "Potentially" can be replaced with an equivalent 
word. I just want to make it super clear that logging of the event isn't 
mandatory.

I would also suggest new wording to the following sentence:

"Devices should count the number of packets dropped/
    rejected, but the logging of drop/reject events should be limited so
    as to not overburden device resources."

Is replaced at the end with:

"... should be limit so packet the packet handling isn't affected by 
computing resources used to handle log entries." (or something to this 
effect). I believe this is the intention of "overburden device resources", 
but I would like to see something in there about what should be 
prioritized, ie the handling of packets.

Otoh, I am sure there are devices where they'd rather log the packet 
because this is an absolute requirement from somewhere, and they don't 
care about the consequences for other functions of the box, ie they'd 
rather log the traffic that needs logging and let this negatively affect 
the rest of the box, than to potentially miss log entries.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Wed Jan  7 04:54:29 2015
Return-Path: <pthubert@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2F621A8A48; Wed,  7 Jan 2015 04:54:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XxsygcY6rIVU; Wed,  7 Jan 2015 04:54:24 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B88A1A8A45; Wed,  7 Jan 2015 04:54:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7495; q=dns/txt; s=iport; t=1420635263; x=1421844863; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=BjiYphW+Am0WHEWSh+Aa7BDJRvFRojCP9tmr217KH2M=; b=eDxA+8aXI1WY+J1z+DFGX3T1qRzyTHpjn8yWTZeQQrswrFtq0QRj1iTX y/yF7WWBWfUJlqrY9LkRLcYSJq5qr9wgofMykwBO96UOqKSoN04PTNj1S yD/87U/gFRsw79tyTVuTWOHt6l0EhK3GSS5PWgR+0XL9D8EkoKsXR3OFj Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AncFAE0rrVStJV2d/2dsb2JhbABcgwZSWATEDIIhhGmBDgKBDkMBAQEBAX2EDAEBAQQdChM/DAQCAQgRBAEBAQoUCQchERQJCAIEAQ0FCIgQAxG+dA2DWgEBAQEBAQEBAQEBAQEBAQEBAQEBAReNToFcHTEHBoMQgRMBBI4uhzyNS4VdIoNub4FFfgEBAQ
X-IronPort-AV: E=Sophos;i="5.07,714,1413244800"; d="scan'208";a="111046709"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-4.cisco.com with ESMTP; 07 Jan 2015 12:54:21 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id t07CsLDo027005 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 7 Jan 2015 12:54:21 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.179]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0195.001; Wed, 7 Jan 2015 06:54:21 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: RE: [6tisch] [6lo] [Roll] call for consensus for the RPL RPI / RH3 compression
Thread-Topic: [6tisch] [6lo] [Roll] call for consensus for the RPL RPI / RH3 compression
Thread-Index: AQHQKTccIER4yneI6UuQFsYm6imsn5y0nQ2w
Date: Wed, 7 Jan 2015 12:54:20 +0000
Deferred-Delivery: Wed, 7 Jan 2015 12:54:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD848B102F2@xmb-rcd-x01.cisco.com>
References: <E045AECD98228444A58C61C200AE1BD848AC2314@xmb-rcd-x01.cisco.com>,  <CE9445B8-BA8E-4112-B892-6BCDED74D8DC@gmail.com> <23FC8FE6-C41D-4627-99FC-DA51FE5777B8@cisco.com> <97A18603-2934-481E-8859-711B00FB359F@gmail.com> <29592.1420563714@sandelman.ca> <4A5D805B-B73E-49E9-952E-8A4683E20C24@gmail.com> <11092.1420586011@sandelman.ca>
In-Reply-To: <11092.1420586011@sandelman.ca>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.49.80.33]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/SLCsPYZTdiI79yPK5RwCUwQpz9s
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "6lo-chairs@tools.ietf.org" <6lo-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>, Routing Over Low power and Lossy networks <roll@ietf.org>, "6lo@ietf.org WG" <6lo@ietf.org>, "int-ads@tools.ietf.org" <int-ads@tools.ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jan 2015 12:54:26 -0000

Hi:

6LoWPAN HC and the new draft proposals (NHC, dispatch, all apart from the f=
low label) are encoding procedures that can be reversed so as to restore th=
e original packet.
The term sub IP, should it refer to an encapsulation like a vlan, would be =
inappropriate. If it refers to an adaptation layer below IP, it would apply=
.=20
But if the meaning is unclear, then we need to clarify before using it.=20

Cheers,

Pascal


> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Michael Richardson
> Sent: mercredi 7 janvier 2015 00:14
> To: Ralph Droms
> Cc: 6man-chairs@tools.ietf.org; 6lo-chairs@tools.ietf.org; 6man WG; Routi=
ng
> Over Low power and Lossy networks; 6lo@ietf.org WG; int-ads@tools.ietf.or=
g;
> 6tisch@ietf.org
> Subject: Re: [6tisch] [6lo] [Roll] call for consensus for the RPL RPI / R=
H3
> compression
>=20
>=20
> Ralph Droms <rdroms.ietf@gmail.com> wrote:
>     >> Ralph Droms <rdroms.ietf@gmail.com> wrote:
>     >>> But ... in my opinion, moving the LLN artifacts to the header/dis=
patch
>     >>> in the way defined in draft-thubert-6lo-routing-dispatch raises,
>     >>> implicitly, an important architectural issue: is the information =
in the
>     >>> dispatch header compressed IPv6 headers or headers for an indepen=
dent,
>     >>> sub-IP protocol?
>     >>
>     >> My answer is that a sub-IP protocol can encapsulate arbitrary laye=
r-3
> packets.
>     >> In particular, one can have overlapping IP addressing contexts,
>=20
>     > "addressing contexts"?
>=20
> It's a meaningless and ambiguous term, particularly in IPv6.  Perhaps the=
re is a
> better one in some BEHAVE document.
> What I mean is that you can run ten different 10.0.0.0/8 RFC1918 networks
> simultaneously on the same link using one of the sub-IP protocols...
>=20
>     >> In the LLN case, the l3-layer is constrained; the additional "tag"=
 (the RPL
>     >> Instance ID) is used to select a particular QoS much like the DSCP=
 can do.
>     >> Routing between instanceIDs is assumed;
>=20
>     > ..instanceIDs covering intersecting sets of nodes; i.e., some nodes=
 are
>     > part of multiple instances?
>=20
> Correct, any node could be part of multiple DODAGs which have been optimi=
zed
> differently.  Whether those nodes will route traffic along a shorter path=
 than
> going to (respective) DODAG roots, and then out again is really outside o=
f our
> scope, let's just agree that it is a reasonable.
> (Consider a powered light bulb router that participates in both the light=
 control
> DODAG, and also the TV remote control DODAG)
>=20
>     >> but potentially not every node has
>     >> the specific routes that permits it to do that.
>=20
>     > Not sure how that relates to a sub-IP protocol for carrying source =
routes
> and RPL tags?
>=20
> I guess it depends upon what you mean by "sub-IP".
> I think that we are speaking about it in the former IETF AREA sense; thin=
gs which
> are below IP, which have a layering distinction from IP, and which can
> simultaenously carry a multitude of layer-3 protocols.  MPLS for instance=
.
>=20
> Are you considering 6lowpan HC to be a sub-IP protocol?
> Is PPP a sub-IP protocol?
> Is PPP VJ compression a sub-IP protocol?
>=20
>     >>> My understanding is that the IETF has made an architectural decis=
ion to
>     >>> do all the mesh network forwarding and routing in IPv6, so as to =
reuse
>     >>> as much as possible existing technology and associated infrastruc=
ture
>     >>> such as OAM.  If the dispatch header does not contain compressed =
IPv6
>     >>> headers, per se, then this architectural question would lead me t=
o
>     >>> investigate the completeness of the new protocol and the impacts =
of the
>     >>> new protocol on IPv6 and network operations.
>     >>
>     >> I think that all of the HC methods *can* be implemented as Bump-in=
-the-
> Stack
>     >> activities;
>=20
>     > That statement gets to part of my question about
>     > draft-thubert-6lo-routing-dispatch: in the abstract, is
>     > draft-thubert-6lo-routing-dispatch intended to provide a mechanism
>     > through which the original RPI, RH3 and IP-in-IP headers can be
>     > reconstructed before sending the resulting IPv6 datagram up to the =
IPv6
>     > stack?  At the risk of being overly concerned with the details, I
>     > really mean "reconstruct the header" as opposed to "carry informati=
on
>     > that can be used to perform the same function".
>=20
> I think that this is the intent, and I see this as a good thing.
>=20
>     >> and in particular the loop LLN->ethernet->LLN should be
>     >> lossless(%).
>=20
>     > ...where both LLNs and ethernet are part of the same RPL instance?
>=20
> Yes, exactly: ethernet bridge of LLN between metal floors or other radio =
opaque
> barriers.
>=20
>     >> A think that concerns me is that I think that most constrained dev=
ices will
>     >> not implement HC as a bump in the stack, but will uncompress the h=
eaders
>     >> directly into internal control structures, and may have loose the =
ability to
>     >> process uncompressed 6553/6554 headers.
>=20
>     > Yeah.  We already see a side-effect of this form of implementation =
in
>     > the desire for compression techniques that do not result in expansi=
on
>     > during transit, because such expansion can require re-fragmentation=
 of
>     > a datagram that might otherwise be forwarded in place without
>     > explicitly uncompressing to the full IPv6 representation.
>=20
>     >> One could view this as a vestigal appendix-like thing that evolved=
 away.
>     >> This could be regarded as good: less unused/untested code that wil=
l get
>     >> exploited.  This could be regarded as bad: as frame sizes in LLN r=
adios grow
>     >> (802.15.4g, I'm told, has much larger frames) some systems might h=
ave no
>     >> 6lowpan layer, and interoperation opportunities might become diffi=
cult.
>=20
>     > I think there are also important issues to think about the interact=
ion
>     > between a sub-IP protocol and the rest of the IPv6 protocol.  If th=
e
>     > abstraction is that the sub-IP bits reconstruct into IPv6 headers, =
we
>     > may have less collateral damage to worry about.  Documents defining
>     > that behavior will beed to be careful to show the details and that =
the
>     > conversions are lossless.
>=20
> I agree completely.
> One of the concerns I realized with rpl-flow-label was that it created an
> alternative to 6553 which was not equivalent.  It's better actually, even=
 on
> Ethernet-like media.  It's also easier to implement in ASICs and current =
protocol
> stacks because filters which match the flow label area available already.=
  As
> such, if we go the rpl-flow-label way, we should probably obsolete 6553 s=
ince
> we have present way to negotiate or announce what should be used for a gi=
ven
> network.
>=20
> --
> ]               Never tell me the odds!                 | ipv6 mesh netwo=
rks [
> ]   Michael Richardson, Sandelman Software Works        | network archite=
ct  [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails=
    [
>=20
>=20
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works  -=
=3D
> IPv6 IoT consulting =3D-
>=20
>=20


From nobody Wed Jan  7 06:59:22 2015
Return-Path: <mcr@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CE341A90D7; Wed,  7 Jan 2015 06:59:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iCXAIthAPyqv; Wed,  7 Jan 2015 06:59:03 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A25711A6F2B; Wed,  7 Jan 2015 06:59:02 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id E62C920098; Wed,  7 Jan 2015 10:04:23 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 2B6DB637FE; Wed,  7 Jan 2015 09:59:01 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 14E9963745; Wed,  7 Jan 2015 09:59:01 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "6man-chairs\@tools.ietf.org" <6man-chairs@tools.ietf.org>, "6lo-chairs\@tools.ietf.org" <6lo-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>, Routing Over Low power and Lossy networks <roll@ietf.org>, "6lo\@ietf.org WG" <6lo@ietf.org>, "int-ads\@tools.ietf.org" <int-ads@tools.ietf.org>, "6tisch\@ietf.org" <6tisch@ietf.org>
Subject: Re: [6tisch] [6lo] [Roll] call for consensus for the RPL RPI / RH3 compression
In-Reply-To: <E045AECD98228444A58C61C200AE1BD848B102F2@xmb-rcd-x01.cisco.com>
References: <E045AECD98228444A58C61C200AE1BD848AC2314@xmb-rcd-x01.cisco.com>,  <CE9445B8-BA8E-4112-B892-6BCDED74D8DC@gmail.com> <23FC8FE6-C41D-4627-99FC-DA51FE5777B8@cisco.com> <97A18603-2934-481E-8859-711B00FB359F@gmail.com> <29592.1420563714@sandelman.ca> <4A5D805B-B73E-49E9-952E-8A4683E20C24@gmail.com> <11092.1420586011@sandelman.ca> <E045AECD98228444A58C61C200AE1BD848B102F2@xmb-rcd-x01.cisco.com>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 07 Jan 2015 09:59:01 -0500
Message-ID: <14523.1420642741@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/RQChDoOcqiTEwtifr51P6gX7KGQ
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jan 2015 14:59:06 -0000

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


Thank you Tom for point at RFC2663 for "address domain".=20

Pascal Thubert (pthubert) <pthubert@cisco.com> wrote:
    > 6LoWPAN HC and the new draft proposals (NHC, dispatch, all apart from
    > the flow label) are encoding procedures that can be reversed so as to
    > restore the original packet.=20
    > The term sub IP, should it refer to an encapsulation like a vlan, wou=
ld
    > be inappropriate. If it refers to an adaptation layer below IP, it
    > would apply.=20=20

So, again, I think a key reason why the various HC are not a sub-IP protocol
is because rfc6553 does not create new addressing domains with the RPL
InstanceID.

Can we agree that this is not a sub-IP signalization problem.

=2D-=20
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -=3D IPv6 IoT consulting =3D-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVK1JsYCLcPvd0N1lAQJlkwf+JgaYP6XWpONle9riPxXc/cP29p7PV/GK
tSRKNBbGiJxZr1NlhHgIRdoNzIulJ13d2acGU/p8qievraWEhkTBadLURgPznk8A
uMY/wVpFxrrI6f37jN2ITFMiBky2nxwXXcweF3cO8y+Qyb1BCpY7SGwn8k4qejtG
JEJaZLPGDFuDkHiurSqTmFvKPs54w5QOy4WqljNfvE3kW89ykKMjAMe4klz+/3TT
SPKpKauP46BRponm6Aq1u0ifRN207w/4N7bBzRlRtpfhwdZandfogXRdt3tb1fD+
WV8MZEsJe+6dJvRJOBiZXRIa7y/ailRPXVDofZbp9ZPojYHvmn0vaA==
=wilf
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Jan  7 07:15:28 2015
Return-Path: <pthubert@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BDDF1A911A; Wed,  7 Jan 2015 07:15:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x4bZMS6PFpHR; Wed,  7 Jan 2015 07:15:22 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BFA741A9118; Wed,  7 Jan 2015 07:15:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1431; q=dns/txt; s=iport; t=1420643722; x=1421853322; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=1SRL2UQkdU6H1jdDwUF7xT8+ZGuEU8JCxbT1yMN4uQE=; b=I+a0jQRter+UXwvcok8s/G0xGeRgc7jG2QWrQSaHGPlgKFl1/78ei781 lRfDo4JYVVE/21lcCrsgC+5sAv3FBKpZgOv2krcqvJ7NHgNZUNcF/qDFa ursyT86QatfM1yWXnAsReligHGOZCJ/Pg3KH1T4tNk4/gtYxRKA0Rz9tJ M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnQFAEZNrVStJA2N/2dsb2JhbABcgwaBKgTEDYcKgQ4CgQ9DAQEBAQF9hAwBAQEEHR1LBAIBCBEEAQEBChQJBzIUCQgCBAESCIgkwzwBAQEBAQEBAQEBAQEBAQEBAQEBAQEXjyodOAaDEIETAQSOLppkIoNub4FFfgEBAQ
X-IronPort-AV: E=Sophos;i="5.07,715,1413244800"; d="scan'208";a="111087628"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-5.cisco.com with ESMTP; 07 Jan 2015 15:15:21 +0000
Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t07FFKlK014042 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 7 Jan 2015 15:15:21 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.179]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.03.0195.001; Wed, 7 Jan 2015 09:15:20 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "6lo-chairs@tools.ietf.org" <6lo-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>, "Routing Over Low power and Lossy networks" <roll@ietf.org>, "6lo@ietf.org WG" <6lo@ietf.org>, "int-ads@tools.ietf.org" <int-ads@tools.ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>
Subject: RE: [6tisch] [6lo] [Roll] call for consensus for the RPL RPI / RH3 compression
Thread-Topic: [6tisch] [6lo] [Roll] call for consensus for the RPL RPI / RH3 compression
Thread-Index: AQHQKTccIER4yneI6UuQFsYm6imsn5yyn8j8gAIiyjiAAAQPQA==
Date: Wed, 7 Jan 2015 15:15:20 +0000
Deferred-Delivery: Wed, 7 Jan 2015 15:15:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD848B109AC@xmb-rcd-x01.cisco.com>
References: <E045AECD98228444A58C61C200AE1BD848AC2314@xmb-rcd-x01.cisco.com>,  <CE9445B8-BA8E-4112-B892-6BCDED74D8DC@gmail.com> <23FC8FE6-C41D-4627-99FC-DA51FE5777B8@cisco.com> <97A18603-2934-481E-8859-711B00FB359F@gmail.com> <29592.1420563714@sandelman.ca> <4A5D805B-B73E-49E9-952E-8A4683E20C24@gmail.com> <11092.1420586011@sandelman.ca> <E045AECD98228444A58C61C200AE1BD848B102F2@xmb-rcd-x01.cisco.com> <14523.1420642741@sandelman.ca>
In-Reply-To: <14523.1420642741@sandelman.ca>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.49.80.33]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/5f1k4mHGFsbYWpGMREeW0Y2J528
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jan 2015 15:15:23 -0000

Yes, Michael.

I think it would help to take that out of the equation.

Cheers,

Pascal

> -----Original Message-----
> From: 6tisch [mailto:6tisch-bounces@ietf.org] On Behalf Of Michael Richar=
dson
> Sent: mercredi 7 janvier 2015 15:59
> To: 6man-chairs@tools.ietf.org; 6lo-chairs@tools.ietf.org; 6man WG; Routi=
ng
> Over Low power and Lossy networks; 6lo@ietf.org WG; int-ads@tools.ietf.or=
g;
> 6tisch@ietf.org
> Subject: Re: [6tisch] [6lo] [Roll] call for consensus for the RPL RPI / R=
H3
> compression
>=20
>=20
> Thank you Tom for point at RFC2663 for "address domain".
>=20
> Pascal Thubert (pthubert) <pthubert@cisco.com> wrote:
>     > 6LoWPAN HC and the new draft proposals (NHC, dispatch, all apart fr=
om
>     > the flow label) are encoding procedures that can be reversed so as =
to
>     > restore the original packet.
>     > The term sub IP, should it refer to an encapsulation like a vlan, w=
ould
>     > be inappropriate. If it refers to an adaptation layer below IP, it
>     > would apply.
>=20
> So, again, I think a key reason why the various HC are not a sub-IP proto=
col is
> because rfc6553 does not create new addressing domains with the RPL
> InstanceID.
>=20
> Can we agree that this is not a sub-IP signalization problem.
>=20
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works  -=
=3D
> IPv6 IoT consulting =3D-
>=20
>=20


From nobody Wed Jan  7 07:57:49 2015
Return-Path: <mcr@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FD661A7000 for <ipv6@ietfa.amsl.com>; Wed,  7 Jan 2015 07:57:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, WEIRD_PORT=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OVGcTIWhg1el for <ipv6@ietfa.amsl.com>; Wed,  7 Jan 2015 07:57:36 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AB5C1A90AE for <ipv6@ietf.org>; Wed,  7 Jan 2015 07:57:26 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id B2BEA20098; Wed,  7 Jan 2015 11:02:47 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 8AE3A637FE; Wed,  7 Jan 2015 10:57:24 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 75453637EA; Wed,  7 Jan 2015 10:57:24 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
to: "6man-chairs\@tools.ietf.org" <6man-chairs@tools.ietf.org>, "6lo-chairs\@tools.ietf.org" <6lo-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>, "int-ads\@tools.ietf.org" <int-ads@tools.ietf.org>
Subject: "11am" meeting, re: RPL RPI / RH3 compression
In-Reply-To: <14523.1420642741@sandelman.ca>
References: <E045AECD98228444A58C61C200AE1BD848AC2314@xmb-rcd-x01.cisco.com>,  <CE9445B8-BA8E-4112-B892-6BCDED74D8DC@gmail.com> <23FC8FE6-C41D-4627-99FC-DA51FE5777B8@cisco.com> <97A18603-2934-481E-8859-711B00FB359F@gmail.com> <29592.1420563714@sandelman.ca> <4A5D805B-B73E-49E9-952E-8A4683E20C24@gmail.com> <11092.1420586011@sandelman.ca> <E045AECD98228444A58C61C200AE1BD848B102F2@xmb-rcd-x01.cisco.com> <14523.1420642741@sandelman.ca>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 07 Jan 2015 10:57:24 -0500
Message-ID: <26104.1420646244@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/wWrgbtxr-E7fZdwEjibs6tEiLGI
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jan 2015 15:57:45 -0000

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


Ines did this etherpad with details:
     http://etherpad.tools.ietf.org:9000/p/lg05TzPmsl

=2D-=20
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -=3D IPv6 IoT consulting =3D-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVK1XYYCLcPvd0N1lAQL7jwf9HKjC6z2olMP2QeCIRioWHC147aT4YE5M
7pa99ZU4xLoNY+GJvzp3dnEl6lImELfVu//P5W5/x5+5EUSPRfEaQF5InkyUUcRo
WYXYmdV86IVLpHJFjEmrmiBBw8E6XJqSFhVMnYSicBrCJExYMblzcFsm+OOTTncu
nB1ev/mirp0CgCw0+0HBlW4Ikd9AaGfFpYrKoWW0Rc1AxI7IflA3vwqjNhi6bHNX
ZrABzOIbGIbOyqDfmxKtFQ7WRnCO3kOf2Br0Q289xde6CyVp05nef90/7mRr4RbN
Lx3jwptYjRUnvGfDO0yGCXfNU1zMeoW6QBpr+7B/NUfqiG5P+1FX/Q==
=tjP9
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Jan  7 11:08:08 2015
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ABBF1A012D; Wed,  7 Jan 2015 11:08:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J-WkZ5rmT6gG; Wed,  7 Jan 2015 11:08:03 -0800 (PST)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EE711A0004; Wed,  7 Jan 2015 11:08:03 -0800 (PST)
Received: by mail-we0-f170.google.com with SMTP id w61so1740745wes.15; Wed, 07 Jan 2015 11:08:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=YZQWXAf5lM2vFuhQUGUnJMj/sY7ll4MkgmpW07ZqnPc=; b=RC6jQBgSZcYZDWHyFF7Ga7shqPukuxjwhHyEDUTEcWYRvep5Y2YTDtaLWU6oL2KjTJ 1PDXLgKZNQh8tKlcPC0CzYNMIQO0+DC2NkEWnaHWpimU3/XJvDbmeWZL2x9dUPmV1v6/ NO3JdyL1OLeMQGmyZHSpEoRtbbOpOInanQ7NEw3BtiBiaIed+JJyzAA/stiPMGzxgHwl cKshsfvBX4emPOYJ93uPHH980TA+yRx0pGWDwv3QfPk06pY3IMHA0MFnz42d7DvPZVoa Q/nk8VVbjMxiXy2NIGJ+1kRiFNYPsPJ9bChofHYaQ4wd8ACdORqeOrPUDP0BLFicG6EM lcBQ==
MIME-Version: 1.0
X-Received: by 10.194.179.166 with SMTP id dh6mr9382511wjc.87.1420657681911; Wed, 07 Jan 2015 11:08:01 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.194.44.66 with HTTP; Wed, 7 Jan 2015 11:08:01 -0800 (PST)
In-Reply-To: <232077E7-7135-41E8-B0DB-C786F8C410CA@employees.org>
References: <232077E7-7135-41E8-B0DB-C786F8C410CA@employees.org>
Date: Wed, 7 Jan 2015 11:08:01 -0800
X-Google-Sender-Auth: m7WbIroIEAbR3ppFMsvsP18uZQ0
Message-ID: <CAJE_bqdQwTQ3X5=tKMAbm1FSmXO3MawbXNAHckgtkhS_f5pcsQ@mail.gmail.com>
Subject: Re: 6MAN cross-wg review: draft-ietf-l2tpext-keyed-ipv6-tunnel-01
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/ALFV8PWUXp69xidNIxdlXSEDamA
Cc: 6man WG <ipv6@ietf.org>, l2tpext@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jan 2015 19:08:05 -0000

At Tue, 6 Jan 2015 12:14:14 +0100,
Ole Troan <otroan@employees.org> wrote:

> The chairs of l2tpext have asked for a 6man review of:
>
> Title: Keyed IPv6 Tunnel
> https://tools.ietf.org/html/draft-ietf-l2tpext-keyed-ipv6-tunnel-01
>
> Can we get a couple of volunteers please? As well as any other comments to the lists are welcome of course.
> Please keep l2tpext@ietf.org in CC.

>From a quick read of the draft, my only comment is this:

- In Section 4:

   o  Hop Limit.  Set to 0xFF, and decremented by one by each router in
      the path to the egress router.

What's the rationale of 0xFF (the possible maximum hop limit)?  It's
way too large compared to other general cases, and it's not
immediately clear how the L2TP usage is different.

As for volunteering to do a 6man review: if there's no other (or
enough) volunteer who is more familiar with the underlying topic, I'm
willing to spend my time for it.  But I'm afraid I'll not be able to
provide very useful feedback due to lack of my understanding of the
background technology (as it's suggested by the fact that my only
comment so far is the above one).  I'm stating this anyway as I've not
seen any public response to the request yet, but if there are already
volunteers who replied offlist, please just ignore this paragraph.

--
JINMEI, Tatuya


From nobody Wed Jan  7 13:17:12 2015
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62DF21A1C03 for <ipv6@ietfa.amsl.com>; Wed,  7 Jan 2015 13:17:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J_6MGcZDRqu0 for <ipv6@ietfa.amsl.com>; Wed,  7 Jan 2015 13:17:07 -0800 (PST)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001:c05::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B52211A1BF4 for <ipv6@ietf.org>; Wed,  7 Jan 2015 13:17:07 -0800 (PST)
Received: by mail-ig0-f171.google.com with SMTP id z20so6530805igj.16 for <ipv6@ietf.org>; Wed, 07 Jan 2015 13:17:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=DrU+a6UZnFBKlnDYk/kZNSFW9Z1hF+hVmEry/a3OjTM=; b=iDFtYiA8A2amBttdoqIREIDLefbqJP8Ak1id/kjja/zzOmaeNPR4FFyI6kNgHmKhpK 7BYNoQmqt6P8uNcNYPSjBJ+vHq65u0to3eKDRJTcE1HgGXPxGpfmu0r2elCTpLB1SP9t LS2WoorOmmq1jW654Jt8BEyPh0aoQzlsznolpBPtS9kjDwFxAki5BfCeag88TWqD4gPf 43USEDi+lb+nkNdC1o9dwIOV5e3UZxbh4tEI8ypOVEKXr6BAuLRMUzCLPfDWOki6PTkR hO8OL6lQTRtp4HvQMvrtr/ngoVQSFCqOUSiBWvqnSG+DTpTSrpYSlxsZx1P0giScCIht GV5Q==
X-Received: by 10.50.107.36 with SMTP id gz4mr6091528igb.25.1420665426814; Wed, 07 Jan 2015 13:17:06 -0800 (PST)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPSA id h36sm1291334iod.17.2015.01.07.13.17.05 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 07 Jan 2015 13:17:06 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
Subject: Conclusion of 6MAN WG Adoption Call: draft-gont-6man-nd-opt-validation-01
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <CAJE_bqc=LX6YAn58SNWiHK3dAnrdRZ2-7bmEmvPs+PV8fqN4Aw@mail.gmail.com>
Date: Wed, 7 Jan 2015 13:16:57 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <E02F6DBF-A295-46BD-B67E-7434A3F0C36A@gmail.com>
References: <2812B09B-1A2B-4D28-8317-FCB05ACB030C@employees.org> <CAJE_bqc=LX6YAn58SNWiHK3dAnrdRZ2-7bmEmvPs+PV8fqN4Aw@mail.gmail.com>
To: IPv6 List <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/cCY9IxBMiLeKAK7Y8F11Xix4Djo
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jan 2015 21:17:10 -0000

All,

Based on the feedback received, the 6man chairs believe there is =
consensus to adopt draft-gont-6man-nd-opt-validation-01 as a 6MAN =
working group document.

The authors should submit the next revision as an 6MAN document. =20

Regards,
Bob Hinden and Ole Troan


> This message starts a two week 6MAN Working Group Last Call on =
adopting:
>=20
>      Title           : Validation of IPv6 Neighbor Discovery Options
>      Authors         : F. Gont, R. Bonica, W. Liu
>      Filename        : draft-gont-6man-nd-opt-validation-01
>      Pages           : 15
>      Date            : 2014-10-21
>=20
>      https://tools.ietf.org/html/draft-gont-6man-nd-opt-validation-01
>=20
> as a working group item.



From nobody Thu Jan  8 12:16:32 2015
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E33651A9143 for <ipv6@ietfa.amsl.com>; Thu,  8 Jan 2015 12:16:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MUyAbbQsGiEZ for <ipv6@ietfa.amsl.com>; Thu,  8 Jan 2015 12:16:29 -0800 (PST)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBAD21ACC86 for <ipv6@ietf.org>; Thu,  8 Jan 2015 12:16:28 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id z12so4850558lbi.3 for <ipv6@ietf.org>; Thu, 08 Jan 2015 12:16:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=QMUYTIieU2DWY+7X+hhghxZDsVInP2XZwYeIRtwKE9o=; b=sc3pzxUYxCkpzGZIL3H29aWGdUs8oyvX5cBEDbV8xkURVGto1joAkbwWH9TrALec1K AvMleRSTFc56ZO5NCpF8u8oSVDnRmt2A02PGunaZ3nwKcrA3j+757xRzcG37Icp6E00P OlP/nQ0xcVaZc6IUNBGlKCKb3C/D7yAUtnY+LuXrbW8/HkSStvS87dnUyAQTg90PfkSU l+H6TCRffyqq/ug/siBgNd9a4+ZnnEtVTwOYkVzbGi3wFjavf0lEHn+EfIYPdomKtX3D KhN591c+PFC++VnoNmVeE198RB9O0k7f4sn9oOqmh5Dv7xV7D/zjGdF8uuReF4dJT6kM 7jwA==
MIME-Version: 1.0
X-Received: by 10.112.156.169 with SMTP id wf9mr17178353lbb.85.1420748187125;  Thu, 08 Jan 2015 12:16:27 -0800 (PST)
Received: by 10.114.63.51 with HTTP; Thu, 8 Jan 2015 12:16:27 -0800 (PST)
In-Reply-To: <54AC7B84.8000902@gmail.com>
References: <20141208171247.21096.35754.idtracker@ietfa.amsl.com> <54AC7B84.8000902@gmail.com>
Date: Thu, 8 Jan 2015 14:16:27 -0600
Message-ID: <CAC8QAcfQzWXw2AV-_O86fU9i3qV5nR-BZO5EV0-3uscPiOK0NQ@mail.gmail.com>
Subject: Re: I-D Action: draft-sarikaya-6man-sadr-overview-03.txt
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ibGxr-CD4Lf3YLttjf92b0W8wQg>
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jan 2015 20:16:31 -0000

 Hi Brian,

On Tue, Jan 6, 2015 at 6:19 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> Hi,
>
> One general comment is that I think the title of the draft
> is a little misleading, because it doesn't emphasise the
> host aspect. This is clumsy but might be clearer:
>
> "Source Address Dependent Routing and Source Address Selection for IPv6 Hosts"
>

Done that.

> I think the discussion in Section 5 "What Needs to be Done"
> is getting closer to what we need to say, but is not quite
> there yet. I think it would be better formulated in two
> parts:
>
> #1. Scenarios solved by Rule 5.5 in [RFC6724], and what needs
> to be done for that to work (mainly, as I understand it, that
> hosts SHOULD register which next-hop router announced each
> prefix).
>

Will do.

> #2. Scenarios *not* solved by that, and exactly what information
> hosts need for correct SA selection in that case.

Will do.
>
> Also, I think it's probably not made clear enough that SADR
> SHOULD be supported by routers throughout a site that has
> multiple exits. I guess Fred's draft implies that, but doesn't
> say it in so many words.

Will do.
>
> (I don't want to comment on details of draft-sarikaya-6man-next-hop-ra
> or draft-sarikaya-dhc-dhcpv6-raoptions-sadr

Please use this latest version:
http://tools.ietf.org/id/draft-sarikaya-dhc-6man-dhcpv6-sadr-00.txt

> until point #2 above
> is settled.)

Regards,

Behcet
>
> Regards
>    Brian
>
> On 09/12/2014 06:12, internet-drafts@ietf.org wrote:
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>
>>
>>         Title           : Overview of Source Address Dependent Routing
>>         Author          : Behcet Sarikaya
>>       Filename        : draft-sarikaya-6man-sadr-overview-03.txt
>>       Pages           : 14
>>       Date            : 2014-12-08
>>
>> Abstract:
>>    This document presents an overview of source address dependent
>>    routing from the host perspective.  Multihomed hosts and hosts with
>>    multiple interfaces are considered.  Different architectures are
>>    introduced and with their help, why source address selection and next
>>    hop resolution in view of source address dependent routing is needed
>>    is explained.  The document concludes with a discussion on the
>>    standardization work that is needed.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-sarikaya-6man-sadr-overview/
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-sarikaya-6man-sadr-overview-03
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-sarikaya-6man-sadr-overview-03
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Thu Jan  8 13:25:59 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 572A61A0383 for <ipv6@ietfa.amsl.com>; Thu,  8 Jan 2015 13:25:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.505
X-Spam-Level: 
X-Spam-Status: No, score=-0.505 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, SUBJ_ALL_CAPS=1.506, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XVe5r2NnBEzo for <ipv6@ietfa.amsl.com>; Thu,  8 Jan 2015 13:25:57 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6959A1A00FA for <ipv6@ietf.org>; Thu,  8 Jan 2015 13:25:57 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id DBC6361EC; Thu,  8 Jan 2015 13:25:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version; s=selector1; bh=eXRd1BTZkG+tmAgwJS/OAyDZXuI =; b=mZSEcJIlDq6PAS6AwGeSHFisD695yU6BMWkd49zU44yOUDY/PyCMvmzfOit IYxTmxWtRSREKAaRj8MCwCPob19UbculNWei7l5uuNhhWGCJXtWj3o5sspQIiw3u uK5QFFkRVP9ojRNkNYu5re+JBO0kR3Dx689Mltie03h03bw0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version; q=dns; s=selector1; b=JNV0jtLmxr44tV+/DuT/P 8Jvc4pK+4JlZEhVqAwKDSuLy/vGl2FiHecA2Rhx0ivipvbS2CWtjggASeu/Yo7Za zDciHfAA0Dx56V7ZrudW9i9KO+EfixOTySUI6vwPeKEAfx2buCY+tY9jVo7RUSnL Us2qrJvD+tOcWBrPpbyyC0=
Received: from gomlefisk.localdomain (cm-84.215.198.95.getinternet.no [84.215.198.95]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 94AC661B1; Thu,  8 Jan 2015 13:25:55 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id B3CFF3C60BF6; Thu,  8 Jan 2015 22:25:52 +0100 (CET)
From: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: 6MAN @ IETF92
Date: Thu, 8 Jan 2015 22:25:52 +0100
Message-Id: <36AFE802-3A19-4CCB-9FEB-1D328F3D582A@employees.org>
To: 6man WG <ipv6@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.1\))
X-Mailer: Apple Mail (2.2070.1)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/w7FK0q3JRlee1LdovbNWDxB4h5U>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jan 2015 21:25:58 -0000

We have requested a 2.5 hour slot for a 6MAN Working Group meeting at =
IETF92.

The conflict list is as follows:
 First Priority:	6lo 6tisch dnssd mif sdnrg v6ops softwire dhc =
homenet
 Second Priority: alto aqm intarea rtgarea rtgwg savi tcpm

We have also requested a Meetecho support in the room in case anyone is =
remote / need to present remotely.

We plan to organise the meeting in three sections as before. Working =
groups drafts, Active Individual drafts and New Individual drafts. We =
prioritise in that order.

Active individual drafts are drafts that have seen active discussion on =
the IPv6 list, and the New Individual drafts are ones that are new =
and/or have not seen a lot of discussion.  There is only enough time to =
give the last category five minutes to allow the authors to do a =
introduction to the work and then start a discussion on the mailing =
list. Depending on how full the agenda is we can't guarantee time for =
new individual drafts.

We will send out a request for agenda items mid February.

Best regards,
Bob and Ole=


From nobody Fri Jan  9 01:50:25 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FDA61A8735 for <ipv6@ietfa.amsl.com>; Fri,  9 Jan 2015 01:50:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ELhWEG9H23BH for <ipv6@ietfa.amsl.com>; Fri,  9 Jan 2015 01:50:20 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 664031A871D for <ipv6@ietf.org>; Fri,  9 Jan 2015 01:50:20 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 4F5B661E9; Fri,  9 Jan 2015 01:50:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=ENt74kN7cS0lXY4j8Hk7AthNBhY=; b=rWtlJ7hFXL/9lW8R/X 3gqDsRfM8HC6aYSllrFCHHAevgWeg/imJ+5MKNrMCn5XI0Khve80iHaL9YUOWULL Mj8JC3RHceocfFvC7EgtluVJ8VeR6+CkkGnYRJHcdswX0oTSsVbUzbp8v1riPp67 uPNyOH9pI+HBcXLsadBktX93o=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=F7e9abL4igJnZNtls+rfvwi54aqWaepwCPZTwcMIEA5JvHjfjl1 2Wd1W2rRrpIZVUjV4olbxcd9D4gnlB2bvQIIx52BzNwhtvezf0twkTlnHiLYAuYQ CneP9CtwoY3UPgH1p3WTxHgn803uDJIl5JGwQ7E2oJKzol3Bx+MAW3is=
Received: from gomlefisk.localdomain (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id E294861CE; Fri,  9 Jan 2015 01:50:17 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 4E47E3C686AB; Fri,  9 Jan 2015 10:50:15 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.1\))
Subject: Re: 6MAN WG Last Call: draft-ietf-6man-predictable-fragment-id-01
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CC2EE99E-475C-4DB5-9E7F-ED00B4D48561@employees.org>
Date: Fri, 9 Jan 2015 10:50:15 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F61E78C8-5AF0-4528-B046-AC7D45E5140F@employees.org>
References: <CC2EE99E-475C-4DB5-9E7F-ED00B4D48561@employees.org>
To: 6man WG <ipv6@ietf.org>
X-Mailer: Apple Mail (2.2070.1)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/VgolA9DWkN_v0ANMxvL-aZ5QG5k>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Jan 2015 09:50:22 -0000

All,

Based on the feedback received, the 6man chairs believe there is =
consensus to advance draft-ietf-6man-predictable-fragment-id-02 to the =
IESG as an Informational document.

Regards,
Ole and Bob

> On 04 Dec 2014, at 9:07 , Ole Troan <otroan@employees.org> wrote:
>=20
> This message starts a two week 6MAN Working Group Last Call on =
advancing:
>=20
>     Title           : Security Implications of Predictable Fragment =
Identification Values
>     Authors     : Fernando Gont
>     Filename   : draft-ietf-6man-predictable-fragment-id-01.txt
>     Pages        : 16
>     Date           : 2014-04-30
>=20
>      =
http://tools.ietf.org/html/draft-ietf-6man-predictable-fragment-id-01
>=20
> as a Best Current Practice Document.  Substantive comments and =
statements of support for publishing this document should be directed to =
the mailing list.  Editorial suggestions can be sent to the authors.  =
This last call will end on December 18, 2014.
>=20
> Note: While the document has expired, we didn't consider it necessary =
to refresh it purely for the sake of initiating the working group last =
call.
>=20
> Regards,
>=20
> Bob Hinden & Ole Tr=C3=B8an
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Mon Jan 12 03:52:48 2015
Return-Path: <karsten_thomann@linfre.de>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE1D71A8BC2; Mon, 12 Jan 2015 03:52:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.338
X-Spam-Level: 
X-Spam-Status: No, score=0.338 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pTp4fhnNPrxu; Mon, 12 Jan 2015 03:52:43 -0800 (PST)
Received: from linfre.de (linfre.de [83.151.26.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9B771A7003; Mon, 12 Jan 2015 03:52:42 -0800 (PST)
Received: from linne.localnet (178.142.123.166) by linfreserv.linfre (Axigen) with (ECDHE-RSA-AES256-SHA encrypted) ESMTPSA id 10920C; Mon, 12 Jan 2015 12:52:31 +0100
From: Karsten Thomann <karsten_thomann@linfre.de>
To: ipv6@ietf.org
Subject: Re: 6MAN cross-wg review: draft-ietf-l2tpext-keyed-ipv6-tunnel-01
Date: Mon, 12 Jan 2015 12:52:31 +0100
Message-ID: <1816705.A9t7GNQOdE@linne>
User-Agent: KMail/4.10.4 (Windows/6.1; KDE/4.10.4; i686; ; )
In-Reply-To: <232077E7-7135-41E8-B0DB-C786F8C410CA@employees.org>
References: <232077E7-7135-41E8-B0DB-C786F8C410CA@employees.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="nextPart4123148.1RlpNb6qs0"
Content-Transfer-Encoding: 7Bit
X-AXIGEN-DK-Result: No records
DomainKey-Status: no signature
X-AxigenSpam-Level: 6
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/FG-y0KSYvfoIOvGl68nA2qYAk58>
Cc: l2tpext@ietf.org, l2tpext-chairs@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Jan 2015 11:52:45 -0000

This is a multi-part message in MIME format.

--nextPart4123148.1RlpNb6qs0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

As Jinmai already wrote, I can volunteer, but only under the same constrains, as I have no prior 
experience with reviews.

Some comments:
I know it is also written in RFC4719, but why was "or" used at "Ethernet frame, without the 
preamble or frame check sequence (FCS)".
At the payload section is "and" used...
"As noted above preamble and FCS are stripped before encapsulation."

As already written by Jinmai, the hop limit is with 255 as a default setting a bit high, a default of 
64 should be high enough for nearly all cases.

Kind regards
Karsten

Am Dienstag, 6. Januar 2015, 12:14:14 schrieb Ole Troan:
> Hi,
> 
> The chairs of l2tpext have asked for a 6man review of:
> 
> Title: Keyed IPv6 Tunnel
> https://tools.ietf.org/html/draft-ietf-l2tpext-keyed-ipv6-tunnel-01
> 
> Can we get a couple of volunteers please? As well as any other comments to
> the lists are welcome of course. Please keep l2tpext@ietf.org in CC.
> 
> Best regards,
> Ole
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

--nextPart4123148.1RlpNb6qs0
Content-Transfer-Encoding: 7Bit
Content-Type: text/html; charset="us-ascii"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd">
<html><head><meta name="qrichtext" content="1" /><style type="text/css">
p, li { white-space: pre-wrap; }
</style></head><body style=" font-family:'Tahoma'; font-size:8.25pt; font-weight:400; font-style:normal;">
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">As Jinmai already wrote, I can volunteer, but only under the same constrains, as I have no prior experience with reviews.</p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; ">&nbsp;</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Some comments:</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">I know it is also written in RFC4719, but why was &quot;or&quot; used at &quot;Ethernet frame, without the preamble or frame check sequence (FCS)&quot;.</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">At the payload section is &quot;and&quot; used...</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&quot;As noted above preamble and FCS are stripped before encapsulation.&quot;</p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; ">&nbsp;</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">As already written by Jinmai, the hop limit is with 255 as a default setting a bit high, a default of 64 should be high enough for nearly all cases.</p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; ">&nbsp;</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Kind regards</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Karsten</p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; ">&nbsp;</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Am Dienstag, 6. Januar 2015, 12:14:14 schrieb Ole Troan:</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; Hi,</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; The chairs of l2tpext have asked for a 6man review of:</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; Title: Keyed IPv6 Tunnel</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; https://tools.ietf.org/html/draft-ietf-l2tpext-keyed-ipv6-tunnel-01</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; Can we get a couple of volunteers please? As well as any other comments to</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; the lists are welcome of course. Please keep l2tpext@ietf.org in CC.</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; Best regards,</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; Ole</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; --------------------------------------------------------------------</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; IETF IPv6 working group mailing list</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; ipv6@ietf.org</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; --------------------------------------------------------------------</p></body></html>
--nextPart4123148.1RlpNb6qs0--


From nobody Tue Jan 13 00:59:37 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28B0B1A8A6A; Tue, 13 Jan 2015 00:59:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JcX3lxZepDUj; Tue, 13 Jan 2015 00:59:31 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 73F481A8A43; Tue, 13 Jan 2015 00:59:31 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id A472E616C; Tue, 13 Jan 2015 00:59:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=e4SDtI++HOhjoiLgwedjLNFvecI=; b=ORsZyyRQ0Twwzdbi2R 53jPP01vwWHKq7gAxparVY1KjkcZjdkgdK1QYQj4nXokaJad6Ddg+Gq3mknkH0S2 OlFAZUN9GnQdh6X5XfCs1sfJ+XLFvfwx4IwycoKdWT0Dc0C7K0OamECyFPUre9W6 xRQbkPAa/1RGglnvvZyPqgWUk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=EDLUXxTrVRfkCBXAmiBoo86UELKZLNWz0dnjwIVjamrUP8A02Jj wtSp1aZgldAysaOQyC7zwMclU8opOFleFs4BF0c4/zlt04ifs7SXQcXvHYMS3Rtd Uc7Jl4x/vMPgrU2FRua882epJ2loRVt2NUxnLCmWmAx94nSKpctr49sg=
Received: from gomlefisk.localdomain (173-38-208-170.cisco.com [173.38.208.170]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 5C8E2613E; Tue, 13 Jan 2015 00:59:30 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 64C7C3CA80F3; Tue, 13 Jan 2015 09:59:28 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.1\))
Subject: Re: 6MAN cross-wg review: draft-ietf-l2tpext-keyed-ipv6-tunnel-01
From: Ole Troan <otroan@employees.org>
In-Reply-To: <1816705.A9t7GNQOdE@linne>
Date: Tue, 13 Jan 2015 09:59:28 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <68C9F850-89F5-4759-9FD0-1A00B33DDD46@employees.org>
References: <232077E7-7135-41E8-B0DB-C786F8C410CA@employees.org> <1816705.A9t7GNQOdE@linne>
To: Karsten Thomann <karsten_thomann@linfre.de>
X-Mailer: Apple Mail (2.2070.1)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/WgUj3TQwDB4JCF6D-uAA2dr8hPA>
Cc: 6man WG <ipv6@ietf.org>, l2tpext@ietf.org, l2tpext-chairs@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jan 2015 08:59:33 -0000

Thanks Karsten, I look forward to your review.

Best regards,
Ole

> On 12 Jan 2015, at 12:52 , Karsten Thomann <karsten_thomann@linfre.de> =
wrote:
>=20
> As Jinmai already wrote, I can volunteer, but only under the same =
constrains, as I have no prior experience with reviews.
> =20
> Some comments:
> I know it is also written in RFC4719, but why was "or" used at =
"Ethernet frame, without the preamble or frame check sequence (FCS)".
> At the payload section is "and" used...
> "As noted above preamble and FCS are stripped before encapsulation."
> =20
> As already written by Jinmai, the hop limit is with 255 as a default =
setting a bit high, a default of 64 should be high enough for nearly all =
cases.
> =20
> Kind regards
> Karsten
> =20
> Am Dienstag, 6. Januar 2015, 12:14:14 schrieb Ole Troan:
> > Hi,
> >=20
> > The chairs of l2tpext have asked for a 6man review of:
> >=20
> > Title: Keyed IPv6 Tunnel
> > https://tools.ietf.org/html/draft-ietf-l2tpext-keyed-ipv6-tunnel-01
> >=20
> > Can we get a couple of volunteers please? As well as any other =
comments to
> > the lists are welcome of course. Please keep l2tpext@ietf.org in CC.
> >=20
> > Best regards,
> > Ole
> >=20
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------


From nobody Tue Jan 13 02:06:02 2015
Return-Path: <armandoortiz088@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24FB31ACE58 for <ipv6@ietfa.amsl.com>; Tue, 13 Jan 2015 02:06:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level: 
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, TVD_SPACE_RATIO=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D8wy4Ot6sIch for <ipv6@ietfa.amsl.com>; Tue, 13 Jan 2015 02:06:00 -0800 (PST)
Received: from mail-wg0-x243.google.com (mail-wg0-x243.google.com [IPv6:2a00:1450:400c:c00::243]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4C891ACE4C for <ipv6@ietf.org>; Tue, 13 Jan 2015 02:05:59 -0800 (PST)
Received: by mail-wg0-f67.google.com with SMTP id k14so566325wgh.2 for <ipv6@ietf.org>; Tue, 13 Jan 2015 02:05:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=DeyZKvktyMWwNDCxOs85/AJkW9bznd8qJEBu0f+USEc=; b=OUnLvrlhafm85D5EccYAtCt5KmJsyXBU/iu6dIlNVqzV52bOrJmARHScH5PebwfUS6 SG8dICPqpGcRXgaxc2bQms+Gped/9Oxpn1OFeQD7B3qHIcuH0HqNkFdjLXtQneUnXz85 j2TfPIVnlPdhZ79UvAym12aYOoMNexXIOXgQTiI86tumbRvO3pabaK806J5aO4iiiAmM dPygdiIxr2iJB0DOAaetbGOoOoejul7qDPZVOtL1O6IeJFDlekL1rop1mly/ZGrljRQ6 YuHVryTgIO1Q5CGyhQA+YJXCfX4ryNfO+6BhLCKbsyxos/EqnDKU2zANFvd3Eidrl1r/ b7BA==
MIME-Version: 1.0
X-Received: by 10.194.94.38 with SMTP id cz6mr3247559wjb.136.1421143558593; Tue, 13 Jan 2015 02:05:58 -0800 (PST)
Received: by 10.194.83.199 with HTTP; Tue, 13 Jan 2015 02:05:58 -0800 (PST)
Received: by 10.194.83.199 with HTTP; Tue, 13 Jan 2015 02:05:58 -0800 (PST)
Date: Tue, 13 Jan 2015 02:05:58 -0800
Message-ID: <CA+Wo+y_AFXdNABGB08KBOyaWmV7D-WkLFwP6K4o4hNyOFcLGXw@mail.gmail.com>
Subject: Facebook
From: armando ortiz <armandoortiz088@gmail.com>
To: ipv6@ietf.org
Content-Type: multipart/alternative; boundary=047d7bb0395cfc26d5050c85c4db
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Amwue560qJUIdZqLucr7YhLcC0U>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jan 2015 10:06:01 -0000

--047d7bb0395cfc26d5050c85c4db
Content-Type: text/plain; charset=UTF-8

Juguetitos

--047d7bb0395cfc26d5050c85c4db
Content-Type: text/html; charset=UTF-8

<p dir="ltr">Juguetitos </p>

--047d7bb0395cfc26d5050c85c4db--


From nobody Wed Jan 14 06:40:06 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AA261B2CCE; Wed, 14 Jan 2015 06:40:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W5hyes_X86FR; Wed, 14 Jan 2015 06:40:02 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0732C1B2C67; Wed, 14 Jan 2015 06:40:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-enhanced-dad-11.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150114144002.30074.72710.idtracker@ietfa.amsl.com>
Date: Wed, 14 Jan 2015 06:40:02 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/MQ4_ErgoGqaYIWKA8xKu7AMBbbA>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jan 2015 14:40:04 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the IPv6 Maintenance Working Group of the IETF.

        Title           : Enhanced Duplicate Address Detection
        Authors         : Rajiv Asati
                          Hemant Singh
                          Wes Beebee
                          Carlos Pignataro
                          Eli Dart
                          Wesley George
	Filename        : draft-ietf-6man-enhanced-dad-11.txt
	Pages           : 10
	Date            : 2015-01-14

Abstract:
   IPv6 Loopback Suppression and Duplicate Address Detection (DAD) are
   discussed in Appendix A of RFC4862.  That specification mentions a
   hardware-assisted mechanism to detect looped back DAD messages.  If
   hardware cannot suppress looped back DAD messages, a software
   solution is required.  Several service provider communities have
   expressed a need for automated detection of looped back Neighbor
   Discovery (ND) messages used by DAD.  This document includes
   mitigation techniques and outlines the Enhanced DAD algorithm to
   automate the detection of looped back IPv6 ND messages used by DAD.
   For network loopback tests, the Enhanced DAD algorithm allows IPv6 to
   self-heal after a loopback is placed and removed.  Further, for
   certain access networks the document automates resolving a specific
   duplicate address conflict.  This document updates RFC4861, RFC4862,
   and RFC3971.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-dad/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-enhanced-dad-11

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-enhanced-dad-11


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Jan 14 06:40:10 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A94C1B2CD4 for <ipv6@ietfa.amsl.com>; Wed, 14 Jan 2015 06:40:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Haqo75y0WYjC; Wed, 14 Jan 2015 06:40:04 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BA0D1B2CC8; Wed, 14 Jan 2015 06:40:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: 6man-chairs@tools.ietf.org, ot@cisco.com, draft-ietf-6man-enhanced-dad.all@tools.ietf.org, ipv6@ietf.org, brian@innovationslab.net
Subject: New Version Notification - draft-ietf-6man-enhanced-dad-11.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150114144002.30074.95482.idtracker@ietfa.amsl.com>
Date: Wed, 14 Jan 2015 06:40:02 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/pQc1TZ3fQGTnUk5OumKRm2Vo_F8>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jan 2015 14:40:08 -0000

A new version (-11) has been submitted for draft-ietf-6man-enhanced-dad:
http://www.ietf.org/internet-drafts/draft-ietf-6man-enhanced-dad-11.txt

Sub state has been changed to AD Followup from Revised ID Needed


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-dad/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-enhanced-dad-11

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

IETF Secretariat.


From nobody Wed Jan 14 14:43:54 2015
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B470E1ACEC8; Wed, 14 Jan 2015 14:43:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level: 
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dt_HumuwPQL5; Wed, 14 Jan 2015 14:43:50 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 9EFA11ACEC7; Wed, 14 Jan 2015 14:43:50 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id A7661180448; Wed, 14 Jan 2015 14:43:01 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7421 on Analysis of the 64-bit Boundary in IPv6 Addressing
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150114224301.A7661180448@rfc-editor.org>
Date: Wed, 14 Jan 2015 14:43:01 -0800 (PST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/sfAlY7sNMUu2Dq3P2sHbVdI_0Ps>
Cc: ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jan 2015 22:43:52 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7421

        Title:      Analysis of the 64-bit Boundary 
                    in IPv6 Addressing 
        Author:     B. Carpenter, Ed.,
                    T. Chown, F. Gont,
                    S. Jiang, A. Petrescu,
                    A. Yourtchenko
        Status:     Informational
        Stream:     IETF
        Date:       January 2015
        Mailbox:    brian.e.carpenter@gmail.com, 
                    tjc@ecs.soton.ac.uk, 
                    fgont@si6networks.com,
                    jiangsheng@huawei.com, 
                    alexandru.petrescu@cea.fr,
                    ayourtch@cisco.com
        Pages:      24
        Characters: 60469
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-6man-why64-08.txt

        URL:        https://www.rfc-editor.org/info/rfc7421

The IPv6 unicast addressing format includes a separation between the
prefix used to route packets to a subnet and the interface identifier
used to specify a given interface connected to that subnet.
Currently, the interface identifier is defined as 64 bits long for
almost every case, leaving 64 bits for the subnet prefix.  This
document describes the advantages of this fixed boundary and analyzes
the issues that would be involved in treating it as a variable
boundary.

This document is a product of the IPv6 Maintenance Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Wed Jan 14 15:51:54 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 682E31AD0AB; Wed, 14 Jan 2015 15:51:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a-LJVbHWj5Vj; Wed, 14 Jan 2015 15:51:50 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 674151AD0A2; Wed, 14 Jan 2015 15:51:50 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-enhanced-dad-12.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150114235150.26494.53124.idtracker@ietfa.amsl.com>
Date: Wed, 14 Jan 2015 15:51:50 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/s_VDDO9FDTgXGic9-421PTTGRVg>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jan 2015 23:51:52 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the IPv6 Maintenance Working Group of the IETF.

        Title           : Enhanced Duplicate Address Detection
        Authors         : Rajiv Asati
                          Hemant Singh
                          Wes Beebee
                          Carlos Pignataro
                          Eli Dart
                          Wesley George
	Filename        : draft-ietf-6man-enhanced-dad-12.txt
	Pages           : 10
	Date            : 2015-01-14

Abstract:
   IPv6 Loopback Suppression and Duplicate Address Detection (DAD) are
   discussed in Appendix A of RFC4862.  That specification mentions a
   hardware-assisted mechanism to detect looped back DAD messages.  If
   hardware cannot suppress looped back DAD messages, a software
   solution is required.  Several service provider communities have
   expressed a need for automated detection of looped back Neighbor
   Discovery (ND) messages used by DAD.  This document includes
   mitigation techniques and outlines the Enhanced DAD algorithm to
   automate the detection of looped back IPv6 ND messages used by DAD.
   For network loopback tests, the Enhanced DAD algorithm allows IPv6 to
   self-heal after a loopback is placed and removed.  Further, for
   certain access networks the document automates resolving a specific
   duplicate address conflict.  This document updates RFC4861, RFC4862,
   and RFC4429.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-dad/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-enhanced-dad-12

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-enhanced-dad-12


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Jan 14 15:52:00 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 536821B2A68 for <ipv6@ietfa.amsl.com>; Wed, 14 Jan 2015 15:51:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2NsmMcKvvDtm; Wed, 14 Jan 2015 15:51:52 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F1181AD0B3; Wed, 14 Jan 2015 15:51:50 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: 6man-chairs@tools.ietf.org, ot@cisco.com, draft-ietf-6man-enhanced-dad.all@tools.ietf.org, ipv6@ietf.org, brian@innovationslab.net
Subject: New Version Notification - draft-ietf-6man-enhanced-dad-12.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150114235150.26494.73888.idtracker@ietfa.amsl.com>
Date: Wed, 14 Jan 2015 15:51:50 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/tb9ieb3PlqLA2dr8uxpNME89leM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Jan 2015 23:51:54 -0000

A new version (-12) has been submitted for draft-ietf-6man-enhanced-dad:
http://www.ietf.org/internet-drafts/draft-ietf-6man-enhanced-dad-12.txt


The IETF datatracker page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-dad/

Diff from previous version:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-enhanced-dad-12

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

IETF Secretariat.


From nobody Thu Jan 15 13:02:58 2015
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1C861B29DF for <ipv6@ietfa.amsl.com>; Thu, 15 Jan 2015 13:02:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zIM0o3oLyb_i for <ipv6@ietfa.amsl.com>; Thu, 15 Jan 2015 13:02:55 -0800 (PST)
Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85BB91B29C8 for <ipv6@ietf.org>; Thu, 15 Jan 2015 13:02:55 -0800 (PST)
Received: by mail-la0-f47.google.com with SMTP id hz20so15799687lab.6 for <ipv6@ietf.org>; Thu, 15 Jan 2015 13:02:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:date:message-id:subject:from:to:content-type;  bh=bhQpqmLKc2nLYXXbORdg5LkJ/92zWoJW4XCajfl/yn4=; b=YPkrdm1xRLXt/N/XmFzZj+KmoZlgAcvb+ostRhs/qWHa0lCoL0QlLLStE1Xbtc8Z7e FxyTXvuqlVq6rLqAnUNrRPQeW8oZTZFtB8NV15lEwaZZeOuH/3rfQlplU9s+EpFKn95b xe0l4V6CCjfdb6ZAODZK0cT0pF/N7mhri9pZ4WXJXH1RfexBG921l3H89NC5RzNHu10N vs82PO0UkHwMNtAKB7+aDQkUCz0bwyTUBW66HbKTRdkLXsONf5cWH6qePZqCq96kV5GJ Jq8lIaxa0PIU+dMxtNo8JFB3R5AwmpNkez1Rvb0lSwdYWEQqGoK/abGd1lkC3MusuM/t ytJA==
MIME-Version: 1.0
X-Received: by 10.112.156.169 with SMTP id wf9mr12011643lbb.85.1421355774011;  Thu, 15 Jan 2015 13:02:54 -0800 (PST)
Received: by 10.114.63.51 with HTTP; Thu, 15 Jan 2015 13:02:53 -0800 (PST)
Date: Thu, 15 Jan 2015 15:02:53 -0600
Message-ID: <CAC8QAcfqZJ_z1LETybp6tx057eTLe9wQoaXfmagzBh82AStfHg@mail.gmail.com>
Subject: New Version Notification for draft-sarikaya-6man-sadr-overview-04.txt
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: "ipv6@ietf.org" <ipv6@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/SZqj-GfkW0lP6EBAUlOI3mw_Hlo>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jan 2015 21:02:57 -0000

 Hi all,

Based on latest comments received, we revised the draft as follows.
Please check.

Regards,

Behcet


A new version of I-D, draft-sarikaya-6man-sadr-overview-04.txt
has been successfully submitted by Behcet Sarikaya and posted to the
IETF repository.

Name:           draft-sarikaya-6man-sadr-overview
Revision:       04
Title:          Source Address Dependent Routing and Source Address
Selection for IPv6 Hosts
Document date:  2015-01-15
Group:          Individual Submission
Pages:          15
URL:
http://www.ietf.org/internet-drafts/draft-sarikaya-6man-sadr-overview-04.txt
Status:
https://datatracker.ietf.org/doc/draft-sarikaya-6man-sadr-overview/
Htmlized:       http://tools.ietf.org/html/draft-sarikaya-6man-sadr-overview-04
Diff:
http://www.ietf.org/rfcdiff?url2=draft-sarikaya-6man-sadr-overview-04

Abstract:
   This document presents the source address dependent routing from the
   host perspective.  Multihomed hosts and hosts with multiple
   interfaces are considered.  Different architectures are introduced
   and with their help, why source address selection and next hop
   resolution in view of source address dependent routing is needed is
   explained.  The document concludes with an informative guidelines on
   the different solution approaches.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat


From nobody Thu Jan 15 13:16:02 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FE161A899E; Thu, 15 Jan 2015 13:15:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5jTbAEPRnPmh; Thu, 15 Jan 2015 13:15:50 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CFDB1B29B3; Thu, 15 Jan 2015 13:15:47 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-ipv6-address-generation-privacy-03.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150115211547.19546.48630.idtracker@ietfa.amsl.com>
Date: Thu, 15 Jan 2015 13:15:47 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ru2YcLgQTkN6j-58vq01FfG-dFA>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jan 2015 21:15:53 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the IPv6 Maintenance Working Group of the IETF.

        Title           : Privacy Considerations for IPv6 Address Generation Mechanisms
        Authors         : Alissa Cooper
                          Fernando Gont
                          Dave Thaler
	Filename        : draft-ietf-6man-ipv6-address-generation-privacy-03.txt
	Pages           : 22
	Date            : 2015-01-15

Abstract:
   This document discusses privacy and security considerations for
   several IPv6 address generation mechanisms, both standardized and
   non-standardized.  It evaluates how different mechanisms mitigate
   different threats and the trade-offs that implementors, developers,
   and users face in choosing different addresses or address generation
   mechanisms.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-ipv6-address-generation-privacy/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-ipv6-address-generation-privacy-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-ipv6-address-generation-privacy-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Jan 15 14:00:26 2015
Return-Path: <mcr@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0745D1A1B91; Thu, 15 Jan 2015 14:00:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_DBL_ABUSE_REDIR=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s8PUHT9g8Adr; Thu, 15 Jan 2015 14:00:18 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E4851A8838; Thu, 15 Jan 2015 14:00:18 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id DFC7B20098; Thu, 15 Jan 2015 17:06:08 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id BF8F063B0E; Thu, 15 Jan 2015 17:00:16 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id A95E1637EC; Thu, 15 Jan 2015 17:00:16 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: iesg-secretary@ietf.org, roll@ietf.org
Subject: virtual interim meeting for ROLL: 2015-02-10, 15:00 UTC
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 15 Jan 2015 17:00:16 -0500
Message-ID: <7200.1421359216@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/yGO8ah8E7EnzlGYqeQgxl6G809Q>
Cc: Adrian Farrel <adrian@olddog.co.uk>, 6tisch@ietf.org, 6man@ietf.org, Brian Haberman <brian@innovationslab.net>, 6lo@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: roll@ietf.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jan 2015 22:00:21 -0000

--=-=-=
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable


In accordance with: https://www.ietf.org/iesg/statement/interim-meetings.ht=
ml
the ROLL Working Group Chairs are announcing a virtual interim meeting for
February 10, 2015, from 15:00 UTC to 18:00 UTC.
      (please see: http://goo.gl/NVefsy to convert the time)

The very draft agenda is in development, and can be seen at:
  http://www.ietf.org/proceedings/interim/2015/02/10/roll/agenda/agenda-int=
erim-2015-roll-1

The goal of this interim meeting is to do a deep technical dive into the
different ways of optimizing the byte/power cost of the RFC6553 (RPI) and
RFC6554 (RH3) options.  This could involve compression or recoding, or???
We invite submissions on this.  Please post your -00 draft by January 23 if
possible, or point us at your other drafts.

We will use JITSI for audio, video and slides, with the following URL:
     https://jitsi.tools.ietf.org/Roll20150210VirtualInterim
  Participants are encouraged to visit this URL in advance to verify that
  it works for them.  If you need another participant to help verify, pleas=
e=20
  email me.

There will be a PSTN bridge for a backup, should things completely fail.
We will have a dial-in phone number connected to the bridge for those that
are unable to connect with a computer, but it won't be toll-free.=20=20
The phone numbers involved will be posted to the agenda as it is finalized,
and we expect to distribute slides by January 27, 2015.

(BTW: we do not believe that ROLL will meet in Dallas/IETF92)



=2D-=20
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works=20
IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/


--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVLg4bYCLcPvd0N1lAQLphQgAghZ8y49HRk0Vbq2vf+o+brNTF4feOYv/
vWMh80LWmsiSIcmYKBblXKRFP61HSY4USlQz3dt0kUme91+kPsL8oFGQzYw2ZhQf
kwrhr+z0q9iOHSHqzLok4aUS9WJo158Hxj55AOA52CWsjLtRvlnBe+6SGUDcvhmj
TE4HeobrKIlFY7hE2SPMYYo08gHNVlc/7QBHq19B9OLD/5fQ8wLGp2OALDgEnWnP
Kyhd4FE4c2PhPtWly1bVxk24hJcfGdp7/TM0kIKyTp4N0yeMYPhvI/+ZLxbCRuGE
Mj5oofsEXXTP/yugBi9rbbE4b7/HkJcbI+4Uh+fz66NwhKe7ZNn5qg==
=JwC+
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Jan 16 01:13:29 2015
Return-Path: <ot@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA18D1AC3AF for <ipv6@ietfa.amsl.com>; Fri, 16 Jan 2015 01:13:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T9Pc14aLEBRF for <ipv6@ietfa.amsl.com>; Fri, 16 Jan 2015 01:13:11 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EAD01AC3AA for <ipv6@ietf.org>; Fri, 16 Jan 2015 01:13:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3392; q=dns/txt; s=iport; t=1421399585; x=1422609185; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=jab19PjghtkAWuVm5JD8+4He8f0NWkiVzBggEOFMqSQ=; b=hCIl6majFvkGMS9CN8sS29OJ6LVhG2GoE4539fHimVYjJ0LbxnO9BnES wzSIVmJQkurQcE9eOzVjAOnNXRxVJtRDCXZXbHpEyJKgCnIeNDn7/cTXV xzIt77T2Hme1/MCYBzoxqvSrcUEGtFo3vD1Z16Bn5JEpQv+Kukb7KGSTo Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArsEAFvVuFStJssW/2dsb2JhbABagmR0UwW8b4kvDIVvAoFaAQEBAQF9hAwBAQEDAQEBATc0CQIFCwsYLiEGMBkJEod9AwkIAQcFzRQNhAMBAQEBAQEBAwEBAQEBAQEBAQEBF41PgXczB4MWgRMFhTiHOIUjhASBRIEPMIJDiB2FayKDb24BgkIBAQE
X-IronPort-AV: E=Sophos;i="5.09,409,1418083200"; d="scan'208";a="313715228"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 16 Jan 2015 09:13:03 +0000
Received: from gomlefisk.localdomain (ssh-ams-2.cisco.com [144.254.73.146]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t0G9D21Z025864 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Jan 2015 09:13:03 GMT
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 9B0953CDCFC5; Fri, 16 Jan 2015 10:13:02 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.1\))
Subject: Re: New Version Notification for draft-sarikaya-6man-sadr-overview-04.txt
From: Ole Troan <ot@cisco.com>
In-Reply-To: <CAC8QAcfqZJ_z1LETybp6tx057eTLe9wQoaXfmagzBh82AStfHg@mail.gmail.com>
Date: Fri, 16 Jan 2015 10:13:02 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <50578ECA-9DC0-4FBF-98B3-1B7149E34392@cisco.com>
References: <CAC8QAcfqZJ_z1LETybp6tx057eTLe9wQoaXfmagzBh82AStfHg@mail.gmail.com>
To: sarikaya@ieee.org
X-Mailer: Apple Mail (2.2070.1)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/9oxW5BiqfXucSpAsX4cIVlQM4A4>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jan 2015 09:13:14 -0000

Behcet,

a few comments if I may.

with regards to section 5.1 and rule 5.5 from rfc6724:
you state that rule 5.5. solves the scenarios in figure 1, 2 and 3. I =
would rather say that a strong ES model would solve those. rule 5.5. =
solves the scenario in figure 4.

you also reference rfc7078 in section 5.1. 7078 does not have any means =
to configure rule 5.5 on a host, if that was what you tried to imply (I =
might have misread you here though).

given that, I still don't understand the need for section 5.2 and a new =
router advertisement option.

a minor point on section 4.2 and provisioning domains. in any =
multi-homed network, I think it is a policy choice if the "external" =
provisioning domains are presented to the host or if the network =
presents itself as a single provisioning domain. i.e. the network =
"merges" the information.

in section 5.4 you mention other solutions and probing as a possibility. =
if we go back to the multi-homing requirements from rfc3582, there are =
still many gaps with multi-prefix multi-homing. as far as I can see =
those gaps need to be closed by changes at the transport layer, a new =
intermediate layer (aka session) or in the application layer. do you =
intend for this document also to point out these gaps, or do you intend =
for this to be dealing with the network layer gaps only?

Best regards,
Ole




> On 15 Jan 2015, at 22:02 , Behcet Sarikaya <sarikaya2012@gmail.com> =
wrote:
>=20
> Hi all,
>=20
> Based on latest comments received, we revised the draft as follows.
> Please check.
>=20
> Regards,
>=20
> Behcet
>=20
>=20
> A new version of I-D, draft-sarikaya-6man-sadr-overview-04.txt
> has been successfully submitted by Behcet Sarikaya and posted to the
> IETF repository.
>=20
> Name:           draft-sarikaya-6man-sadr-overview
> Revision:       04
> Title:          Source Address Dependent Routing and Source Address
> Selection for IPv6 Hosts
> Document date:  2015-01-15
> Group:          Individual Submission
> Pages:          15
> URL:
> =
http://www.ietf.org/internet-drafts/draft-sarikaya-6man-sadr-overview-04.t=
xt
> Status:
> https://datatracker.ietf.org/doc/draft-sarikaya-6man-sadr-overview/
> Htmlized:       =
http://tools.ietf.org/html/draft-sarikaya-6man-sadr-overview-04
> Diff:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-sarikaya-6man-sadr-overview-04
>=20
> Abstract:
>   This document presents the source address dependent routing from the
>   host perspective.  Multihomed hosts and hosts with multiple
>   interfaces are considered.  Different architectures are introduced
>   and with their help, why source address selection and next hop
>   resolution in view of source address dependent routing is needed is
>   explained.  The document concludes with an informative guidelines on
>   the different solution approaches.
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of =
submission
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> The IETF Secretariat
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Mon Jan 19 11:59:50 2015
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA0161B2C30 for <ipv6@ietfa.amsl.com>; Mon, 19 Jan 2015 11:59:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KJfKwHFT4pDT for <ipv6@ietfa.amsl.com>; Mon, 19 Jan 2015 11:59:43 -0800 (PST)
Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C21F1B2C14 for <ipv6@ietf.org>; Mon, 19 Jan 2015 11:59:43 -0800 (PST)
Received: by mail-la0-f42.google.com with SMTP id ms9so8486690lab.1 for <ipv6@ietf.org>; Mon, 19 Jan 2015 11:59:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=v6NG046C0lRkJk8n8rNo7nCvxQpXXuWJY3jXE/kC/IM=; b=Kw/9actUTQI4M763LWJ+cdFE7NntWPn7bhnQTRWA6POZg48rD2CikHc7gnDXXvYDUt x3QcY9wcQptZi6wbL+JmcygTXIKmdG7kopcDwcyn+XICghOKYB5XGFrC1rjbkuir3m9r cRm/1haZXYINyD5J06KmrZalbXS5bIOQ1uckKGE6aK8mJlAIRC/aS6b6h14DaYtYYD7X KoELi7bfefBy9nl6a6mK1UWanNd1HW//VfqfJpDaogv/8BCNw9DSNDTBc+KRQvKgLt3Z u2DTuiEN8TkRqEArGcnqq9RyKerSg/WR+7MF7PAiwmERZw+/HjdZGcisqC0y+TX3zFD6 VkhQ==
MIME-Version: 1.0
X-Received: by 10.152.42.198 with SMTP id q6mr32936214lal.48.1421697581435; Mon, 19 Jan 2015 11:59:41 -0800 (PST)
Received: by 10.114.63.51 with HTTP; Mon, 19 Jan 2015 11:59:41 -0800 (PST)
In-Reply-To: <50578ECA-9DC0-4FBF-98B3-1B7149E34392@cisco.com>
References: <CAC8QAcfqZJ_z1LETybp6tx057eTLe9wQoaXfmagzBh82AStfHg@mail.gmail.com> <50578ECA-9DC0-4FBF-98B3-1B7149E34392@cisco.com>
Date: Mon, 19 Jan 2015 13:59:41 -0600
Message-ID: <CAC8QAcd9PJ9Q5pTWC6hSw1ixpx8vN5ibfLCnuHAnoXv4xtN4vw@mail.gmail.com>
Subject: Re: New Version Notification for draft-sarikaya-6man-sadr-overview-04.txt
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Ole Troan <ot@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/9mdbi3ZdiEEU9rVzboFJax2Ffpo>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jan 2015 19:59:46 -0000

 Hi Ole,

On Fri, Jan 16, 2015 at 3:13 AM, Ole Troan <ot@cisco.com> wrote:
> Behcet,
>
> a few comments if I may.

Sure.

>
> with regards to section 5.1 and rule 5.5 from rfc6724:
> you state that rule 5.5. solves the scenarios in figure 1, 2 and 3. I wou=
ld rather say that a strong ES model would solve those. rule 5.5. solves th=
e scenario in figure 4.
>

This seems to contradict what you said in your mail:
http://www.ietf.org/mail-archive/web/ipv6/current/msg21639.html

to Pierre.

You said
Rule 5.5 and strict (or strong) host model.

Strong end system defined in RFC 1122 and Rule 5.5 are not the same
thing as you have alluded to in your mail above. Strong ES model is
saying that any multihomed host is a set of logical hosts.


As to Fig. 4 or Scenario 4, I have added this scenario based on Pierre
suggestion, it (this home networking scenario) was described in his
mail. Also in your mail referenced above you said that this case makes
sense.

Scenarios 1,2 and 3 are showing multihomed host (Scenario 2) or
multiple interfaced host (scenarios 1 and 3) cases. These are the
scenarios you need SADR at the host.
BTW I noticed that I put multihomed in all three figure captions by
mistake, I will correct it in the next rev. But the text is clear, I
think.

> you also reference rfc7078 in section 5.1. 7078 does not have any means t=
o configure rule 5.5 on a host, if that was what you tried to imply (I migh=
t have misread you here though).
>

Have you read RFC 7078?
Here is what the abstract says:

RFC 6724 defines default address selection mechanisms for IPv6 that
   allow nodes to select an appropriate address when faced with multiple
   source and/or destination addresses to choose between.  RFC 6724
   allows for the future definition of methods to administratively
   configure the address selection policy information.  This document
   defines a new DHCPv6 option for such configuration,


and that's what I am saying in Section 5.1. Is there any issue with this?

> given that, I still don't understand the need for section 5.2 and a new r=
outer advertisement option.
>

Please see the above comments. Section 5.2 is the solution that Pierre
suggested to Scenario 4.

> a minor point on section 4.2 and provisioning domains. in any multi-homed=
 network, I think it is a policy choice if the "external" provisioning doma=
ins are presented to the host or if the network presents itself as a single=
 provisioning domain. i.e. the network "merges" the information.
>

I can add a sentence to this effect to Section 4.2, thanks.

> in section 5.4 you mention other solutions and probing as a possibility. =
if we go back to the multi-homing requirements from rfc3582, there are stil=
l many gaps with multi-prefix multi-homing. as far as I can see those gaps =
need to be closed by changes at the transport layer, a new intermediate lay=
er (aka session) or in the application layer. do you intend for this docume=
nt also to point out these gaps, or do you intend for this to be dealing wi=
th the network layer gaps only?
>

In the draft on
Experience with IPv6 path probing,

two models have been investigated, one is network layer or REAP and
the other is transport layer or MPTCP.

No, I do not intend to elaborate IPv6 probing and solutions in this
document any further than Section 5.4 because the document
concentrates on host based approaches.

Regards,

Behcet

> Best regards,
> Ole
>
>
>
>
>> On 15 Jan 2015, at 22:02 , Behcet Sarikaya <sarikaya2012@gmail.com> wrot=
e:
>>
>> Hi all,
>>
>> Based on latest comments received, we revised the draft as follows.
>> Please check.
>>
>> Regards,
>>
>> Behcet
>>
>>
>> A new version of I-D, draft-sarikaya-6man-sadr-overview-04.txt
>> has been successfully submitted by Behcet Sarikaya and posted to the
>> IETF repository.
>>
>> Name:           draft-sarikaya-6man-sadr-overview
>> Revision:       04
>> Title:          Source Address Dependent Routing and Source Address
>> Selection for IPv6 Hosts
>> Document date:  2015-01-15
>> Group:          Individual Submission
>> Pages:          15
>> URL:
>> http://www.ietf.org/internet-drafts/draft-sarikaya-6man-sadr-overview-04=
.txt
>> Status:
>> https://datatracker.ietf.org/doc/draft-sarikaya-6man-sadr-overview/
>> Htmlized:       http://tools.ietf.org/html/draft-sarikaya-6man-sadr-over=
view-04
>> Diff:
>> http://www.ietf.org/rfcdiff?url2=3Ddraft-sarikaya-6man-sadr-overview-04
>>
>> Abstract:
>>   This document presents the source address dependent routing from the
>>   host perspective.  Multihomed hosts and hosts with multiple
>>   interfaces are considered.  Different architectures are introduced
>>   and with their help, why source address selection and next hop
>>   resolution in view of source address dependent routing is needed is
>>   explained.  The document concludes with an informative guidelines on
>>   the different solution approaches.
>>
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of submis=
sion
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>


From nobody Tue Jan 20 05:43:22 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0D951B2A49 for <ipv6@ietfa.amsl.com>; Tue, 20 Jan 2015 05:43:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DthwOtc12fWV; Tue, 20 Jan 2015 05:43:18 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C471A1AD1C3; Tue, 20 Jan 2015 05:43:18 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: 6man-chairs@tools.ietf.org, ot@cisco.com, draft-ietf-6man-enhanced-dad.all@tools.ietf.org, ipv6@ietf.org
Subject: ID Tracker State Update Notice: <draft-ietf-6man-enhanced-dad-12.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150120134318.25873.13162.idtracker@ietfa.amsl.com>
Date: Tue, 20 Jan 2015 05:43:18 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/yKtzCHZbYaAFpTmiVz9NXUjBymM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jan 2015 13:43:20 -0000

IESG state changed to Last Call Requested from AD Evaluation::AD Followup
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-dad/


From nobody Tue Jan 20 05:44:39 2015
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2276A1B2A18 for <ipv6@ietfa.amsl.com>; Tue, 20 Jan 2015 05:44:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id amoPTggWaeKv for <ipv6@ietfa.amsl.com>; Tue, 20 Jan 2015 05:44:37 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01A791B2A4A for <ipv6@ietf.org>; Tue, 20 Jan 2015 05:44:37 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id DE95288119; Tue, 20 Jan 2015 05:44:36 -0800 (PST)
Received: from clemson.local (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 6C8F371C0002; Tue, 20 Jan 2015 05:44:36 -0800 (PST)
Message-ID: <54BE5BBD.6000902@innovationslab.net>
Date: Tue, 20 Jan 2015 08:44:29 -0500
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: 6man-chairs@tools.ietf.org,  draft-ietf-6man-enhanced-dad.all@tools.ietf.org, ipv6@ietf.org
Subject: Re: New Version Notification - draft-ietf-6man-enhanced-dad-12.txt
References: <20150114235150.26494.73888.idtracker@ietfa.amsl.com>
In-Reply-To: <20150114235150.26494.73888.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="vAVs5tE2eMQATnx3BgNN8vg4BeDEpaJkr"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/6sPgt2ZfhJ8qO9YQoR82mn33HFc>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jan 2015 13:44:38 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--vAVs5tE2eMQATnx3BgNN8vg4BeDEpaJkr
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

All,
     I have started the IETF Last Call process for this draft.

Regards,
Brian


On 1/14/15 6:51 PM, internet-drafts@ietf.org wrote:
>=20
> A new version (-12) has been submitted for draft-ietf-6man-enhanced-dad=
:
> http://www.ietf.org/internet-drafts/draft-ietf-6man-enhanced-dad-12.txt=

>=20
>=20
> The IETF datatracker page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-dad/
>=20
> Diff from previous version:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-enhanced-dad-12
>=20
> Please note that it may take a couple of minutes from the time of submi=
ssion
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> IETF Secretariat.
>=20


--vAVs5tE2eMQATnx3BgNN8vg4BeDEpaJkr
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.20 (Darwin)
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJUvlvDAAoJEBOZRqCi7goqOysIAKFU5kjeSHPmmryie40DMU5j
qz12pkwH+6Q32O3NpA8ZhK1KbstlnTMFA7jaDN708yn8ax0gwthYdXDoT96zzu71
bJYefAEUbnZRNvZhrfVBh22DvyqhxDeWZKedZd5cq3moNbRkDJOPF7tvJOaklktV
FaF/Y/FqrcByKCw8F+2nGv3HqYjQDysqQcLc2DfQRxlgSbWIxHljuJv2bNrHebor
fAyiSwoUEaQKQ4lToW+Ff4Fi+57AbNsU9OqVeLKWT6TejjCj7P+OYXtFIfgj9Wvm
QeDJ3jqs+lRL2wA1RM4hHMC0q3sNFtTJxDTxWE4BT7gmhXjYQSsRKnE12xAv8VE=
=3KyD
-----END PGP SIGNATURE-----

--vAVs5tE2eMQATnx3BgNN8vg4BeDEpaJkr--


From nobody Tue Jan 20 06:57:38 2015
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCEA61B2A88; Tue, 20 Jan 2015 06:57:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uIjxMAHrg5lJ; Tue, 20 Jan 2015 06:57:35 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 31A711B2DB6; Tue, 20 Jan 2015 06:57:35 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-6man-enhanced-dad-12.txt> (Enhanced Duplicate Address Detection) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Sender: <iesg-secretary@ietf.org>
Message-ID: <20150120145735.11874.30201.idtracker@ietfa.amsl.com>
Date: Tue, 20 Jan 2015 06:57:35 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/WQYFfJneKFplhVGljZFXXWDzYEI>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jan 2015 14:57:36 -0000

The IESG has received a request from the IPv6 Maintenance WG (6man) to
consider the following document:
- 'Enhanced Duplicate Address Detection'
  <draft-ietf-6man-enhanced-dad-12.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2015-02-03. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   IPv6 Loopback Suppression and Duplicate Address Detection (DAD) are
   discussed in Appendix A of RFC4862.  That specification mentions a
   hardware-assisted mechanism to detect looped back DAD messages.  If
   hardware cannot suppress looped back DAD messages, a software
   solution is required.  Several service provider communities have
   expressed a need for automated detection of looped back Neighbor
   Discovery (ND) messages used by DAD.  This document includes
   mitigation techniques and outlines the Enhanced DAD algorithm to
   automate the detection of looped back IPv6 ND messages used by DAD.
   For network loopback tests, the Enhanced DAD algorithm allows IPv6 to
   self-heal after a loopback is placed and removed.  Further, for
   certain access networks the document automates resolving a specific
   duplicate address conflict.  This document updates RFC4861, RFC4862,
   and RFC4429.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-dad/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-dad/ballot/


No IPR declarations have been submitted directly on this I-D.



From nobody Tue Jan 20 06:57:42 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6980C1B2DCA for <ipv6@ietfa.amsl.com>; Tue, 20 Jan 2015 06:57:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ea0_CpxrnGDw; Tue, 20 Jan 2015 06:57:38 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1108E1B2A88; Tue, 20 Jan 2015 06:57:37 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: 6man-chairs@tools.ietf.org, ot@cisco.com, draft-ietf-6man-enhanced-dad.all@tools.ietf.org, ipv6@ietf.org
Subject: ID Tracker State Update Notice: <draft-ietf-6man-enhanced-dad-12.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150120145737.11874.50237.idtracker@ietfa.amsl.com>
Date: Tue, 20 Jan 2015 06:57:37 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/1YXswyV2iAR7y9SiiobAvfFL7x8>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jan 2015 14:57:39 -0000

Last call has been made for draft-ietf-6man-enhanced-dad and state has been changed to In Last Call
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-dad/


From nobody Wed Jan 21 13:42:57 2015
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70B8B1A88F7 for <ipv6@ietfa.amsl.com>; Wed, 21 Jan 2015 13:42:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QrLxSCyUguwk for <ipv6@ietfa.amsl.com>; Wed, 21 Jan 2015 13:42:54 -0800 (PST)
Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F04E81A0018 for <6man@ietf.org>; Wed, 21 Jan 2015 13:42:53 -0800 (PST)
Received: by mail-la0-f48.google.com with SMTP id pv20so111141lab.7 for <6man@ietf.org>; Wed, 21 Jan 2015 13:42:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:date:message-id:subject:from:to:content-type;  bh=Z7Txdwtdz5I7T1ZGixrxycNI6LNnRJGbacY+V2u38fY=; b=SxwEYtB54Up9CkESo3kzs/kuZ2h6jAqNXGjJzdROgLKCITDJSCoejQQyOzKfs09OX5 GmZhH0QHiJM5Q4dghE7CnWQ+ZpYrHTYyE5IICn3ynL4P7IdVIpk+2PI/e3OQhKwdZD6Q czUlAGaXQhaUmexquXTeXdFAP6M2LzMEyaeDYLN1MpAk0KSkZ8MRA6vnQALvthJudLwk PHyiUqKCR/s7JLZ8JUnYG4vAgCvE96O+HGqWPXAmGP2gfjG/3ZWd+Ye4RtXpRXatm9Bd y633IBj1MOH+Y32x7Ii9GW+nPIsBe8tSAhTthhS2zf3OYKbmo0c7JR1JH7pGdlEoOx5l ZLng==
MIME-Version: 1.0
X-Received: by 10.112.8.69 with SMTP id p5mr46341506lba.97.1421876572503; Wed, 21 Jan 2015 13:42:52 -0800 (PST)
Received: by 10.114.63.51 with HTTP; Wed, 21 Jan 2015 13:42:52 -0800 (PST)
Date: Wed, 21 Jan 2015 15:42:52 -0600
Message-ID: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com>
Subject: Source Address Dependent Routing and Source Address Selection for IPv6
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: "6man@ietf.org" <6man@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/yE0FpSQEOUY92GB99VTjVP6Tlf0>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Jan 2015 21:42:55 -0000

 Hi all,

On the solutions to the problem and issues discussed in this draft:
http://tools.ietf.org/id/draft-sarikaya-6man-sadr-overview-04.txt

we would like to hear from the working group. Referring to Section 5,
which solution approach WG prefers? RA options as in Section 5.2?
Section 5.3?
Also regarding the corresponding DHCP work, which direction is the
preferred direction?

Your opinions are welcome.

Regards,

Behcet


From nobody Wed Jan 21 16:44:38 2015
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B95851A8ADC for <ipv6@ietfa.amsl.com>; Wed, 21 Jan 2015 16:44:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.202
X-Spam-Level: **
X-Spam-Status: No, score=2.202 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vkng10hpij0E for <ipv6@ietfa.amsl.com>; Wed, 21 Jan 2015 16:44:35 -0800 (PST)
Received: from nm48.bullet.mail.bf1.yahoo.com (nm48.bullet.mail.bf1.yahoo.com [216.109.114.64]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93F451A8713 for <6man@ietf.org>; Wed, 21 Jan 2015 16:44:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s2048;  t=1421887474; bh=pXrwWprxhqM1NaeKveDJtJeorKt+cbZXbsEvORJngMw=;  h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject;  b=eygNQHoRa0y+kDcWrmN/hXLH2x5KG15RMMqGHTHBwTEp/LsNtMR2nH6DSNb/TZLmqw98rOTZ9bSoUAUtBpKPFQzC57J+fnWYlS6WbTyJIf73x5CUlpd1nGubijNaR8OS4REinIN7q5ddq4C9XaT2Bh7beIb35W8OJh46wi+vRKbWU2yio9nNvcRXnORJ4iCt7+APcNUfa6Hdg9I8mzpqQ/6O5nfJ+b9lRm9RlT4YOttrN3nzkfc0ETIhBQ3wzr/+VUNFH66y3eQoyIKPIH1w6aEN8dwERX5nVAVvn5xDO9anPf4Opu6TlqKJ/W8mZfI+9F2RysdMIF5YxSlrzjL1FA==
Received: from [98.139.212.151] by nm48.bullet.mail.bf1.yahoo.com with NNFMP;  22 Jan 2015 00:44:34 -0000
Received: from [98.139.212.208] by tm8.bullet.mail.bf1.yahoo.com with NNFMP; 22 Jan 2015 00:44:34 -0000
Received: from [127.0.0.1] by omp1017.mail.bf1.yahoo.com with NNFMP; 22 Jan 2015 00:44:34 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 653282.98496.bm@omp1017.mail.bf1.yahoo.com
X-YMail-OSG: W6MjHj8VM1m71MsBMRam98RYHvRnfdKqZLxoUSDWyjmlZfvRZEDrZGNUfTYUrPV Ek4MwoH3ETboFOqCm.AC8H6t4LSBdO5NuNAqR2RcxVIrw8RsxaZWzb5mCoHIMAl6Ti5jhQYMMIOZ Lp.0dTmf6P5nbFN6hWYxdRjHTy.ZAj3XDGAGGMiJf19GTdW4ejjEoS9OXha0aYFniQCFaEKu.lmX d2bnSxMzi2m2l6lXrJ2yIMx7OZY.74ia3CCHWQ0upgnQfmeHPNDWPd5_u1T1jbF.RWjkvEnwDsUu Kv8W3gzvPy43shruYtNZbm8t9ys_pIOosdyR_GNspnPh47aEnwzWf14lYfh5Bj8.WTa89gQJP82l rXnIrd2jPkIwPqcxgJFgfAJEVb1Cq7_bDgFCdY956Kuq_J93BnuHqyKJBx.Q_vVcUolOSMXQPLjR 9rE7po5KER5nduFe5C1adX4XoVkazsgITUNutHO8Cmq7WlBVrGEL7cNk3fTsMG2RSB0H3v2E1sfN F20WVBYQaoMM1hQ--
Received: by 76.13.26.108; Thu, 22 Jan 2015 00:44:34 +0000 
Date: Thu, 22 Jan 2015 00:44:32 +0000 (UTC)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
To: "sarikaya@ieee.org" <sarikaya@ieee.org>, "6man@ietf.org" <6man@ietf.org>
Message-ID: <212072260.1230054.1421887472454.JavaMail.yahoo@jws10663.mail.bf1.yahoo.com>
In-Reply-To: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/YvyaFEqRxHWzBrZNAf8_yDb0Lto>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2015 00:44:36 -0000

I think the principles described in RFC5505 are worth following:

"Principles of Internet Host Configuration"
https://tools.ietf.org/html/rfc5505#section-2


More options to configure and more methods to choose from just make things harder to make work and make them break more often.




----- Original Message -----
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: "6man@ietf.org" <6man@ietf.org>
Cc: 
Sent: Thursday, 22 January 2015, 8:42
Subject: Source Address Dependent Routing and Source Address Selection for IPv6

Hi all,

On the solutions to the problem and issues discussed in this draft:
http://tools.ietf.org/id/draft-sarikaya-6man-sadr-overview-04.txt

we would like to hear from the working group. Referring to Section 5,
which solution approach WG prefers? RA options as in Section 5.2?
Section 5.3?
Also regarding the corresponding DHCP work, which direction is the
preferred direction?

Your opinions are welcome.

Regards,

Behcet

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


From nobody Wed Jan 21 18:13:44 2015
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 566321A00DF for <ipv6@ietfa.amsl.com>; Wed, 21 Jan 2015 18:13:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nv1Y3uV0uXeu for <ipv6@ietfa.amsl.com>; Wed, 21 Jan 2015 18:13:40 -0800 (PST)
Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93F9F1A007C for <6man@ietf.org>; Wed, 21 Jan 2015 18:13:40 -0800 (PST)
Received: by mail-ie0-f171.google.com with SMTP id tr6so15518108ieb.2 for <6man@ietf.org>; Wed, 21 Jan 2015 18:13:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=MRZO0Ih+aRrNM2Noj4MOeMrgXSFhTt95ZzrXVksmeXE=; b=aBQfmSik8qT0LcBFXSwVrSu6foLYm000bVqNtJq/t35tGJ6YcZKqH4kty+yu8j7oNu QdSblAi3e76c0EEO6ur37G37dJIHojy1/M8Z86AQL5TyjDLD1+MCGykCUj3/zXfJDRJj seLONtPf6tVehT1J4lhFchieuSxf+ICWTN8Xv4udL8T9ap7GFN8mj3QMBvtWThxUcnKl NBjjgcp7Ook2IXbpMvlJyiK2Xavxrg73rQ+SzmJffu2ze38hGTUBpt/IIGxVdWhDCC9d qjGHU0+PQyMe8bE4nvA81z7qJSLSQIqc1SAhL5EL5whHiJrRk3VNd/aIkO2tkhOUB5GV gLFQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=MRZO0Ih+aRrNM2Noj4MOeMrgXSFhTt95ZzrXVksmeXE=; b=fx5UnHh3Wc8uyVgcivxVnEMuly+XBYS4jxrpIHJ8ZpvxovBNjPec/5lVS0UPJtECwJ GQTekmxo/eT2eImophVbAq4iGhgWgztiqekKs0CYvl0ZR+c7YGpcwAqLf2AJ1NGveXTZ H2OH28Q7a12uWmMwr5qDRKbRKFDj8/weA4jb+2eVRTV3hOP1HCE7No0tdrLS0ey5ZHcU jffpSiTZQ8YWXtqChdas+45gw1EqjUI/HHFxRwJVuq4N7EQKriE79gM+tfvkOZ3rI6Gl sbsxl3NERGHkk68h44o/wPRBsClHcBgHPZZR5wFriMt9+GR2e4ax90LzwLtxHaqi40n6 n53A==
X-Gm-Message-State: ALoCoQmJixsAqorKk3TDneAVClGLppJYVMVvqzlMl/YfwtvK6zgNI+oijrd7ZOO8mM0fh2l6bjPy
X-Received: by 10.50.66.131 with SMTP id f3mr9013895igt.7.1421892819741; Wed, 21 Jan 2015 18:13:39 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.93.102 with HTTP; Wed, 21 Jan 2015 18:13:19 -0800 (PST)
In-Reply-To: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 22 Jan 2015 11:13:19 +0900
Message-ID: <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
To: Behcet Sarikaya <sarikaya@ieee.org>
Content-Type: multipart/alternative; boundary=047d7bdc07a26e10bc050d343834
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/oZJcDkMYR-Wb83FOZdLCBfjnPfc>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2015 02:13:42 -0000

--047d7bdc07a26e10bc050d343834
Content-Type: text/plain; charset=UTF-8

On Thu, Jan 22, 2015 at 6:42 AM, Behcet Sarikaya <sarikaya2012@gmail.com>
wrote:

> Referring to Section 5,
> which solution approach WG prefers? RA options as in Section 5.2?
> Section 5.3?
>

I feel strongly that configuration option that allows a router to specify
another on-link next hop (or, even worse, a next hop on another interface)
is a bad idea because it breaks the fate-sharing properties provided by RAs.

If all that is necessary is a means to tell the host what source address to
prefer for what prefixes, then we already have a DHCP option for that.

Looking at the scenarios, I don't see anything that requires any new work
to solve.

Figure 1:
Case 1: rtr1 and rtr2 are connected to different interfaces on the host
(e.g., wifi and 3G), This is solved by rule 5 in RFC 6724.
Case 2: rtr1 and rtr2 are connected to the same interface on the host. This
is solved by SADR forwarding between rtr1 and rtr2 with no host changes.

Figure 2: solved by implementing SADR in the router. The router already has
the information it needs. In the case of specialized address routing,
that's solved using the DHCPv6 address selection policy option (RFC 7078).

Figure 3: Same as case 2 in Figure 1; solved by rule 5 in RFC 6724.

Figure 4: Same as case 1 in Figure 1; solved by SADR forwarding between
rtr1 and rtr2. Better performance if the host implements rule 5.5 in RFC
6724.

Figure 5: Solved by SADR forwarding between rtr, rtrE and rtrF.

--047d7bdc07a26e10bc050d343834
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Jan 22, 2015 at 6:42 AM, Behcet Sarikaya <span dir=3D"ltr">&lt;<a href=
=3D"mailto:sarikaya2012@gmail.com" target=3D"_blank">sarikaya2012@gmail.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204)=
;border-left-style:solid;padding-left:1ex">Referring to Section 5,<br>
which solution approach WG prefers? RA options as in Section 5.2?<br>
Section 5.3?<br></blockquote><div><br></div><div>I feel strongly that confi=
guration option that allows a router to specify another on-link next hop (o=
r, even worse, a next hop on another interface) is a bad idea because it br=
eaks the fate-sharing properties provided by RAs.</div><div><br></div><div>=
If all that is necessary is a means to tell the host what source address to=
 prefer for what prefixes, then we already have a DHCP option for that.</di=
v><div><br></div><div>Looking at the scenarios, I don&#39;t see anything th=
at requires any new work to solve.</div><div><br></div><div>Figure 1:</div>=
<div>Case 1: rtr1 and rtr2 are connected to different interfaces on the hos=
t (e.g., wifi and 3G), This is solved by rule 5 in RFC 6724.</div><div>Case=
 2: rtr1 and rtr2 are connected to the same interface on the host. This is =
solved by SADR forwarding between rtr1 and rtr2 with no host changes.</div>=
<div><br></div><div>Figure 2: solved by implementing SADR in the router. Th=
e router already has the information it needs. In the case of specialized a=
ddress routing, that&#39;s solved using the DHCPv6 address selection policy=
 option (RFC 7078).=C2=A0</div><div><br></div><div>Figure 3: Same as case 2=
 in Figure 1; solved by rule 5 in RFC 6724.</div><div><br></div><div>Figure=
 4: Same as case 1 in Figure 1; solved by SADR forwarding between rtr1 and =
rtr2. Better performance if the host implements rule 5.5 in RFC 6724.</div>=
<div><br></div><div>Figure 5: Solved by SADR forwarding between rtr, rtrE a=
nd rtrF.</div></div></div></div>

--047d7bdc07a26e10bc050d343834--


From nobody Thu Jan 22 00:38:33 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D24F61A03AB for <ipv6@ietfa.amsl.com>; Thu, 22 Jan 2015 00:38:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l3H-q5lxDygz for <ipv6@ietfa.amsl.com>; Thu, 22 Jan 2015 00:38:26 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6D4D1A01D8 for <6man@ietf.org>; Thu, 22 Jan 2015 00:38:26 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 5089A6161; Thu, 22 Jan 2015 00:38:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=3+LW1jzCAYM2217X9qAy6+5yI6E=; b=kOszKrSkUIQczlsCMv Fyi2moBKNaYX5mOYrC5Lc8mVz6ILmJmCTHqFujvKulK4+p3oYPHpPvhU44gPwuUw zs4YzYH8b4jwNnzDwsBYmcQBRBefjxISPZy5sUNsVqKvdhAewrPYtg1ZOPPkRSjZ aE9i1tK42QnKybpHLPVA5Hh+U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=jHWdkRyR1bQReG7n94yuLOubc+9FtaFJewGDjPkKgEVzJWmHu7h naBCnaugefSGdXyfGWmYgu2tzNDhrzgeVDWg2ZrwC27Msd2aH/7VWaonByCFOrn9 4LGY7SATxhoo9tMSehVM9Xdm4Wn3ku5kWxmLyljcV2YXl69aWFGzchaA=
Received: from gomlefisk.localdomain (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id E595A613E; Thu, 22 Jan 2015 00:38:25 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 7A7603D16AED; Thu, 22 Jan 2015 09:38:23 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.1\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com>
Date: Thu, 22 Jan 2015 09:38:23 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DC23461A-8AF8-4704-9604-9E88A5B48298@employees.org>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com>
To: sarikaya@ieee.org
X-Mailer: Apple Mail (2.2070.1)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/bhFLDcemLVmw5IjlGoCbGM2KW-8>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2015 08:38:32 -0000

Behcet,

> On the solutions to the problem and issues discussed in this draft:
> http://tools.ietf.org/id/draft-sarikaya-6man-sadr-overview-04.txt
>=20
> we would like to hear from the working group. Referring to Section 5,
> which solution approach WG prefers? RA options as in Section 5.2?
> Section 5.3?
> Also regarding the corresponding DHCP work, which direction is the
> preferred direction?

I'm still not convinced that any specific configuration for source based =
next-hop determination is needed.
until then my preferred direction is to do none of these.

can you please explain in excruciating detail in which case these =
configuration options (including 3rd party nexthop)  are required?

Best regards,
Ole=


From SRS0=Uuzw=CJ=darou.fr=pierre.pfister@bounces.m4x.org  Thu Jan 22 01:30:43 2015
Return-Path: <SRS0=Uuzw=CJ=darou.fr=pierre.pfister@bounces.m4x.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 955DB1A064C for <ipv6@ietfa.amsl.com>; Thu, 22 Jan 2015 01:30:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kr-S4-fBuAr1 for <ipv6@ietfa.amsl.com>; Thu, 22 Jan 2015 01:30:40 -0800 (PST)
Received: from mx1.polytechnique.org (mx1.polytechnique.org [129.104.30.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 370A31A049A for <6man@ietf.org>; Thu, 22 Jan 2015 01:30:40 -0800 (PST)
Received: from [10.148.10.54] (173-38-208-170.cisco.com [173.38.208.170]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ssl.polytechnique.org (Postfix) with ESMTPSA id 0EEFB1408EEE1; Thu, 22 Jan 2015 10:30:35 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com>
Date: Thu, 22 Jan 2015 10:30:34 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1878.6)
X-AV-Checked: ClamAV using ClamSMTP at svoboda.polytechnique.org (Thu Jan 22 10:30:36 2015 +0100 (CET))
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/0MtKQl65ZAeHRkiE7Zccu8y1r14>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2015 09:31:23 -0000

Hello Lorenzo, Ole and Behcet,

>=20
> I feel strongly that configuration option that allows a router to =
specify another on-link next hop (or, even worse, a next hop on another =
interface) is a bad idea because it breaks the fate-sharing properties =
provided by RAs.
>=20

I fully agree there. If another router should be next-hop, then that =
other router can send RAs by itself.

> If all that is necessary is a means to tell the host what source =
address to prefer for what prefixes, then we already have a DHCP option =
for that.
>=20
> Looking at the scenarios, I don't see anything that requires any new =
work to solve.
>=20
> Figure 1:
> Case 1: rtr1 and rtr2 are connected to different interfaces on the =
host (e.g., wifi and 3G), This is solved by rule 5 in RFC 6724.
> Case 2: rtr1 and rtr2 are connected to the same interface on the host. =
This is solved by SADR forwarding between rtr1 and rtr2 with no host =
changes.

Yes, but if we rely on routers=92 capabilities only, we will have =
suboptimal routing. e.g., the next-hop will send the packet back on the =
same link. Which would halve the throughput.
And if we rely on redirects, well=85 Redirects are not source-specific, =
so we may have redirect ping-pongs between the two routers.

>=20
> Figure 2: solved by implementing SADR in the router. The router =
already has the information it needs. In the case of specialized address =
routing, that's solved using the DHCPv6 address selection policy option =
(RFC 7078).=20
>=20
> Figure 3: Same as case 2 in Figure 1; solved by rule 5 in RFC 6724.
>=20
> Figure 4: Same as case 1 in Figure 1; solved by SADR forwarding =
between rtr1 and rtr2. Better performance if the host implements rule =
5.5 in RFC 6724.
>=20
> Figure 5: Solved by SADR forwarding between rtr, rtrE and rtrF.


Something bugs me in general with the source address selection process.

If we assume the host is dumb, it will first select the next-hop/oif and =
pick the source address using rule 5 or rule 5.5.
If we assume the host is clever, it will first select the source-address =
based on the information it has (e.g., DHCPv6 address selection). But =
how is it supposed to select the next-hop then ? rule 5 and 5.5 solve =
source address selection when you know the next hop, but not next-hop =
selection when you know the source address.

In other words, when you say DHCPv6 address selection policy solves the =
issue, you say the host should select the address based on =
configuration, which implies that you do that before you pick the next =
hop.
But when you say rule 5 or 5.5 solve the issue, you assume the next-hop =
has already been selected. So, picking each figure and propose different =
solutions which seems to exclude each other seems unfair to me.

Source address selection by the host/application is, IMHO, the simplest =
approach to upstream selection, as it reduces interface/next-hop/cpe =
selection to the selection of a single element. Homenet is moving toward =
this kind of solutions. But once the application or host has chosen the =
source address, we need some process to select the next hop.

When I ask myself =91where should we pick the next-hop=92=85 The routing =
table seems to be the answer. And if we consider we want different next =
hops depending on the source address, source-dest routing looks like the =
right thing to do to me.=20

Now, either we require hosts to look at PIOs and always add =
source-routes based on the RAs they receive (which means the router =
hides things to the host and the host hacks a solution to deal with it - =
and it may not always work), or we provide a longer-term solution where =
routers tell the truth to hosts.

I disagree with the overall approach of this draft. I think what we need =
is a source-specific extension to RFC4191. With only one single new =
option similar to RIOs but with a source-prefix included.

Cheers,

- Pierre





From nobody Thu Jan 22 04:30:26 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3978E1ACC8F for <ipv6@ietfa.amsl.com>; Thu, 22 Jan 2015 04:30:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IEJbazyZxGr0 for <ipv6@ietfa.amsl.com>; Thu, 22 Jan 2015 04:30:21 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37EBD1ACC85 for <6man@ietf.org>; Thu, 22 Jan 2015 04:30:21 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 723AD62AD; Thu, 22 Jan 2015 04:30:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=7VZMZyYPQtEg3jknbN3BP8+xi+g=; b=sbETJTJUuiCNMR/OKl /irpU7CAXXxA7R6/QfjjrWp42SIPDU9qLsBVQ6h1lXnljrBfoQvD8BDP7gdMucXV 7pD4Aw7NP2mCEFAXIrmQSgKW4Aa9X1WTU9+dF3pyrmVEkZMc/O+3ps3Qa9uc0gUJ /6tqNPDLQAhbytZbXiZCW3LEY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=jTW5FG92gkq/SbWYFmSPeR+k6lsisF+LcciVqRZp/rJNuquqCdI MRG7zFsUNmBE1HEfPGVadYZ63LthC2l6Qmdj6xvaVUnKsWLH3hMTxdZWThCNVNTI 5mkOZIUDK3FQZBsPSamKNj87ScgCY5kXoM+IIbKn+0kgHHOzP8k3tj/M=
Received: from gomlefisk.localdomain (173-38-208-170.cisco.com [173.38.208.170]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id DE0BC62A8; Thu, 22 Jan 2015 04:30:18 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 492953D2538E; Thu, 22 Jan 2015 13:30:16 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.1\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr>
Date: Thu, 22 Jan 2015 13:30:15 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <7DC0A974-1D69-41A0-A23E-D8F60D0780B5@employees.org>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr>
To: Pierre Pfister <pierre.pfister@darou.fr>
X-Mailer: Apple Mail (2.2070.1)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/iYqOBXtm0yN2kDYn7rLJ3yT38Ik>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2015 12:30:23 -0000

Pierre,

>> I feel strongly that configuration option that allows a router to =
specify another on-link next hop (or, even worse, a next hop on another =
interface) is a bad idea because it breaks the fate-sharing properties =
provided by RAs.
>>=20
>=20
> I fully agree there. If another router should be next-hop, then that =
other router can send RAs by itself.
>=20
>> If all that is necessary is a means to tell the host what source =
address to prefer for what prefixes, then we already have a DHCP option =
for that.
>>=20
>> Looking at the scenarios, I don't see anything that requires any new =
work to solve.
>>=20
>> Figure 1:
>> Case 1: rtr1 and rtr2 are connected to different interfaces on the =
host (e.g., wifi and 3G), This is solved by rule 5 in RFC 6724.
>> Case 2: rtr1 and rtr2 are connected to the same interface on the =
host. This is solved by SADR forwarding between rtr1 and rtr2 with no =
host changes.
>=20
> Yes, but if we rely on routers=92 capabilities only, we will have =
suboptimal routing. e.g., the next-hop will send the packet back on the =
same link. Which would halve the throughput.
> And if we rely on redirects, well=85 Redirects are not =
source-specific, so we may have redirect ping-pongs between the two =
routers.
>=20
>>=20
>> Figure 2: solved by implementing SADR in the router. The router =
already has the information it needs. In the case of specialized address =
routing, that's solved using the DHCPv6 address selection policy option =
(RFC 7078).=20
>>=20
>> Figure 3: Same as case 2 in Figure 1; solved by rule 5 in RFC 6724.
>>=20
>> Figure 4: Same as case 1 in Figure 1; solved by SADR forwarding =
between rtr1 and rtr2. Better performance if the host implements rule =
5.5 in RFC 6724.
>>=20
>> Figure 5: Solved by SADR forwarding between rtr, rtrE and rtrF.
>=20
>=20
> Something bugs me in general with the source address selection =
process.

I think source address selection bugs a lot of people. encoding what's =
essentially policy in an RFC...

> If we assume the host is dumb, it will first select the next-hop/oif =
and pick the source address using rule 5 or rule 5.5.
> If we assume the host is clever, it will first select the =
source-address based on the information it has (e.g., DHCPv6 address =
selection). But how is it supposed to select the next-hop then ? rule 5 =
and 5.5 solve source address selection when you know the next hop, but =
not next-hop selection when you know the source address.

the selection of next-hop is tied to the source address. if you choose =
the next-hop first, then that will force which set of source addresses =
you can choose from. if you choose the source address first, that limits =
the possible next-hops you have. that's essentially what SADR is, right.

> In other words, when you say DHCPv6 address selection policy solves =
the issue, you say the host should select the address based on =
configuration, which implies that you do that before you pick the next =
hop.
> But when you say rule 5 or 5.5 solve the issue, you assume the =
next-hop has already been selected. So, picking each figure and propose =
different solutions which seems to exclude each other seems unfair to =
me.
>=20
> Source address selection by the host/application is, IMHO, the =
simplest approach to upstream selection, as it reduces =
interface/next-hop/cpe selection to the selection of a single element. =
Homenet is moving toward this kind of solutions. But once the =
application or host has chosen the source address, we need some process =
to select the next hop.
>=20
> When I ask myself =91where should we pick the next-hop=92=85 The =
routing table seems to be the answer. And if we consider we want =
different next hops depending on the source address, source-dest routing =
looks like the right thing to do to me.=20
>=20
> Now, either we require hosts to look at PIOs and always add =
source-routes based on the RAs they receive (which means the router =
hides things to the host and the host hacks a solution to deal with it - =
and it may not always work), or we provide a longer-term solution where =
routers tell the truth to hosts.

I do agree with you that the host learns this information implicitly. I =
don't see that the network would be able to pass you any _more_ =
information even though the information was passed explicitly in a new =
RA option. at least the forwarding algorithm outlines above would still =
be the same I believe.

> I disagree with the overall approach of this draft. I think what we =
need is a source-specific extension to RFC4191. With only one single new =
option similar to RIOs but with a source-prefix included.

it might be useful that the network is much more explicit about "network =
policy" to the hosts. like some of the information we've talked about =
with the "prefix properties" draft. e.g. this is a walled garden prefix, =
this prefix is charged, and so on.
we might have more pressing problems with MHMP though. given that we =
either need SHIM6, transport layer support (MP-TCP) or application =
changes to make it work well.

cheers,
Ole=


From nobody Thu Jan 22 04:45:50 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C3EF1A1A06 for <ipv6@ietfa.amsl.com>; Thu, 22 Jan 2015 04:45:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VZUGu5aQNJjq for <ipv6@ietfa.amsl.com>; Thu, 22 Jan 2015 04:45:47 -0800 (PST)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E5071A19EF for <ipv6@ietf.org>; Thu, 22 Jan 2015 04:45:46 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t0MCjips019596 for <ipv6@ietf.org>; Thu, 22 Jan 2015 13:45:44 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 976FB203532 for <ipv6@ietf.org>; Thu, 22 Jan 2015 13:46:06 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 8E7B9202C01 for <ipv6@ietf.org>; Thu, 22 Jan 2015 13:46:06 +0100 (CET)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t0MCjJOG011120 for <ipv6@ietf.org>; Thu, 22 Jan 2015 13:45:43 +0100
Message-ID: <54C0F0DF.7040701@gmail.com>
Date: Thu, 22 Jan 2015 13:45:19 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: RFC 7421 on Analysis of the 64-bit Boundary in IPv6 Addressing
References: <20150114224301.A7661180448@rfc-editor.org>
In-Reply-To: <20150114224301.A7661180448@rfc-editor.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/4RxWhL6QpreQuhK0nfMDyF9Jh8g>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2015 12:45:49 -0000

Hello 6man,

I have a comment with respect to this RFC.

Should its content mean anything in particular to the designers of new 
IP-over-foo methods?  Not the existing IP/foo documents, but new ones.

New links come out regularly in recent years, featuring different L2 
addressing schemes, multicast capabilities, etc.

Should new IP-over-foo documents continue with the 64bit boundary 
(notable the IID length in SLAAC)?  Or should they be flexible in that 
respect?

For example, IPv6-over-802.11p uses IID length 64, although its MAC 
address is 48bit.  My suggestion is to allow the IID of this to be 
variable length.

This suggestion is based on the earlier discussion around this why64 
RFC, where I noticed that some people proposed to continue with the 
64bit limit, whereas others proposed flexibility.

What do you think?

Alex

Le 14/01/2015 23:43, rfc-editor@rfc-editor.org a écrit :
> A new Request for Comments is now available in online RFC libraries.
>
>
>          RFC 7421
>
>          Title:      Analysis of the 64-bit Boundary
>                      in IPv6 Addressing
>          Author:     B. Carpenter, Ed.,
>                      T. Chown, F. Gont,
>                      S. Jiang, A. Petrescu,
>                      A. Yourtchenko
>          Status:     Informational
>          Stream:     IETF
>          Date:       January 2015
>          Mailbox:    brian.e.carpenter@gmail.com,
>                      tjc@ecs.soton.ac.uk,
>                      fgont@si6networks.com,
>                      jiangsheng@huawei.com,
>                      alexandru.petrescu@cea.fr,
>                      ayourtch@cisco.com
>          Pages:      24
>          Characters: 60469
>          Updates/Obsoletes/SeeAlso:   None
>
>          I-D Tag:    draft-ietf-6man-why64-08.txt
>
>          URL:        https://www.rfc-editor.org/info/rfc7421
>
> The IPv6 unicast addressing format includes a separation between the
> prefix used to route packets to a subnet and the interface identifier
> used to specify a given interface connected to that subnet.
> Currently, the interface identifier is defined as 64 bits long for
> almost every case, leaving 64 bits for the subnet prefix.  This
> document describes the advantages of this fixed boundary and analyzes
> the issues that would be involved in treating it as a variable
> boundary.
>
> This document is a product of the IPv6 Maintenance Working Group of the IETF.
>
>
> INFORMATIONAL: This memo provides information for the Internet community.
> It does not specify an Internet standard of any kind. Distribution of
> this memo is unlimited.
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>    https://www.ietf.org/mailman/listinfo/ietf-announce
>    https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>
> For searching the RFC series, see https://www.rfc-editor.org/search
> For downloading RFCs, see https://www.rfc-editor.org/rfc.html
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
>
> The RFC Editor Team
> Association Management Solutions, LLC
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>



From nobody Thu Jan 22 06:54:14 2015
Return-Path: <karsten_thomann@linfre.de>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCBDB1A1AA6; Thu, 22 Jan 2015 06:54:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3TCnFa2eA-Tj; Thu, 22 Jan 2015 06:54:10 -0800 (PST)
Received: from linfre.de (linfre.de [83.151.26.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 477051A1A9D; Thu, 22 Jan 2015 06:54:10 -0800 (PST)
Received: from e7240.linfre (109.47.0.244) by linfreserv.linfre (Axigen) with (ECDHE-RSA-AES256-SHA encrypted) ESMTPSA id 13A85A; Thu, 22 Jan 2015 15:54:00 +0100
From: Karsten Thomann <karsten_thomann@linfre.de>
To: Ole Troan <otroan@employees.org>
Subject: Re: 6MAN cross-wg review: draft-ietf-l2tpext-keyed-ipv6-tunnel-01
Date: Thu, 22 Jan 2015 15:50:19 +0100
Message-ID: <24947916.dqx4YFu3F7@e7240.linfre>
User-Agent: KMail/4.14.3 (Linux/3.17.1-52.g5c4d099-desktop; KDE/4.14.3; x86_64; ; )
In-Reply-To: <68C9F850-89F5-4759-9FD0-1A00B33DDD46@employees.org>
References: <232077E7-7135-41E8-B0DB-C786F8C410CA@employees.org> <1816705.A9t7GNQOdE@linne> <68C9F850-89F5-4759-9FD0-1A00B33DDD46@employees.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="nextPart4694497.5cCDmNZOi8"
Content-Transfer-Encoding: 7Bit
X-AXIGEN-DK-Result: No records
DomainKey-Status: no signature
X-AxigenSpam-Level: 5
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/fvk1NUkFsAtBpNsYVqtqg9tWXMs>
Cc: 6man WG <ipv6@ietf.org>, l2tpext@ietf.org, l2tpext-chairs@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2015 14:54:13 -0000

This is a multi-part message in MIME format.

--nextPart4694497.5cCDmNZOi8
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

Hi,

my comments about the draft:
1. As far as I know the IETF processes this must be a standards track draft 
instead of a informational, as it not only simplifies the tunnels like 
removing the control plane, but uses MUST where the L2TPv3 RFC only set 
it as optional (e.g. Cookie).

2. In my opinion the terms key, cookie and authentication key for the 
required 64bit cookie should be cleaned up, as the terms have in some 
context of the rfc the same meaning

3. Why is the explicit value for the hop limit mentioned? In my opinion it 
should be lower, or are there any implementations which really use that 
value as a default? Should be rewritten to something without a fixed hop 
limit

4. Is there any reason to not use src + dst ip for all cases instead to only 
use it for the case that the local ip is used for more than one tunnel?
I think every device should know from which IPs it receives packets for a 
specific local l2tp ip as the cookie must be configured and should be 
unique per tunnel.

5. I didn't understand the meaning of the last sentence:
   o  Payload.  The customer data, with s-tag or s-tag/c-tag removed.
      As noted above preamble and FCS are stripped before encapsulation.
      A new FCS will be added at each hop when the IP packet is
      transmitted.
There is no relation between the routing of the l2tp packet and the 
payload FCS, as there is no FCS in the payload.
6. I'm not sure if it should be added to the security considerations section, 
but in RFC 3931 it is mentioned that there are no checksums for the 
packets as ipv6 and l2tp have none. I know it was especially mentioned for 
the control packets, but it also applies to all other packets with payload.

Regards
Karsten


Am Dienstag, 13. Januar 2015, 09:59:28 schrieb Ole Troan:
> Thanks Karsten, I look forward to your review.
> 
> Best regards,
> Ole
> 
> > On 12 Jan 2015, at 12:52 , Karsten Thomann 
<karsten_thomann@linfre.de>
> > wrote:
> > 
> > As Jinmai already wrote, I can volunteer, but only under the same
> > constrains, as I have no prior experience with reviews.
> > 
> > Some comments:
> > I know it is also written in RFC4719, but why was "or" used at "Ethernet
> > frame, without the preamble or frame check sequence (FCS)". At the
> > payload section is "and" used...
> > "As noted above preamble and FCS are stripped before 
encapsulation."
> > 
> > As already written by Jinmai, the hop limit is with 255 as a default
> > setting a bit high, a default of 64 should be high enough for nearly all
> > cases.
> > 
> > Kind regards
> > Karsten
> > 
> > Am Dienstag, 6. Januar 2015, 12:14:14 schrieb Ole Troan:
> > > Hi,
> > > 
> > > The chairs of l2tpext have asked for a 6man review of:
> > > 
> > > Title: Keyed IPv6 Tunnel
> > > https://tools.ietf.org/html/draft-ietf-l2tpext-keyed-ipv6-tunnel-01
> > > 
> > > Can we get a couple of volunteers please? As well as any other 
comments
> > > to
> > > the lists are welcome of course. Please keep l2tpext@ietf.org in CC.
> > > 
> > > Best regards,
> > > Ole
> > > 
> > > --------------------------------------------------------------------
> > > IETF IPv6 working group mailing list
> > > ipv6@ietf.org
> > > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > > --------------------------------------------------------------------


--nextPart4694497.5cCDmNZOi8
Content-Transfer-Encoding: 7Bit
Content-Type: text/html; charset="us-ascii"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd">
<html><head><meta name="qrichtext" content="1" /><style type="text/css">
p, li { white-space: pre-wrap; }
</style></head><body style=" font-family:'Sans Serif'; font-size:9pt; font-weight:400; font-style:normal;">
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Hi,</p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; ">&nbsp;</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">my comments about the draft:</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">1. As far as I know the IETF processes this must be a standards track draft instead of a informational, as it not only simplifies the tunnels like removing the control plane, but uses MUST where the L2TPv3 RFC only set it as optional (e.g. Cookie).</p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; ">&nbsp;</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">2. In my opinion the terms key, cookie and authentication key for the required 64bit cookie should be cleaned up, as the terms have in some context of the rfc the same meaning</p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; ">&nbsp;</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">3. Why is the explicit value for the hop limit mentioned? In my opinion it should be lower, or are there any implementations which really use that value as a default? Should be rewritten to something without a fixed hop limit</p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; ">&nbsp;</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">4. Is there any reason to not use src + dst ip for all cases instead to only use it for the case that the local ip is used for more than one tunnel?</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">I think every device should know from which IPs it receives packets for a specific local l2tp ip as the cookie must be configured and should be unique per tunnel.</p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; ">&nbsp;</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">5. I didn't understand the meaning of the last sentence:</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><span style=" font-family:'Courier New,courier';">   o  Payload.  The customer data, with s-tag or s-tag/c-tag removed.</span></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><span style=" font-family:'Courier New,courier';">      As noted above preamble and FCS are stripped before encapsulation.</span></p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><span style=" font-family:'Courier New,courier';">      A new FCS will be added at each hop when the IP packet is</span></p>
<p style=" margin-top:0px; margin-bottom:12px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><span style=" font-family:'Courier New,courier';">      transmitted.</span></p>
<p style=" margin-top:0px; margin-bottom:12px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'Courier New,courier';">There is no relation between the routing of the l2tp packet and the payload FCS, as there is no FCS in the payload.</span></p>
<p style=" margin-top:0px; margin-bottom:12px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'Courier New,courier';">6. I'm not sure if it should be added to the security considerations section, but in RFC 3931 it is mentioned that there are no checksums for the packets as ipv6 and l2tp have none. I know it was especially mentioned for the control packets, but it also applies to all other packets with payload.</span></p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; ">&nbsp;</p>
<p style=" margin-top:0px; margin-bottom:12px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'Courier New,courier';">Regards</span></p>
<p style=" margin-top:0px; margin-bottom:12px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'Courier New,courier';">Karsten</span></p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; ">&nbsp;</p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; ">&nbsp;</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Am Dienstag, 13. Januar 2015, 09:59:28 schrieb Ole Troan:</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; Thanks Karsten, I look forward to your review.</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; Best regards,</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; Ole</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; On 12 Jan 2015, at 12:52 , Karsten Thomann &lt;karsten_thomann@linfre.de&gt;</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; wrote:</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; As Jinmai already wrote, I can volunteer, but only under the same</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; constrains, as I have no prior experience with reviews.</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; Some comments:</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; I know it is also written in RFC4719, but why was &quot;or&quot; used at &quot;Ethernet</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; frame, without the preamble or frame check sequence (FCS)&quot;. At the</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; payload section is &quot;and&quot; used...</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &quot;As noted above preamble and FCS are stripped before encapsulation.&quot;</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; As already written by Jinmai, the hop limit is with 255 as a default</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; setting a bit high, a default of 64 should be high enough for nearly all</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; cases.</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; Kind regards</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; Karsten</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; Am Dienstag, 6. Januar 2015, 12:14:14 schrieb Ole Troan:</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &gt; Hi,</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &gt; The chairs of l2tpext have asked for a 6man review of:</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &gt; Title: Keyed IPv6 Tunnel</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &gt; https://tools.ietf.org/html/draft-ietf-l2tpext-keyed-ipv6-tunnel-01</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &gt; Can we get a couple of volunteers please? As well as any other comments</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &gt; to</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &gt; the lists are welcome of course. Please keep l2tpext@ietf.org in CC.</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &gt; Best regards,</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &gt; Ole</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &gt; </p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &gt; --------------------------------------------------------------------</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &gt; IETF IPv6 working group mailing list</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &gt; ipv6@ietf.org</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &gt; Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6</p>
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">&gt; &gt; &gt; --------------------------------------------------------------------</p>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; ">&nbsp;</p></body></html>
--nextPart4694497.5cCDmNZOi8--


From nobody Thu Jan 22 23:52:24 2015
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDE811A0266 for <ipv6@ietfa.amsl.com>; Thu, 22 Jan 2015 23:52:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.561
X-Spam-Level: 
X-Spam-Status: No, score=-2.561 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8EDXxEIsEGwa for <ipv6@ietfa.amsl.com>; Thu, 22 Jan 2015 23:52:18 -0800 (PST)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 936871A1A3C for <6man@ietf.org>; Thu, 22 Jan 2015 23:52:18 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 639D6A4; Fri, 23 Jan 2015 08:52:16 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1421999536; bh=dyMrWI7rjcgVx0VkBUYBqXzuWpeam/M9gy5BRv2hfas=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=Ku12EiFhvII1csA2PQ+b5+6N9Ee3gUmC5RH9JvqEt8zEpEgkgEv8wl/xZ9htQg+Dk OgmrqSzCvnI2PfJeEYKaVraahJnGQDdEQ2oqDygb8kUPUyCCAWS2QI6nJOSRSGMvEd LdTHdP/eKKuzLuuQjKjMkk1mbR0E2euWFbvsNSDc=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 58BBEA3; Fri, 23 Jan 2015 08:52:16 +0100 (CET)
Date: Fri, 23 Jan 2015 08:52:16 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ole Troan <otroan@employees.org>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
In-Reply-To: <7DC0A974-1D69-41A0-A23E-D8F60D0780B5@employees.org>
Message-ID: <alpine.DEB.2.02.1501230847000.22729@uplift.swm.pp.se>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <7DC0A974-1D69-41A0-A23E-D8F60D0780B5@employees.org>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/0TBiVp0xbh7pngTrvhHhCdMpNog>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 07:52:21 -0000

On Thu, 22 Jan 2015, Ole Troan wrote:

> we might have more pressing problems with MHMP though. given that we 
> either need SHIM6, transport layer support (MP-TCP) or application 
> changes to make it work well.

I also don't know where to start.

Right now source address selection and routing is done "ships in the 
night" which I think is the wrong thing to do. We need to tie together 
what source address is used and what next hop is chosen. Personally I 
think the MIF route here of having implicit PVDs is the best way to go, 
and to do this in the host IP stack. What needs to be changed where when 
it comes to network support of this, how information should be propagated, 
if more information is needed etc, is a discussion that seems to quickly 
get very confused because we haven't even agreed what the end goal is and 
how we want it to work.

A big problem I have with this is that the posix interfaces people 
generally think of are fast becoming close to obsolete, considering all 
the innovation seems to be in vendor-proprietary interfaces by Apple, 
Microsoft and others.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Fri Jan 23 00:32:30 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 602A21A8A7A for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 00:32:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v0SWZOjPfBEU for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 00:32:28 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 664551A040C for <6man@ietf.org>; Fri, 23 Jan 2015 00:32:28 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 8148C61A9; Fri, 23 Jan 2015 00:32:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=JI8lm93kUR8Pe1GTarK8gdUIAYE=; b=ct+dFtIq1b2+AlLsY2 Uba7QZt4f1dUC3dq3crj4nDI0Bb798/FF2nfwWgZnDsnpyf855t/r5bgG/p8B4LN BkntcG0bmx92dHlnULSv2bOwBxIwa6KSqh3pKyJuAewloUZR7VB73vkwm7OJqPiB J/KffrzbvKhMH2QUxpXbrsDWM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=Xj+A1Y1Ww2cUGRH53oNI5zwnOfIOnOzHEqEtdKXW5bRZ7S/OlY2 fmC4SAOxqn9ok/G/F96kZFGjEao67w4KwekkcnllAUX82JwYHJRej1IzbMwOpo0F RWv5Kp8Bc3NL5UmGOIMxwrDcPTXSH+Njop8V62jK4Q0DYiKzN16w9k7o=
Received: from gomlefisk.localdomain (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 4718C6127; Fri, 23 Jan 2015 00:32:27 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 19F963D31687; Fri, 23 Jan 2015 09:32:27 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.4\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <alpine.DEB.2.02.1501230847000.22729@uplift.swm.pp.se>
Date: Fri, 23 Jan 2015 09:32:26 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <038BA70D-8EDD-4454-83C5-2DE1817BC2DF@employees.org>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <7DC0A974-1D69-41A0-A23E-D8F60D0780B5@employees.org> <alpine.DEB.2.02.1501230847000.22729@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.2070.4)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/lJ6xk3hX3zJms3KhIejdNeMv-_Y>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 08:32:29 -0000

Mikael,

>> we might have more pressing problems with MHMP though. given that we =
either need SHIM6, transport layer support (MP-TCP) or application =
changes to make it work well.
>=20
> I also don't know where to start.
>=20
> Right now source address selection and routing is done "ships in the =
night" which I think is the wrong thing to do. We need to tie together =
what source address is used and what next hop is chosen.

agreed, and I think RFC6724 already implies that. even more so with rule =
5.5.

> Personally I think the MIF route here of having implicit PVDs is the =
best way to go, and to do this in the host IP stack.

from a forwarding perspective, at least if we look at the 'simple' use =
cases of multi-homing to congruent networks. what do you see MIF adding =
here?

> What needs to be changed where when it comes to network support of =
this, how information should be propagated, if more information is =
needed etc, is a discussion that seems to quickly get very confused =
because we haven't even agreed what the end goal is and how we want it =
to work.

if we stick to multi-prefix multi-homing, I think we have a decent set =
of requirements from RFC3582 and RFC7157.
isn't the goal of MHMP to implement the requirements in 3582?

> A big problem I have with this is that the posix interfaces people =
generally think of are fast becoming close to obsolete, considering all =
the innovation seems to be in vendor-proprietary interfaces by Apple, =
Microsoft and others.

TAPS?

cheers,
Ole=


From nobody Fri Jan 23 00:57:33 2015
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D944A1A01D5 for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 00:57:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ni3V4ltVKYtX for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 00:57:29 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA2591A00B8 for <6man@ietf.org>; Fri, 23 Jan 2015 00:57:28 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 4549AA4; Fri, 23 Jan 2015 09:57:25 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1422003445; bh=KypKxc9pNkOW3z7SlY/Rm4+B8kIJNedI0vElLQOhbdA=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=OxtsjFKYwCaHnqxhMD2AyjfyNBJtPByd1TdvUPhvUUlGRTGAjjh+Hro0wfJpd1Hr/ 7e4c6XsJciz/21bQg2sDnDd0IgWVMVLIhZ8zVMDCR6toapu/8zsQbcBKu7DKPBJnXA iYVk+Y7dGnSWXOaUFaxLXc5V+nXiy1a7vJaQ/PJk=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 4163FA3; Fri, 23 Jan 2015 09:57:25 +0100 (CET)
Date: Fri, 23 Jan 2015 09:57:25 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ole Troan <otroan@employees.org>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
In-Reply-To: <038BA70D-8EDD-4454-83C5-2DE1817BC2DF@employees.org>
Message-ID: <alpine.DEB.2.02.1501230934040.22729@uplift.swm.pp.se>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <7DC0A974-1D69-41A0-A23E-D8F60D0780B5@employees.org> <alpine.DEB.2.02.1501230847000.22729@uplift.swm.pp.se> <038BA70D-8EDD-4454-83C5-2DE1817BC2DF@employees.org>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/oL9kE_ENGkPNwWEVMFYPU7GwwZE>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 08:57:31 -0000

On Fri, 23 Jan 2015, Ole Troan wrote:

> from a forwarding perspective, at least if we look at the 'simple' use cases of multi-homing to congruent networks. what do you see MIF adding here?

If my host has three different IP addresses (from different /64s, 
potentially even on different interfaces), my application chooses to use 
one of these, what next-hop is chosen is now depending on routing and 
RFC6724 has nothing to do with it. I want the routing choice to be done 
based on the source address chosen. I consider this part of MIF, but I 
guess a case can be made that it's not. However, it's SADR I'm implying 
here.

> if we stick to multi-prefix multi-homing, I think we have a decent set 
> of requirements from RFC3582 and RFC7157. isn't the goal of MHMP to 
> implement the requirements in 3582?

Ok, I now looked into 7157, and yes, that's exactly what I'm talking 
about. 7157 talks in section 5 of source address selection, next-hop 
selection, and dns server selection, and these are all in what I called 
"PVD" in the MIF context. I want these to be a implicit PVD to which the 
application binds, and then everything happens within that PVD.

For instance, in the homenet scenario, if two routers are announcing 
multiple prefixes, is it enough that the router that has the better path 
to the ISP wherefrom that prefix is coming, is announcing itself as router 
with higher preference than the one that would send traffic from that 
prefix back onto the same link it came from? Should the host send multiple 
RAs, because in the scenario:

       /-- rtr1 --- ISP1
host -
       \-- rtr2 --- ISP2

In the homenet scenario, only one of the routers would announce both 
prefixes (?), meaning if this was rtr1, traffic to ISP2 would always 
bounce via rtr1, which is suboptimal. I'm not sure I like having rtr1 
announcing the route to ISP2 with rtr2 as next-hop, I would prefer if we 
had a tool where rtr2 would communicate to the host that it's a better 
exit for packet with source address of ISP2. Last I checked, in RAs, there 
is an implicit "I am the default gateway for everything". I would like to 
see "I am the $PRIORIRY default gateway for PREFIX" option. It seems this 
is what draft-sarikaya-6man-next-hop-ra is talking about.

So instead of having one router announce another router as next-hop (which 
seems to remove the fate-sharing of RAs with availability of that node), 
can't we have both routers announce themselves with different priorities 
for the respective prefixes based on IGP metric or similar?

>> A big problem I have with this is that the posix interfaces people generally think of are fast becoming close to obsolete, considering all the innovation seems to be in vendor-proprietary interfaces by Apple, Microsoft and others.
>
> TAPS?

I don't know what that is.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Fri Jan 23 01:32:02 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BC951A0203 for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 01:32:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 692N-TVoNeFF for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 01:31:58 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3472D1A01D8 for <6man@ietf.org>; Fri, 23 Jan 2015 01:31:58 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id A7F3862AD; Fri, 23 Jan 2015 01:31:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=IH1/+s52gtGc/mXyWzWshW4kMsc=; b=dXaeX0O9WkM5k6/TMg iqPmFnm+CbEN78N7elC8wLA2rjAWCP8uqiuxRjw4eXeiFPZGn0lYaOkpzaG4h6Kg TCbcKUTHjYSHRgYXOyhdATfC+mggKoXOrVeih2YWkIVX+dfO1SFRmJty1DuX6jd+ MNCCJtig/dmvLLHGc6Ausl7N8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=EPptPkwxN2ySUcASvMyOF2Y7/URzZVxS3jXKJcxemehDQ4AQkv8 y04/sBThohWGb048o2Tca+hx33ERSkepE75LbVpSI5na2gk+b8qtezS6Ns1Cdh1i C9pMv3Wq//131fNbeN5vykYcn9o0dV5jkAKERxcdjENwRJ1Iqt99wmfc=
Received: from gomlefisk.localdomain (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 0906E6284; Fri, 23 Jan 2015 01:31:56 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id D56483D329AC; Fri, 23 Jan 2015 10:31:53 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.4\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <alpine.DEB.2.02.1501230934040.22729@uplift.swm.pp.se>
Date: Fri, 23 Jan 2015 10:31:53 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <08371EFF-A2F3-4F38-AAB6-B4637BBF8A81@employees.org>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <7DC0A974-1D69-41A0-A23E-D8F60D0780B5@employees.org> <alpine.DEB.2.02.1501230847000.22729@uplift.swm.pp.se> <038BA70D-8EDD-4454-83C5-2DE1817BC2DF@employees.org> <alpine.DEB.2.02.1501230934040.22729@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.2070.4)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/8OPgD_fG8cTFml4i8C1tX-bDckw>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 09:32:00 -0000

Mikael,

>> from a forwarding perspective, at least if we look at the 'simple' =
use cases of multi-homing to congruent networks. what do you see MIF =
adding here?
>=20
> If my host has three different IP addresses (from different /64s, =
potentially even on different interfaces), my application chooses to use =
one of these, what next-hop is chosen is now depending on routing and =
RFC6724 has nothing to do with it. I want the routing choice to be done =
based on the source address chosen. I consider this part of MIF, but I =
guess a case can be made that it's not. However, it's SADR I'm implying =
here.

I think we agree on how this should work, so it doesn't so much matter =
which document it is written in. ;-)

cut and paste from RFC6724:
   Rule 5.5: Prefer addresses in a prefix advertised by the next-hop.
   If SA or SA's prefix is assigned by the selected next-hop that will
   be used to send to D and SB or SB's prefix is assigned by a different
   next-hop, then prefer SA.  Similarly, if SB or SB's prefix is
   assigned by the next-hop that will be used to send to D and SA or
   SA's prefix is assigned by a different next-hop, then prefer SB.

I haven't seen any MIF document on host sending rules?

>> if we stick to multi-prefix multi-homing, I think we have a decent =
set of requirements from RFC3582 and RFC7157. isn't the goal of MHMP to =
implement the requirements in 3582?
>=20
> Ok, I now looked into 7157, and yes, that's exactly what I'm talking =
about. 7157 talks in section 5 of source address selection, next-hop =
selection, and dns server selection, and these are all in what I called =
"PVD" in the MIF context. I want these to be a implicit PVD to which the =
application binds, and then everything happens within that PVD.
>=20
> For instance, in the homenet scenario, if two routers are announcing =
multiple prefixes, is it enough that the router that has the better path =
to the ISP wherefrom that prefix is coming, is announcing itself as =
router with higher preference than the one that would send traffic from =
that prefix back onto the same link it came from? Should the host send =
multiple RAs, because in the scenario:
>=20
>      /-- rtr1 --- ISP1
> host -
>      \-- rtr2 --- ISP2
>=20
> In the homenet scenario, only one of the routers would announce both =
prefixes (?), meaning if this was rtr1, traffic to ISP2 would always =
bounce via rtr1, which is suboptimal. I'm not sure I like having rtr1 =
announcing the route to ISP2 with rtr2 as next-hop, I would prefer if we =
had a tool where rtr2 would communicate to the host that it's a better =
exit for packet with source address of ISP2. Last I checked, in RAs, =
there is an implicit "I am the default gateway for everything". I would =
like to see "I am the $PRIORIRY default gateway for PREFIX" option. It =
seems this is what draft-sarikaya-6man-next-hop-ra is talking about.

OK, now you have lost me. in the figure above does host have 2 separate =
interfaces or 1?

- 2 separate interfaces. host receives RA with ISP1 prefix on interface =
1, and RA with ISP2 prefix on interface 2. strong host model ensures =
appropriate source address is used given chosen next-hop/interface. =
likewise chosen if the application picks source, then the host picks the =
appropriate next-hop for the interface the source is attached to.

- 1 single interface. host receives two RAs, one from rtr1 one from =
rtr2. rule 5.5 will ensure that host picks correct router for given =
source. there is no need for any collaboration between rtr1 and rtr3.

if there was a rtr3 between host and rtr1/2 then rtr3 must implement =
SADR forwarding, and the host will have 2 addresses but a single =
next-hop.

for the purpose of sending packets to congruent networks I don't know =
what PVDs would add to this puzzle. as far as I can see the host has =
enough information already to make a choice.

diverging into PVDs; I do think that in a home network, pushing external =
PVDs all the way to the hosts is a policy issue. in my home network, =
even though I have multiple ISPs, I have only a single provisioning =
domain, which is _my_ home network, as I wouldn't let ISPs =
configure/control hosts/applications directly.=20

> So instead of having one router announce another router as next-hop =
(which seems to remove the fate-sharing of RAs with availability of that =
node), can't we have both routers announce themselves with different =
priorities for the respective prefixes based on IGP metric or similar?
>=20
>>> A big problem I have with this is that the posix interfaces people =
generally think of are fast becoming close to obsolete, considering all =
the innovation seems to be in vendor-proprietary interfaces by Apple, =
Microsoft and others.
>>=20
>> TAPS?
>=20
> I don't know what that is.

http://datatracker.ietf.org/wg/taps/documents/

cheers,
Ole=


From nobody Fri Jan 23 02:10:49 2015
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8ABB81A044D for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 02:10:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RuW5tOuimDA2 for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 02:10:37 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 357F11A03A2 for <6man@ietf.org>; Fri, 23 Jan 2015 02:10:37 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 5CC15A4; Fri, 23 Jan 2015 11:10:35 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1422007835; bh=P1kli8qtMgw9EvqXibPc95YfoHjjaDyTmqjTwvKwFbk=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=nt5Vq+69e7v14Id18N6v/DcLPyalA6xxC6iL5e0fnPWTWxoDy/+EgwMWNMWyZEdbw PjGiUj1r3sHuDoeif+Cc/sWNw5MG8uKplh3vje10T3tb/xlsLLbjg9EYfEbFIDe6ED 7pMIUWZ68SGC3iRaM9/TK54wuAA/3p2wsjdUeeo4=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 520E8A3; Fri, 23 Jan 2015 11:10:35 +0100 (CET)
Date: Fri, 23 Jan 2015 11:10:35 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ole Troan <otroan@employees.org>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
In-Reply-To: <08371EFF-A2F3-4F38-AAB6-B4637BBF8A81@employees.org>
Message-ID: <alpine.DEB.2.02.1501231051160.22729@uplift.swm.pp.se>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <7DC0A974-1D69-41A0-A23E-D8F60D0780B5@employees.org> <alpine.DEB.2.02.1501230847000.22729@uplift.swm.pp.se> <038BA70D-8EDD-4454-83C5-2DE1817BC2DF@employees.org> <alpine.DEB.2.02.1501230934040.22729@uplift.swm.pp.se> <08371EFF-A2F3-4F38-AAB6-B4637BBF8A81@employees.org>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-137064504-1584333216-1422007835=:22729"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ao7pfqo01oazVlEz7gbx3j6kPNo>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 10:10:46 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---137064504-1584333216-1422007835=:22729
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Fri, 23 Jan 2015, Ole Troan wrote:

> Mikael,
>
>>> from a forwarding perspective, at least if we look at the 'simple' use cases of multi-homing to congruent networks. what do you see MIF adding here?
>>
>> If my host has three different IP addresses (from different /64s, potentially even on different interfaces), my application chooses to use one of these, what next-hop is chosen is now depending on routing and RFC6724 has nothing to do with it. I want the routing choice to be done based on the source address chosen. I consider this part of MIF, but I guess a case can be made that it's not. However, it's SADR I'm implying here.
>
> I think we agree on how this should work, so it doesn't so much matter which document it is written in. ;-)
>
> cut and paste from RFC6724:
>   Rule 5.5: Prefer addresses in a prefix advertised by the next-hop.
>   If SA or SA's prefix is assigned by the selected next-hop that will
>   be used to send to D and SB or SB's prefix is assigned by a different
>   next-hop, then prefer SA.  Similarly, if SB or SB's prefix is
>   assigned by the next-hop that will be used to send to D and SA or
>   SA's prefix is assigned by a different next-hop, then prefer SB.
>
> I haven't seen any MIF document on host sending rules?

I don't know if there is, but I think we're going to need them, for 
instance if we have different prefixes for different functions. Prefix 
properties.

> OK, now you have lost me. in the figure above does host have 2 separate 
> interfaces or 1?

I interface.

> - 1 single interface. host receives two RAs, one from rtr1 one from 
> rtr2. rule 5.5 will ensure that host picks correct router for given 
> source. there is no need for any collaboration between rtr1 and rtr3.

Since this is a "homenet", these routers will have decided which one 
should send RAs for the LAN, and only one router will send RAs, but for 
both prefixes.

My idea was to send 4 RAs, one per prefix per router. The same information 
could potentially be sent in a single RA per router in case there is 
enough information in there to discern SADR, implicit "I am default 
gateway" and priority from a different SADR.

That way rtr1 would send RA for ISP1 with high preference, rtr2 would send 
RAs for ISP2 with high preference, RTR1 would send ISP2 prefix with low 
preference, and RTR2 would send ISP1 prefix with low preference. This 
isn't strictly needed or helping in my example network, but imagine a more 
advanced network where there would be multiple paths to one or each ISP.

> if there was a rtr3 between host and rtr1/2 then rtr3 must implement 
> SADR forwarding, and the host will have 2 addresses but a single 
> next-hop.

   â€‰â€‰â€‰+--+rtr3++rtr1+---+ISP1
â€‰â€‰â€‰â€‰â€‰|â€‰â€‰â€‰â€‰â€‰â€‰â€‰â€‰â€‰â€‰+
â€‰â€‰â€‰â€‰â€‰|â€‰â€‰â€‰â€‰+-----+
â€‰â€‰H1++â€‰â€‰â€‰â€‰+â€‰â€‰â€‰â€‰â€‰â€‰â€‰â€‰â€‰â€‰â€‰â€‰â€‰â€‰â€‰â€‰â€‰â€‰
â€‰â€‰â€‰â€‰â€‰+--+rtr2+-+ISP2â€‰â€‰â€‰â€‰â€‰â€‰â€‰â€‰â€‰

So lets say rtr2-rtr1 link is really slow. This would mean that 
rtr3-rtr1->ISP1 is to be preferred before rtr2->rtr1->ISP1.

In the homenet case either rtr3 or rtr2 would be default gw for the lan, 
meaning packet flow would be going rtr3->rtr2->ISP2 if rtr3 is the 
handling router for the subnet, or rtr2->rtr3->rtr1->ISP1 if rtr2 is the 
handling router for the subnet.

With my proposal, rtr3 could announce itself as a more optimal router for 
ISP1 prefix, and rtr2 could announce itself as a more optimal router for 
ISP2.

If this is needed or not depends on if one considers an extra routing hop 
being a problem or not.

> http://datatracker.ietf.org/wg/taps/documents/

That seems to be mostly investigation, not defining new APIs? "Submit an 
Experimental document to the IESG specifying one or more methods to 
provide applications with the Transport Services identified by the WG" , 
so this is mostly about doing preparation before defining new APIs?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se
---137064504-1584333216-1422007835=:22729--


From SRS0=d+iv=CK=darou.fr=pierre.pfister@bounces.m4x.org  Fri Jan 23 02:33:49 2015
Return-Path: <SRS0=d+iv=CK=darou.fr=pierre.pfister@bounces.m4x.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 318E91A0687 for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 02:33:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pC650hxhI04r for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 02:33:46 -0800 (PST)
Received: from mx1.polytechnique.org (mx1.polytechnique.org [129.104.30.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB0B91A06FD for <6man@ietf.org>; Fri, 23 Jan 2015 02:33:44 -0800 (PST)
Received: from mbp.home (ANantes-652-1-151-102.w109-211.abo.wanadoo.fr [109.211.230.102]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ssl.polytechnique.org (Postfix) with ESMTPSA id 354581408EEED; Fri, 23 Jan 2015 11:33:41 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <7DC0A974-1D69-41A0-A23E-D8F60D0780B5@employees.org>
Date: Fri, 23 Jan 2015 11:33:41 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <5AF4DC81-BC35-44CA-8A55-27AC9501364E@darou.fr>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <7DC0A974-1D69-41A0-A23E-D8F60D0780B5@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1878.6)
X-AV-Checked: ClamAV using ClamSMTP at svoboda.polytechnique.org (Fri Jan 23 11:33:41 2015 +0100 (CET))
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/N3K41u12OHretMH9XDlopsnioWo>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 10:34:05 -0000

Ole,


>=20
>=20
>>> I feel strongly that configuration option that allows a router to =
specify another on-link next hop (or, even worse, a next hop on another =
interface) is a bad idea because it breaks the fate-sharing properties =
provided by RAs.
>>>=20
>>=20
>> I fully agree there. If another router should be next-hop, then that =
other router can send RAs by itself.
>>=20
>>> If all that is necessary is a means to tell the host what source =
address to prefer for what prefixes, then we already have a DHCP option =
for that.
>>>=20
>>> Looking at the scenarios, I don't see anything that requires any new =
work to solve.
>>>=20
>>> Figure 1:
>>> Case 1: rtr1 and rtr2 are connected to different interfaces on the =
host (e.g., wifi and 3G), This is solved by rule 5 in RFC 6724.
>>> Case 2: rtr1 and rtr2 are connected to the same interface on the =
host. This is solved by SADR forwarding between rtr1 and rtr2 with no =
host changes.
>>=20
>> Yes, but if we rely on routers=92 capabilities only, we will have =
suboptimal routing. e.g., the next-hop will send the packet back on the =
same link. Which would halve the throughput.
>> And if we rely on redirects, well=85 Redirects are not =
source-specific, so we may have redirect ping-pongs between the two =
routers.
>>=20
>>>=20
>>> Figure 2: solved by implementing SADR in the router. The router =
already has the information it needs. In the case of specialized address =
routing, that's solved using the DHCPv6 address selection policy option =
(RFC 7078).=20
>>>=20
>>> Figure 3: Same as case 2 in Figure 1; solved by rule 5 in RFC 6724.
>>>=20
>>> Figure 4: Same as case 1 in Figure 1; solved by SADR forwarding =
between rtr1 and rtr2. Better performance if the host implements rule =
5.5 in RFC 6724.
>>>=20
>>> Figure 5: Solved by SADR forwarding between rtr, rtrE and rtrF.
>>=20
>>=20
>> Something bugs me in general with the source address selection =
process.
>=20
> I think source address selection bugs a lot of people. encoding what's =
essentially policy in an RFC...
>=20
>> If we assume the host is dumb, it will first select the next-hop/oif =
and pick the source address using rule 5 or rule 5.5.
>> If we assume the host is clever, it will first select the =
source-address based on the information it has (e.g., DHCPv6 address =
selection). But how is it supposed to select the next-hop then ? rule 5 =
and 5.5 solve source address selection when you know the next hop, but =
not next-hop selection when you know the source address.
>=20
> the selection of next-hop is tied to the source address. if you choose =
the next-hop first, then that will force which set of source addresses =
you can choose from. if you choose the source address first, that limits =
the possible next-hops you have. that's essentially what SADR is, right.

Yes for the first part. But no for the second. As far as I know, SADR =
does not tell you anything about how to select the next hop once you =
selected the source address. This is the role of the routing table. =
Which may break BCP38. So it looks to me there is something to be done =
here.

>=20
>> In other words, when you say DHCPv6 address selection policy solves =
the issue, you say the host should select the address based on =
configuration, which implies that you do that before you pick the next =
hop.
>> But when you say rule 5 or 5.5 solve the issue, you assume the =
next-hop has already been selected. So, picking each figure and propose =
different solutions which seems to exclude each other seems unfair to =
me.
>>=20
>> Source address selection by the host/application is, IMHO, the =
simplest approach to upstream selection, as it reduces =
interface/next-hop/cpe selection to the selection of a single element. =
Homenet is moving toward this kind of solutions. But once the =
application or host has chosen the source address, we need some process =
to select the next hop.
>>=20
>> When I ask myself =91where should we pick the next-hop=92=85 The =
routing table seems to be the answer. And if we consider we want =
different next hops depending on the source address, source-dest routing =
looks like the right thing to do to me.=20
>>=20
>> Now, either we require hosts to look at PIOs and always add =
source-routes based on the RAs they receive (which means the router =
hides things to the host and the host hacks a solution to deal with it - =
and it may not always work), or we provide a longer-term solution where =
routers tell the truth to hosts.
>=20
> I do agree with you that the host learns this information implicitly. =
I don't see that the network would be able to pass you any _more_ =
information even though the information was passed explicitly in a new =
RA option. at least the forwarding algorithm outlines above would still =
be the same I believe.

Your solution would interpret PIOs as source-specific default routes. =
Depending on the router=92s lifetime obviously.=20
It would explicitly tie on-link address configuration to routing. =
Routers would need to modify the PIOs they advertise based on other =
router=92s presence (dynamically updating address configuration which =
could not change). Routing and address configuration are separated in =
ND, and I think it is a good thing. It reduces complexity.

Additionally, what if you don=92t want a source-specific default route, =
but a source and destination specific route ? For instance, I have an SP =
that allows le to reach a single destination prefix. That does not mean =
it won=92t implement BCP38. Why would I have a default route for only a =
restricted set of destinations ? Maybe I can use the same source address =
to reach other destinations through a different next-hop.

>=20
>> I disagree with the overall approach of this draft. I think what we =
need is a source-specific extension to RFC4191. With only one single new =
option similar to RIOs but with a source-prefix included.
>=20
> it might be useful that the network is much more explicit about =
"network policy" to the hosts. like some of the information we've talked =
about with the "prefix properties" draft. e.g. this is a walled garden =
prefix, this prefix is charged, and so on.
> we might have more pressing problems with MHMP though. given that we =
either need SHIM6, transport layer support (MP-TCP) or application =
changes to make it work well.
>=20
> cheers,
> Ole


From nobody Fri Jan 23 02:43:35 2015
Return-Path: <SRS0=d+iv=CK=darou.fr=pierre.pfister@bounces.m4x.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 974E41A8987 for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 02:43:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zgzYyaPNMPc8 for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 02:43:30 -0800 (PST)
Received: from mx1.polytechnique.org (mx1.polytechnique.org [129.104.30.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B85151A1AFF for <6man@ietf.org>; Fri, 23 Jan 2015 02:43:29 -0800 (PST)
Received: from mbp.home (ANantes-652-1-151-102.w109-211.abo.wanadoo.fr [109.211.230.102]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ssl.polytechnique.org (Postfix) with ESMTPSA id 7F73A1408EEED; Fri, 23 Jan 2015 11:43:27 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <alpine.DEB.2.02.1501231051160.22729@uplift.swm.pp.se>
Date: Fri, 23 Jan 2015 11:43:29 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E88E95F-47C0-498D-914A-07DFA4B11DB8@darou.fr>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <7DC0A974-1D69-41A0-A23E-D8F60D0780B5@employees.org> <alpine.DEB.2.02.1501230847000.22729@uplift.swm.pp.se> <038BA70D-8EDD-4454-83C5-2DE1817BC2DF@employees.org> <alpine.DEB.2.02.1501230934040.22729@uplift.swm.pp.se> <08371EFF-A2F3-4F38-AAB6-B4637BBF8A81@employees.org> <alpine.DEB.2.02.1501231051160.22729@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1878.6)
X-AV-Checked: ClamAV using ClamSMTP at svoboda.polytechnique.org (Fri Jan 23 11:43:28 2015 +0100 (CET))
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/bnutX_rB-EAI5uUcp_73_BWdT6A>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 10:43:32 -0000

Hello Mikael,

> On Fri, 23 Jan 2015, Ole Troan wrote:
>=20
>> Mikael,
>>=20
>>>> from a forwarding perspective, at least if we look at the 'simple' =
use cases of multi-homing to congruent networks. what do you see MIF =
adding here?
>>>=20
>>> If my host has three different IP addresses (from different /64s, =
potentially even on different interfaces), my application chooses to use =
one of these, what next-hop is chosen is now depending on routing and =
RFC6724 has nothing to do with it. I want the routing choice to be done =
based on the source address chosen. I consider this part of MIF, but I =
guess a case can be made that it's not. However, it's SADR I'm implying =
here.
>>=20
>> I think we agree on how this should work, so it doesn't so much =
matter which document it is written in. ;-)
>>=20
>> cut and paste from RFC6724:
>>  Rule 5.5: Prefer addresses in a prefix advertised by the next-hop.
>>  If SA or SA's prefix is assigned by the selected next-hop that will
>>  be used to send to D and SB or SB's prefix is assigned by a =
different
>>  next-hop, then prefer SA.  Similarly, if SB or SB's prefix is
>>  assigned by the next-hop that will be used to send to D and SA or
>>  SA's prefix is assigned by a different next-hop, then prefer SB.
>>=20
>> I haven't seen any MIF document on host sending rules?
>=20
> I don't know if there is, but I think we're going to need them, for =
instance if we have different prefixes for different functions. Prefix =
properties.
>=20
>> OK, now you have lost me. in the figure above does host have 2 =
separate interfaces or 1?
>=20
> I interface.
>=20
>> - 1 single interface. host receives two RAs, one from rtr1 one from =
rtr2. rule 5.5 will ensure that host picks correct router for given =
source. there is no need for any collaboration between rtr1 and rtr3.
>=20
> Since this is a "homenet", these routers will have decided which one =
should send RAs for the LAN, and only one router will send RAs, but for =
both prefixes.
>=20
> My idea was to send 4 RAs, one per prefix per router. The same =
information could potentially be sent in a single RA per router in case =
there is enough information in there to discern SADR, implicit "I am =
default gateway" and priority from a different SADR.
>=20
> That way rtr1 would send RA for ISP1 with high preference, rtr2 would =
send RAs for ISP2 with high preference, RTR1 would send ISP2 prefix with =
low preference, and RTR2 would send ISP1 prefix with low preference. =
This isn't strictly needed or helping in my example network, but imagine =
a more advanced network where there would be multiple paths to one or =
each ISP.
>=20
>> if there was a rtr3 between host and rtr1/2 then rtr3 must implement =
SADR forwarding, and the host will have 2 addresses but a single =
next-hop.
>=20
>  =E2=80=89=E2=80=89=E2=80=89+--+rtr3++rtr1+---+ISP1
> =E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89|=E2=80=89=E2=80=89=E2=80=89=
=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89+
> =E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89|=E2=80=89=E2=80=89=E2=80=89=
=E2=80=89+-----+
> =
=E2=80=89=E2=80=89H1++=E2=80=89=E2=80=89=E2=80=89=E2=80=89+=E2=80=89=E2=80=
=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=
=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89
> =E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89+--+rtr2+-+ISP2=E2=80=89=E2=
=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89
>=20
> So lets say rtr2-rtr1 link is really slow. This would mean that =
rtr3-rtr1->ISP1 is to be preferred before rtr2->rtr1->ISP1.
>=20
> In the homenet case either rtr3 or rtr2 would be default gw for the =
lan, meaning packet flow would be going rtr3->rtr2->ISP2 if rtr3 is the =
handling router for the subnet, or rtr2->rtr3->rtr1->ISP1 if rtr2 is the =
handling router for the subnet.
>=20
> With my proposal, rtr3 could announce itself as a more optimal router =
for ISP1 prefix, and rtr2 could announce itself as a more optimal router =
for ISP2.
>=20
> If this is needed or not depends on if one considers an extra routing =
hop being a problem or not.

This really looks like the design I have in mind too.

I think all routers connected to the same link should advertise all the =
PIOs they know about (in homenet case, it means all of them, as HNCP and =
Prefix Assignment take care of sharing the information).
Then, they would advertise different Source-Specific RIOs with different =
priorities and prefixes, just like you said.

This way, when a router disappears, not only the host does not deprecate =
its address (waiting for another router to start advertising the lost =
PIO), but it can automatically backup the routing the the lower-priority =
route.

This approach also supports source and destination specific routes.

- Pierre


>=20
>> http://datatracker.ietf.org/wg/taps/documents/
>=20
> That seems to be mostly investigation, not defining new APIs? "Submit =
an Experimental document to the IESG specifying one or more methods to =
provide applications with the Transport Services identified by the WG" , =
so this is mostly about doing preparation before defining new APIs?
>=20
> --=20
> Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Fri Jan 23 03:05:15 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFF091A9089 for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 03:05:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KSkZmaR6bR9Z for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 03:05:08 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38DEA1A906F for <6man@ietf.org>; Fri, 23 Jan 2015 03:04:56 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 516F3617B; Fri, 23 Jan 2015 03:04:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=qv9xNNyL/VI31VdIfA72VGwQp/8=; b=JcEITzt8lwA0rly4W9 Kzl4dYrCxAVIZgVOO9ETx+zteHBb4rKOr+B7cQL/0beyXOe4AUBh+ExbTmVHRnA8 97AqWcJa+vLmo81S3f5Z++OxlKdQK4oN/O105Ea54ovhRo9VDr+M/PCgd8MmeAgE 1CvmbjOVd8HBpq6O/u5CBd428=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=VuBYhcN1IZCrZvh6njCfr8TI8oj+/celL05Oq0MttgQpee30XrP YtswTK2G69VP7KhRwi9Fn7pjdnDKf+IempfSYARtCt3lzgKaGE6b66/DERGEHUrk qjSpi2mQOIgNX3M7ObmflUT21jOLcOZxFmw9B5/1r2nAHIQsq3FSZNyo=
Received: from gomlefisk.localdomain (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id BF3F5616C; Fri, 23 Jan 2015 03:04:53 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id A60F23D3417D; Fri, 23 Jan 2015 12:04:51 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.4\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <5AF4DC81-BC35-44CA-8A55-27AC9501364E@darou.fr>
Date: Fri, 23 Jan 2015 12:04:51 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DE1852B4-653D-4B64-9034-48C8E07D0660@employees.org>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <7DC0A974-1D69-41A0-A23E-D8F60D0780B5@employees.org> <5AF4DC81-BC35-44CA-8A55-27AC9501364E@darou.fr>
To: Pierre Pfister <pierre.pfister@darou.fr>
X-Mailer: Apple Mail (2.2070.4)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/S2U55GdAF7F_3njzNDDEiRv2Ayk>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 11:05:12 -0000

Pierre,

>>> If we assume the host is dumb, it will first select the next-hop/oif =
and pick the source address using rule 5 or rule 5.5.
>>> If we assume the host is clever, it will first select the =
source-address based on the information it has (e.g., DHCPv6 address =
selection). But how is it supposed to select the next-hop then ? rule 5 =
and 5.5 solve source address selection when you know the next hop, but =
not next-hop selection when you know the source address.
>>=20
>> the selection of next-hop is tied to the source address. if you =
choose the next-hop first, then that will force which set of source =
addresses you can choose from. if you choose the source address first, =
that limits the possible next-hops you have. that's essentially what =
SADR is, right.
>=20
> Yes for the first part. But no for the second. As far as I know, SADR =
does not tell you anything about how to select the next hop once you =
selected the source address. This is the role of the routing table. =
Which may break BCP38. So it looks to me there is something to be done =
here.

isn't that just an implementation detail? some host implementations =
don't use routing tables btw.
my point is that the host has the necessary information already, and =
that rule 5.5 as far as I can see specifies how the external behaviour =
should be.

>>> In other words, when you say DHCPv6 address selection policy solves =
the issue, you say the host should select the address based on =
configuration, which implies that you do that before you pick the next =
hop.
>>> But when you say rule 5 or 5.5 solve the issue, you assume the =
next-hop has already been selected. So, picking each figure and propose =
different solutions which seems to exclude each other seems unfair to =
me.
>>>=20
>>> Source address selection by the host/application is, IMHO, the =
simplest approach to upstream selection, as it reduces =
interface/next-hop/cpe selection to the selection of a single element. =
Homenet is moving toward this kind of solutions. But once the =
application or host has chosen the source address, we need some process =
to select the next hop.
>>>=20
>>> When I ask myself =91where should we pick the next-hop=92=85 The =
routing table seems to be the answer. And if we consider we want =
different next hops depending on the source address, source-dest routing =
looks like the right thing to do to me.=20
>>>=20
>>> Now, either we require hosts to look at PIOs and always add =
source-routes based on the RAs they receive (which means the router =
hides things to the host and the host hacks a solution to deal with it - =
and it may not always work), or we provide a longer-term solution where =
routers tell the truth to hosts.
>>=20
>> I do agree with you that the host learns this information implicitly. =
I don't see that the network would be able to pass you any _more_ =
information even though the information was passed explicitly in a new =
RA option. at least the forwarding algorithm outlines above would still =
be the same I believe.
>=20
> Your solution would interpret PIOs as source-specific default routes. =
Depending on the router=92s lifetime obviously.=20
> It would explicitly tie on-link address configuration to routing. =
Routers would need to modify the PIOs they advertise based on other =
router=92s presence (dynamically updating address configuration which =
could not change). Routing and address configuration are separated in =
ND, and I think it is a good thing. It reduces complexity.

hosts don't do routing. the PIO would be tied to next-hop selection. =
yes.
I don't think it has to be tied to the router's lifetime. when the =
relevant router expires, then the tie is broken.
rule 5.5 already makes that tie, and I don't see how you can avoid that =
if you want to ensure that a source address influences next-hop =
selection.

I don't see why this would imply that one router has to modify what it =
advertises based on other routers. the PIO isn't routing.

> Additionally, what if you don=92t want a source-specific default =
route, but a source and destination specific route ? For instance, I =
have an SP that allows le to reach a single destination prefix. That =
does not mean it won=92t implement BCP38. Why would I have a default =
route for only a restricted set of destinations ? Maybe I can use the =
same source address to reach other destinations through a different =
next-hop.

yes, that's why I limited my answer to multi-homing to congruent =
networks.
in the use case we're talking about, that would be solved by an RA with =
the PIO and the more specific with lifetime =3D 0 from the other router.

>>> I disagree with the overall approach of this draft. I think what we =
need is a source-specific extension to RFC4191. With only one single new =
option similar to RIOs but with a source-prefix included.
>>=20
>> it might be useful that the network is much more explicit about =
"network policy" to the hosts. like some of the information we've talked =
about with the "prefix properties" draft. e.g. this is a walled garden =
prefix, this prefix is charged, and so on.
>> we might have more pressing problems with MHMP though. given that we =
either need SHIM6, transport layer support (MP-TCP) or application =
changes to make it work well.

cheers,
Ole


From nobody Fri Jan 23 03:12:56 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ACA71A909D for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 03:12:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6fqwxTVkoT8V for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 03:11:58 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D29741A9078 for <6man@ietf.org>; Fri, 23 Jan 2015 03:11:57 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id ABD9D617B; Fri, 23 Jan 2015 03:11:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=KMykuBScHRN/egDPhiL+Yd10ew8=; b=MqX5StN2cAKRVT+Pv2 tIguSOpPTEd3RU/BZSQRMa9ljhMCfnbwku9rbhSQoMcMhmzAq741HHRO7zfN0bHr zpRQtgh6p7RArq+yQ8QOLq5fDz/8OU/TIlkvSm+iwuby0bOKMGDOdMZ+69SlxV7G kboZJTN5xXAb2tzanbBDPqmi4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=VFUz2SXNSgICSuvtclH2scQOdTWeJkpEydm8Y20X9xd+4hj8w3F zVoSEjryKB/F9sraVy5SFv3Jg9coq2CP9k3QDaOd3yVR2PwRWI5x2dgSq1+TeywP gRvV83xYC03MnxoxgytNwnaEmmQuoIuj6zRXqDwh7E79ypG2WNpHY0I0=
Received: from gomlefisk.localdomain (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id E4C4B616C; Fri, 23 Jan 2015 03:11:55 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 4A8883D342EC; Fri, 23 Jan 2015 12:11:53 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.4\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <3E88E95F-47C0-498D-914A-07DFA4B11DB8@darou.fr>
Date: Fri, 23 Jan 2015 12:11:53 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <440A410F-CC4E-4577-8ED4-B7E606E35D6D@employees.org>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <7DC0A974-1D69-41A0-A23E-D8F60D0780B5@employees.org> <alpine.DEB.2.02.1501230847000.22729@uplift.swm.pp.se> <038BA70D-8EDD-4454-83C5-2DE1817BC2DF@employees.org> <alpine.DEB.2.02.1501230934040.22729@uplift.swm.pp.se> <08371EFF-A2F3-4F38-AAB6-B4637BBF8A81@employees.org> <alpine.DEB.2.02.1501231051160.22729@uplift.swm.pp.se> <3E88E95F-47C0-498D-914A-07DFA4B11DB8@darou.fr>
To: Pierre Pfister <pierre.pfister@darou.fr>
X-Mailer: Apple Mail (2.2070.4)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/jCAvzQO77-vCbeJYW6kmJMNEzAI>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 11:12:15 -0000

Pierre,

>>> if there was a rtr3 between host and rtr1/2 then rtr3 must implement =
SADR forwarding, and the host will have 2 addresses but a single =
next-hop.
>>=20
>> =E2=80=89=E2=80=89=E2=80=89+--+rtr3++rtr1+---+ISP1
>> =E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89|=E2=80=89=E2=80=89=E2=80=89=
=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89+
>> =E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89|=E2=80=89=E2=80=89=E2=80=89=
=E2=80=89+-----+
>> =
=E2=80=89=E2=80=89H1++=E2=80=89=E2=80=89=E2=80=89=E2=80=89+=E2=80=89=E2=80=
=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=
=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89
>> =E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89+--+rtr2+-+ISP2=E2=80=89=E2=
=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89=E2=80=89
>>=20
>> So lets say rtr2-rtr1 link is really slow. This would mean that =
rtr3-rtr1->ISP1 is to be preferred before rtr2->rtr1->ISP1.
>>=20
>> In the homenet case either rtr3 or rtr2 would be default gw for the =
lan, meaning packet flow would be going rtr3->rtr2->ISP2 if rtr3 is the =
handling router for the subnet, or rtr2->rtr3->rtr1->ISP1 if rtr2 is the =
handling router for the subnet.
>>=20
>> With my proposal, rtr3 could announce itself as a more optimal router =
for ISP1 prefix, and rtr2 could announce itself as a more optimal router =
for ISP2.
>>=20
>> If this is needed or not depends on if one considers an extra routing =
hop being a problem or not.
>=20
> This really looks like the design I have in mind too.
>=20
> I think all routers connected to the same link should advertise all =
the PIOs they know about (in homenet case, it means all of them, as HNCP =
and Prefix Assignment take care of sharing the information).
> Then, they would advertise different Source-Specific RIOs with =
different priorities and prefixes, just like you said.
>=20
> This way, when a router disappears, not only the host does not =
deprecate its address (waiting for another router to start advertising =
the lost PIO), but it can automatically backup the routing the the =
lower-priority route.
>=20
> This approach also supports source and destination specific routes.

you could do that.
I think the options we have are:

1) current specifications (rule 5.5, works as I described)
2) Homenet case, all routers advertise all PIOs. depends on redirects
3) Extend RFC4191 with source specific routes
4) Instead of making ND into a routing protocol just make hosts =
participate in a real RP.

I have argued for 1, from the standpoint that this is what's most likely =
to get current hosts to implement today, and it works with two =
independent routers that doesn't support homenet protocols.

cheers,
Ole=


From nobody Fri Jan 23 03:52:47 2015
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 675431A90A2 for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 03:52:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g2A0mHojBToC for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 03:52:43 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8F571A9097 for <6man@ietf.org>; Fri, 23 Jan 2015 03:52:43 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 78FBBA4; Fri, 23 Jan 2015 12:52:41 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1422013961; bh=HPS+kKPe/XeU/daGToj+8W8efS9bWO3Z3uC5sEoQqD4=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=sa8d+wg7SjAa5p5qNcLw8cGarR1z2Mp5voi3bk3IwM0Qb80GXvfh7MeGRRaDc3Z7k zP/In84gf5OCZciPmzkQ0cN++1Uyj7DOrmF06mZzzSaSudO2lLp7VHTmPK3r9g0c69 /HhAaLGccKwBNRsSa/cyoy7FImX9MGSsQvuJNDSI=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 70F15A3; Fri, 23 Jan 2015 12:52:41 +0100 (CET)
Date: Fri, 23 Jan 2015 12:52:41 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ole Troan <otroan@employees.org>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
In-Reply-To: <440A410F-CC4E-4577-8ED4-B7E606E35D6D@employees.org>
Message-ID: <alpine.DEB.2.02.1501231245230.22729@uplift.swm.pp.se>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <7DC0A974-1D69-41A0-A23E-D8F60D0780B5@employees.org> <alpine.DEB.2.02.1501230847000.22729@uplift.swm.pp.se> <038BA70D-8EDD-4454-83C5-2DE1817BC2DF@employees.org> <alpine.DEB.2.02.1501230934040.22729@uplift.swm.pp.se> <08371EFF-A2F3-4F38-AAB6-B4637BBF8A81@employees.org> <alpine.DEB.2.02.1501231051160.22729@uplift.swm.pp.se> <3E88E95F-47C0-498D-914A-07DFA4B11DB8@darou.fr> <440A410F-CC4E-4577-8ED4-B7E606E35D6D@employees.org>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/NjuyLs0EzT-dxxdPHkiLhKZw8lc>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 11:52:45 -0000

On Fri, 23 Jan 2015, Ole Troan wrote:

> you could do that.
> I think the options we have are:
>
> 1) current specifications (rule 5.5, works as I described)
> 2) Homenet case, all routers advertise all PIOs. depends on redirects
> 3) Extend RFC4191 with source specific routes
> 4) Instead of making ND into a routing protocol just make hosts participate in a real RP.
>
> I have argued for 1, from the standpoint that this is what's most likely to get current hosts to implement today, and it works with two independent routers that doesn't support homenet protocols.

Ok, pasting 5.5 again:

"
    Rule 5.5: Prefer addresses in a prefix advertised by the next-hop.
    If SA or SA's prefix is assigned by the selected next-hop that will
    be used to send to D and SB or SB's prefix is assigned by a different
    next-hop, then prefer SA.  Similarly, if SB or SB's prefix is
    assigned by the next-hop that will be used to send to D and SA or
    SA's prefix is assigned by a different next-hop, then prefer SB.
"

This is still source address selection. What text handles to which 
next-hop the host should send traffic with this SA? RFC 7157 section 6.2 
has some texts on this, but I don't see it answering the question.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Fri Jan 23 04:12:34 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0D661A909B for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 04:12:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q4Ce0OwdNTsH for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 04:12:31 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6523C1A90A8 for <6man@ietf.org>; Fri, 23 Jan 2015 04:12:28 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id D19BE62A8; Fri, 23 Jan 2015 04:12:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=HcatAzg3gdWUGEiUd/BHTcv+gCU=; b=FZX0Z5icxkeROEmB+9 k9AdVCk+lwL24FDHS1jxvt0M9wlQ4Lwz86+WObMr5ecAjKqJmK9QmjO+uOUe3ZzQ O0QmzFKGFMwvOoUmP/xBEN8vkMrhrvMr6oIKDaNf2WGyfDGKjtATUGCs1VBEt0uR OV0Rnfr/riG84olPtsgkqS2Y8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=pEf9fXO/EwhPUGdKTzNidap9B1F0chT8cMbMa72h6s492DDkhtK WB7iL/QUA60ep4Gaeb2vpFI2VQmw3PLooMzmS4JO0PRF+loEBCf6deCNeW4ZkOtz XfAFHu5ihXu0o6XiPw/P9D/vf++7kgiz52ymxneeSNRo7aOlzZq0jwso=
Received: from gomlefisk.localdomain (173-38-208-170.cisco.com [173.38.208.170]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 82ED062A6; Fri, 23 Jan 2015 04:12:26 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 6E0293D374FD; Fri, 23 Jan 2015 13:12:24 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.4\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <alpine.DEB.2.02.1501231245230.22729@uplift.swm.pp.se>
Date: Fri, 23 Jan 2015 13:12:24 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B44F6001-E077-4700-89E4-0C37F78F7DBA@employees.org>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <7DC0A974-1D69-41A0-A23E-D8F60D0780B5@employees.org> <alpine.DEB.2.02.1501230847000.22729@uplift.swm.pp.se> <038BA70D-8EDD-4454-83C5-2DE1817BC2DF@employees.org> <alpine.DEB.2.02.1501230934040.22729@uplift.swm.pp.se> <08371EFF-A2F3-4F38-AAB6-B4637BBF8A81@employees.org> <alpine.DEB.2.02.1501231051160.22729@uplift.swm.pp.se> <3E88E95F-47C0-498D-914A-07DFA4B11DB8@darou.fr> <440A410F-CC4E-4577-8ED4-B7E606E35D6D@employees.org> <alpine.DEB.2.02.1501231245230.22729@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.2070.4)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/WFTKtswS3rvQN_syQjB19ZmicHI>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 12:12:33 -0000

Mikael,

>> you could do that.
>> I think the options we have are:
>>=20
>> 1) current specifications (rule 5.5, works as I described)
>> 2) Homenet case, all routers advertise all PIOs. depends on redirects
>> 3) Extend RFC4191 with source specific routes
>> 4) Instead of making ND into a routing protocol just make hosts =
participate in a real RP.
>>=20
>> I have argued for 1, from the standpoint that this is what's most =
likely to get current hosts to implement today, and it works with two =
independent routers that doesn't support homenet protocols.
>=20
> Ok, pasting 5.5 again:
>=20
> "
>   Rule 5.5: Prefer addresses in a prefix advertised by the next-hop.
>   If SA or SA's prefix is assigned by the selected next-hop that will
>   be used to send to D and SB or SB's prefix is assigned by a =
different
>   next-hop, then prefer SA.  Similarly, if SB or SB's prefix is
>   assigned by the next-hop that will be used to send to D and SA or
>   SA's prefix is assigned by a different next-hop, then prefer SB.
> "
>=20
> This is still source address selection. What text handles to which =
next-hop the host should send traffic with this SA? RFC 7157 section 6.2 =
has some texts on this, but I don't see it answering the question.

right, this text doesn't say exactly what to do if you pick the SA. but =
it isn't a big jump to conclude that you can use the same  coupling =
between source prefix and next-hop.

cheers,
Ole



From nobody Fri Jan 23 04:18:01 2015
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C7C91A90AE for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 04:18:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x7M6ZFJNOaw5 for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 04:17:59 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 254941A90AD for <6man@ietf.org>; Fri, 23 Jan 2015 04:17:59 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id A716BA5; Fri, 23 Jan 2015 13:17:57 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1422015477; bh=GCXH+PD6iP4AFvRkDxpWBPqdckbGVbD4eNkpSsAY9Ek=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=aJeM3kw7/JveUCYlfKScj//qAp6Vz7EnRtwk9sCrMC9AVZNjQ4xCvTV+YRmjDKnRO St/PzFcnuDIum9X0neOJb6ocH9V679kcHOawnw0+Liyw48ccnkrzxUxqV9v/j1oM1X ObCribd/0h41T/BEEtvI8qgqShkjTKqj546alddk=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id A27B9A3; Fri, 23 Jan 2015 13:17:57 +0100 (CET)
Date: Fri, 23 Jan 2015 13:17:57 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ole Troan <otroan@employees.org>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
In-Reply-To: <B44F6001-E077-4700-89E4-0C37F78F7DBA@employees.org>
Message-ID: <alpine.DEB.2.02.1501231316360.22729@uplift.swm.pp.se>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <7DC0A974-1D69-41A0-A23E-D8F60D0780B5@employees.org> <alpine.DEB.2.02.1501230847000.22729@uplift.swm.pp.se> <038BA70D-8EDD-4454-83C5-2DE1817BC2DF@employees.org> <alpine.DEB.2.02.1501230934040.22729@uplift.swm.pp.se> <08371EFF-A2F3-4F38-AAB6-B4637BBF8A81@employees.org> <alpine.DEB.2.02.1501231051160.22729@uplift.swm.pp.se> <3E88E95F-47C0-498D-914A-07DFA4B11DB8@darou.fr> <440A410F-CC4E-4577-8ED4-B7E606E35D6D@employees.org> <alpine.DEB.2.02.1501231245230.22729@uplift.swm.pp.se> <B44F6001-E077-4700-89E4-0C37F78F7DBA@employees.org>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/8b9xwkFz-47tuq-5TdFXRQLkH-k>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 12:18:00 -0000

On Fri, 23 Jan 2015, Ole Troan wrote:

> right, this text doesn't say exactly what to do if you pick the SA. but 
> it isn't a big jump to conclude that you can use the same coupling 
> between source prefix and next-hop.

Do you expect MIF to say this outright, or is that something we should do 
in 6MAN, or both?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Fri Jan 23 09:30:26 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A0CB1A8BC2; Fri, 23 Jan 2015 09:30:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I8lY3m01clCl; Fri, 23 Jan 2015 09:30:11 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 08AEC1A1ADB; Fri, 23 Jan 2015 09:30:11 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-default-iids-02.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p8
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150123173011.18444.83799.idtracker@ietfa.amsl.com>
Date: Fri, 23 Jan 2015 09:30:11 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/f9Dm90z1iDGOu6y_K0VN0DAZt7E>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 17:30:18 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the IPv6 Maintenance Working Group of the IETF.

        Title           : Recommendation on Stable IPv6 Interface Identifiers
        Authors         : Fernando Gont
                          Alissa Cooper
                          Dave Thaler
                          Will Liu
	Filename        : draft-ietf-6man-default-iids-02.txt
	Pages           : 8
	Date            : 2015-01-23

Abstract:
   The IPv6 addressing architecture defines Modified EUI-64 format
   Interface Identifiers, and the existing IPv6 over various link-layers
   specify how such identifiers are derived from the underlying link-
   layer address (e.g., an IEEE LAN MAC address) when employing IPv6
   Stateless Address Autoconfiguration (SLAAC).  The security and
   privacy implications of embedding link-layer addresses in the
   Interface Identifier have been known and understood for some time
   now, and some popular IPv6 implementations have already deviated from
   such schemes to mitigate these issues.  This document changes the
   recommended default Interface Identifier generation scheme to that
   specified in RFC7217, and recommends against embedding link-layer
   addresses in IPv6 Interface Identifiers.  It formally updates
   RFC2464, RFC2467, RFC2470, RFC2491, RFC2492, RFC2497, RFC2590,
   RFC3146, RFC3572, RFC4291, RFC4338, RFC4391, RFC4944, RFC5072, and
   RFC5121, which require IPv6 Interface Identifiers to be derived from
   the underlying link-layer address.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-default-iids/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-default-iids-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-default-iids-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Jan 23 10:41:43 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 680F31A888C for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 10:41:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e51PNu8W5koQ for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 10:41:17 -0800 (PST)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 976641A7113 for <ipv6@ietf.org>; Fri, 23 Jan 2015 10:41:17 -0800 (PST)
Received: from cl-1071.udi-01.br.sixxs.net ([2001:1291:200:42e::2]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fgont@si6networks.com>) id 1YEjAD-00079O-SQ; Fri, 23 Jan 2015 19:41:05 +0100
Message-ID: <54C28EE7.4070704@si6networks.com>
Date: Fri, 23 Jan 2015 15:11:51 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Default IIDs (Re: I-D Action: draft-ietf-6man-default-iids-02.txt)
References: <20150123173011.18444.83799.idtracker@ietfa.amsl.com>
In-Reply-To: <20150123173011.18444.83799.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Z8Vu3k766HaBXAcHduQ8_tDqgfQ>
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@tools.ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 18:41:20 -0000

Folks,

We've posted a revision of the aforementioned I-D. This version is
mostly meant to address:

1) Ralph's comments regarding relaxing the requirements for some
link-layer technologies

2) Comments about our use of hardware addresses (now changed to
link-layer addresses).


This version of the document should be ready for WGLC... but please let
us know if we have missed something.

Thanks,
Fernando




On 01/23/2015 02:30 PM, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the IPv6 Maintenance Working Group of the IETF.
> 
>         Title           : Recommendation on Stable IPv6 Interface Identifiers
>         Authors         : Fernando Gont
>                           Alissa Cooper
>                           Dave Thaler
>                           Will Liu
> 	Filename        : draft-ietf-6man-default-iids-02.txt
> 	Pages           : 8
> 	Date            : 2015-01-23
> 
> Abstract:
>    The IPv6 addressing architecture defines Modified EUI-64 format
>    Interface Identifiers, and the existing IPv6 over various link-layers
>    specify how such identifiers are derived from the underlying link-
>    layer address (e.g., an IEEE LAN MAC address) when employing IPv6
>    Stateless Address Autoconfiguration (SLAAC).  The security and
>    privacy implications of embedding link-layer addresses in the
>    Interface Identifier have been known and understood for some time
>    now, and some popular IPv6 implementations have already deviated from
>    such schemes to mitigate these issues.  This document changes the
>    recommended default Interface Identifier generation scheme to that
>    specified in RFC7217, and recommends against embedding link-layer
>    addresses in IPv6 Interface Identifiers.  It formally updates
>    RFC2464, RFC2467, RFC2470, RFC2491, RFC2492, RFC2497, RFC2590,
>    RFC3146, RFC3572, RFC4291, RFC4338, RFC4391, RFC4944, RFC5072, and
>    RFC5121, which require IPv6 Interface Identifiers to be derived from
>    the underlying link-layer address.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-default-iids/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6man-default-iids-02
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-default-iids-02
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Fri Jan 23 11:39:40 2015
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 617611A000A for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 11:39:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nJB00uMR1EU1 for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 11:39:15 -0800 (PST)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 656461A0006 for <6man@ietf.org>; Fri, 23 Jan 2015 11:39:14 -0800 (PST)
Received: by mail-lb0-f180.google.com with SMTP id b6so8737365lbj.11 for <6man@ietf.org>; Fri, 23 Jan 2015 11:39:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=xeby2QC186Xwc89bL+9z6ziGktqj1pCIY7TI1s5KNAQ=; b=UpfbwilGUEFRSCpWQssbI7h9USG7AJSvWyTYa5nVlI+29nOOm5Wny8HVcfMC0iAnQR Uh8gh/nN3gLqqo1kJD/z6Poo66zjWt20kNu5gDv0LCltt4PjWl99Gn+vMzJCxX564X2c BYsnuSNDKkXKOR2rqzaJxU3rLHYbtj9aB4UybylPiLtElbYiOYdZ65Rpc+7w7azcRaZw lUNflIaCry//bU6W5PT+1OKHY0Bg04soxniXz4wp9kgmkCuIBL3zCZ0a+3wcRNtb57N6 bDJ3ycgkfBkvDmVhNb3UlYxqKAQciUVwu3u6Yx0qw7LgRXSbTJ8KuaJs0LwAujQeP/Kj Zl6g==
MIME-Version: 1.0
X-Received: by 10.152.219.3 with SMTP id pk3mr9154261lac.19.1422041952830; Fri, 23 Jan 2015 11:39:12 -0800 (PST)
Received: by 10.114.80.231 with HTTP; Fri, 23 Jan 2015 11:39:12 -0800 (PST)
In-Reply-To: <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr>
Date: Fri, 23 Jan 2015 13:39:12 -0600
Message-ID: <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Pierre Pfister <pierre.pfister@darou.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Scg6IeoVRtRwW1cTUinaMKPmdwY>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 19:39:16 -0000

 Hi Pierre,

On Thu, Jan 22, 2015 at 3:30 AM, Pierre Pfister <pierre.pfister@darou.fr> w=
rote:
> Hello Lorenzo, Ole and Behcet,
>
>>
>> I feel strongly that configuration option that allows a router to specif=
y another on-link next hop (or, even worse, a next hop on another interface=
) is a bad idea because it breaks the fate-sharing properties provided by R=
As.
>>
>
> I fully agree there. If another router should be next-hop, then that othe=
r router can send RAs by itself.
>
>> If all that is necessary is a means to tell the host what source address=
 to prefer for what prefixes, then we already have a DHCP option for that.
>>
>> Looking at the scenarios, I don't see anything that requires any new wor=
k to solve.
>>
>> Figure 1:
>> Case 1: rtr1 and rtr2 are connected to different interfaces on the host =
(e.g., wifi and 3G), This is solved by rule 5 in RFC 6724.
>> Case 2: rtr1 and rtr2 are connected to the same interface on the host. T=
his is solved by SADR forwarding between rtr1 and rtr2 with no host changes=
.
>
> Yes, but if we rely on routers=E2=80=99 capabilities only, we will have s=
uboptimal routing. e.g., the next-hop will send the packet back on the same=
 link. Which would halve the throughput.
> And if we rely on redirects, well=E2=80=A6 Redirects are not source-speci=
fic, so we may have redirect ping-pongs between the two routers.
>
>>
>> Figure 2: solved by implementing SADR in the router. The router already =
has the information it needs. In the case of specialized address routing, t=
hat's solved using the DHCPv6 address selection policy option (RFC 7078).
>>
>> Figure 3: Same as case 2 in Figure 1; solved by rule 5 in RFC 6724.
>>
>> Figure 4: Same as case 1 in Figure 1; solved by SADR forwarding between =
rtr1 and rtr2. Better performance if the host implements rule 5.5 in RFC 67=
24.
>>
>> Figure 5: Solved by SADR forwarding between rtr, rtrE and rtrF.
>
>
> Something bugs me in general with the source address selection process.
>
> If we assume the host is dumb, it will first select the next-hop/oif and =
pick the source address using rule 5 or rule 5.5.
> If we assume the host is clever, it will first select the source-address =
based on the information it has (e.g., DHCPv6 address selection). But how i=
s it supposed to select the next-hop then ? rule 5 and 5.5 solve source add=
ress selection when you know the next hop, but not next-hop selection when =
you know the source address.
>
> In other words, when you say DHCPv6 address selection policy solves the i=
ssue, you say the host should select the address based on configuration, wh=
ich implies that you do that before you pick the next hop.
> But when you say rule 5 or 5.5 solve the issue, you assume the next-hop h=
as already been selected. So, picking each figure and propose different sol=
utions which seems to exclude each other seems unfair to me.
>
> Source address selection by the host/application is, IMHO, the simplest a=
pproach to upstream selection, as it reduces interface/next-hop/cpe selecti=
on to the selection of a single element. Homenet is moving toward this kind=
 of solutions. But once the application or host has chosen the source addre=
ss, we need some process to select the next hop.
>
> When I ask myself =E2=80=98where should we pick the next-hop=E2=80=99=E2=
=80=A6 The routing table seems to be the answer. And if we consider we want=
 different next hops depending on the source address, source-dest routing l=
ooks like the right thing to do to me.
>
> Now, either we require hosts to look at PIOs and always add source-routes=
 based on the RAs they receive (which means the router hides things to the =
host and the host hacks a solution to deal with it - and it may not always =
work), or we provide a longer-term solution where routers tell the truth to=
 hosts.
>
> I disagree with the overall approach of this draft. I think what we need =
is a source-specific extension to RFC4191. With only one single new option =
similar to RIOs but with a source-prefix included.


I am not sure if you read Section 5.2 in this draft and Section 13 in
draft-sarikaya-6man-next-hop-ra-04?
I had these in an effort to satisfy your concerns. Your mails seems to
indicate that you did not even read them.
Poor me :-)

I can see from this long discussion thread that some people, e.g.
Mikael are soliciting all RA based solutions. I am OK with it.
But RFC 7157 which Ole, et al. wrote seems to advocate DHCPv6 based
approach. That was the reason I wrote DHCP solution draft.

Regards,

Behcet
>
> Cheers,
>
> - Pierre
>
>
>
>


From nobody Fri Jan 23 12:12:04 2015
Return-Path: <jhw@nestlabs.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B7F71A03A5 for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 12:11:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fe1eXg5NtZMh for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 12:11:31 -0800 (PST)
Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE6D71A039A for <ipv6@ietf.org>; Fri, 23 Jan 2015 12:11:30 -0800 (PST)
Received: by mail-ob0-f182.google.com with SMTP id gq1so9084321obb.13 for <ipv6@ietf.org>; Fri, 23 Jan 2015 12:11:30 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=jlzkZsnbgv20Drdn1/ta9B8Nf9qvTyj0/4KbojJqIbs=; b=HEd7T4PqcNZnfYY1MVEnDfceV61MT5tmfrjVCb1vi4Kf74LTlEfye6XCOzS7bipEeB VAfX4g0qj+i3BfZ/t91lrCkg1kB/97bWcJZDoptTWdX/WRGJSEDHMJRDpACkZXtBE6Uk qVmutqkrnxGas5iQu9GHyb3u17Yj9rmyywWDsaTXJHuH61ecgYyKckqQqg/TpHJEW1U7 UGs7oNAcFRFEjZcFNqOD60niYMYnsUgI7TsPCA4yMZVbKfllpBIvmesKPOleAPevNyBN yrgDekTq5KSyq4AxRUO2B11/KFM8Wj7F6jymkXnzaOMyivJn4fcSf1gyMyPoY1Zc3+HP J/ww==
X-Gm-Message-State: ALoCoQkF7KBaGUcnILw0N6OWM5XEy54e5c79r9oVq562gx+u1UA2/65X1iMUCtDvl/Nx3nU48KgJ
MIME-Version: 1.0
X-Received: by 10.182.44.132 with SMTP id e4mr5591638obm.86.1422043890201; Fri, 23 Jan 2015 12:11:30 -0800 (PST)
Received: by 10.76.150.2 with HTTP; Fri, 23 Jan 2015 12:11:30 -0800 (PST)
In-Reply-To: <20150123173011.18444.83799.idtracker@ietfa.amsl.com>
References: <20150123173011.18444.83799.idtracker@ietfa.amsl.com>
Date: Fri, 23 Jan 2015 12:11:30 -0800
Message-ID: <CADhXe52m97Pk4PxY=iu5mbWaK8ZGmQMzwEO5MfNDfi5SjJywVg@mail.gmail.com>
Subject: Re: I-D Action: draft-ietf-6man-default-iids-02.txt
From: James Woodyatt <jhw@nestlabs.com>
To: 6man WG <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c2f49aee4fdc050d576440
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/kVV7CkCIrHj6N3hf4m_5erY9Gvg>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 20:11:40 -0000

--001a11c2f49aee4fdc050d576440
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Everyone=E2=80=94

Link layers MUST define a mechanism that provides that mitigates the
> security and privacy implications discussed in Section 1.


Editorial nit: "that provides that mitigates" seems like an awkward phrase,
and I'm not sure what it means. This is a pretty important requirement
specification, so I'd like to see it written with optimal clarity. How
about this for starters:

  Link layers MUST define a mechanism that provides mitigation of the
security and privacy issues discussed in section 1.


On Fri, Jan 23, 2015 at 9:30 AM, <internet-drafts@ietf.org> wrote:

>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
>  This draft is a work item of the IPv6 Maintenance Working Group of the
> IETF.
>
>         Title           : Recommendation on Stable IPv6 Interface
> Identifiers
>         Authors         : Fernando Gont
>                           Alissa Cooper
>                           Dave Thaler
>                           Will Liu
>         Filename        : draft-ietf-6man-default-iids-02.txt
>         Pages           : 8
>         Date            : 2015-01-23
>
> Abstract:
>    The IPv6 addressing architecture defines Modified EUI-64 format
>    Interface Identifiers, and the existing IPv6 over various link-layers
>    specify how such identifiers are derived from the underlying link-
>    layer address (e.g., an IEEE LAN MAC address) when employing IPv6
>    Stateless Address Autoconfiguration (SLAAC).  The security and
>    privacy implications of embedding link-layer addresses in the
>    Interface Identifier have been known and understood for some time
>    now, and some popular IPv6 implementations have already deviated from
>    such schemes to mitigate these issues.  This document changes the
>    recommended default Interface Identifier generation scheme to that
>    specified in RFC7217, and recommends against embedding link-layer
>    addresses in IPv6 Interface Identifiers.  It formally updates
>    RFC2464, RFC2467, RFC2470, RFC2491, RFC2492, RFC2497, RFC2590,
>    RFC3146, RFC3572, RFC4291, RFC4338, RFC4391, RFC4944, RFC5072, and
>    RFC5121, which require IPv6 Interface Identifiers to be derived from
>    the underlying link-layer address.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-default-iids/
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6man-default-iids-02
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-default-iids-02
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>



--=20
james woodyatt <jhw@nestlabs.com>
Nest Labs, Communications Engineering

--001a11c2f49aee4fdc050d576440
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Everyone=E2=80=94<div><br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left=
-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Link laye=
rs MUST define a mechanism that provides that mitigates the security and pr=
ivacy implications discussed in Section 1.</blockquote><div><br></div><div>=
Editorial nit: &quot;that provides that mitigates&quot; seems like an awkwa=
rd phrase, and I&#39;m not sure what it means. This is a pretty important r=
equirement specification, so I&#39;d like to see it written with optimal cl=
arity. How about this for starters:</div><div><br></div><div>=C2=A0 Link la=
yers MUST define a mechanism that provides mitigation of the security and p=
rivacy issues discussed in section 1.</div><div><br></div></div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Jan 23, 2015 at 9:3=
0 AM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:internet-drafts@ietf.org" ta=
rget=3D"_blank">internet-drafts@ietf.org</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex"><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
=C2=A0This draft is a work item of the IPv6 Maintenance Working Group of th=
e IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Recommendation on Stable IPv6 Interface Identifiers<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Fern=
ando Gont<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Alissa Cooper<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Dave Thaler<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Will Liu<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-6man-default-iids-02.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 8<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2015-01-23<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0The IPv6 addressing architecture defines Modified EUI-64 forma=
t<br>
=C2=A0 =C2=A0Interface Identifiers, and the existing IPv6 over various link=
-layers<br>
=C2=A0 =C2=A0specify how such identifiers are derived from the underlying l=
ink-<br>
=C2=A0 =C2=A0layer address (e.g., an IEEE LAN MAC address) when employing I=
Pv6<br>
=C2=A0 =C2=A0Stateless Address Autoconfiguration (SLAAC).=C2=A0 The securit=
y and<br>
=C2=A0 =C2=A0privacy implications of embedding link-layer addresses in the<=
br>
=C2=A0 =C2=A0Interface Identifier have been known and understood for some t=
ime<br>
=C2=A0 =C2=A0now, and some popular IPv6 implementations have already deviat=
ed from<br>
=C2=A0 =C2=A0such schemes to mitigate these issues.=C2=A0 This document cha=
nges the<br>
=C2=A0 =C2=A0recommended default Interface Identifier generation scheme to =
that<br>
=C2=A0 =C2=A0specified in RFC7217, and recommends against embedding link-la=
yer<br>
=C2=A0 =C2=A0addresses in IPv6 Interface Identifiers.=C2=A0 It formally upd=
ates<br>
=C2=A0 =C2=A0RFC2464, RFC2467, RFC2470, RFC2491, RFC2492, RFC2497, RFC2590,=
<br>
=C2=A0 =C2=A0RFC3146, RFC3572, RFC4291, RFC4338, RFC4391, RFC4944, RFC5072,=
 and<br>
=C2=A0 =C2=A0RFC5121, which require IPv6 Interface Identifiers to be derive=
d from<br>
=C2=A0 =C2=A0the underlying link-layer address.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-6man-default-iids/" =
target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-6man-default-=
iids/</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-6man-default-iids-02" targ=
et=3D"_blank">http://tools.ietf.org/html/draft-ietf-6man-default-iids-02</a=
><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-default-iids-=
02" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-de=
fault-iids-02</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
--------------------------------------------------------------------<br>
IETF IPv6 working group mailing list<br>
<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listinfo/i=
pv6" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
--------------------------------------------------------------------<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature"><div dir=3D"ltr">james woodyatt &lt;<a href=3D"mailto:=
jhw@nestlabs.com" target=3D"_blank">jhw@nestlabs.com</a>&gt;<div>Nest Labs,=
 Communications Engineering</div></div></div>
</div>

--001a11c2f49aee4fdc050d576440--


From nobody Fri Jan 23 12:32:01 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E5851A1BDF for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 12:31:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QSZ5ypNznhPk for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 12:31:38 -0800 (PST)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5ADF1A000F for <ipv6@ietf.org>; Fri, 23 Jan 2015 12:31:37 -0800 (PST)
Received: from cl-1071.udi-01.br.sixxs.net ([2001:1291:200:42e::2]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fgont@si6networks.com>) id 1YEkt8-0001TL-6J; Fri, 23 Jan 2015 21:31:30 +0100
Message-ID: <54C2AF7F.1000708@si6networks.com>
Date: Fri, 23 Jan 2015 17:30:55 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: James Woodyatt <jhw@nestlabs.com>, 6man WG <ipv6@ietf.org>
Subject: Re: I-D Action: draft-ietf-6man-default-iids-02.txt
References: <20150123173011.18444.83799.idtracker@ietfa.amsl.com> <CADhXe52m97Pk4PxY=iu5mbWaK8ZGmQMzwEO5MfNDfi5SjJywVg@mail.gmail.com>
In-Reply-To: <CADhXe52m97Pk4PxY=iu5mbWaK8ZGmQMzwEO5MfNDfi5SjJywVg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/QRix3LsxbQKQ0FSY1ZdJuH9viFU>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 20:31:40 -0000

Hi, James,

On 01/23/2015 05:11 PM, James Woodyatt wrote:
> Everyone—
> 
>     Link layers MUST define a mechanism that provides that mitigates the
>     security and privacy implications discussed in Section 1.
> 
> 
> Editorial nit: "that provides that mitigates" seems like an awkward
> phrase, and I'm not sure what it means. This is a pretty important
> requirement specification, so I'd like to see it written with optimal
> clarity. How about this for starters:
> 
>   Link layers MUST define a mechanism that provides mitigation of the
> security and privacy issues discussed in section 1.

You're right (my bad!) -- will get this fixed in the next rev.

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Fri Jan 23 14:34:18 2015
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2BDD1A6EDB for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 14:34:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.498
X-Spam-Level: 
X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c_L4NwZ2kvI2 for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 14:34:14 -0800 (PST)
Received: from nm19-vm0.bullet.mail.bf1.yahoo.com (nm19-vm0.bullet.mail.bf1.yahoo.com [98.139.213.162]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 324441A1B1C for <ipv6@ietf.org>; Fri, 23 Jan 2015 14:34:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s2048;  t=1422052453; bh=ys+1CoqNEv1PQEz52IdTZB7Y0BWIV577rrw2FMS2NDM=;  h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject;  b=qvu5lfw3IlT1dINDn9wa80ZUyUDmYWJqxnsY13Z7xseVrflvmtEUGL+jq4z497OhrbUw8veTKB6GUyKU+CSy1vs6an5NbqLw5P/OGYlXon9flQB0vxrNzN0GVku4Z9NBd9nC0AAwUj5Gv37/FgvzY5UviuAOuzuVDF5VKIg2lx8ZuA7f6REV6m9l8m/TJl5A8ZrPo31rYk8Yv5l9osMDzp7m3EZJuPCoaT7PHET1Vc7KQ3jO7drgkU1euUITAK++4WTD1B4gvnVRBf4GzID281LQPa09qaa3W1EVSoSNRQrVpobG53U664scNx36l/8O/qrVD7M/I7V+ui1GcE77Zw==
Received: from [66.196.81.174] by nm19.bullet.mail.bf1.yahoo.com with NNFMP; 23 Jan 2015 22:34:13 -0000
Received: from [98.139.212.239] by tm20.bullet.mail.bf1.yahoo.com with NNFMP;  23 Jan 2015 22:34:13 -0000
Received: from [127.0.0.1] by omp1048.mail.bf1.yahoo.com with NNFMP; 23 Jan 2015 22:34:13 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 322483.12010.bm@omp1048.mail.bf1.yahoo.com
X-YMail-OSG: VnFIgN8VM1nwDs3_pHvseTzoLQ6ZF6S7xn.svgOk2Py45RxHd5YYTSZVX3Kcu0S PO1oDr.H.ppl0agv1b0tNGRs9NezODelIAI.Pp.Z9jfED8PREJOKkqIm8twHfRKZx.5ff5.q52qU 5_9E7qQ1Hqy.MGsjIeE.bJQOlr0m1SxR8eQvD1fohfCYT4Nm9TToDuqi943a1xOgEX9eQFhpSkxM jimgvMkiMqCY0wCxuyZ3ncTwBLfh7zHblYWgdLBX_Gs2SjyyXyewjSDYI1aUyyM0tWnETX5yyFCI JOJ2s2B2Ut6mK420s7H.a_3FVBxvgqTnD9BBAGxp7PR8TQR.9H06T3WHayvEvAt4_Z9x1Dxc.wKv Ouny_l_eTXDII.Tsc6MRWV42mYuTxDuurBN_FUATlzw5jj5IwSrsP89OIk8SPPzDWyOvaqtC3B2_ alke0ZePda8ehfTOV5LfzyoqcfrC1Fcx3zsGhFrsB07fLmZWWzXmxQ6AXKmniX4UsYfqNHfJQ1dl gHqB3iE85qaBEonhB7yqFXmQulGcPSryV0kuNimZuRCI2Zg--
Received: by 76.13.27.133; Fri, 23 Jan 2015 22:34:12 +0000 
Date: Fri, 23 Jan 2015 22:34:12 +0000 (UTC)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
To: Fernando Gont <fgont@si6networks.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Message-ID: <475654542.413561.1422052452324.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <54C28EE7.4070704@si6networks.com>
References: <54C28EE7.4070704@si6networks.com>
Subject: Re: Default IIDs (Re: I-D Action: draft-ietf-6man-default-iids-02.txt)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/uIiqvOVdMonYgBp8gr6wsPBLz3k>
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@tools.ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 22:34:17 -0000

Hi,

I think there is a bit of a mismatch between the ID's title and the contents. I think the title is a bit too general when the ID is only specific to the SLAAC methods of address generation and address configuration.


I'd much prefer to see the title left as it is and the advice extended to 

- the use of RFC7217 like IIDs as a default policy for stateful DHCPv6 (i.e., draft-ietf-dhc-stable-privacy-addresses), unless overridden by the stateful DHCPv6 operator (as a side note and to support advising on a default DHCPv6 address generation policy, the current version of OpenWRT comes with both SLAAC and stateful DHCPv6 addressing enabled by default (not sure why though).)


- a bit of advice that manually/statically generated and configured interface IDs should also be chosen with these sorts of properties too


Alternatively, I think the title needs to be changed to something like "Recommendation on Stable SLAAC IPv6 Interface Identifiers"

Regards,
Mark.



________________________________
From: Fernando Gont <fgont@si6networks.com>
To: ipv6@ietf.org 
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>; "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@tools.ietf.org>; Ralph Droms <rdroms.ietf@gmail.com> 
Sent: Saturday, 24 January 2015, 5:11
Subject: Default IIDs (Re: I-D Action: draft-ietf-6man-default-iids-02.txt)


Folks,

We've posted a revision of the aforementioned I-D. This version is
mostly meant to address:

1) Ralph's comments regarding relaxing the requirements for some
link-layer technologies

2) Comments about our use of hardware addresses (now changed to
link-layer addresses).


This version of the document should be ready for WGLC... but please let
us know if we have missed something.

Thanks,
Fernando




On 01/23/2015 02:30 PM, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the IPv6 Maintenance Working Group of the IETF.
> 
>         Title           : Recommendation on Stable IPv6 Interface Identifiers
>         Authors         : Fernando Gont
>                           Alissa Cooper
>                           Dave Thaler
>                           Will Liu
>     Filename        : draft-ietf-6man-default-iids-02.txt
>     Pages           : 8
>     Date            : 2015-01-23
> 
> Abstract:
>    The IPv6 addressing architecture defines Modified EUI-64 format
>    Interface Identifiers, and the existing IPv6 over various link-layers
>    specify how such identifiers are derived from the underlying link-
>    layer address (e.g., an IEEE LAN MAC address) when employing IPv6
>    Stateless Address Autoconfiguration (SLAAC).  The security and
>    privacy implications of embedding link-layer addresses in the
>    Interface Identifier have been known and understood for some time
>    now, and some popular IPv6 implementations have already deviated from
>    such schemes to mitigate these issues.  This document changes the
>    recommended default Interface Identifier generation scheme to that
>    specified in RFC7217, and recommends against embedding link-layer
>    addresses in IPv6 Interface Identifiers.  It formally updates
>    RFC2464, RFC2467, RFC2470, RFC2491, RFC2492, RFC2497, RFC2590,
>    RFC3146, RFC3572, RFC4291, RFC4338, RFC4391, RFC4944, RFC5072, and
>    RFC5121, which require IPv6 Interface Identifiers to be derived from
>    the underlying link-layer address.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-default-iids/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6man-default-iids-02
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-default-iids-02
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492







--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------


From nobody Fri Jan 23 15:12:34 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 709651AD0C4 for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 15:12:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id puAA6a461DHm for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 15:12:29 -0800 (PST)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDDCD1A882C for <ipv6@ietf.org>; Fri, 23 Jan 2015 15:12:29 -0800 (PST)
Received: from cl-1071.udi-01.br.sixxs.net ([2001:1291:200:42e::2]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fgont@si6networks.com>) id 1YEnOl-0002HW-Nh; Sat, 24 Jan 2015 00:12:20 +0100
Message-ID: <54C2D52D.6000307@si6networks.com>
Date: Fri, 23 Jan 2015 20:11:41 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>,  "ipv6@ietf.org" <ipv6@ietf.org>
Subject: Re: Default IIDs (Re: I-D Action: draft-ietf-6man-default-iids-02.txt)
References: <54C28EE7.4070704@si6networks.com> <475654542.413561.1422052452324.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <475654542.413561.1422052452324.JavaMail.yahoo@mail.yahoo.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/f5QxlbgE--KbCEoWW86SHzAi93U>
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@tools.ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 23:12:32 -0000

Hi, Mark,

On 01/23/2015 07:34 PM, Mark ZZZ Smith wrote:
> 
> I think there is a bit of a mismatch between the ID's title and the
> contents. I think the title is a bit too general when the ID is only
> specific to the SLAAC methods of address generation and address
> configuration.
> 
> I'd much prefer to see the title left as it is and the advice
> extended to
> 
> - the use of RFC7217 like IIDs as a default policy for stateful
> DHCPv6 (i.e., draft-ietf-dhc-stable-privacy-addresses), unless
> overridden by the stateful DHCPv6 operator (as a side note and to
> support advising on a default DHCPv6 address generation policy, the
> current version of OpenWRT comes with both SLAAC and stateful DHCPv6
> addressing enabled by default (not sure why though).)

You make a good observation. What you suggest sound sensible (although
default-iids has reqs for hosts, while
draft-ietf-dhc-stable-privacy-addresses would apply to servers). What do
other folks think?

(FWIW, what do you mean by "both enabled by default"? Since DHCPv6 is
triggered by having the relevant bits of RA messages set appropriately,
I think it make sense to have the "DHCPv6 machinery" enabled by
default.. or did I miss something?)



> - a bit of advice that manually/statically generated and configured
> interface IDs should also be chosen with these sorts of properties
> too

Well. this wouldn't be "default iids", so... I guess we could leave them
out?



> Alternatively, I think the title needs to be changed to something
> like "Recommendation on Stable SLAAC IPv6 Interface Identifiers"

Having words on the DHCPv6 IIDs sound sensible. But I can certainly live
with this other alternative option.

What does the wg think about this?

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Fri Jan 23 15:51:45 2015
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A55291A88FF for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 15:51:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.498
X-Spam-Level: 
X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2KuCuUuROcXS for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 15:51:41 -0800 (PST)
Received: from nm10-vm0.bullet.mail.bf1.yahoo.com (nm10-vm0.bullet.mail.bf1.yahoo.com [98.139.213.147]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82FDA1A88CB for <ipv6@ietf.org>; Fri, 23 Jan 2015 15:51:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s2048;  t=1422057097; bh=gEpsEbRlFrTT4bT48mWHaexKUTdpiIAn5yXVZmjLTZ8=;  h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject;  b=NkHeSWF8VdJ1NK3I+V417dwol8Lkm0Z9CM9DSGe2sGSi/XKKPT+hHr2MOGoqX/H8wGIT73FT4+qQ0kRFqLpXzdjI/oQuTXF3CI80Z+Ajsok+7tNla1o1VB880Ow5DQ9iTm8lxoNz4+0nOmfgxEPKdOXSQdGNZbEwihiar6aWXxvLKNVEq9S/PE3qPb0XgrpC40HuQBkEhm5MzAJgCop+YuFHf98MdLJAtsZxfdLj31rP36NWkD4As5wiTQQfJyXIl0lzaU6gJxx6UfI3DoOC7NoFzX1zXmDbzYtKDqoLczEHgNTSKsyv6ESynbaTXvsb2InlN8HaqF/o4/iZAoFsYw==
Received: from [98.139.215.143] by nm10.bullet.mail.bf1.yahoo.com with NNFMP;  23 Jan 2015 23:51:37 -0000
Received: from [98.139.212.234] by tm14.bullet.mail.bf1.yahoo.com with NNFMP;  23 Jan 2015 23:51:37 -0000
Received: from [127.0.0.1] by omp1043.mail.bf1.yahoo.com with NNFMP; 23 Jan 2015 23:51:37 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 641326.41396.bm@omp1043.mail.bf1.yahoo.com
X-YMail-OSG: zdr3cGQVM1m1tGaahBRHeCwc2nP2OEXXkxZ0l9wEgCWuVjhGCxHH9kE17WX0s05 UI0g8bzMV_U3KD.YBmvkfJGKXU97Mv9L7I0SIIKSeqDVZcnSM4IB8hU.7zDJ6XyS2OaNNF3E7H_I 8dqCtH6gxvejPPagOf7DFy_7l.T9dMxvdcpveuvjPK5KNs2KeBvSQH_ORLPQ57pE.j48fG4xXp7D s5XmtGgbs917R4MLyMJOLsxEZCJ_wXvlzB7IlGhlHb8n1g1LmOg7xeJPK7eqEEG3eL4ZAzdKP7xx LUcxZMFHFFkEnkuosvcEa22LnaxZSbHaUXCixkrUk.r4vbqw2MvIOPu794BVxSTE1u4g.keRtlVq XEPBhI2kscIqpdTvIpELWNwGdT7QgcDddwjFM6FGEZF5m8srMpYw26ntJp7L97z04yW_IThRz9ZW cJOcaHGxooltCnD3xEhPPeL5MDShTOuwYzHe.wyd11fIOJzhx.__h6UDXtexEyNDXb75rMRSeKlB 02Zou3swAXdhEA.JNYpf__IXCkTFFi9USfIeJGdLE1aFeWg--
Received: by 66.196.80.118; Fri, 23 Jan 2015 23:51:37 +0000 
Date: Fri, 23 Jan 2015 23:51:07 +0000 (UTC)
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
To: Fernando Gont <fgont@si6networks.com>, "ipv6@ietf.org" <ipv6@ietf.org>
Message-ID: <714570460.442496.1422057067484.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <54C2D52D.6000307@si6networks.com>
References: <54C2D52D.6000307@si6networks.com>
Subject: Re: Default IIDs (Re: I-D Action: draft-ietf-6man-default-iids-02.txt)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Y2dISkE5qcp3ncSMU1t0Lsm-koQ>
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@tools.ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Jan 2015 23:51:42 -0000

Hi Fernando,


----- Original Message -----
From: Fernando Gont <fgont@si6networks.com>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>; "ipv6@ietf.org" <ipv6@ietf.org>
Cc: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>; "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@tools.ietf.org>; Ralph Droms <rdroms.ietf@gmail.com>
Sent: Saturday, 24 January 2015, 10:11
Subject: Re: Default IIDs (Re: I-D Action: draft-ietf-6man-default-iids-02.txt)

Hi, Mark,

On 01/23/2015 07:34 PM, Mark ZZZ Smith wrote:
> 
> I think there is a bit of a mismatch between the ID's title and the
> contents. I think the title is a bit too general when the ID is only
> specific to the SLAAC methods of address generation and address
> configuration.
> 
> I'd much prefer to see the title left as it is and the advice
> extended to
> 
> - the use of RFC7217 like IIDs as a default policy for stateful
> DHCPv6 (i.e., draft-ietf-dhc-stable-privacy-addresses), unless
> overridden by the stateful DHCPv6 operator (as a side note and to
> support advising on a default DHCPv6 address generation policy, the
> current version of OpenWRT comes with both SLAAC and stateful DHCPv6
> addressing enabled by default (not sure why though).)

You make a good observation. What you suggest sound sensible (although
default-iids has reqs for hosts, while
draft-ietf-dhc-stable-privacy-addresses would apply to servers). What do
other folks think?


* So perhaps that is further evidence that the title is currently a bit too general - I interpret the title mean advice on choosing stable IID values, regardless of what device or method is used to generate or choose them ("Recommendation on Stable IPv6 Interface Identifiers"). In the case of SLAAC that is the host, in the case of stateful DHCPv6, that is the DHCPv6 server, and in the case of manual/static, that is the operator. I think the primary and fundamental motivation for using manual/static addresses has always been to have stable IDs, so people might even interpret the current title to mean it only applies to the choice of manual/static addresses and not SLAAC (and possibly stateful DHCPv6).

(FWIW, what do you mean by "both enabled by default"? Since DHCPv6 is
triggered by having the relevant bits of RA messages set appropriately,
I think it make sense to have the "DHCPv6 machinery" enabled by
default.. or did I miss something?)

* I meant that a stateful DHCPv6 server is enabled by default on OpenWRT, in parallel with RAs with PIOs with their A bit set too ("SLAAC enabled" by default) - and a few of my hosts that are stateful DHCPv6 enabled by default (Fedora 20/21) are getting addresses using both SLAAC and stateful DHCPv6. I thought and broadly still think that it would be more common for SLAAC to be enabled by default on a link and an operator would choose to enable stateful DHCPv6 (and probably then disable SLAAC). That is why I'm little surprised that OpenWRT enables stateful DHCPv6 by default, however I think that then means that advice on default IID selection for stateful DHCPv6 becomes more useful as there is at least one instance where stateful DHCPv6 has been enabled by default 'in the wild'.


> - a bit of advice that manually/statically generated and configured
> interface IDs should also be chosen with these sorts of properties
> too

Well. this wouldn't be "default iids", so... I guess we could leave them
out?

* That's a good point, there is of course no such thing as a 'default' manually generated IID. I'd see text regarding advice on choosing IID values for static addresses as more of a side note or passing comment, just to cover it off somewhere (perhaps as the title might imply that it is covered), as it is currently the third alternative method of address generation and configuration to SLAAC and stateful DHCPv6.


Regards,
Mark.

> Alternatively, I think the title needs to be changed to something
> like "Recommendation on Stable SLAAC IPv6 Interface Identifiers"

Having words on the DHCPv6 IIDs sound sensible. But I can certainly live
with this other alternative option.

What does the wg think about this?


Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492


From nobody Fri Jan 23 16:40:36 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C9571A0040 for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 16:40:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q60utQpaOA5V for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 16:40:33 -0800 (PST)
Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BCD01A0100 for <ipv6@ietf.org>; Fri, 23 Jan 2015 16:40:33 -0800 (PST)
Received: by mail-pd0-f171.google.com with SMTP id fp1so827028pdb.2 for <ipv6@ietf.org>; Fri, 23 Jan 2015 16:40:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=vuT0tkAd3+bf5InQV+UNCuzsPX2vwdF7So+nocZ/Tn8=; b=Ax5nkbBWfakEYmC3kDtn2ydVZukLssrwxSFlcsnG6xYfriIfWPNAH/ttFdi0nDY5Mq D20X8++u4Hfnn+ViAHafTdhSvgb/6trDOX1ThpdyQy8Mq/FozUss6Xr6rxWh4+dYAR4v sZw8FO2ZMUqt8QJc6OT4rQcaRKLlIr8HBUM+Txq6DEEx4BcnG/pElE64iwCcgf/zjmyQ U1tJ23hcn6OHpSfzOKb17TfbdIcm1iJVySnKbObq+baZh8C0Syr5U/FmoMkgMv2NMmGD t8xKXNF/VD4GM4dHS+hj5QNUd8/9DHivHjjXPFLcukMSUDYbnP4KiszJt6c5kQPQPBm3 /iDQ==
X-Received: by 10.70.29.67 with SMTP id i3mr15751279pdh.132.1422060032614; Fri, 23 Jan 2015 16:40:32 -0800 (PST)
Received: from [192.168.171.21] ([119.225.211.122]) by mx.google.com with ESMTPSA id rb5sm3080121pab.14.2015.01.23.16.40.29 for <ipv6@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 23 Jan 2015 16:40:31 -0800 (PST)
Message-ID: <54C2EA04.1040503@gmail.com>
Date: Sat, 24 Jan 2015 13:40:36 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: 6man <ipv6@ietf.org>
Subject: Re: I-D Action: draft-ietf-6man-default-iids-02.txt
References: <20150123173011.18444.83799.idtracker@ietfa.amsl.com>
In-Reply-To: <20150123173011.18444.83799.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/9f_IgOE2rz50YD49MtzZMGtHc9M>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Jan 2015 00:40:35 -0000

I'm all for this draft.

I think it might benefit from informational references to
RFC 7136 and RFC 7421, as context for the reader.

Regards
   Brian

On 24/01/2015 06:30, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the IPv6 Maintenance Working Group of the IETF.
> 
>         Title           : Recommendation on Stable IPv6 Interface Identifiers
>         Authors         : Fernando Gont
>                           Alissa Cooper
>                           Dave Thaler
>                           Will Liu
> 	Filename        : draft-ietf-6man-default-iids-02.txt
> 	Pages           : 8
> 	Date            : 2015-01-23
> 
> Abstract:
>    The IPv6 addressing architecture defines Modified EUI-64 format
>    Interface Identifiers, and the existing IPv6 over various link-layers
>    specify how such identifiers are derived from the underlying link-
>    layer address (e.g., an IEEE LAN MAC address) when employing IPv6
>    Stateless Address Autoconfiguration (SLAAC).  The security and
>    privacy implications of embedding link-layer addresses in the
>    Interface Identifier have been known and understood for some time
>    now, and some popular IPv6 implementations have already deviated from
>    such schemes to mitigate these issues.  This document changes the
>    recommended default Interface Identifier generation scheme to that
>    specified in RFC7217, and recommends against embedding link-layer
>    addresses in IPv6 Interface Identifiers.  It formally updates
>    RFC2464, RFC2467, RFC2470, RFC2491, RFC2492, RFC2497, RFC2590,
>    RFC3146, RFC3572, RFC4291, RFC4338, RFC4391, RFC4944, RFC5072, and
>    RFC5121, which require IPv6 Interface Identifiers to be derived from
>    the underlying link-layer address.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-default-iids/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6man-default-iids-02
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-default-iids-02
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 


From nobody Fri Jan 23 21:56:31 2015
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 909831A010C for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 21:56:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Qe_WsoFpTjb for <ipv6@ietfa.amsl.com>; Fri, 23 Jan 2015 21:56:27 -0800 (PST)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 805F51A00F7 for <ipv6@ietf.org>; Fri, 23 Jan 2015 21:56:27 -0800 (PST)
Received: from [186.137.82.224] (helo=[192.168.3.107]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fgont@si6networks.com>) id 1YEthS-0005eD-Na; Sat, 24 Jan 2015 06:56:03 +0100
Message-ID: <54C31EFA.7020508@si6networks.com>
Date: Sat, 24 Jan 2015 01:26:34 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, 6man <ipv6@ietf.org>
Subject: Re: I-D Action: draft-ietf-6man-default-iids-02.txt
References: <20150123173011.18444.83799.idtracker@ietfa.amsl.com> <54C2EA04.1040503@gmail.com>
In-Reply-To: <54C2EA04.1040503@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/orBY5g6rtEiKq79jZCB-U1DXN6U>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Jan 2015 05:56:29 -0000

Hi, Brian!

Thanks so much for your feedback! -- Please find my comments in-line....

On 01/23/2015 09:40 PM, Brian E Carpenter wrote:
> I'm all for this draft.
> 
> I think it might benefit from informational references to
> RFC 7136 and RFC 7421, as context for the reader.

How about adding this:
"  [RFC7136] clarifies that the IID should be treated as an
   opaque value, while [RFC7421] provides an analysis of the 64-bit
   boundary in IPv6 addressing."

to the very end of Section 1, as part of the "NOTE"?

P.S.: Any thoughts on Mark's proposal regarding DHCPv6 and the document
title?

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Sat Jan 24 11:21:40 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC3FA1A7008 for <ipv6@ietfa.amsl.com>; Sat, 24 Jan 2015 11:21:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A55agBV52MM2 for <ipv6@ietfa.amsl.com>; Sat, 24 Jan 2015 11:21:36 -0800 (PST)
Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A70C71A1B23 for <6man@ietf.org>; Sat, 24 Jan 2015 11:21:36 -0800 (PST)
Received: by mail-pd0-f174.google.com with SMTP id ft15so4172296pdb.5 for <6man@ietf.org>; Sat, 24 Jan 2015 11:21:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=zraarQ95GosY0zhyEqg7JCK345gD8JTfaDw3UJkRv/U=; b=u93FKNRPDPD4MigCDgHEY+nI1/Jvt1sH0EvfiSg0KTyKVD88V/ujJGcH/Lm+OAVX0b 6miyYHvBvsRpTWYo0fHGS4Mzit/73r0ROY9oX8V+0ipR2ZnvYD+KF5bebVJKZFOoTUsk f+viF3V2S/L3P0f63gjZ+FYWD2ioGhgVrkWUgbpuuVC62oAysu4rpxI/SpYiIm0iuNJN KLJa5YkI0HoxET77Pzudb2VumcfpwF+IqVbrEExk2pdDrY7JudS8hNaNS/vHYj2XlcW+ qufIe0ZVRsA6Za7XmjV6u/ySowFSedlX3lhKnx3WmkrdWBehLMIqamzaCuJmYDFOH5nY olKw==
X-Received: by 10.70.26.196 with SMTP id n4mr21570540pdg.85.1422127295935; Sat, 24 Jan 2015 11:21:35 -0800 (PST)
Received: from [192.168.178.26] (189.228.69.111.dynamic.snap.net.nz. [111.69.228.189]) by mx.google.com with ESMTPSA id c9sm5487909pdj.52.2015.01.24.11.21.32 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 24 Jan 2015 11:21:34 -0800 (PST)
Message-ID: <54C3F0C7.6060603@gmail.com>
Date: Sun, 25 Jan 2015 08:21:43 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: sarikaya@ieee.org
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com>
In-Reply-To: <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/9PLZKvMgLrKK-l1uv9KcPpBwHsE>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Jan 2015 19:21:39 -0000

Below...
On 24/01/2015 08:39, Behcet Sarikaya wrote:
>  Hi Pierre,
>=20
> On Thu, Jan 22, 2015 at 3:30 AM, Pierre Pfister <pierre.pfister@darou.f=
r> wrote:
>> Hello Lorenzo, Ole and Behcet,
>>
>>>
>>> I feel strongly that configuration option that allows a router to spe=
cify another on-link next hop (or, even worse, a next hop on another inte=
rface) is a bad idea because it breaks the fate-sharing properties provid=
ed by RAs.
>>>
>>
>> I fully agree there. If another router should be next-hop, then that o=
ther router can send RAs by itself.
>>
>>> If all that is necessary is a means to tell the host what source addr=
ess to prefer for what prefixes, then we already have a DHCP option for t=
hat.
>>>
>>> Looking at the scenarios, I don't see anything that requires any new =
work to solve.
>>>
>>> Figure 1:
>>> Case 1: rtr1 and rtr2 are connected to different interfaces on the ho=
st (e.g., wifi and 3G), This is solved by rule 5 in RFC 6724.
>>> Case 2: rtr1 and rtr2 are connected to the same interface on the host=
=2E This is solved by SADR forwarding between rtr1 and rtr2 with no host =
changes.
>>
>> Yes, but if we rely on routers=E2=80=99 capabilities only, we will hav=
e suboptimal routing. e.g., the next-hop will send the packet back on the=
 same link. Which would halve the throughput.
>> And if we rely on redirects, well=E2=80=A6 Redirects are not source-sp=
ecific, so we may have redirect ping-pongs between the two routers.
>>
>>>
>>> Figure 2: solved by implementing SADR in the router. The router alrea=
dy has the information it needs. In the case of specialized address routi=
ng, that's solved using the DHCPv6 address selection policy option (RFC 7=
078).
>>>
>>> Figure 3: Same as case 2 in Figure 1; solved by rule 5 in RFC 6724.
>>>
>>> Figure 4: Same as case 1 in Figure 1; solved by SADR forwarding betwe=
en rtr1 and rtr2. Better performance if the host implements rule 5.5 in R=
FC 6724.
>>>
>>> Figure 5: Solved by SADR forwarding between rtr, rtrE and rtrF.
>>
>>
>> Something bugs me in general with the source address selection process=
=2E
>>
>> If we assume the host is dumb, it will first select the next-hop/oif a=
nd pick the source address using rule 5 or rule 5.5.
>> If we assume the host is clever, it will first select the source-addre=
ss based on the information it has (e.g., DHCPv6 address selection). But =
how is it supposed to select the next-hop then ? rule 5 and 5.5 solve sou=
rce address selection when you know the next hop, but not next-hop select=
ion when you know the source address.
>>
>> In other words, when you say DHCPv6 address selection policy solves th=
e issue, you say the host should select the address based on configuratio=
n, which implies that you do that before you pick the next hop.
>> But when you say rule 5 or 5.5 solve the issue, you assume the next-ho=
p has already been selected. So, picking each figure and propose differen=
t solutions which seems to exclude each other seems unfair to me.
>>
>> Source address selection by the host/application is, IMHO, the simples=
t approach to upstream selection, as it reduces interface/next-hop/cpe se=
lection to the selection of a single element. Homenet is moving toward th=
is kind of solutions. But once the application or host has chosen the sou=
rce address, we need some process to select the next hop.
>>
>> When I ask myself =E2=80=98where should we pick the next-hop=E2=80=99=E2=
=80=A6 The routing table seems to be the answer. And if we consider we wa=
nt different next hops depending on the source address, source-dest routi=
ng looks like the right thing to do to me.
>>
>> Now, either we require hosts to look at PIOs and always add source-rou=
tes based on the RAs they receive (which means the router hides things to=
 the host and the host hacks a solution to deal with it - and it may not =
always work), or we provide a longer-term solution where routers tell the=
 truth to hosts.
>>
>> I disagree with the overall approach of this draft. I think what we ne=
ed is a source-specific extension to RFC4191. With only one single new op=
tion similar to RIOs but with a source-prefix included.
>=20
>=20
> I am not sure if you read Section 5.2 in this draft and Section 13 in
> draft-sarikaya-6man-next-hop-ra-04?
> I had these in an effort to satisfy your concerns. Your mails seems to
> indicate that you did not even read them.
> Poor me :-)
>=20
> I can see from this long discussion thread that some people, e.g.
> Mikael are soliciting all RA based solutions. I am OK with it.
> But RFC 7157 which Ole, et al. wrote seems to advocate DHCPv6 based
> approach. That was the reason I wrote DHCP solution draft.

And surely the role of draft-sarikaya-6man-sadr-overview is to set
the context for that choice (or we could do both, which is not actually
forbidden when there is a clear split in the community's preferred practi=
ce).

I'm sure Behcet can tune his text to include all the considerations
that have been mentioned, but is there anything seriously wrong
with the analysis of scenarios 1-5?

   Brian


From nobody Sat Jan 24 12:13:08 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F4601A1A1F for <ipv6@ietfa.amsl.com>; Sat, 24 Jan 2015 12:13:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 68AlJtTCeXjJ for <ipv6@ietfa.amsl.com>; Sat, 24 Jan 2015 12:13:05 -0800 (PST)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31A8D1A039A for <ipv6@ietf.org>; Sat, 24 Jan 2015 12:13:05 -0800 (PST)
Received: by mail-pa0-f54.google.com with SMTP id eu11so3866644pac.13 for <ipv6@ietf.org>; Sat, 24 Jan 2015 12:13:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=74zjgPvdbiGvz/nTngHzLhQwlq1NbRdJuV6+ZXzFoF0=; b=QdcGzIoetPOOGg/mG1wQo93eCwNhYjOZTVr4kyQPKG8OFxLHqbxqaRrfmGhoBUze+o Ol3pFXsPSJ+JR90zpjvO3J1ff/AXiCN+MyG81YYx/Nfm4Nq40zFCZyCJIvrxHsWS5tsz Y9sV38mwg3q8wYj48J10Y0VdrNhECF0PwigEYgUmudh4eoI2ooGte+gDCdqo/VLllt+s D7LTdBwQz80+0Ma41hs4NMyMq9/MJYYeXBsjdLONILrSdlrikzGiiY1XZxwLZ8XeGjda g9RKCQcAJZvlZ8UOQgSrizj44IyFBWuaMbdislUA6O3XJ83MfTYkKADt/9RZo48p8Y4U S0AQ==
X-Received: by 10.68.192.100 with SMTP id hf4mr22271700pbc.54.1422130384497; Sat, 24 Jan 2015 12:13:04 -0800 (PST)
Received: from [192.168.178.26] (189.228.69.111.dynamic.snap.net.nz. [111.69.228.189]) by mx.google.com with ESMTPSA id zr4sm5568351pbb.18.2015.01.24.12.13.01 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 24 Jan 2015 12:13:03 -0800 (PST)
Message-ID: <54C3FCDE.3030507@gmail.com>
Date: Sun, 25 Jan 2015 09:13:18 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Fernando Gont <fgont@si6networks.com>, 6man <ipv6@ietf.org>
Subject: Re: I-D Action: draft-ietf-6man-default-iids-02.txt
References: <20150123173011.18444.83799.idtracker@ietfa.amsl.com> <54C2EA04.1040503@gmail.com> <54C31EFA.7020508@si6networks.com>
In-Reply-To: <54C31EFA.7020508@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/tnhNj3Lr0D4jR8IAra0wO4MRaHE>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Jan 2015 20:13:06 -0000

Hi Fernando,
On 24/01/2015 17:26, Fernando Gont wrote:
> Hi, Brian!
> 
> Thanks so much for your feedback! -- Please find my comments in-line....
> 
> On 01/23/2015 09:40 PM, Brian E Carpenter wrote:
>> I'm all for this draft.
>>
>> I think it might benefit from informational references to
>> RFC 7136 and RFC 7421, as context for the reader.
> 
> How about adding this:
> "  [RFC7136] clarifies that the IID should be treated as an
>    opaque value, while [RFC7421] provides an analysis of the 64-bit
>    boundary in IPv6 addressing."
> 
> to the very end of Section 1, as part of the "NOTE"?

OK, thanks.

> 
> P.S.: Any thoughts on Mark's proposal regarding DHCPv6 and the document
> title?

I think it's a good idea. Otherwise we'll see people using guessable
sequences for DHCPv6-based addresses, and that can't be a good thing.

   Brian


From nobody Sat Jan 24 13:21:30 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD72F1A0079 for <ipv6@ietfa.amsl.com>; Sat, 24 Jan 2015 13:21:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ztCS3cxLOHeh for <ipv6@ietfa.amsl.com>; Sat, 24 Jan 2015 13:21:27 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D686C1A000F for <6man@ietf.org>; Sat, 24 Jan 2015 13:21:27 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 500556141; Sat, 24 Jan 2015 13:21:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=3nlJmZ/sced75CqD+/WaknKJduA=; b=pq5EZBVW9cuV98QhRb KGM0G1nDf++40yj5YxxMuVrknugmXQTq5CWp/vgy330tM73RpHxfnK/Yh8anYTlR 4sgnUDYtZpXvr9+dMDl/zDHJqCO5WtTNrIYlI7bt6SSdvng8xX/Sm4QRW9vVVZrB K4Oguvon8A/fYScQkFyMrkmLY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=AZ8P0Q088ny8D6kPX2JAREwZa7sI3XhYcGOayjp7iXIdJcOr0YT YyoOl6KcgIq27pHlW4/lIFD9O6kF0FsgBEISjprRH7LLx2B9wUDk3RkOLLcoaSBs Z+DNnSeHD4jQqrCvuiAKJfL+5kuwRZjnRc3fVFd21H+cQTPglrjxkMbI=
Received: from gomlefisk.localdomain (unknown [195.159.234.46]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 0897A6129; Sat, 24 Jan 2015 13:21:26 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 1FD7F3D42A09; Sat, 24 Jan 2015 22:21:29 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.4\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <54C3F0C7.6060603@gmail.com>
Date: Sat, 24 Jan 2015 22:21:28 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <0BB30257-0F3A-4DD4-AEE5-01CA36C25407@employees.org>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <54C3F0C7.6060603@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.2070.4)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/D5D6fb2h9yG1NAXBP-KUjCJR8KE>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Jan 2015 21:21:29 -0000

[...]

>>=20
>> I can see from this long discussion thread that some people, e.g.
>> Mikael are soliciting all RA based solutions. I am OK with it.
>> But RFC 7157 which Ole, et al. wrote seems to advocate DHCPv6 based
>> approach. That was the reason I wrote DHCP solution draft.
>=20
> And surely the role of draft-sarikaya-6man-sadr-overview is to set
> the context for that choice (or we could do both, which is not =
actually
> forbidden when there is a clear split in the community's preferred =
practice).

what makes you say that? RFC7157 sets the context for choosing DCPv6. =
the use-case was a multi-homed network, with one link to a walled =
garden, and only some hosts on the link needed to reach the walled =
garden.

>=20
> I'm sure Behcet can tune his text to include all the considerations
> that have been mentioned, but is there anything seriously wrong
> with the analysis of scenarios 1-5?

yes, there are a number of serious flaws in this document.

cheers,
Ole=


From nobody Sat Jan 24 14:38:03 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54AAA1A1A34 for <ipv6@ietfa.amsl.com>; Sat, 24 Jan 2015 14:38:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ghEjWVYAtm6Y for <ipv6@ietfa.amsl.com>; Sat, 24 Jan 2015 14:38:01 -0800 (PST)
Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC4C21A1A31 for <6man@ietf.org>; Sat, 24 Jan 2015 14:38:00 -0800 (PST)
Received: by mail-pd0-f171.google.com with SMTP id fp1so4713524pdb.2 for <6man@ietf.org>; Sat, 24 Jan 2015 14:38:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=zzvbShsu2mj/rTqBISz300JPc83hCNvI2vlFHfuZvN8=; b=T+acCKtV958XinUikYV2yKmsNLKHpBajve9vKt28ibtVa61cCsiKzRvHjdYEPCV/3c H2Mpm2/VAjtetJbSt4UbmvVJK14f2Q8E64FEmeAq16N1krw0TChhPepbyBpmkQz0j1BS qs/7NW+N7SYOpvTQOQw15XntWbjoR5AvUBnGclqjgunl1k2eoeeyPeIry5EAgaZkooKS ++RujZUQUhyv5/M4pvUjBcFSoOMOwpxBSKcAHyUV5u5arRhzwjFZRAmMGlgTZs6k64rB VvyMV5Eg0jtWD/+NSR3w9mQSTX7iWY3qs3mXXKdQEfKziUgA+oA82fokYUR0483kLJxU X4/w==
X-Received: by 10.68.221.165 with SMTP id qf5mr22068448pbc.101.1422139080207;  Sat, 24 Jan 2015 14:38:00 -0800 (PST)
Received: from [192.168.178.26] (189.228.69.111.dynamic.snap.net.nz. [111.69.228.189]) by mx.google.com with ESMTPSA id oq2sm5702240pbb.60.2015.01.24.14.37.57 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 24 Jan 2015 14:37:59 -0800 (PST)
Message-ID: <54C41EC2.509@gmail.com>
Date: Sun, 25 Jan 2015 11:37:54 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <54C3F0C7.6060603@gmail.com> <0BB30257-0F3A-4DD4-AEE5-01CA36C25407@employees.org>
In-Reply-To: <0BB30257-0F3A-4DD4-AEE5-01CA36C25407@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/0-Hlz493c9hKtQtkF44B_b9KE70>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Jan 2015 22:38:02 -0000

On 25/01/2015 10:21, Ole Troan wrote:
> [...]
> 
>>>
>>> I can see from this long discussion thread that some people, e.g.
>>> Mikael are soliciting all RA based solutions. I am OK with it.
>>> But RFC 7157 which Ole, et al. wrote seems to advocate DHCPv6 based
>>> approach. That was the reason I wrote DHCP solution draft.
>>
>> And surely the role of draft-sarikaya-6man-sadr-overview is to set
>> the context for that choice (or we could do both, which is not actually
>> forbidden when there is a clear split in the community's preferred practice).
> 
> what makes you say that? RFC7157 sets the context for choosing DCPv6. the use-case was a multi-homed network, with one link to a walled garden, and only some hosts on the link needed to reach the walled garden.

Sure. In that context DHCPv6 would probably be chosen. But we haven't
made it a MUST in the node requirements. As long as it's a SHOULD
(RFC6434 section 5.9.5) we have to assume there will be hosts without it.

>> I'm sure Behcet can tune his text to include all the considerations
>> that have been mentioned, but is there anything seriously wrong
>> with the analysis of scenarios 1-5?
> 
> yes, there are a number of serious flaws in this document.

Well, I'll leave that between you and Behcet. fwiw I think we need
such a document, because the situation is not as clear for
everybody, so the flaws needs to be corrected.

    Brian


From nobody Sun Jan 25 00:07:38 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EAE61A6F38 for <ipv6@ietfa.amsl.com>; Sun, 25 Jan 2015 00:07:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SgjVjYTyLuTd for <ipv6@ietfa.amsl.com>; Sun, 25 Jan 2015 00:07:34 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64C491A6F15 for <6man@ietf.org>; Sun, 25 Jan 2015 00:07:34 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id AE345629F; Sun, 25 Jan 2015 00:07:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=fR6gRm4TMroFvh1WvY3RK9l4H6M=; b=igEWQohM7Pl39tyX8l 6x72xXcOPtbZ4vYqEPugvFQCF15FCKUJlDEurYVrk6JbMuCp3qItx7lNwIQlJtVT iyPMTTHAgFJ+RrTt+Kybt0E7np8svjZ6AodiNEW2X05/XUI5ZMaNYfHfr/f9Si8v n+8CdAemnQKsZ3MFz8PrSbNUI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=lyPlv3owvtB5DGWv3kNqkG9hDFOg2+1NO+XK+Bu9BoIVGGWAg4r P5XkyuEETJQfk4pEaCc/Fq/1ERXc8QM0LfXjsv1yJ3K3bSrAtLVZoXy96mj9bkHx hR8FEx2Rv7ZExkjrs3zL3wL1HwBM+RpkI7i1nQPVraoxz+6Swg/U95JU=
Received: from gomlefisk.localdomain (unknown [195.159.234.46]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 7A87061C5; Sun, 25 Jan 2015 00:07:32 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 1C6E03D44795; Sun, 25 Jan 2015 09:07:27 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.4\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <54C41EC2.509@gmail.com>
Date: Sun, 25 Jan 2015 09:07:26 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <16A24C7B-4B3F-43F8-B72C-10ED04EDCC39@employees.org>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <54C3F0C7.6060603@gmail.com> <0BB30257-0F3A-4DD4-AEE5-01CA36C25407@employees.org> <54C41EC2.509@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.2070.4)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ZVm4e17u-PhCmoIHKz_35ccWoR0>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Jan 2015 08:07:36 -0000

Brian,

>>>> I can see from this long discussion thread that some people, e.g.
>>>> Mikael are soliciting all RA based solutions. I am OK with it.
>>>> But RFC 7157 which Ole, et al. wrote seems to advocate DHCPv6 based
>>>> approach. That was the reason I wrote DHCP solution draft.
>>>=20
>>> And surely the role of draft-sarikaya-6man-sadr-overview is to set
>>> the context for that choice (or we could do both, which is not =
actually
>>> forbidden when there is a clear split in the community's preferred =
practice).
>>=20
>> what makes you say that? RFC7157 sets the context for choosing DCPv6. =
the use-case was a multi-homed network, with one link to a walled =
garden, and only some hosts on the link needed to reach the walled =
garden.
>=20
> Sure. In that context DHCPv6 would probably be chosen. But we haven't
> made it a MUST in the node requirements. As long as it's a SHOULD
> (RFC6434 section 5.9.5) we have to assume there will be hosts without =
it.

yes, and that's likely something we have to live with.
note that 7157 resulted in a DHCP option to program the source address =
selection policy table.
that isn't exactly the same as SADR although the two are tightly =
connected.

>>> I'm sure Behcet can tune his text to include all the considerations
>>> that have been mentioned, but is there anything seriously wrong
>>> with the analysis of scenarios 1-5?
>>=20
>> yes, there are a number of serious flaws in this document.
>=20
> Well, I'll leave that between you and Behcet. fwiw I think we need
> such a document, because the situation is not as clear for
> everybody, so the flaws needs to be corrected.

yes, I also think we need such a document. I think Behcet's draft is a =
good start, but there are a few "red flags" and bugs in there that makes =
it a hard read. e.g. the 3rd party next-hop.

can we try to agree on the behaviour we desire? let me posit a few =
suggestions:

1) given a destination, interface and next-hop
    =3D> prefer the source address on the outbound interface.
    RFC6724: Rule 5.
    that covers Behcet's use case 1,2,3.

2) given a destination, interface and next-hop
    =3D> prefer the source address on the outbound interface and =
associated with the next-hop
    RFC6724: Rule 5.5.
    that covers Behcet's use case 4

now to the inverse:

3) given a source address
    =3D> choose the outgoing interface that the source address is =
associated with
    Behcet's use case 4 (with single ISP)

4) given a source address
    =3D> choose the outgoing interface and next-hop that the source =
address is associated with
   Behcet's use case 4

3,4 aren't specified in IETF text I believe.
those 4 rules are implementable to hosts using Default Router Lists.

in which cases wouldn't these rules suffice? and would any more specific =
source dependent routes require a host with a Routing Table?

cheers,
Ole=


From SRS0=8RVV=CM=darou.fr=pierre.pfister@bounces.m4x.org  Sun Jan 25 02:47:40 2015
Return-Path: <SRS0=8RVV=CM=darou.fr=pierre.pfister@bounces.m4x.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 493611A0275 for <ipv6@ietfa.amsl.com>; Sun, 25 Jan 2015 02:47:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eG1-Bff17V_Y for <ipv6@ietfa.amsl.com>; Sun, 25 Jan 2015 02:47:37 -0800 (PST)
Received: from mx1.polytechnique.org (mx1.polytechnique.org [129.104.30.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65E3C1A026F for <6man@ietf.org>; Sun, 25 Jan 2015 02:47:36 -0800 (PST)
Received: from mbp.home (ANantes-652-1-234-78.w2-9.abo.wanadoo.fr [2.9.49.78]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ssl.polytechnique.org (Postfix) with ESMTPSA id 9B2D31408EFA2; Sun, 25 Jan 2015 11:47:33 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <16A24C7B-4B3F-43F8-B72C-10ED04EDCC39@employees.org>
Date: Sun, 25 Jan 2015 11:47:33 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <127A700A-34BD-40B0-9234-9AF3521EE543@darou.fr>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <54C3F0C7.6060603@gmail.com> <0BB30257-0F3A-4DD4-AEE5-01CA36C25407@employees.org> <54C41EC2.509@gmail.com> <16A24C7B-4B3F-43F8-B72C-10ED04EDCC39@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1878.6)
X-AV-Checked: ClamAV using ClamSMTP at svoboda.polytechnique.org (Sun Jan 25 11:47:34 2015 +0100 (CET))
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Gv8tYXDoPmg9EJWHsdBlaZcDKo8>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Jan 2015 10:48:30 -0000

Ole,
=20
>=20
>>>> I'm sure Behcet can tune his text to include all the considerations
>>>> that have been mentioned, but is there anything seriously wrong
>>>> with the analysis of scenarios 1-5?
>>>=20
>>> yes, there are a number of serious flaws in this document.
>>=20
>> Well, I'll leave that between you and Behcet. fwiw I think we need
>> such a document, because the situation is not as clear for
>> everybody, so the flaws needs to be corrected.
>=20
> yes, I also think we need such a document. I think Behcet's draft is a =
good start, but there are a few "red flags" and bugs in there that makes =
it a hard read. e.g. the 3rd party next-hop.
>=20
> can we try to agree on the behaviour we desire? let me posit a few =
suggestions:
>=20
> 1) given a destination, interface and next-hop
>    =3D> prefer the source address on the outbound interface.
>    RFC6724: Rule 5.
>    that covers Behcet's use case 1,2,3.
>=20
> 2) given a destination, interface and next-hop
>    =3D> prefer the source address on the outbound interface and =
associated with the next-hop
>    RFC6724: Rule 5.5.
>    that covers Behcet's use case 4
>=20
> now to the inverse:
>=20
> 3) given a source address
>    =3D> choose the outgoing interface that the source address is =
associated with
>    Behcet's use case 4 (with single ISP)
>=20
> 4) given a source address
>    =3D> choose the outgoing interface and next-hop that the source =
address is associated with
>   Behcet's use case 4
>=20
> 3,4 aren't specified in IETF text I believe.
> those 4 rules are implementable to hosts using Default Router Lists.
>=20
> in which cases wouldn't these rules suffice? and would any more =
specific source dependent routes require a host with a Routing Table?

I think they would suffice. I don=92t think they are satisfying.
In current homenet, when there are multiple routers on the same link, =
they all advertise the same prefixes. And I think this is the correct =
behavior. I see two possibilities:
a. Routers do not advertise all PIOs, but only those they are best =
next-hop for (Works with your 4th proposition).
b. Routers advertise all PIOs. Best next-hop advertise something more =
(Source-Specific RIO).

With (a), when there are topology changes, routers will start and stop =
advertising PIOs as they detect they are best next-hop or not. Although =
addresses may have remained valid the whole time.
With (b), valid PIOs are always advertised by at least one router. As =
suggested Mikael, we can even use priorities to let hosts backup to a =
different next-hop when the best fails. Also, you separate the routing =
information and the address assignment information, which I think is =
better.

Cheers,

Pierre

>=20
> cheers,
> Ole
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Sun Jan 25 02:55:03 2015
Return-Path: <SRS0=8RVV=CM=darou.fr=pierre.pfister@bounces.m4x.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4B721A028A for <ipv6@ietfa.amsl.com>; Sun, 25 Jan 2015 02:55:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uZkYFlOaXK_a for <ipv6@ietfa.amsl.com>; Sun, 25 Jan 2015 02:55:01 -0800 (PST)
Received: from mx1.polytechnique.org (mx1.polytechnique.org [129.104.30.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 446FE1A0141 for <6man@ietf.org>; Sun, 25 Jan 2015 02:55:01 -0800 (PST)
Received: from mbp.home (ANantes-652-1-234-78.w2-9.abo.wanadoo.fr [2.9.49.78]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ssl.polytechnique.org (Postfix) with ESMTPSA id 368D71408EFA2; Sun, 25 Jan 2015 11:54:59 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com>
Date: Sun, 25 Jan 2015 11:54:59 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1F17C514-D466-4069-9D1E-9EE15E59995F@darou.fr>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com>
To: sarikaya@ieee.org
X-Mailer: Apple Mail (2.1878.6)
X-AV-Checked: ClamAV using ClamSMTP at svoboda.polytechnique.org (Sun Jan 25 11:54:59 2015 +0100 (CET))
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/K6EVsYQy0Z6SEqhLqf75AGnP9BQ>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Jan 2015 10:55:02 -0000

Hello Behcet

>=20
> I am not sure if you read Section 5.2 in this draft and Section 13 in
> draft-sarikaya-6man-next-hop-ra-04?
> I had these in an effort to satisfy your concerns. Your mails seems to
> indicate that you did not even read them.
> Poor me :-)

Thank you for the effort. I actually read the update.
My point was that we only need one single RA option to solve all the =
situations. You added yet-another option.
Also, as Ole mentioned, third party next-hop doesn=92t seem like a good =
idea to me (at least in RAs, I dont know in DHCP).

And I just realized all your options contain one single source address.
But what we actually need, IMHO, is rather a source prefix.

Regards,

- Pierre


From nobody Mon Jan 26 00:42:48 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 246471A876E for <ipv6@ietfa.amsl.com>; Mon, 26 Jan 2015 00:42:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.411
X-Spam-Level: 
X-Spam-Status: No, score=-1.411 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_29=0.6, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OxQ1etptIQsU for <ipv6@ietfa.amsl.com>; Mon, 26 Jan 2015 00:42:45 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 145561A1BE7 for <6man@ietf.org>; Mon, 26 Jan 2015 00:42:45 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 51DF0627B; Mon, 26 Jan 2015 00:42:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=zrsso3jIF7rSQ0l6qzElHFOJoAg=; b=hHUdfp1IdiW9reWmYc 1YLEVxDjZTUfVXNTbwrN3eR9NM3mA+1X9FFoJfCjVsLr3J5qx/dmODJR5kz1jMwJ Q+VTD4mSK/iHYKoqPd+06kEosaEfNXdZxl3INzOE6cXvI2Bbyl0LYMqFNFLUk9Xi cSdbKEi5Umn+yDqH5Ed3JrQ2s=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=cPamY7qHNSwZiaI3No7jM1C5PEGCm2owXnMw2cDTLcpSJnd7ZJf cFRrj1XqeN6GdZkFvNtdrYBDC0P2zO3YNRn4Oxsp5/IiyvPyyDpRjcdCb3C2GXQx nNlBsENbN7NRecW8UJ+FvkLkyaD5AezAf/vwmnqYfXGBGsopaMi1XyR8=
Received: from gomlefisk.localdomain (173-38-208-170.cisco.com [173.38.208.170]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id C8B006159; Mon, 26 Jan 2015 00:42:43 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 2A8BA3D4D119; Mon, 26 Jan 2015 09:42:51 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.4\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <127A700A-34BD-40B0-9234-9AF3521EE543@darou.fr>
Date: Mon, 26 Jan 2015 09:42:50 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <AB43E5F2-326B-4617-AA38-1971BFC82851@employees.org>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <54C3F0C7.6060603@gmail.com> <0BB30257-0F3A-4DD4-AEE5-01CA36C25407@employees.org> <54C41EC2.509@gmail.com> <16A24C7B-4B3F-43F8-B72C-10ED04EDCC39@employees.org> <127A700A-34BD-40B0-9234-9AF3521EE543@darou.fr>
To: Pierre Pfister <pierre.pfister@darou.fr>
X-Mailer: Apple Mail (2.2070.4)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/UpJqF2JjnUtO0VKr7FfyKQ9cpdc>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 08:42:46 -0000

Pierre,

>> can we try to agree on the behaviour we desire? let me posit a few =
suggestions:
>>=20
>> 1) given a destination, interface and next-hop
>>   =3D> prefer the source address on the outbound interface.
>>   RFC6724: Rule 5.
>>   that covers Behcet's use case 1,2,3.
>>=20
>> 2) given a destination, interface and next-hop
>>   =3D> prefer the source address on the outbound interface and =
associated with the next-hop
>>   RFC6724: Rule 5.5.
>>   that covers Behcet's use case 4
>>=20
>> now to the inverse:
>>=20
>> 3) given a source address
>>   =3D> choose the outgoing interface that the source address is =
associated with
>>   Behcet's use case 4 (with single ISP)
>>=20
>> 4) given a source address
>>   =3D> choose the outgoing interface and next-hop that the source =
address is associated with
>>  Behcet's use case 4
>>=20
>> 3,4 aren't specified in IETF text I believe.
>> those 4 rules are implementable to hosts using Default Router Lists.
>>=20
>> in which cases wouldn't these rules suffice? and would any more =
specific source dependent routes require a host with a Routing Table?
>=20
> I think they would suffice. I don=92t think they are satisfying.
> In current homenet, when there are multiple routers on the same link, =
they all advertise the same prefixes. And I think this is the correct =
behavior. I see two possibilities:
> a. Routers do not advertise all PIOs, but only those they are best =
next-hop for (Works with your 4th proposition).
> b. Routers advertise all PIOs. Best next-hop advertise something more =
(Source-Specific RIO).
>=20
> With (a), when there are topology changes, routers will start and stop =
advertising PIOs as they detect they are best next-hop or not. Although =
addresses may have remained valid the whole time.
> With (b), valid PIOs are always advertised by at least one router. As =
suggested Mikael, we can even use priorities to let hosts backup to a =
different next-hop when the best fails. Also, you separate the routing =
information and the address assignment information, which I think is =
better.

this information only has value to the host when it is on the same link =
as the border router(s) right?
I don't think topology changes should result in routers starting and =
stopping advertising PIOs (unless it gets changes from a border router =
to an internal router). addresses are of course valid regardless of the =
PIO not being advertised (e.g. one of the border routers reboot).

so we're creating a special case here regardless. on the multiple border =
routers on a link case:
 I) ISP A border router only advertises ISP A prefixes in PIO
II) ISP A border router advertises both ISP A and ISP B prefixes in PIO, =
but only ISP A prefix in SS-RIO

all other internal routers advertise all prefixes in PIO. and presumably =
no internal routers include the SS-RIO.

RFC4191 has an interesting discussion:
---------
 There are several reasons for using a new Route Information Option
   instead of using flag bits to overload the existing Prefix
   Information Option:

   1. Prefixes will typically only show up in one option, not both, so a
      new option does not introduce duplication.

   2. The Route Information Option is typically 16 octets while the
      Prefix Information Option is 32 octets.

   3. Using a new option may improve backwards-compatibility with some
      host implementations.
---------

in our case, wouldn't typically the SS-RIO include the prefix that's =
already is in the PIO?
can we think of cases where you would use a different source prefix?

with regards to backwards compatibility, the cat might be out of the bag =
already.

do we need to also take care of the case of MHMP where the uplinks =
aren't ingress filtered? if so we need to be explicit.

a) implicit. describe how existing PIO, RIO should tie together =
SA,interface and next-hop selection
b) explicit with new SS-RIO
c) explicit with flags. new SS flag in PIO, and new SS flag in RIO

I'm not sure what's the best choice. are there use cases that one would =
cover and the other would not? are any of them more backwards =
compatible? other considerations in making the choice?

cheers,
Ole




From nobody Mon Jan 26 02:20:43 2015
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 995311A88A6 for <ipv6@ietfa.amsl.com>; Mon, 26 Jan 2015 02:20:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.361
X-Spam-Level: 
X-Spam-Status: No, score=-3.361 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, J_CHICKENPOX_29=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oh7u96Fr1BdJ for <ipv6@ietfa.amsl.com>; Mon, 26 Jan 2015 02:20:28 -0800 (PST)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 441E51A8874 for <6man@ietf.org>; Mon, 26 Jan 2015 02:20:28 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 39173A4; Mon, 26 Jan 2015 11:20:26 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1422267626; bh=7P9r0SXsuhurX3EKkqI+j29lMbjq1r56ateEgTNEgas=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=eTRIPaw2T8zYw5R2pqUa2bjfQ+hgFrSVa2YlRnI7yJABM2M0+hF/ctYlC8xhL/ZGj dEnNIFZXSzTSwmOjx4PWw4tp5aOADgjKrSv7msjjFzABTbCUqx/C8K7dnWNlmkfRr3 jgwdO5dTX7F8sAYO7cuOseXon9lI3KmBWEyw2F8k=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 309E6A3; Mon, 26 Jan 2015 11:20:26 +0100 (CET)
Date: Mon, 26 Jan 2015 11:20:26 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ole Troan <otroan@employees.org>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
In-Reply-To: <AB43E5F2-326B-4617-AA38-1971BFC82851@employees.org>
Message-ID: <alpine.DEB.2.02.1501261116300.22729@uplift.swm.pp.se>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <54C3F0C7.6060603@gmail.com> <0BB30257-0F3A-4DD4-AEE5-01CA36C25407@employees.org> <54C41EC2.509@gmail.com> <16A24C7B-4B3F-43F8-B72C-10ED04EDCC39@employees.org> <127A700A-34BD-40B0-9234-9AF3521EE543@darou.fr> <AB43E5F2-326B-4617-AA38-1971BFC82851@employees.org>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/oZnMJZ4gj-0fe0YM0I9JQmUMvWc>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 10:20:41 -0000

On Mon, 26 Jan 2015, Ole Troan wrote:

> a) implicit. describe how existing PIO, RIO should tie together SA,interface and next-hop selection

If the same router is announcing three different prefixes, with this 
suggestion I guess it'd need to announce with three different RAs if it 
wants the hosts to treat the prefixes differently?

> b) explicit with new SS-RIO

The good and bad thing with this one is that legacy hosts will not 
understand this new option.

> c) explicit with flags. new SS flag in PIO, and new SS flag in RIO

How do hosts generally treat flags?

> I'm not sure what's the best choice. are there use cases that one would cover and the other would not? are any of them more backwards compatible? other considerations in making the choice?

Good question!

In MIF, there is talk about having a PVD UUID of some kind. Where do we 
want to put that information? I believe that would be good input in this 
discussion.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Mon Jan 26 03:30:48 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CE721A88F8 for <ipv6@ietfa.amsl.com>; Mon, 26 Jan 2015 03:30:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.411
X-Spam-Level: 
X-Spam-Status: No, score=-1.411 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_29=0.6, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 59Psfb9Tukv8 for <ipv6@ietfa.amsl.com>; Mon, 26 Jan 2015 03:30:46 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3946F1A02F1 for <6man@ietf.org>; Mon, 26 Jan 2015 03:30:46 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 0524E61CE; Mon, 26 Jan 2015 03:30:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=fIYWQj0grFr8DNL/S7GfxsR0z9w=; b=nNt5FJKtUxR6JsfiAV fzkwQWdtz3bzEGfO9LqOh3MDVMY2XZygpvcer55lhuQBZK+KUimbHyxuOR4zcYm1 TQV6ShmDCeHEzGK2EjWKo5bZETUWYxAd+MKctMWh3vwHonaYYIc1RvolcDqsh+5c SinRPdScxHRlcMrGDaB8EZpEA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=FgNzYZI1QY4w5BuvTuJiNIUNccbCKpZXkAljlGNnbY1SE2FEAc8 43l3gmX3cE2/SGAxLxMRhz/+y6y2qnUXUzYmikZZ+pl1aK0sy3QQdY9aHSAUNh0i Z2RRcW4bn9iGRjnuCmxdi+D3p4tu9UhUHCy6z8FQgBAVOsFPjAsjifGs=
Received: from gomlefisk.localdomain (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id AAE2161C5; Mon, 26 Jan 2015 03:30:44 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id D91213D50854; Mon, 26 Jan 2015 12:30:41 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.4\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <alpine.DEB.2.02.1501261116300.22729@uplift.swm.pp.se>
Date: Mon, 26 Jan 2015 12:30:41 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E6B22E0-4DAB-4CC1-9CA1-4B03422FC1FA@employees.org>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <54C3F0C7.6060603@gmail.com> <0BB30257-0F3A-4DD4-AEE5-01CA36C25407@employees.org> <54C41EC2.509@gmail.com> <16A24C7B-4B3F-43F8-B72C-10ED04EDCC39@employees.org> <127A700A-34BD-40B0-9234-9AF3521EE543@darou.fr> <AB43E5F2-326B-4617-AA38-1971BFC82851@employees.org> <alpine.DEB.2.02.1501261116300.22729@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.2070.4)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/SQ6ngMgJhZwM5SrlvzZwiQrc6xo>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 11:30:47 -0000

Mikael,

>> a) implicit. describe how existing PIO, RIO should tie together =
SA,interface and next-hop selection
>=20
> If the same router is announcing three different prefixes, with this =
suggestion I guess it'd need to announce with three different RAs if it =
wants the hosts to treat the prefixes differently?

what different treatment could you imagine?
I'm not sure with this option that you can differentiate very much at =
all.

>=20
>> b) explicit with new SS-RIO
>=20
> The good and bad thing with this one is that legacy hosts will not =
understand this new option.

right, but I think we have that with either of the solutions.

>> c) explicit with flags. new SS flag in PIO, and new SS flag in RIO
>=20
> How do hosts generally treat flags?

well, they would have to implement them. ;-)

>=20
>> I'm not sure what's the best choice. are there use cases that one =
would cover and the other would not? are any of them more backwards =
compatible? other considerations in making the choice?
>=20
> Good question!
>=20
> In MIF, there is talk about having a PVD UUID of some kind. Where do =
we want to put that information? I believe that would be good input in =
this discussion.

I'm not sure where to place PVDs here, I suppose you could look at them =
as being represented by multiple interfaces on the host, thereby making =
an MHMP host a MIMH (multi-interface multihomed) host instead.

at least in homenet I would think the network will amalgamate the =
information from external sources and present a single view on the =
inside.

cheers,
Ole


From nobody Mon Jan 26 03:38:58 2015
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B2B21A892F for <ipv6@ietfa.amsl.com>; Mon, 26 Jan 2015 03:38:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.361
X-Spam-Level: 
X-Spam-Status: No, score=-3.361 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, J_CHICKENPOX_29=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tfb8dFLzUe34 for <ipv6@ietfa.amsl.com>; Mon, 26 Jan 2015 03:38:55 -0800 (PST)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28ECA1A892C for <6man@ietf.org>; Mon, 26 Jan 2015 03:38:55 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id B016FA4; Mon, 26 Jan 2015 12:38:53 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1422272333; bh=i/Vn3Pzqg1Vpj8/d5sCRH1Q/9RsEPb56RhNjkjiskmE=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=WDycLvFdIuA9otTg20fzWO5AnCsxRDTv1wgzLAmn2WH83OFMq5H+0tnJkF6wVKkKr +AMunoQI36yE2JXLDNQf20m+GKetnK4svQceIE0gqV9eXM3jtQtzRmbh1oA+J8F7bk +C7VebTRrcaBjknHviRhbh/e83QVAjeHQXfY0J7U=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id A666DA3; Mon, 26 Jan 2015 12:38:53 +0100 (CET)
Date: Mon, 26 Jan 2015 12:38:53 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ole Troan <otroan@employees.org>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
In-Reply-To: <7E6B22E0-4DAB-4CC1-9CA1-4B03422FC1FA@employees.org>
Message-ID: <alpine.DEB.2.02.1501261234340.22729@uplift.swm.pp.se>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <54C3F0C7.6060603@gmail.com> <0BB30257-0F3A-4DD4-AEE5-01CA36C25407@employees.org> <54C41EC2.509@gmail.com> <16A24C7B-4B3F-43F8-B72C-10ED04EDCC39@employees.org> <127A700A-34BD-40B0-9234-9AF3521EE543@darou.fr> <AB43E5F2-326B-4617-AA38-1971BFC82851@employees.org> <alpine.DEB.2.02.1501261116300.22729@uplift.swm.pp.se> <7E6B22E0-4DAB-4CC1-9CA1-4B03422FC1FA@employees.org>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/oBI6dIEih0V_WikDqnqoxLoKBiA>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 11:38:57 -0000

On Mon, 26 Jan 2015, Ole Troan wrote:

>>> a) implicit. describe how existing PIO, RIO should tie together SA,interface and next-hop selection
>>
>> If the same router is announcing three different prefixes, with this suggestion I guess it'd need to announce with three different RAs if it wants the hosts to treat the prefixes differently?
>
> what different treatment could you imagine?
> I'm not sure with this option that you can differentiate very much at all.

Well, you could for instance send RAs with different router priorities for 
different prefixes. Since it's implicit, I guess hosts would treat 
whatever came in an RA as a "bundle", so if the host received two 
different RAs from the same router for different prefixes, with different 
default router priority, it would actually use this information?

>>> b) explicit with new SS-RIO
>>
>> The good and bad thing with this one is that legacy hosts will not understand this new option.
>
> right, but I think we have that with either of the solutions.
>
>>> c) explicit with flags. new SS flag in PIO, and new SS flag in RIO
>>
>> How do hosts generally treat flags?
>
> well, they would have to implement them. ;-)

Will they ignore the option if it has flags it doesn't understand?

That's what differenting b from c here right?

> I'm not sure where to place PVDs here, I suppose you could look at them 
> as being represented by multiple interfaces on the host, thereby making 
> an MHMP host a MIMH (multi-interface multihomed) host instead.
>
> at least in homenet I would think the network will amalgamate the 
> information from external sources and present a single view on the 
> inside.

Well, how would the host find out that there might be multiple PVDs on the 
same wire? One was was to come up with a new RIO that would include this 
information, ie a PVD identifier included in RAs.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Mon Jan 26 03:57:29 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 750771A8966 for <ipv6@ietfa.amsl.com>; Mon, 26 Jan 2015 03:57:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.411
X-Spam-Level: 
X-Spam-Status: No, score=-1.411 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_29=0.6, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lT0J_Je_rmfI for <ipv6@ietfa.amsl.com>; Mon, 26 Jan 2015 03:57:23 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A9111A8960 for <ipv6@ietf.org>; Mon, 26 Jan 2015 03:57:23 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 4144061E9; Mon, 26 Jan 2015 03:57:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=u+UYAOVYs24i7JznhruuD3aYfW4=; b=B4Kzd3oV2k1OZWphxA 8JgPOIwAnoSXRsfKVPdu6wSI3BpSsJ34gI71jx/g7d2KNJGEzC9cJOdNKBYXE3u2 iCOhpoN066K0bIGgOdo6e+T4qedU8drSsE+OAL5eLSjGbv+EtV35Fv9rIQ8l7S6o t4OwQh28dj08d7HeqPbXQImh0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=CDK6sfCtWQTqMtkhpx8ubupZKvdXc+r+8bRtBd71nTg77Fqc8OT zgn4FTwOW9EDhPbVVE1CIDMDjdsuywc4g4Ppi6IC3CIctJxBgDPnYemlGM88lkPU WhzAy4+Wt82OxVR4vT6uld1FYlZ3WA8YqBf+2R/MomkBa+Wvg/ZiSROw=
Received: from gomlefisk.localdomain (173-38-208-170.cisco.com [173.38.208.170]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 9A99961CE; Mon, 26 Jan 2015 03:57:21 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 0C52C3D51970; Mon, 26 Jan 2015 12:57:19 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.4\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <alpine.DEB.2.02.1501261234340.22729@uplift.swm.pp.se>
Date: Mon, 26 Jan 2015 12:57:18 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D09138C1-236A-49E0-B23D-D8B823DF1F69@employees.org>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <54C3F0C7.6060603@gmail.com> <0BB30257-0F3A-4DD4-AEE5-01CA36C25407@employees.org> <54C41EC2.509@gmail.com> <16A24C7B-4B3F-43F8-B72C-10ED04EDCC39@employees.org> <127A700A-34BD-40B0-9234-9AF3521EE543@darou.fr> <AB43E5F2-326B-4617-AA38-1971BFC82851@employees.org> <alpine.DEB.2.02.1501261116300.22729@uplift.swm.pp.se> <7E6B22E0-4DAB-4CC1-9CA1-4B03422FC1FA@employees.org> <alpine.DEB.2.02.1501261234340.22729@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.2070.4)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/jexBt16bNMXCnau7H5NZNYxdbow>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 11:57:24 -0000

>>>> a) implicit. describe how existing PIO, RIO should tie together =
SA,interface and next-hop selection
>>>=20
>>> If the same router is announcing three different prefixes, with this =
suggestion I guess it'd need to announce with three different RAs if it =
wants the hosts to treat the prefixes differently?
>>=20
>> what different treatment could you imagine?
>> I'm not sure with this option that you can differentiate very much at =
all.
>=20
> Well, you could for instance send RAs with different router priorities =
for different prefixes. Since it's implicit, I guess hosts would treat =
whatever came in an RA as a "bundle", so if the host received two =
different RAs from the same router for different prefixes, with =
different default router priority, it would actually use this =
information?

if each border router advertises what's essentially a source constrained =
default route, would you need different priorities? you could of course, =
but then I think you would need the SS-RIO option.

>>>> b) explicit with new SS-RIO
>>>=20
>>> The good and bad thing with this one is that legacy hosts will not =
understand this new option.
>>=20
>> right, but I think we have that with either of the solutions.
>>=20
>>>> c) explicit with flags. new SS flag in PIO, and new SS flag in RIO
>>>=20
>>> How do hosts generally treat flags?
>>=20
>> well, they would have to implement them. ;-)
>=20
> Will they ignore the option if it has flags it doesn't understand?
>=20
> That's what differenting b from c here right?

yes, the flags are ignored.
so with re-using the PIO/RIO options a host would continue to use those =
as normal just without, or if implementing a) with source constrains. =
for the new SS-RIO option hosts that don't implement it would just =
ignore it altogether.

>> I'm not sure where to place PVDs here, I suppose you could look at =
them as being represented by multiple interfaces on the host, thereby =
making an MHMP host a MIMH (multi-interface multihomed) host instead.
>>=20
>> at least in homenet I would think the network will amalgamate the =
information from external sources and present a single view on the =
inside.
>=20
> Well, how would the host find out that there might be multiple PVDs on =
the same wire? One was was to come up with a new RIO that would include =
this information, ie a PVD identifier included in RAs.

I don't know. there might be two models, one where the network =
amalgamates the external information, and the only thing visible to the =
host is the prefixes, and the other which is the "virtual interface" to =
the host with PVDs. are PVDs largely needed to support walled gardens?

cheers,
Ole=


From nobody Mon Jan 26 08:15:00 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63FC61A90C6 for <ipv6@ietfa.amsl.com>; Mon, 26 Jan 2015 08:14:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VhtVt0un9YA6 for <ipv6@ietfa.amsl.com>; Mon, 26 Jan 2015 08:14:56 -0800 (PST)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 595421A8A93 for <ipv6@ietf.org>; Mon, 26 Jan 2015 08:14:56 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t0QGEs1h007512 for <ipv6@ietf.org>; Mon, 26 Jan 2015 17:14:54 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 05148205A0C for <ipv6@ietf.org>; Mon, 26 Jan 2015 17:15:23 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id E6C242059C8 for <ipv6@ietf.org>; Mon, 26 Jan 2015 17:15:22 +0100 (CET)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t0QGEpXP027006 for <ipv6@ietf.org>; Mon, 26 Jan 2015 17:14:53 +0100
Message-ID: <54C667FB.2080008@gmail.com>
Date: Mon, 26 Jan 2015 17:14:51 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: I-D Action: draft-ietf-6man-default-iids-02.txt
References: <20150123173011.18444.83799.idtracker@ietfa.amsl.com> <CADhXe52m97Pk4PxY=iu5mbWaK8ZGmQMzwEO5MfNDfi5SjJywVg@mail.gmail.com> <54C2AF7F.1000708@si6networks.com>
In-Reply-To: <54C2AF7F.1000708@si6networks.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/vuJIXNeVn02Cthgp1i-Ru11QHsg>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 16:14:58 -0000

Le 23/01/2015 21:30, Fernando Gont a écrit :
> Hi, James,
>
> On 01/23/2015 05:11 PM, James Woodyatt wrote:
>> Everyone—
>>
>>      Link layers MUST define a mechanism that provides that mitigates the
>>      security and privacy implications discussed in Section 1.
>>
>>
>> Editorial nit: "that provides that mitigates" seems like an awkward
>> phrase, and I'm not sure what it means. This is a pretty important
>> requirement specification, so I'd like to see it written with optimal
>> clarity. How about this for starters:
>>
>>    Link layers MUST define a mechanism that provides mitigation of the
>> security and privacy issues discussed in section 1.
>
> You're right (my bad!) -- will get this fixed in the next rev.

HEllo,

BEyond fixing the double that, what does this requirement mean to link 
layers?

For example, ieee 802.11p does not offer security features, assuming 
some other ieee protocol (and why not an IP protocol) will.  Would the 
default-iid requirement still apply to ieee 802.11p links?

Also, better privacy needs IIDs bigger than 64 (what does 'mitigate' 
mean).  Does default-iid requirement mean that new link layers should 
use IIDs of other length than 64?

What is this requirement more clearly?

Alex


>
> Thanks!
>
> Best regards,
>



From nobody Mon Jan 26 10:57:48 2015
Return-Path: <ot@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC8691ACE2B; Mon, 26 Jan 2015 10:57:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27i7yJKBR-L8; Mon, 26 Jan 2015 10:57:45 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 997731ACE30; Mon, 26 Jan 2015 10:57:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Ole Troan" <ot@cisco.com>
To: brian@innovationslab.net
Subject: Publication has been requested for draft-ietf-6man-resilient-rs-04
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150126185702.21749.14548.idtracker@ietfa.amsl.com>
Date: Mon, 26 Jan 2015 10:57:02 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/b-PB_xdv06PAw5uSABHDSww4kuw>
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-resilient-rs.all@tools.ietf.org, iesg-secretary@ietf.org, ot@cisco.com, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 18:57:47 -0000

Ole Troan has requested publication of draft-ietf-6man-resilient-rs-04 as Proposed Standard on behalf of the 6MAN working group.

Please verify the document's state at http://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/


From nobody Mon Jan 26 11:13:12 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B2471A8ADB for <ipv6@ietfa.amsl.com>; Mon, 26 Jan 2015 11:13:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g299dxvDfjIN for <ipv6@ietfa.amsl.com>; Mon, 26 Jan 2015 11:13:08 -0800 (PST)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 181CE1ACE9E for <ipv6@ietf.org>; Mon, 26 Jan 2015 11:13:06 -0800 (PST)
Received: by mail-pd0-f172.google.com with SMTP id v10so13620901pde.3 for <ipv6@ietf.org>; Mon, 26 Jan 2015 11:13:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Ihm5QrkqBC4fkkBlolU6k2VpKUdF+3cudaJhFbVVOvw=; b=ougZV6QsBhPGtZnvb+dUfLPG51kHLa+5YUnyS9G3a8jvuc9ThADD1q8z0qtxCNa/TD VWHIQTIlgJBwOMl8LxP2RdJwE9qZjotGCrj2ju5DlisU2w08dEEx0wfP9wgQv/+n7LOY 8hRTnWXyfhbvVXVi9GAMzD0BX8R9pgcFIho4j/bf6KxqlngcYLHPrDQmLMKC1l3Y+Lxj b63VuyVEw3gfEmYVKDXDBIwQLahddSBFuKdKuZaamt0nXZ1Ki4Q+rvzbdFPvrbquG6GP JkicutqeY8TmJnq7yxEvJb/CG3jmRixBQHe8nq8PSFzjGNmkctNb0bIrDKycJv6vOZjt BIKg==
X-Received: by 10.70.132.73 with SMTP id os9mr6683000pdb.110.1422299585291; Mon, 26 Jan 2015 11:13:05 -0800 (PST)
Received: from ?IPv6:2406:e007:73ff:1:28cc:dc4c:9703:6781? ([2406:e007:73ff:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id j8sm10394395pdo.79.2015.01.26.11.13.02 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Jan 2015 11:13:04 -0800 (PST)
Message-ID: <54C691BB.2090503@gmail.com>
Date: Tue, 27 Jan 2015 08:12:59 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>,  Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <54C3F0C7.6060603@gmail.com> <0BB30257-0F3A-4DD4-AEE5-01CA36C25407@employees.org> <54C41EC2.509@gmail.com> <16A24C7B-4B3F-43F8-B72C-10ED04EDCC39@employees.org> <127A700A-34BD-40B0-9234-9AF3521EE543@darou.fr> <AB43E5F2-326B-4617-AA38-1971BFC82851@employees.org> <alpine.DEB.2.02.1501261116300.22729@uplift.swm.pp.se> <7E6B22E0-4DAB-4CC1-9CA1-4B03422FC1FA@employees.org> <alpine.DEB.2.02.1501261234340.22729@uplift.swm.pp.se> <D09138C1-236A-49E0-B23D-D8B823DF1F69@employees.org>
In-Reply-To: <D09138C1-236A-49E0-B23D-D8B823DF1F69@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/FUFH8r2j5nI6sZKv-LI7mo1cHcI>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 19:13:10 -0000

On 27/01/2015 00:57, Ole Troan wrote:

<snip>

>>> at least in homenet I would think the network will amalgamate the information from external sources and present a single view on the inside.
>>
>> Well, how would the host find out that there might be multiple PVDs on the same wire? One was was to come up with a new RIO that would include this information, ie a PVD identifier included in RAs.
> 
> I don't know. there might be two models, one where the network amalgamates the external information, and the only thing visible to the host is the prefixes, and the other which is the "virtual interface" to the host with PVDs. are PVDs largely needed to support walled gardens?

I am puzzled. Has "the network" evolved into a super-brain that can amalgamate
information on its own? Either every host will have to accumulate all the
information and perform some kind of analysis, or a designated router will
have to do so, or a distributed autonomic process will have to do so.
I see a lot of dots in this discussion that need joining together still.

    Brian


From nobody Mon Jan 26 11:20:37 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BACC1A90BC for <ipv6@ietfa.amsl.com>; Mon, 26 Jan 2015 11:20:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CTlDC5jpLY8x for <ipv6@ietfa.amsl.com>; Mon, 26 Jan 2015 11:20:32 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39F381A8BC2 for <ipv6@ietf.org>; Mon, 26 Jan 2015 11:20:32 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id E85586289; Mon, 26 Jan 2015 11:20:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=cw9YQRE6KKbvHrIQ5jdkgKTVAcg=; b=jtayfUqBgvEI4QBcWA Ng7ap3YKZmwH25u47I3zwHGcGJLCEV/1rjFnXqNWXElEJVMgEI8dSiK5gJaaKzEa AunyNIYwMtP8lrPuec/hJ8F/PJArACfmqKB7UfeKYcoHE+VORrNzx+6v/pU57Hus ckaLXKfUFzfHlWAacfL9KvJc0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=HVBBDhN91HyqcuFTlW2Zqifdb+LGTWoeWSk8AbGMSIKtlT08zDM 6c5QCcPiC5/669xmOZ1cE+0jM5EG31h44Jdg2eWrFBlQnaSDg50uqUvKwjz4GGsj /4V3BBSQCQZm4hfyHh6yMWW1BD30jn7GZMaQssFlUcmU6xG4R1If7bNo=
Received: from gomlefisk.localdomain (unknown [195.159.234.46]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id A369D61E9; Mon, 26 Jan 2015 11:20:29 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 3262B3D5A809; Mon, 26 Jan 2015 20:20:29 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.4\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <54C691BB.2090503@gmail.com>
Date: Mon, 26 Jan 2015 20:20:28 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <535F6916-3BA8-4521-8BBA-024DD7DBD3F2@employees.org>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <54C3F0C7.6060603@gmail.com> <0BB30257-0F3A-4DD4-AEE5-01CA36C25407@employees.org> <54C41EC2.509@gmail.com> <16A24C7B-4B3F-43F8-B72C-10ED04EDCC39@employees.org> <127A700A-34BD-40B0-9234-9AF3521EE543@darou.fr> <AB43E5F2-326B-4617-AA38-1971BFC82851@employees.org> <alpine.DEB.2.02.1501261116300.22729@uplift.swm.pp.se> <7E6B22E0-4DAB-4CC1-9CA1-4B03422FC1FA@employees.org> <alpine.DEB.2.02.1501261234340.22729@uplift.swm.pp.se> <D09138C1-236A-49E0-B23D-D8B823DF1F69@employees.org> <54C691BB.2090503@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.2070.4)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/bSJjussoEGl_vRnHeGPeMHBAs5o>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 19:20:34 -0000

Brian,

> <snip>
>=20
>>>> at least in homenet I would think the network will amalgamate the =
information from external sources and present a single view on the =
inside.
>>>=20
>>> Well, how would the host find out that there might be multiple PVDs =
on the same wire? One was was to come up with a new RIO that would =
include this information, ie a PVD identifier included in RAs.
>>=20
>> I don't know. there might be two models, one where the network =
amalgamates the external information, and the only thing visible to the =
host is the prefixes, and the other which is the "virtual interface" to =
the host with PVDs. are PVDs largely needed to support walled gardens?
>=20
> I am puzzled. Has "the network" evolved into a super-brain that can =
amalgamate
> information on its own? Either every host will have to accumulate all =
the
> information and perform some kind of analysis, or a designated router =
will
> have to do so, or a distributed autonomic process will have to do so.
> I see a lot of dots in this discussion that need joining together =
still.

a super-brain I think not. ;-)
if we take homenet as an example, then there really isn't that much that =
is learnt from the upstreams.
one example of amalgamation would be the border routers learn the ISPs =
recursive resolvers, but the homenet offers its own DNS caching server =
forwarding to the ISPs one (according to whatever DNS server selection =
policy received).

that's pretty much how most homenets work today. examples of the other =
model, would be where each host had PPPoE sessions to a set of ISPs =
directly.

cheers,
Ole=


From nobody Mon Jan 26 13:29:38 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8CFD1AC3B1 for <ipv6@ietfa.amsl.com>; Mon, 26 Jan 2015 13:29:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, TVD_SPACE_RATIO=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4S_-ZFuA009H; Mon, 26 Jan 2015 13:29:35 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DB6EB1A6F96; Mon, 26 Jan 2015 13:29:35 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: 6man-chairs@tools.ietf.org, draft-ietf-6man-resilient-rs.all@tools.ietf.org, ipv6@ietf.org, ot@cisco.com
Subject: ID Tracker State Update Notice: <draft-ietf-6man-resilient-rs-04.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.1.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150126212935.26698.24867.idtracker@ietfa.amsl.com>
Date: Mon, 26 Jan 2015 13:29:35 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/-PvZwZWPPU0MK72txflcBNS7x2A>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jan 2015 21:29:37 -0000

IESG state changed to AD Evaluation from Publication Requested
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/


From nobody Tue Jan 27 09:59:41 2015
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FF641A1F16 for <ipv6@ietfa.amsl.com>; Tue, 27 Jan 2015 09:59:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id InBEPI2pSZ7T for <ipv6@ietfa.amsl.com>; Tue, 27 Jan 2015 09:59:38 -0800 (PST)
Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37A3B1A1F20 for <6man@ietf.org>; Tue, 27 Jan 2015 09:59:38 -0800 (PST)
Received: by mail-lb0-f173.google.com with SMTP id p9so14509885lbv.4 for <6man@ietf.org>; Tue, 27 Jan 2015 09:59:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=m/9+NhCNLPL7NI2oG5hvwl9iEPCuW+AYFfcwP2B/j1c=; b=fFrIEH/fasoSr8HfQhiTkZL/JRMklO57VRM/w8GLMSRAkQtT50abIQG0Z7vL+5gl/5 Qx9x31riTj4TxIjnpssoYPqd2dxW9FmH8HoQN9g/JJAwKhWMtgN2t/miYxl7mqezSmEw ONf2FJ6fdXeYaP3gboRlp7bkuOKbhoT31I0dsphZLGRy8dqY+AlIrRQf2s4ZE5wNBNIt 5/UoVqjlkRGjawny7fwUc6oDNvkExgpKAGYyE6emDtGdVJdNxG0uvf7tAT/WiC62h3QN JqdnW+i9rmpUbZaw7D7caEJf/Os9fJoe4dHs+w9ZnKvG90fqFOOQBDCHQwyPJJt1MMn/ A5dw==
MIME-Version: 1.0
X-Received: by 10.152.163.100 with SMTP id yh4mr3197151lab.98.1422381576638; Tue, 27 Jan 2015 09:59:36 -0800 (PST)
Received: by 10.114.80.231 with HTTP; Tue, 27 Jan 2015 09:59:36 -0800 (PST)
In-Reply-To: <1F17C514-D466-4069-9D1E-9EE15E59995F@darou.fr>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <1F17C514-D466-4069-9D1E-9EE15E59995F@darou.fr>
Date: Tue, 27 Jan 2015 11:59:36 -0600
Message-ID: <CAC8QAceabpe+bHPyQD7fJCXzS-kh17ESw-zoax_pJSKhbmz4Dw@mail.gmail.com>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Pierre Pfister <pierre.pfister@darou.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/SldywtzKZ0lXDEAUIbjJNKAZbE4>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jan 2015 17:59:39 -0000

Hello Pierre,

On Sun, Jan 25, 2015 at 4:54 AM, Pierre Pfister <pierre.pfister@darou.fr> w=
rote:
> Hello Behcet
>
>>
>> I am not sure if you read Section 5.2 in this draft and Section 13 in
>> draft-sarikaya-6man-next-hop-ra-04?
>> I had these in an effort to satisfy your concerns. Your mails seems to
>> indicate that you did not even read them.
>> Poor me :-)
>
> Thank you for the effort. I actually read the update.
> My point was that we only need one single RA option to solve all the situ=
ations. You added yet-another option.

Again, it seems like you did not read my reply to your mail

http://www.ietf.org/mail-archive/web/ipv6/current/msg21655.html
on December 8.

In that mail, I explained that your proposal comes down to proposing 3
new options.

> Also, as Ole mentioned, third party next-hop doesn=E2=80=99t seem like a =
good idea to me (at least in RAs, I dont know in DHCP).

I think it makes more sense with DHCP because DHCP server is not a router.
>

I meant Section 13 by itself, not including the others with the next
hop. That was the idea with Section 2 in SADR Overview draft entitled
Router Advertisement Option
 While Section 3 includes an Option Set with next hop options as well.


> And I just realized all your options contain one single source address.
> But what we actually need, IMHO, is rather a source prefix.

Absolutely. Anywhere it says source address, it refers to source prefix.

Regards,

Behcet
>
> Regards,
>
> - Pierre
>


From nobody Tue Jan 27 12:05:36 2015
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C6651A8A8C for <ipv6@ietfa.amsl.com>; Tue, 27 Jan 2015 12:05:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cFHpgvkLkTqy; Tue, 27 Jan 2015 12:05:19 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 501921A8A50; Tue, 27 Jan 2015 12:05:12 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: 6man-chairs@tools.ietf.org, ot@cisco.com, draft-ietf-6man-enhanced-dad.all@tools.ietf.org, ipv6@ietf.org
Subject: ID Tracker State Update Notice: <draft-ietf-6man-enhanced-dad-12.txt>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.1.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150127200512.8606.87142.idtracker@ietfa.amsl.com>
Date: Tue, 27 Jan 2015 12:05:12 -0800
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/8USxGd-SzxhEEvgfpu0Qe2poZYU>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jan 2015 20:05:27 -0000

IANA review state changed to IANA OK - No Actions Needed
ID Tracker URL: http://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-dad/


From nobody Tue Jan 27 16:59:59 2015
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2256A1A0095 for <ipv6@ietfa.amsl.com>; Tue, 27 Jan 2015 16:59:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mYVCi6gmFHLu for <ipv6@ietfa.amsl.com>; Tue, 27 Jan 2015 16:59:56 -0800 (PST)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAED61A006B for <6man@ietf.org>; Tue, 27 Jan 2015 16:59:55 -0800 (PST)
Received: by mail-ie0-f177.google.com with SMTP id vy18so18791859iec.8 for <6man@ietf.org>; Tue, 27 Jan 2015 16:59:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=sJBit3fxipB8CJ+FROA6YHBQCbaX3O6ioEkAqynhkos=; b=jPK+2shY2H2cCWYOTpouAbWBwJgi9DQODUSevmBuiy5pVZHCJyRbKaGv4VlGMSfM9o xovJv2wITCCpQGkf/SKsXeabTUeHBT1efZ1RUg9xcNPMDNNsbfgZhHZ4b6umyZq1qdT5 baqCUjWbxkJQKmjgKU7Zy0qiX6UAv8PtvDGptkkY8W3Bi93IIGhkTZspx5G1536/B6qw hbxqNU8vvlIEa+diSg8IVo+JE/ZYolNQMtv/9gi537LV/X9jsGUnpWwBGcm5jT+l/h0a DInjCW64OO78p5QM/kgrM9sA7Yxn+HFcmu/nhAwRd1O3UhcQrQC3HqkSU+l86DW4vcUX jHPQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=sJBit3fxipB8CJ+FROA6YHBQCbaX3O6ioEkAqynhkos=; b=gcrXjp62584RdevbaZlJXoHTYEQzbD+NjcbcSAogUP+LwUE7fSxRNEq+mg33lJkJig ZDg3QXmue56tuQH/30Nq4OiwaDzw2hzDHCCA8PQ4a/yEuUPqESemEIdpo3dtM6Dnm9jg e3B2G+YnYVB16t8KvOepajhf9BwlddP3yvkuOWDEOTomhl9366vlWOr/EUhwd//Vx0fs VlK5Viw/vkh+RtMSkn/wRrOpkWFjqH94QEJ5qC4N3RnLQTrdr/Ehi4bkISesTjKnJ+nA Dx6CXtfeQ6XDbCjiDewIQZscnihYVo54Ac2W/lJ+6FHlELmgVjLHrrfhJTsQZtQdKvNv nB0A==
X-Gm-Message-State: ALoCoQk+XFObBwQt/u5jGdo8mHuysU2EDW7jyhMX4GUh48eu94+oUdwbyDBhrc/9LkstOhvV27KH
X-Received: by 10.107.136.20 with SMTP id k20mr961032iod.59.1422406795025; Tue, 27 Jan 2015 16:59:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.138.136 with HTTP; Tue, 27 Jan 2015 16:59:33 -0800 (PST)
In-Reply-To: <CAC8QAceabpe+bHPyQD7fJCXzS-kh17ESw-zoax_pJSKhbmz4Dw@mail.gmail.com>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <1F17C514-D466-4069-9D1E-9EE15E59995F@darou.fr> <CAC8QAceabpe+bHPyQD7fJCXzS-kh17ESw-zoax_pJSKhbmz4Dw@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 28 Jan 2015 09:59:33 +0900
Message-ID: <CAKD1Yr0waXtgp3g2gcH64ygQ3zE_ktfi3mA+2tqpUYtAXujOzg@mail.gmail.com>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
To: Behcet Sarikaya <sarikaya@ieee.org>
Content-Type: multipart/alternative; boundary=001a113ed152be8fb3050dabe3d5
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/-q1AQgNoz31T-ZB6JK6u5yjWhuY>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jan 2015 00:59:57 -0000

--001a113ed152be8fb3050dabe3d5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 28, 2015 at 2:59 AM, Behcet Sarikaya <sarikaya2012@gmail.com>
wrote:

> > Also, as Ole mentioned, third party next-hop doesn=E2=80=99t seem like =
a good
> idea to me (at least in RAs, I dont know in DHCP).
>
> I think it makes more sense with DHCP because DHCP server is not a router=
.


And that is why we don't do routing in DHCP: it's a bad idea.

--001a113ed152be8fb3050dabe3d5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Jan 28, 2015 at 2:59 AM, Behcet Sarikaya <span dir=3D"ltr">&lt;<a href=
=3D"mailto:sarikaya2012@gmail.com" target=3D"_blank">sarikaya2012@gmail.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">&=
gt; Also, as Ole mentioned, third party next-hop doesn=E2=80=99t seem like =
a good idea to me (at least in RAs, I dont know in DHCP).<br>
<br>
</span>I think it makes more sense with DHCP because DHCP server is not a r=
outer.</blockquote><div><br></div><div>And that is why we don&#39;t do rout=
ing in DHCP: it&#39;s a bad idea.</div></div></div></div>

--001a113ed152be8fb3050dabe3d5--


From nobody Tue Jan 27 20:31:21 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 293C61ACD0C for <ipv6@ietfa.amsl.com>; Tue, 27 Jan 2015 20:31:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gabj2vjQMj7w for <ipv6@ietfa.amsl.com>; Tue, 27 Jan 2015 20:31:18 -0800 (PST)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84A671A1B9B for <6man@ietf.org>; Tue, 27 Jan 2015 20:31:18 -0800 (PST)
Received: by mail-pd0-f172.google.com with SMTP id v10so23212203pde.3 for <6man@ietf.org>; Tue, 27 Jan 2015 20:31:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=b9ldK5rV4boWLSyeQbjcJurxrwM4H5JbLQphvCVt/Fg=; b=HG3sOQUB0B7HOuE381ZzkaoCl3vfVbEoIJCtyZ2Q4kBVmLnNEBgEk7SV6A+nVYBwRW xzgHSn/p+SrLehLVs50/W9EHLHbGyx5Fpf2Jx1x0KvOhfHYJJoIW7TBsewEv2HfIIT9x b6X29DWZsU088ohNLoQzn1eNStyuJrdE0WngdCbzdBaOBD62lrGnXyJiZpeKwKDfJrc3 wHyRrefsok8Wi4dU4OEe/KhI9PdmB5lz028eIx1UemXvqkLLj2Z88y9SoZVtU9XvKfkR 8wx7Y/9nRWU1N1c49Mcy98a8IwcYKHqQOAy968kxZ+YQAOH/Bt4R6YpI2GQjNQ1+dsQJ 9KAQ==
X-Received: by 10.68.236.67 with SMTP id us3mr2183358pbc.121.1422419477765; Tue, 27 Jan 2015 20:31:17 -0800 (PST)
Received: from [192.168.1.67] (210-86-2-198.adsl.xtra.co.nz. [210.86.2.198]) by mx.google.com with ESMTPSA id hx9sm3178563pad.38.2015.01.27.20.31.14 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 Jan 2015 20:31:16 -0800 (PST)
Message-ID: <54C86618.4070505@gmail.com>
Date: Wed, 28 Jan 2015 17:31:20 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>, Behcet Sarikaya <sarikaya@ieee.org>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <1F17C514-D466-4069-9D1E-9EE15E59995F@darou.fr> <CAC8QAceabpe+bHPyQD7fJCXzS-kh17ESw-zoax_pJSKhbmz4Dw@mail.gmail.com> <CAKD1Yr0waXtgp3g2gcH64ygQ3zE_ktfi3mA+2tqpUYtAXujOzg@mail.gmail.com>
In-Reply-To: <CAKD1Yr0waXtgp3g2gcH64ygQ3zE_ktfi3mA+2tqpUYtAXujOzg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/plfFHhQiq9Loa6Oul3jXOyxl3_I>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jan 2015 04:31:20 -0000

On 28/01/2015 13:59, Lorenzo Colitti wrote:
> On Wed, Jan 28, 2015 at 2:59 AM, Behcet Sarikaya <sarikaya2012@gmail.co=
m>
> wrote:
>=20
>>> Also, as Ole mentioned, third party next-hop doesn=E2=80=99t seem lik=
e a good
>> idea to me (at least in RAs, I dont know in DHCP).
>>
>> I think it makes more sense with DHCP because DHCP server is not a rou=
ter.
>=20
>=20
> And that is why we don't do routing in DHCP: it's a bad idea.

Nevertheless, DHCP(v4) hands out the address of the default router.
By a strange coincidence, in most unmanaged networks the DHCP server
has the same IP address as the default router. However, in v4 and v6
the DHCP server is logically disjoint from the default router, and
Lorenzo and Behcet seem to agree on that. They disagree on whether
it matters.

   Brian


From nobody Tue Jan 27 20:57:07 2015
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 565861ACD2E for <ipv6@ietfa.amsl.com>; Tue, 27 Jan 2015 20:57:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Epe7uRhpCe7r for <ipv6@ietfa.amsl.com>; Tue, 27 Jan 2015 20:56:59 -0800 (PST)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 585B31ACD2C for <6man@ietf.org>; Tue, 27 Jan 2015 20:56:59 -0800 (PST)
Received: by mail-ie0-f176.google.com with SMTP id rd18so19592139iec.7 for <6man@ietf.org>; Tue, 27 Jan 2015 20:56:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=OuUMg4Og2sxXQWoTM52M+JXGE0i/PdPZi+v22gOLTqc=; b=mkNZZ8iCt0AbG3rna5UfawL1oo4Xtr/8YllCV2zGxbvWbKQ13pGPxaomWZ5CXcKKqz YmnSmkK+pC0oLG8zdnah83rk6nm5pUf8nZIyyw9XzgPwGwRtaz87/2CR9fMvRKx5xQ37 SuYoUNB/wLeqKCDt12a3hAgi7wmHa4ROwBC7kM3C+4FIRAVSpncJBRcg9vwdcNblTKpf /sryfIkNcxi8OhIPVZ6ua+XJHVdA2NK8WsEeu7NHA3qh5cd4L06KnEzKAI4okLCQ56zU tUbKXssKZzyjd9nkpbYLRr9IaeUTATEjKI9TriO6vNCGUD+s8XhIDOwz7VXS4X+QVc8B qgiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=OuUMg4Og2sxXQWoTM52M+JXGE0i/PdPZi+v22gOLTqc=; b=J02YZGmCr4qEUEop+ZBCVzHSmuwFlLHf+7fcY9REVl1M15CE8puBrw4DVxb4US+NLI 5KqkwTaKk8nRpAjVuQNs3fVGlUdfvMvCEpnPVQP2DD7GXpYeJRRAlrRmFDzW9m7gvARa j/+ID1RGobBRsT+YMyuvmRHA+Kz01iYcXWBiX8vae2KCLXTkh2tWANLXtsyXNdmxJ0Th ftz5LEmiFUcqQ2YjtUrNTPe/I4uMmHKZzB8YW86N+IFFAJfrnx9oNKqF6bhmMM6ktkQR 09xQQlej50VK7RclN74C8Bo/uF0gg5TQhzJ8ny4zR6OTHkO0YoNrdSQRZ5H/GQ1dGRvd uKNg==
X-Gm-Message-State: ALoCoQllokStUcNaf3OjkGV7Bi0HD59edKGO9fYQ5cv3rKXauUvHFXJeEw21+WaWUKw04H12VcBx
X-Received: by 10.107.133.203 with SMTP id p72mr1728324ioi.31.1422421018419; Tue, 27 Jan 2015 20:56:58 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.138.136 with HTTP; Tue, 27 Jan 2015 20:56:38 -0800 (PST)
In-Reply-To: <54C86618.4070505@gmail.com>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <1F17C514-D466-4069-9D1E-9EE15E59995F@darou.fr> <CAC8QAceabpe+bHPyQD7fJCXzS-kh17ESw-zoax_pJSKhbmz4Dw@mail.gmail.com> <CAKD1Yr0waXtgp3g2gcH64ygQ3zE_ktfi3mA+2tqpUYtAXujOzg@mail.gmail.com> <54C86618.4070505@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 28 Jan 2015 13:56:38 +0900
Message-ID: <CAKD1Yr1=J4RiMDopJi9--WiFUEBbVwpnB91gjfiAaeMn1ZmxqQ@mail.gmail.com>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a113ed494864647050daf3370
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/7Z_Wffgi4UuvLhWdRfACFZmtlQ4>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jan 2015 04:57:04 -0000

--001a113ed494864647050daf3370
Content-Type: text/plain; charset=UTF-8

On Wed, Jan 28, 2015 at 1:31 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> > And that is why we don't do routing in DHCP: it's a bad idea.
>
> Nevertheless, DHCP(v4) hands out the address of the default router.
>

It does, and that's the reason we have to run VRRP. We can do better than
that.

--001a113ed494864647050daf3370
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Jan 28, 2015 at 1:31 PM, Brian E Carpenter <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpente=
r@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div cl=
ass=3D"HOEnZb"><div class=3D"h5">&gt; And that is why we don&#39;t do routi=
ng in DHCP: it&#39;s a bad idea.<br>
<br>
</div></div>Nevertheless, DHCP(v4) hands out the address of the default rou=
ter.<br></blockquote><div><br></div><div>It does, and that&#39;s the reason=
 we have to run VRRP. We can do better than that.</div></div></div></div>

--001a113ed494864647050daf3370--


From nobody Wed Jan 28 00:12:29 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 998F41A00E8 for <ipv6@ietfa.amsl.com>; Wed, 28 Jan 2015 00:12:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xijujLwBucB1 for <ipv6@ietfa.amsl.com>; Wed, 28 Jan 2015 00:12:26 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF4111A004C for <6man@ietf.org>; Wed, 28 Jan 2015 00:12:25 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 9DC68617B; Wed, 28 Jan 2015 00:12:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; s= selector1; bh=kiUVYzGFC9+XN7Qc8Yl8yCiUu9o=; b=e0KIGM93g6L1rGII6A LaBsLFX5mlqMjhELVkQACzxffW3nW6kdEzEw0j0qcDuGkG0ijns89PUFXjLQG+Q1 uI5G8fZw6k14SinJBl6cNjtnPso/2qwWXOeF9mU8Eg0zHM7T5PynerewH1wkYj2c LCNb1Y+OJFswypkguWOWTWZCk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=Y8giWWFd/hwHYcx8fv9O8G4zDW4sbcey+BJRxGvcgxpQF7Mal64 yNR3sXnN4dLHhCcxCDzVWzgQ/n/g42jFgEurVcxuSsMo/klrPbs1RkgvJivP+2XT AvhPmR6y5gJGdkv2nSU8eLNTbEbeFgBFQ5ecOvcXcLMuqqT0TZffCp+k=
Received: from gomlefisk.localdomain (unknown [217.144.253.210]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 59657614B; Wed, 28 Jan 2015 00:12:24 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 2DFFE3D724C4; Wed, 28 Jan 2015 09:12:25 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.4\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <54C86618.4070505@gmail.com>
Date: Wed, 28 Jan 2015 09:12:24 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <323EF2A4-9200-4382-953F-752ABBE29126@employees.org>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <1F17C514-D466-4069-9D1E-9EE15E59995F@darou.fr> <CAC8QAceabpe+bHPyQD7fJCXzS-kh17ESw-zoax_pJSKhbmz4Dw@mail.gmail.com> <CAKD1Yr0waXtgp3g2gcH64ygQ3zE_ktfi3mA+2tqpUYtAXujOzg@mail.gmail.com> <54C86618.4070505@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Lorenzo Colitti <lorenzo@google.com>, Behcet Sarikaya <sarikaya@ieee.org>, "6man@ietf.org" <6man@ietf.org>
X-Mailer: Apple Mail (2.2070.4)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/tfjrICVnFu0obXYTQxUNbNja5uc>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Jan 2015 08:12:28 -0000

<chair>

The proposal of adding a "route option" to DHCPv6 was discussed =
extensively in the MIF working group. The proposal did _not_ reach =
consensus.

I suggest that we do not reopen that debate. Unless there are new =
issues, not already brought up and considered in the MIF discussions. =
Parts of that discussion available here:
=
https://mailarchive.ietf.org/arch/search/?q=3Ddraft-ietf-mif-dhcpv6-route-=
option&f_list=3Dmif

</chair>

Best regards,
Ole

> On 28 Jan 2015, at 5:31 , Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> On 28/01/2015 13:59, Lorenzo Colitti wrote:
>> On Wed, Jan 28, 2015 at 2:59 AM, Behcet Sarikaya =
<sarikaya2012@gmail.com>
>> wrote:
>>=20
>>>> Also, as Ole mentioned, third party next-hop doesn=E2=80=99t seem =
like a good
>>> idea to me (at least in RAs, I dont know in DHCP).
>>>=20
>>> I think it makes more sense with DHCP because DHCP server is not a =
router.
>>=20
>>=20
>> And that is why we don't do routing in DHCP: it's a bad idea.
>=20
> Nevertheless, DHCP(v4) hands out the address of the default router.
> By a strange coincidence, in most unmanaged networks the DHCP server
> has the same IP address as the default router. However, in v4 and v6
> the DHCP server is logically disjoint from the default router, and
> Lorenzo and Behcet seem to agree on that. They disagree on whether
> it matters.
>=20
>   Brian
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Wed Jan 28 23:10:13 2015
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED63D1A0052 for <ipv6@ietfa.amsl.com>; Wed, 28 Jan 2015 23:10:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kqrASOCUUgrX for <ipv6@ietfa.amsl.com>; Wed, 28 Jan 2015 23:10:09 -0800 (PST)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 06B9D1A000C for <6man@ietf.org>; Wed, 28 Jan 2015 23:10:08 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 7D6F3871518; Thu, 29 Jan 2015 08:10:07 +0100 (CET)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V473S6mzIaUg; Thu, 29 Jan 2015 08:10:07 +0100 (CET)
Received: from Rays-iMac.local (092-111-140-211.static.chello.nl [92.111.140.211]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id 54897870069; Thu, 29 Jan 2015 08:10:07 +0100 (CET)
Message-ID: <54C9DCCD.4090802@globis.net>
Date: Thu, 29 Jan 2015 08:10:05 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: sarikaya@ieee.org
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com>
In-Reply-To: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Zc22s7cPGWgB0U-TZiAtRAwXGVo>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 07:10:11 -0000

Behcet Sarikaya wrote:
>   Hi all,
>
> On the solutions to the problem and issues discussed in this draft:
> http://tools.ietf.org/id/draft-sarikaya-6man-sadr-overview-04.txt
>
> we would like to hear from the working group. Referring to Section 5,
> which solution approach WG prefers? RA options as in Section 5.2?
> Section 5.3?
> Also regarding the corresponding DHCP work, which direction is the
> preferred direction?
>
> Your opinions are welcome.
>
> Regards,
>
> Behcet
>
>
I have read this draft. May I humbly suggest that I don't think you guys 
are on the right track at all with your problem statement.

You seem to think the problem with Homenet is how a non-mobile host 
discovers the correct SADR outbound route in the presence of a link 
shared between multiple provider routers, and there being no "cross 
link" higher in the topology to sort out incorrectly routed packets.

To me that's fighting an old battle (equivalent to IPv4 HSRP/VRRP + next 
hop/object trackers to counter split-brain and faults higher in the 
topology).

IMHO the real issue in Homenet routing is how to ensure that hosts that 
roam between various L3 subnets (because they move around in the Homenet 
and pick up various L3 WiFi interfaces) are correctly routed, also in 
the presence of multiple alternative wireless links.

That requires solving the reverse route too, and anything like VRRP is 
going to be hopeless.

IMVHO I think that hosts that want to be this flexible will be forced to 
actively participate in Homenet routing protocols, and that these hosts 
will have to be assigned their own /64 to a non-time-variant 
software-loopback interface that does not have to renumber as the end 
node moves between L3 LANs..

-- 
Regards,
RayH


From nobody Thu Jan 29 14:31:52 2015
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 315791A8869 for <ipv6@ietfa.amsl.com>; Thu, 29 Jan 2015 14:31:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v9IMxBxWjFeq for <ipv6@ietfa.amsl.com>; Thu, 29 Jan 2015 14:31:40 -0800 (PST)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BF541A6FF6 for <6man@ietf.org>; Thu, 29 Jan 2015 14:31:40 -0800 (PST)
Received: by mail-lb0-f178.google.com with SMTP id u10so33310208lbd.9 for <6man@ietf.org>; Thu, 29 Jan 2015 14:31:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=O42r8dwUpz5GAfjLNq/drYcOSC8WoNCaUNbjhh62mCE=; b=gSWWoKKBx4S+fRk+TB6xoIxhhqySdT5frI4kBzfyztlNFba1CnZyEJMNqtvW+0ih5o ANE4FG4Rrwwp7gSPNVxLYpEKSsJcP/n3S0s33oP7vRxjnxBG2dP+cB9tzsG+TI4TguP6 Xgtpswf51mHtAqk98szMdfEBKVyaQuXkso1zFA8rpzwl34Z6Krfoc7Nw/7PjqqfdH9az MV0sd+bkPzgi47cND8MAMGhrapt51dCI2Mw+e6RofVm+kNvJS6wHsjAb7ghqm6UbaKgg eOGg6qXSp46SJ67B1ov14Zoe6OF5S7/IoAefiSAK/PKaGvewezXaXD4WOojzvJ+3G0md RGNg==
MIME-Version: 1.0
X-Received: by 10.152.203.230 with SMTP id kt6mr3587933lac.38.1422570698600; Thu, 29 Jan 2015 14:31:38 -0800 (PST)
Received: by 10.114.80.231 with HTTP; Thu, 29 Jan 2015 14:31:38 -0800 (PST)
In-Reply-To: <323EF2A4-9200-4382-953F-752ABBE29126@employees.org>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <1F17C514-D466-4069-9D1E-9EE15E59995F@darou.fr> <CAC8QAceabpe+bHPyQD7fJCXzS-kh17ESw-zoax_pJSKhbmz4Dw@mail.gmail.com> <CAKD1Yr0waXtgp3g2gcH64ygQ3zE_ktfi3mA+2tqpUYtAXujOzg@mail.gmail.com> <54C86618.4070505@gmail.com> <323EF2A4-9200-4382-953F-752ABBE29126@employees.org>
Date: Thu, 29 Jan 2015 16:31:38 -0600
Message-ID: <CAC8QAcfWAKWDwr9vxw-F04rrZA8cHbrpWdxfh1tJ52VTigL1WA@mail.gmail.com>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/lVVOgtgl4HwdERTsbnFljie-Qk4>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 22:31:42 -0000

On Wed, Jan 28, 2015 at 2:12 AM, Ole Troan <otroan@employees.org> wrote:
> <chair>
>
> The proposal of adding a "route option" to DHCPv6 was discussed extensive=
ly in the MIF working group. The proposal did _not_ reach consensus.
>
> I suggest that we do not reopen that debate. Unless there are new issues,=
 not already brought up and considered in the MIF discussions. Parts of tha=
t discussion available here:
> https://mailarchive.ietf.org/arch/search/?q=3Ddraft-ietf-mif-dhcpv6-route=
-option&f_list=3Dmif
>

I know that discussion as I was co-author of the draft.

I think the conclusion was to move the discussion to 6man.
That's what we have been doing with SADR drafts.
Once we reach consensus on the RA option then we need to decide if a
corresponding DHCP option is needed for networks where DHCP is used
for this type of configuration.

Regards,

Behcet
> </chair>
>
> Best regards,
> Ole
>
>> On 28 Jan 2015, at 5:31 , Brian E Carpenter <brian.e.carpenter@gmail.com=
> wrote:
>>
>> On 28/01/2015 13:59, Lorenzo Colitti wrote:
>>> On Wed, Jan 28, 2015 at 2:59 AM, Behcet Sarikaya <sarikaya2012@gmail.co=
m>
>>> wrote:
>>>
>>>>> Also, as Ole mentioned, third party next-hop doesn=E2=80=99t seem lik=
e a good
>>>> idea to me (at least in RAs, I dont know in DHCP).
>>>>
>>>> I think it makes more sense with DHCP because DHCP server is not a rou=
ter.
>>>
>>>
>>> And that is why we don't do routing in DHCP: it's a bad idea.
>>
>> Nevertheless, DHCP(v4) hands out the address of the default router.
>> By a strange coincidence, in most unmanaged networks the DHCP server
>> has the same IP address as the default router. However, in v4 and v6
>> the DHCP server is logically disjoint from the default router, and
>> Lorenzo and Behcet seem to agree on that. They disagree on whether
>> it matters.
>>
>>   Brian
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>


From nobody Thu Jan 29 14:41:36 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 573871A023E for <ipv6@ietfa.amsl.com>; Thu, 29 Jan 2015 14:41:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VRVuVALQbWQJ for <ipv6@ietfa.amsl.com>; Thu, 29 Jan 2015 14:41:32 -0800 (PST)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D24E1A000D for <6man@ietf.org>; Thu, 29 Jan 2015 14:41:32 -0800 (PST)
Received: by mail-pa0-f51.google.com with SMTP id fb1so44161610pad.10 for <6man@ietf.org>; Thu, 29 Jan 2015 14:41:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=8Ccx0+O26kjxNd+ZavU4WLtoJey0bcg0EnhybAeDJ34=; b=CMr2DlY0ekxeGKOG8EVFV5UAwUjAfDcZnWbLuXMNf/JO/zZwaEagyh3HIsKv+6hyD3 DDFmzVNB9cRADjdmcPYxR4FE9RerUHtGwV4PqE6Zi0Q4UTaTwrpJHaW85TgP0UK44w8/ 7+4dsLA/25OG1ZMFv3D2+9bYDTSVZEuKd9/q/TwajmzkSogzJT+PgUG901iBhaGSSae4 rZwWSo1O6u54RRWOxhJLs0JFfvm1MdHI7wg/ybs/hGYYts12cVrKDrdL0p0enLZbGD89 Id+WrsR5HSi1/Tl6VDTYEQuucfyRP+yc+S5p8Ft+mZCEKmyeJXAs1Eq9OX+66uiguRr6 05HQ==
X-Received: by 10.70.50.102 with SMTP id b6mr4419963pdo.38.1422571291557; Thu, 29 Jan 2015 14:41:31 -0800 (PST)
Received: from ?IPv6:2401:c80:3:0:28cc:dc4c:9703:6781? ([2401:c80:3:0:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id fy2sm8766931pbb.30.2015.01.29.14.41.27 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Jan 2015 14:41:30 -0800 (PST)
Message-ID: <54CAB71F.8010609@gmail.com>
Date: Fri, 30 Jan 2015 11:41:35 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: sarikaya@ieee.org, Ole Troan <otroan@employees.org>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com>	<CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com>	<50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr>	<CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com>	<1F17C514-D466-4069-9D1E-9EE15E59995F@darou.fr>	<CAC8QAceabpe+bHPyQD7fJCXzS-kh17ESw-zoax_pJSKhbmz4Dw@mail.gmail.com>	<CAKD1Yr0waXtgp3g2gcH64ygQ3zE_ktfi3mA+2tqpUYtAXujOzg@mail.gmail.com>	<54C86618.4070505@gmail.com>	<323EF2A4-9200-4382-953F-752ABBE29126@employees.org> <CAC8QAcfWAKWDwr9vxw-F04rrZA8cHbrpWdxfh1tJ52VTigL1WA@mail.gmail.com>
In-Reply-To: <CAC8QAcfWAKWDwr9vxw-F04rrZA8cHbrpWdxfh1tJ52VTigL1WA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/gtOU_cW5kjo0oOfHVTzjjEYFNds>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 22:41:34 -0000

On 30/01/2015 11:31, Behcet Sarikaya wrote:
> On Wed, Jan 28, 2015 at 2:12 AM, Ole Troan <otroan@employees.org> wrote=
:
>> <chair>
>>
>> The proposal of adding a "route option" to DHCPv6 was discussed extens=
ively in the MIF working group. The proposal did _not_ reach consensus.
>>
>> I suggest that we do not reopen that debate. Unless there are new issu=
es, not already brought up and considered in the MIF discussions. Parts o=
f that discussion available here:
>> https://mailarchive.ietf.org/arch/search/?q=3Ddraft-ietf-mif-dhcpv6-ro=
ute-option&f_list=3Dmif
>>
>=20
> I know that discussion as I was co-author of the draft.
>=20
> I think the conclusion was to move the discussion to 6man.
> That's what we have been doing with SADR drafts.
> Once we reach consensus on the RA option then we need to decide if a
> corresponding DHCP option is needed for networks where DHCP is used
> for this type of configuration.

Exactly. We actually need to agree on the scenarios and problems
first.

   Brian

>=20
> Regards,
>=20
> Behcet
>> </chair>
>>
>> Best regards,
>> Ole
>>
>>> On 28 Jan 2015, at 5:31 , Brian E Carpenter <brian.e.carpenter@gmail.=
com> wrote:
>>>
>>> On 28/01/2015 13:59, Lorenzo Colitti wrote:
>>>> On Wed, Jan 28, 2015 at 2:59 AM, Behcet Sarikaya <sarikaya2012@gmail=
=2Ecom>
>>>> wrote:
>>>>
>>>>>> Also, as Ole mentioned, third party next-hop doesn=E2=80=99t seem =
like a good
>>>>> idea to me (at least in RAs, I dont know in DHCP).
>>>>>
>>>>> I think it makes more sense with DHCP because DHCP server is not a =
router.
>>>>
>>>>
>>>> And that is why we don't do routing in DHCP: it's a bad idea.
>>>
>>> Nevertheless, DHCP(v4) hands out the address of the default router.
>>> By a strange coincidence, in most unmanaged networks the DHCP server
>>> has the same IP address as the default router. However, in v4 and v6
>>> the DHCP server is logically disjoint from the default router, and
>>> Lorenzo and Behcet seem to agree on that. They disagree on whether
>>> it matters.
>>>
>>>   Brian
>>>
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>
>=20


From nobody Thu Jan 29 14:46:39 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F22F1A066B for <ipv6@ietfa.amsl.com>; Thu, 29 Jan 2015 14:46:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xAwSJxG1JnNY for <ipv6@ietfa.amsl.com>; Thu, 29 Jan 2015 14:46:36 -0800 (PST)
Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DDC21A012D for <6man@ietf.org>; Thu, 29 Jan 2015 14:46:35 -0800 (PST)
Received: by mail-pa0-f43.google.com with SMTP id eu11so44149191pac.2 for <6man@ietf.org>; Thu, 29 Jan 2015 14:46:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=/d+vfyzVun1pmcVGoz8+gr8nMirwJ9dVuPbaguXBBX8=; b=PZojRCCGEoSorWog+r8IpmsJ9Sf/ycWilWAvWiKjCsVx9MTmVFHE5mJVOEWwW0GD0q 7s/Y6xiwBmCn2Fe17EmIRSgK8pQMqKLD35syedHYXcEHiMiWqIis7l9aiYayRlbErsj3 NcgR2mi8lsX2UYhX2vxtJWDEPx9x6SI9pthXOx+QHv1jN2Ew20AFdRxeHuFeg3YEyVdI CVrDePDvfi20Na0MuASstdV4gnMpCa6RJMCQO19+Yuc1WVOktEsMzvz4g/Vc+HgmyH37 2yfCKIGjHkfk49VdPPpGA+MjhwSbQ9tazP73lKUgHTqPKc8CiItPksvoqnSyjk09A+YX WBeA==
X-Received: by 10.66.253.168 with SMTP id ab8mr3992196pad.153.1422571594040; Thu, 29 Jan 2015 14:46:34 -0800 (PST)
Received: from ?IPv6:2401:c80:3:0:28cc:dc4c:9703:6781? ([2401:c80:3:0:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id rf9sm7294082pab.0.2015.01.29.14.46.30 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Jan 2015 14:46:33 -0800 (PST)
Message-ID: <54CAB84E.5030406@gmail.com>
Date: Fri, 30 Jan 2015 11:46:38 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Ray Hunter <v6ops@globis.net>, sarikaya@ieee.org
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <54C9DCCD.4090802@globis.net>
In-Reply-To: <54C9DCCD.4090802@globis.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/AG2TbwatcdCtPJ6_ODlYGPkP3mg>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2015 22:46:38 -0000

Hi Ray,

On 29/01/2015 20:10, Ray Hunter wrote:
> 
> 
> Behcet Sarikaya wrote:
>>   Hi all,
>>
>> On the solutions to the problem and issues discussed in this draft:
>> http://tools.ietf.org/id/draft-sarikaya-6man-sadr-overview-04.txt
>>
>> we would like to hear from the working group. Referring to Section 5,
>> which solution approach WG prefers? RA options as in Section 5.2?
>> Section 5.3?
>> Also regarding the corresponding DHCP work, which direction is the
>> preferred direction?
>>
>> Your opinions are welcome.
>>
>> Regards,
>>
>> Behcet
>>
>>
> I have read this draft. May I humbly suggest that I don't think you guys are on the right track at all with your problem statement.
> 
> You seem to think the problem with Homenet is how a non-mobile host discovers the correct SADR outbound route in the presence of
> a link shared between multiple provider routers, and there being no "cross link" higher in the topology to sort out incorrectly
> routed packets.
> 
> To me that's fighting an old battle (equivalent to IPv4 HSRP/VRRP + next hop/object trackers to counter split-brain and faults
> higher in the topology).

It may be an old battle but I'm not sure it's over.

> 
> IMHO the real issue in Homenet routing is how to ensure that hosts that roam between various L3 subnets (because they move
> around in the Homenet and pick up various L3 WiFi interfaces) are correctly routed, also in the presence of multiple alternative
> wireless links.

If I roam to a different L3 network I get renumbered (unless I run Mobile IP
in the house). When I get a new address, don't I have to fight the old battle
one more time?

    Brian
> 
> That requires solving the reverse route too, and anything like VRRP is going to be hopeless.
> 
> IMVHO I think that hosts that want to be this flexible will be forced to actively participate in Homenet routing protocols, and
> that these hosts will have to be assigned their own /64 to a non-time-variant software-loopback interface that does not have to
> renumber as the end node moves between L3 LANs..
> 


From nobody Thu Jan 29 20:40:13 2015
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E640E1A8850 for <ipv6@ietfa.amsl.com>; Thu, 29 Jan 2015 20:40:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.512
X-Spam-Level: 
X-Spam-Status: No, score=0.512 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X_Cen9A6UGrj for <ipv6@ietfa.amsl.com>; Thu, 29 Jan 2015 20:40:09 -0800 (PST)
Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98B181A6FFB for <6man@ietf.org>; Thu, 29 Jan 2015 20:40:09 -0800 (PST)
Received: by mail-ie0-f175.google.com with SMTP id ar1so1098292iec.6 for <6man@ietf.org>; Thu, 29 Jan 2015 20:40:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=+WtYYguoRvN7ZrLPgMM2MrEzSuZQHb55gAk5CPJWNgw=; b=KtHUA6HlMLRuKngKc85lGLgkEnnKRWJB0nOONqxOEu1TONDVfGBKh/FEpQQpZ6nYrD +hiKjmcScJCH3W9hXf4/7wxrntMg28d7zdF90ESOS54W+gQplP5QcD7fdV0qYt2N8g43 y5wvUCHSa2XlbOfc6cDhatwPy1sQlWetweSfCIryyDrxe0mFxOccuh+h/nVI0PwzEXfD i9Uug005KPdluFvr/esUIzKefWmlp+tTUPEO5QuM/MR642UGeb7iQ9U/sucaR1bX9Map lxB78JFwY6CZGM6aCMCbMAV5K8kChaAQuX6ZjzXbHPJc8QXZDPFkvd55i3CogzVVOBZL tmwQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=+WtYYguoRvN7ZrLPgMM2MrEzSuZQHb55gAk5CPJWNgw=; b=Js3HjE+9UfjzKi4tVZ/F/8qv5FMGqFei/9eqHrpDUdCl82smYUHDlCKYAD7g4i8ptK T9k2vj2THDd+mKaChp8JWvs97AuZk6UQzGq6HM75arcQAhI+UKsO7e8U+gPXjf0IHZs0 YiAmaDCD6WE3H2yp7zsRhW7Vm93Bg9DOoIAwtBKlWxDg7d3LZYwFLeO2sMDPV9Wy/fCR bmSxSbra/Unx1U3dky5koIxBaYC30Ir0CysTyIzpE0d5qExbElzNGsQZ7cmWvUDx7FxB H8cfSA9eEakatVxgescLHB20x462wD+FiQP0zrZTyBx1Y7V4FO4AbuXvIcbzSXmIcSe2 plxg==
X-Gm-Message-State: ALoCoQnfseirQZNfJl3fMGqo6KqG8BfBIwlHhjpSSq6XcW0BDOu0l8nXFD42jl9DKezmsn56oFCQ
X-Received: by 10.50.112.98 with SMTP id ip2mr574441igb.15.1422592808638; Thu, 29 Jan 2015 20:40:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.138.136 with HTTP; Thu, 29 Jan 2015 20:39:47 -0800 (PST)
In-Reply-To: <CAC8QAcfWAKWDwr9vxw-F04rrZA8cHbrpWdxfh1tJ52VTigL1WA@mail.gmail.com>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <1F17C514-D466-4069-9D1E-9EE15E59995F@darou.fr> <CAC8QAceabpe+bHPyQD7fJCXzS-kh17ESw-zoax_pJSKhbmz4Dw@mail.gmail.com> <CAKD1Yr0waXtgp3g2gcH64ygQ3zE_ktfi3mA+2tqpUYtAXujOzg@mail.gmail.com> <54C86618.4070505@gmail.com> <323EF2A4-9200-4382-953F-752ABBE29126@employees.org> <CAC8QAcfWAKWDwr9vxw-F04rrZA8cHbrpWdxfh1tJ52VTigL1WA@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 30 Jan 2015 13:39:47 +0900
Message-ID: <CAKD1Yr0-pQffp=0HLA2MaFaoUdiTLSPn6TqVkU2k8K3qcQUBxw@mail.gmail.com>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
To: Behcet Sarikaya <sarikaya@ieee.org>
Content-Type: multipart/alternative; boundary=047d7b4141620506cf050dd733e0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/DFs35UVk_i4NHCCBzQOs7Vagdu8>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 04:40:11 -0000

--047d7b4141620506cf050dd733e0
Content-Type: text/plain; charset=UTF-8

On Fri, Jan 30, 2015 at 7:31 AM, Behcet Sarikaya <sarikaya2012@gmail.com>
wrote:

> > I suggest that we do not reopen that debate. Unless there are new
> issues, not already brought up and considered in the MIF discussions. Parts
> of that discussion available here:
> >
> https://mailarchive.ietf.org/arch/search/?q=draft-ietf-mif-dhcpv6-route-option&f_list=mif
> >
>
> I know that discussion as I was co-author of the draft.
>
> I think the conclusion was to move the discussion to 6man.
>

No, the conclusion was that there was no consensus to define the option.
The draft was abandoned as a working group item and the corresponding
bullet was removed from the charter.

--047d7b4141620506cf050dd733e0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Jan 30, 2015 at 7:31 AM, Behcet Sarikaya <span dir=3D"ltr">&lt;<a href=
=3D"mailto:sarikaya2012@gmail.com" target=3D"_blank">sarikaya2012@gmail.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">&=
gt; I suggest that we do not reopen that debate. Unless there are new issue=
s, not already brought up and considered in the MIF discussions. Parts of t=
hat discussion available here:<br>
&gt; <a href=3D"https://mailarchive.ietf.org/arch/search/?q=3Ddraft-ietf-mi=
f-dhcpv6-route-option&amp;f_list=3Dmif" target=3D"_blank">https://mailarchi=
ve.ietf.org/arch/search/?q=3Ddraft-ietf-mif-dhcpv6-route-option&amp;f_list=
=3Dmif</a><br>
&gt;<br>
<br>
</span>I know that discussion as I was co-author of the draft.<br>
<br>
I think the conclusion was to move the discussion to 6man.<br></blockquote>=
<div><br></div><div>No, the conclusion was that there was no consensus to d=
efine the option. The draft was abandoned as a working group item and the c=
orresponding bullet was removed from the charter.</div></div></div></div>

--047d7b4141620506cf050dd733e0--


From nobody Thu Jan 29 23:27:57 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6964E1A8986 for <ipv6@ietfa.amsl.com>; Thu, 29 Jan 2015 23:27:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l-jBvjDbVVsB for <ipv6@ietfa.amsl.com>; Thu, 29 Jan 2015 23:27:54 -0800 (PST)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0DD91A6D3F for <6man@ietf.org>; Thu, 29 Jan 2015 23:27:53 -0800 (PST)
Received: by mail-pa0-f41.google.com with SMTP id kq14so49208426pab.0 for <6man@ietf.org>; Thu, 29 Jan 2015 23:27:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=lrPl5RdNM5o7JllxQfpYATAzdf43ZdLjmXLGkddVglA=; b=WiGFVXCyii1EJEOIqOlZ+S4XJaVY3+N94p3hvAAZxFI1upffQBHs8yHYtwFv5SNOBh UFoaCPDLuQ+EQWpLpz2b3q47pas84TbZi7LkUJ+aZUm+aKADDfPDnaaUQz659dK4ePeQ LBrWJXf7hW3aCcrqcheUS5Lq1naIvUh/1vlTfaM4c6bnfn3Eygd/nad5aHCz8NN87tT1 jqq25LLbdsV+/LKvG2PqUFPPYWtCg6+1hGcX+RQ5d6JOGP9LH2Rr4yrVc5Gikipx525P nnFm8/OXiKkJ8as2sSD0NFjeER+H/qvnvftGoCdeEPbRcW0MEdmGOeqZUR7nvRAcPgB0 eP+Q==
X-Received: by 10.66.66.135 with SMTP id f7mr6706840pat.93.1422602873090; Thu, 29 Jan 2015 23:27:53 -0800 (PST)
Received: from [192.168.1.67] (210-86-2-198.adsl.xtra.co.nz. [210.86.2.198]) by mx.google.com with ESMTPSA id ep2sm9757111pbc.78.2015.01.29.23.27.49 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Jan 2015 23:27:51 -0800 (PST)
Message-ID: <54CB3278.8040001@gmail.com>
Date: Fri, 30 Jan 2015 20:27:52 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>, Behcet Sarikaya <sarikaya@ieee.org>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <1F17C514-D466-4069-9D1E-9EE15E59995F@darou.fr> <CAC8QAceabpe+bHPyQD7fJCXzS-kh17ESw-zoax_pJSKhbmz4Dw@mail.gmail.com> <CAKD1Yr0waXtgp3g2gcH64ygQ3zE_ktfi3mA+2tqpUYtAXujOzg@mail.gmail.com> <54C86618.4070505@gmail.com> <323EF2A4-9200-4382-953F-752ABBE29126@employees.org> <CAC8QAcfWAKWDwr9vxw-F04rrZA8cHbrpWdxfh1tJ52VTigL1WA@mail.gmail.com> <CAKD1Yr0-pQffp=0HLA2MaFaoUdiTLSPn6TqVkU2k8K3qcQUBxw@mail.gmail.com>
In-Reply-To: <CAKD1Yr0-pQffp=0HLA2MaFaoUdiTLSPn6TqVkU2k8K3qcQUBxw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/cDr2A2uewF4xvpMvLbdTo29PGGQ>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 07:27:55 -0000

On 30/01/2015 17:39, Lorenzo Colitti wrote:
> On Fri, Jan 30, 2015 at 7:31 AM, Behcet Sarikaya <sarikaya2012@gmail.com>
> wrote:
> 
>>> I suggest that we do not reopen that debate. Unless there are new
>> issues, not already brought up and considered in the MIF discussions. Parts
>> of that discussion available here:
>>>
>> https://mailarchive.ietf.org/arch/search/?q=draft-ietf-mif-dhcpv6-route-option&f_list=mif
>>>
>>
>> I know that discussion as I was co-author of the draft.
>>
>> I think the conclusion was to move the discussion to 6man.
>>
> 
> No, the conclusion was that there was no consensus to define the option.
> The draft was abandoned as a working group item and the corresponding
> bullet was removed from the charter.

Both your statements are true, and compatible with each other.

   Brian


From nobody Thu Jan 29 23:39:49 2015
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 050A81A8991 for <ipv6@ietfa.amsl.com>; Thu, 29 Jan 2015 23:39:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cSl5jOv405W0 for <ipv6@ietfa.amsl.com>; Thu, 29 Jan 2015 23:39:43 -0800 (PST)
Received: from mail-ig0-x22f.google.com (mail-ig0-x22f.google.com [IPv6:2607:f8b0:4001:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C7121A898F for <6man@ietf.org>; Thu, 29 Jan 2015 23:39:43 -0800 (PST)
Received: by mail-ig0-f175.google.com with SMTP id hn18so1370010igb.2 for <6man@ietf.org>; Thu, 29 Jan 2015 23:39:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=CFu7ZWYa1I5wvIfdxKQWdPoEGNbGbYyZ+4jpww7w0HQ=; b=pnRFOFD66/KaSYrbx47UtWl9eyiZ0ZufZuDeDSaAKSF4OIWNFUE4wwcqUZ6H4G6mOd nRxtAKLpMFv8z989ZZUU52gtqdwKLj2RHdSdcwKsyPnzHclSaaD+PN+1zDoBI2a+aLOm 6jUSwhGvdDasWbP+Jzxs1JVbhQUO+a7JiypEOqYthWaiBJ0yeLbXt5UMB8S+ryjRRW8D ZGg0aujiLm8lgPJatsHSZOpxQGYj+b5iKWUy3AYsl+e9Q9XpZxRHt0KZ45wOlPrlULd1 8uA42T6W1ZgXVUkwuaPXvzywN8zKiwyHCnycsltuk9Onv4MNc2VaBAY+jJAKw8TLRhYQ k8Uw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=CFu7ZWYa1I5wvIfdxKQWdPoEGNbGbYyZ+4jpww7w0HQ=; b=WSerm/5g3oaW52PqotXly5EgPeYGAFZLwCMd+4ep0Z4ibe++QGErIsRTRnOxlEuV38 A4+gyrHg3a1NjQDfUj09MORX/cceIPmUCcm7ZTgR2FQk3LNbbezkNhEXPZhy116Ag0Le T/zAgEsUWjZzLZ6aR2Qkd8TVIuN89hjNjCmVll6Z97G35HuIkIe4+quNa/d5JTLyjTWs Ixl7z711vxwWgSRvyoEdFANX+wiW00s+LexyLxgZfe9frwLvUrledZxje0wY7656mUNe PJDGFj6ctYZbOeaWBJEWJQdKvj7hZiVvJd5RGiWpzu34C8bOtILOObsbsbku3chaijjA 0mog==
X-Gm-Message-State: ALoCoQnB3ugQB2t3eFWZbQI5FW7Zp6SRBTJ1zA02IHSOdNyimD3wyY3VWTwjTH7yITV7oNyj6Ioj
X-Received: by 10.107.136.158 with SMTP id s30mr5732218ioi.8.1422603582041; Thu, 29 Jan 2015 23:39:42 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.138.136 with HTTP; Thu, 29 Jan 2015 23:39:21 -0800 (PST)
In-Reply-To: <54CB3278.8040001@gmail.com>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <1F17C514-D466-4069-9D1E-9EE15E59995F@darou.fr> <CAC8QAceabpe+bHPyQD7fJCXzS-kh17ESw-zoax_pJSKhbmz4Dw@mail.gmail.com> <CAKD1Yr0waXtgp3g2gcH64ygQ3zE_ktfi3mA+2tqpUYtAXujOzg@mail.gmail.com> <54C86618.4070505@gmail.com> <323EF2A4-9200-4382-953F-752ABBE29126@employees.org> <CAC8QAcfWAKWDwr9vxw-F04rrZA8cHbrpWdxfh1tJ52VTigL1WA@mail.gmail.com> <CAKD1Yr0-pQffp=0HLA2MaFaoUdiTLSPn6TqVkU2k8K3qcQUBxw@mail.gmail.com> <54CB3278.8040001@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 30 Jan 2015 16:39:21 +0900
Message-ID: <CAKD1Yr0pOVWFJdT+yZMshAA6g1dh0UrG=P+Dd1RcA4t05zSxuQ@mail.gmail.com>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a113eb3182a2a93050dd9b5f3
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ntSGB1a8jzrLFIjYxiFTaDa_HsM>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 07:39:44 -0000

--001a113eb3182a2a93050dd9b5f3
Content-Type: text/plain; charset=UTF-8

On Fri, Jan 30, 2015 at 4:27 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> > No, the conclusion was that there was no consensus to define the option.
> > The draft was abandoned as a working group item and the corresponding
> > bullet was removed from the charter.
>
> Both your statements are true, and compatible with each other.
>

I do not recall that the conclusion was that this work should be taken up
in 6man. Was this written down anywhere?

--001a113eb3182a2a93050dd9b5f3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Jan 30, 2015 at 4:27 PM, Brian E Carpenter <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpente=
r@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div cl=
ass=3D"HOEnZb"><div class=3D"h5">&gt; No, the conclusion was that there was=
 no consensus to define the option.<br>
&gt; The draft was abandoned as a working group item and the corresponding<=
br>
&gt; bullet was removed from the charter.<br>
<br>
</div></div>Both your statements are true, and compatible with each other.<=
br></blockquote><div><br></div><div>I do not recall that the conclusion was=
 that this work should be taken up in 6man. Was this written down anywhere?=
=C2=A0</div></div></div></div>

--001a113eb3182a2a93050dd9b5f3--


From nobody Fri Jan 30 02:10:24 2015
Return-Path: <pthubert@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDED51A8A81 for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 02:10:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OUnC0FQkYU2T for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 02:10:15 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 998E11A8A8C for <6man@ietf.org>; Fri, 30 Jan 2015 02:10:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3352; q=dns/txt; s=iport; t=1422612616; x=1423822216; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=6n4YiOCLFjVQwKKibpP7e+8bnZtciUOMumzQ3cn7bXg=; b=Tng2bCjecC/42DPZn+Hy00w7sbTqi+4OjS1Wz0gn6xcVLs4eAlNVwAVm ZFemMDC/ZYEwLSBjAtX5Of9xOnPVGS4PFlmV5flzhaKQ5bCUU16pUjMvg k2uhRMHoz35zqkQmgu1gtAIf+MqILvPCuzH/XoXyi8op81bbAku+wkGw3 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmAFAPJXy1StJV2d/2dsb2JhbABagwZSWQTCQ4IbCoVxAoEdQwEBAQEBfYQMAQEBBAEBATc0CwwGAQgRBAEBAQoUCS4LFAkJAQQBDQUIE4gRDdYVAQEBAQEBAQEBAQEBAQEBAQEBAQEBF49HMQ2DEIETBYVHiTWDS4ZuNoUMiDuDPSKDbm8BgUN+AQEB
X-IronPort-AV: E=Sophos;i="5.09,491,1418083200"; d="scan'208";a="388930819"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-9.cisco.com with ESMTP; 30 Jan 2015 10:10:15 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id t0UAADq8006413 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 30 Jan 2015 10:10:13 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.100]) by xhc-rcd-x13.cisco.com ([173.37.183.87]) with mapi id 14.03.0195.001; Fri, 30 Jan 2015 04:10:13 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Ray Hunter <v6ops@globis.net>, "sarikaya@ieee.org" <sarikaya@ieee.org>
Subject: RE: Source Address Dependent Routing and Source Address Selection for IPv6
Thread-Topic: Source Address Dependent Routing and Source Address Selection for IPv6
Thread-Index: AdA8dM6oz5MpOeGuQhOWIBkz/kCO7g==
Date: Fri, 30 Jan 2015 10:10:12 +0000
Deferred-Delivery: Fri, 30 Jan 2015 10:10:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD848B51FD2@xmb-rcd-x01.cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.22.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/6Q4X-Iiu7CxKz24e8hSoU-bzB0M>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 10:10:20 -0000

Hello Brian:

The difference with the generic mobile IP scenario is that the host roams w=
ithin the house.=20
So we could inject host routes in the home, aggregated at the home gateway,=
 as opposed to renumber or tunnel.
RPL does that all day, but currently there's a need for some host support (=
RPL leaf) to advertise the address.=20
With new work at 6lo related to efficient ND, we are generalizing the regis=
tration to make the host agnostic of the routing protocol.

Cheers,

Pascal


> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Brian E Carpenter
> Sent: jeudi 29 janvier 2015 23:47
> To: Ray Hunter; sarikaya@ieee.org
> Cc: 6man@ietf.org
> Subject: Re: Source Address Dependent Routing and Source Address Selectio=
n
> for IPv6
>=20
> Hi Ray,
>=20
> On 29/01/2015 20:10, Ray Hunter wrote:
> >
> >
> > Behcet Sarikaya wrote:
> >>   Hi all,
> >>
> >> On the solutions to the problem and issues discussed in this draft:
> >> http://tools.ietf.org/id/draft-sarikaya-6man-sadr-overview-04.txt
> >>
> >> we would like to hear from the working group. Referring to Section 5,
> >> which solution approach WG prefers? RA options as in Section 5.2?
> >> Section 5.3?
> >> Also regarding the corresponding DHCP work, which direction is the
> >> preferred direction?
> >>
> >> Your opinions are welcome.
> >>
> >> Regards,
> >>
> >> Behcet
> >>
> >>
> > I have read this draft. May I humbly suggest that I don't think you guy=
s are on
> the right track at all with your problem statement.
> >
> > You seem to think the problem with Homenet is how a non-mobile host
> > discovers the correct SADR outbound route in the presence of a link
> > shared between multiple provider routers, and there being no "cross lin=
k"
> higher in the topology to sort out incorrectly routed packets.
> >
> > To me that's fighting an old battle (equivalent to IPv4 HSRP/VRRP +
> > next hop/object trackers to counter split-brain and faults higher in th=
e
> topology).
>=20
> It may be an old battle but I'm not sure it's over.
>=20
> >
> > IMHO the real issue in Homenet routing is how to ensure that hosts
> > that roam between various L3 subnets (because they move around in the
> > Homenet and pick up various L3 WiFi interfaces) are correctly routed, a=
lso in
> the presence of multiple alternative wireless links.
>=20
> If I roam to a different L3 network I get renumbered (unless I run Mobile=
 IP in
> the house). When I get a new address, don't I have to fight the old battl=
e one
> more time?
>=20
>     Brian
> >
> > That requires solving the reverse route too, and anything like VRRP is =
going to
> be hopeless.
> >
> > IMVHO I think that hosts that want to be this flexible will be forced
> > to actively participate in Homenet routing protocols, and that these
> > hosts will have to be assigned their own /64 to a non-time-variant soft=
ware-
> loopback interface that does not have to renumber as the end node moves
> between L3 LANs..
> >
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Fri Jan 30 03:32:32 2015
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9C001A8BC5 for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 03:32:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHDiJnZHpxXr for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 03:32:29 -0800 (PST)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 148F11A8EA9 for <6man@ietf.org>; Fri, 30 Jan 2015 03:32:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 0558D871660; Fri, 30 Jan 2015 12:32:28 +0100 (CET)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oPTEjZtRpcQt; Fri, 30 Jan 2015 12:32:27 +0100 (CET)
Received: from [192.168.1.12] (d75067.upc-d.chello.nl [213.46.75.67]) (Authenticated sender: v6ops@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id D2B39871612; Fri, 30 Jan 2015 12:32:27 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: V6ops <v6ops@globis.net>
X-Mailer: iPad Mail (12B440)
In-Reply-To: <54CAB84E.5030406@gmail.com>
Date: Fri, 30 Jan 2015 12:32:27 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <8C665B1D-4063-4D14-A0CD-B4CA1EC1E7CE@globis.net>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <54C9DCCD.4090802@globis.net> <54CAB84E.5030406@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/0nqzqZcU3LkTP6P_6_DxmX_JIrI>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 11:32:31 -0000

Sent from my iThing

> On 29 Jan 2015, at 23:46, Brian E Carpenter <brian.e.carpenter@gmail.com> w=
rote:
>=20
> Hi Ray,
>=20
>> On 29/01/2015 20:10, Ray Hunter wrote:
>>=20
>>=20
>> Behcet Sarikaya wrote:
>>> Hi all,
>>>=20
>>> On the solutions to the problem and issues discussed in this draft:
>>> http://tools.ietf.org/id/draft-sarikaya-6man-sadr-overview-04.txt
>>>=20
>>> we would like to hear from the working group. Referring to Section 5,
>>> which solution approach WG prefers? RA options as in Section 5.2?
>>> Section 5.3?
>>> Also regarding the corresponding DHCP work, which direction is the
>>> preferred direction?
>>>=20
>>> Your opinions are welcome.
>>>=20
>>> Regards,
>>>=20
>>> Behcet
>> I have read this draft. May I humbly suggest that I don't think you guys a=
re on the right track at all with your problem statement.
>>=20
>> You seem to think the problem with Homenet is how a non-mobile host disco=
vers the correct SADR outbound route in the presence of
>> a link shared between multiple provider routers, and there being no "cros=
s link" higher in the topology to sort out incorrectly
>> routed packets.
>>=20
>> To me that's fighting an old battle (equivalent to IPv4 HSRP/VRRP + next h=
op/object trackers to counter split-brain and faults
>> higher in the topology).
>=20
> It may be an old battle but I'm not sure it's over.

I don't think there's even consensus on what the problem is, never mind wher=
e the problem should be solved: by inefficient routing back out the inbound i=
nterface, the end host knowing SADR information, some sort of VRRP, end node=
 path probing, providing more routing information to end nodes. Yet this dra=
ft is proposing specific mechanisms.
>=20
>>=20
>> IMHO the real issue in Homenet routing is how to ensure that hosts that r=
oam between various L3 subnets (because they move
>> around in the Homenet and pick up various L3 WiFi interfaces) are correct=
ly routed, also in the presence of multiple alternative
>> wireless links.
>=20
> If I roam to a different L3 network I get renumbered (unless I run Mobile I=
P
> in the house). When I get a new address, don't I have to fight the old bat=
tle
> one more time?
>=20
>  Brian
It's much more serious than that. Someone turns on a microwave and one wifi l=
ink drops, and another is preferred. Or radio propagation changes marginally=
. So the node has to renumber and drop all existing sessions? That ain't goi=
ng to fly with consumers. Wifi roaming has been kludged in the enterprise at=
 L2. It needs to be fixed at L3 if homenet is going to be routed. For mobile=
 ipv6 in Homenet, which egress router is going to provide the home address? A=
nd how will that work with 2 or more ISP routers providing walled gardens or=
 BCP38 filtering?

Communicating SADR information between routers and end nodes is a sideshow /=
 sub problem of that whole IMHO. And a stand alone solution for the sub prob=
lem developed in isolation is unlikely to solve the whole IMHO.

>>=20
>> That requires solving the reverse route too, and anything like VRRP is go=
ing to be hopeless.
>>=20
>> IMVHO I think that hosts that want to be this flexible will be forced to a=
ctively participate in Homenet routing protocols, and
>> that these hosts will have to be assigned their own /64 to a non-time-var=
iant software-loopback interface that does not have to
>> renumber as the end node moves between L3 LANs..
>=20
>=20
>=20


From nobody Fri Jan 30 08:38:12 2015
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3942D1A6F07 for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 08:38:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jo7Cs0aHqGMy for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 08:38:06 -0800 (PST)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 549131A6F10 for <ipv6@ietf.org>; Fri, 30 Jan 2015 08:38:06 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id t0UGc4jd008362 for <ipv6@ietf.org>; Fri, 30 Jan 2015 17:38:04 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 267FA204842 for <ipv6@ietf.org>; Fri, 30 Jan 2015 17:38:39 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 14E472047F3 for <ipv6@ietf.org>; Fri, 30 Jan 2015 17:38:39 +0100 (CET)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id t0UGbWDc013560 for <ipv6@ietf.org>; Fri, 30 Jan 2015 17:38:03 +0100
Message-ID: <54CBB34C.7000100@gmail.com>
Date: Fri, 30 Jan 2015 17:37:32 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <7DC0A974-1D69-41A0-A23E-D8F60D0780B5@employees.org> <alpine.DEB.2.02.1501230847000.22729@uplift.swm.pp.se> <038BA70D-8EDD-4454-83C5-2DE1817BC2DF@employees.org> <alpine.DEB.2.02.1501230934040.22729@uplift.swm.pp.se> <08371EFF-A2F3-4F38-AAB6-B4637BBF8A81@employees.org> <alpine.DEB.2.02.1501231051160.22729@uplift.swm.pp.se> <3E88E95F-47C0-498D-914A-07DFA4B11DB8@darou.fr> <440A410F-CC4E-4577-8ED4-B7E606E35D6D@employees.org>
In-Reply-To: <440A410F-CC4E-4577-8ED4-B7E606E35D6D@employees.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/DibgNL0d-e1OL5-2qpAvUIHA8KQ>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 16:38:09 -0000

Le 23/01/2015 12:11, Ole Troan a Ã©crit :
[...]
> I think the options we have are:
>
> 1) current specifications (rule 5.5, works as I described)
> 2) Homenet case, all routers advertise all PIOs. depends on redirects
> 3) Extend RFC4191 with source specific routes
> 4) Instead of making ND into a routing protocol just make hosts participate in a real RP.
>
> I have argued for 1, from the standpoint that this is what's most
> likely to get current hosts to implement today, and it works with two
> independent routers that doesn't support homenet protocols.

As for option 4 - it is hard to bring one routing protocol in each Host 
(which one?), whereas ND is one and in all kernels.

Alex

>
> cheers,
> Ole
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>



From nobody Fri Jan 30 10:17:15 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F2821A00F5 for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 10:17:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QIBHs3BTlCtb for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 10:17:03 -0800 (PST)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A5D21A1A0C for <6man@ietf.org>; Fri, 30 Jan 2015 10:17:00 -0800 (PST)
Received: by mail-pa0-f42.google.com with SMTP id bj1so55267616pad.1 for <6man@ietf.org>; Fri, 30 Jan 2015 10:16:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=kxpTsxtq7FOPXRvinxTQw/M0WYBYtMJUdOmpEI4kJZk=; b=ixE5MoSxyB6N38sik3St9n/BCNRaHnxoB5a8rOdJgRrWxWEzJDo1dZwDjjNRtY7L/j KFbeSR2BOJyhd7iToc7g6JF5Dryla0oF9fuj+vfpl/OB/WGe8AB8QevCSQnyd2ENBgDX BpKEP6km1quE/2y0CRfg8G2MsIzlljVTWQrw0bCpa4qzWNZqUMFVVICfKJ9ztXbhVcGH mOzYHgVh2ukUw4wSvWNfSqWip6I72CdlHph7jtlKW07A5xEPs4k2NA80ft/S+fMHmR4j wspYxN0cRS5COusL3wIYUn1MMr5qnoxGF8F6lctK/gTyiV4KH/rGIhw1Sh52qt75L7hD jfLg==
X-Received: by 10.70.123.197 with SMTP id mc5mr10825480pdb.124.1422641819743;  Fri, 30 Jan 2015 10:16:59 -0800 (PST)
Received: from [192.168.1.67] (210-86-2-198.adsl.xtra.co.nz. [210.86.2.198]) by mx.google.com with ESMTPSA id iv1sm11391531pbc.87.2015.01.30.10.16.56 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Jan 2015 10:16:58 -0800 (PST)
Message-ID: <54CBCA9B.2010308@gmail.com>
Date: Sat, 31 Jan 2015 07:16:59 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <1F17C514-D466-4069-9D1E-9EE15E59995F@darou.fr> <CAC8QAceabpe+bHPyQD7fJCXzS-kh17ESw-zoax_pJSKhbmz4Dw@mail.gmail.com> <CAKD1Yr0waXtgp3g2gcH64ygQ3zE_ktfi3mA+2tqpUYtAXujOzg@mail.gmail.com> <54C86618.4070505@gmail.com> <323EF2A4-9200-4382-953F-752ABBE29126@employees.org> <CAC8QAcfWAKWDwr9vxw-F04rrZA8cHbrpWdxfh1tJ52VTigL1WA@mail.gmail.com> <CAKD1Yr0-pQffp=0HLA2MaFaoUdiTLSPn6TqVkU2k8K3qcQUBxw@mail.gmail.com> <54CB3278.8040001@gmail.com> <CAKD1Yr0pOVWFJdT+yZMshAA6g1dh0UrG=P+Dd1RcA4t05zSxuQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr0pOVWFJdT+yZMshAA6g1dh0UrG=P+Dd1RcA4t05zSxuQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ryVY9wicnvx8CejkRwFEBjPj_bE>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 18:17:08 -0000

Hi Lorenzo,
On 30/01/2015 20:39, Lorenzo Colitti wrote:
> On Fri, Jan 30, 2015 at 4:27 PM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> 
>>> No, the conclusion was that there was no consensus to define the option.
>>> The draft was abandoned as a working group item and the corresponding
>>> bullet was removed from the charter.
>>
>> Both your statements are true, and compatible with each other.
>>
> 
> I do not recall that the conclusion was that this work should be taken up
> in 6man. Was this written down anywhere?

Honestly I have no idea. Of course, a discussion in MIF can't add an item to
6man's work plan - all I recall is somebody saying or writing that further
discussion clearly belonged in 6man.

Anyway, I don't particularly want to discuss solutions yet. I don't feel
we have an agreed set of problem scenarios yet.

    Brian


From nobody Fri Jan 30 12:53:08 2015
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8FE31A8727 for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 12:53:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M-PAcdzgdynm for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 12:53:05 -0800 (PST)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B854F1A8722 for <6man@ietf.org>; Fri, 30 Jan 2015 12:53:05 -0800 (PST)
Received: from slb-mbsout-02.boeing.com (localhost [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id t0UKr4p7002254 for <6man@ietf.org>; Fri, 30 Jan 2015 12:53:05 -0800
Received: from XCH-PHX-306.sw.nos.boeing.com (xch-phx-306.sw.nos.boeing.com [137.136.239.30]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id t0UKr2IJ002136 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 30 Jan 2015 12:53:04 -0800
Received: from XCH-PHX-503.sw.nos.boeing.com ([169.254.6.195]) by XCH-PHX-306.sw.nos.boeing.com ([169.254.3.166]) with mapi id 14.03.0210.002; Fri, 30 Jan 2015 12:52:35 -0800
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Subject: RE: Source Address Dependent Routing and Source Address Selection for IPv6
Thread-Topic: Source Address Dependent Routing and Source Address Selection for IPv6
Thread-Index: AdA8dM6oeWcm+dYark6AGFyRCiaiwAAWWQDw
Date: Fri, 30 Jan 2015 20:52:34 +0000
Message-ID: <021E64FECA7E5A4699562F4E66716481534A0500@XCH-PHX-503.sw.nos.boeing.com>
References: <E045AECD98228444A58C61C200AE1BD848B51FD2@xmb-rcd-x01.cisco.com>
In-Reply-To: <E045AECD98228444A58C61C200AE1BD848B51FD2@xmb-rcd-x01.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/rS_uEI8cdgQmRdNq5KIP0mtN7Bs>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 20:53:07 -0000

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Pascal Thubert
> (pthubert)

> Hello Brian:
>=20
> The difference with the generic mobile IP scenario is that the host roams
> within the house.
> So we could inject host routes in the home, aggregated at the home gatewa=
y,
> as opposed to renumber or tunnel.
> RPL does that all day, but currently there's a need for some host support
> (RPL leaf) to advertise the address.
> With new work at 6lo related to efficient ND, we are generalizing the
> registration to make the host agnostic of the routing protocol.

While it's probably true that WiFi access points are usually sold as router=
s, the painfully simpler option here, if a homenet has more than one WiFi a=
ccess point, is to configure each one as a proper layer 2 AP, no? And then =
connect them to the modem/router to the ISP?

Bert


From nobody Fri Jan 30 12:55:32 2015
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A625A1A8742 for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 12:55:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kT2xilM2U3yw for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 12:55:25 -0800 (PST)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E33081A8727 for <6man@ietf.org>; Fri, 30 Jan 2015 12:55:24 -0800 (PST)
Received: from slb-mbsout-02.boeing.com (localhost [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id t0UKtOi2006322 for <6man@ietf.org>; Fri, 30 Jan 2015 12:55:24 -0800
Received: from XCH-PHX-501.sw.nos.boeing.com (xch-phx-501.sw.nos.boeing.com [137.136.239.53]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id t0UKtNhp006306 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 30 Jan 2015 12:55:24 -0800
Received: from XCH-PHX-503.sw.nos.boeing.com ([169.254.6.195]) by XCH-PHX-501.sw.nos.boeing.com ([169.254.8.178]) with mapi id 14.03.0210.002; Fri, 30 Jan 2015 12:55:23 -0800
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: V6ops <v6ops@globis.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: RE: Source Address Dependent Routing and Source Address Selection for IPv6
Thread-Topic: Source Address Dependent Routing and Source Address Selection for IPv6
Thread-Index: AQHQPIBseWcm+dYark6AGFyRCiaiwJzZJLuQ
Date: Fri, 30 Jan 2015 20:55:22 +0000
Message-ID: <021E64FECA7E5A4699562F4E66716481534A0512@XCH-PHX-503.sw.nos.boeing.com>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <54C9DCCD.4090802@globis.net> <54CAB84E.5030406@gmail.com> <8C665B1D-4063-4D14-A0CD-B4CA1EC1E7CE@globis.net>
In-Reply-To: <8C665B1D-4063-4D14-A0CD-B4CA1EC1E7CE@globis.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/toutY6MBsJcIZSOvSl07mWWE_to>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 20:55:31 -0000

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of V6ops

> It's much more serious than that. Someone turns on a microwave and one wi=
fi
> link drops, and another is preferred. Or radio propagation changes
> marginally. So the node has to renumber and drop all existing sessions? T=
hat
> ain't going to fly with consumers. Wifi roaming has been kludged in the
> enterprise at L2.

But that's not a kludge. WiFi APs were always meant to be L2 devices.

Bert


From nobody Fri Jan 30 15:27:37 2015
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FF101A87CD for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 15:27:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qj8-31wvB0gL for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 15:27:34 -0800 (PST)
Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D51151A87D7 for <6man@ietf.org>; Fri, 30 Jan 2015 15:27:31 -0800 (PST)
Received: by mail-la0-f54.google.com with SMTP id hv19so26170429lab.13 for <6man@ietf.org>; Fri, 30 Jan 2015 15:27:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=cv65XnzQyjEL53j7Mp9RVn/48YQd/toFPWqONS/RjtI=; b=f4sRIsxZjHcjQ8TnUEQtniLH4Brgj8QfJIUCmLpDorf/lMN1lzF7H6/V7TQnSrH0C8 fQ2wmElY2RvUW3Dne3hSjZuPFkuX5Wss5+Z1PGHqpYkeSYshTuoX+EmOZE+kkRqiCanG KbzDyjYtGunQvia/LW7mRureQbRK1CVY6RBAVUIvtBWZGLf4lDfUFRkM/ObrTJCXvadH rl9PdgeKlYtOK63svUvu3jhpN/XIaFtKgg4bzq5bkOAhYYhoYQnfq3/epqOt8lbb2kgx L+Roics3p+7uSZWguKBv58n7mqK2YfoJeFA8jXd0zQtHbcOP2Xzx5YT5ZRkKdERrZYBI VdAw==
MIME-Version: 1.0
X-Received: by 10.152.29.193 with SMTP id m1mr8880251lah.84.1422660450356; Fri, 30 Jan 2015 15:27:30 -0800 (PST)
Received: by 10.114.80.231 with HTTP; Fri, 30 Jan 2015 15:27:30 -0800 (PST)
In-Reply-To: <CAKD1Yr0pOVWFJdT+yZMshAA6g1dh0UrG=P+Dd1RcA4t05zSxuQ@mail.gmail.com>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <1F17C514-D466-4069-9D1E-9EE15E59995F@darou.fr> <CAC8QAceabpe+bHPyQD7fJCXzS-kh17ESw-zoax_pJSKhbmz4Dw@mail.gmail.com> <CAKD1Yr0waXtgp3g2gcH64ygQ3zE_ktfi3mA+2tqpUYtAXujOzg@mail.gmail.com> <54C86618.4070505@gmail.com> <323EF2A4-9200-4382-953F-752ABBE29126@employees.org> <CAC8QAcfWAKWDwr9vxw-F04rrZA8cHbrpWdxfh1tJ52VTigL1WA@mail.gmail.com> <CAKD1Yr0-pQffp=0HLA2MaFaoUdiTLSPn6TqVkU2k8K3qcQUBxw@mail.gmail.com> <54CB3278.8040001@gmail.com> <CAKD1Yr0pOVWFJdT+yZMshAA6g1dh0UrG=P+Dd1RcA4t05zSxuQ@mail.gmail.com>
Date: Fri, 30 Jan 2015 17:27:30 -0600
Message-ID: <CAC8QAce9TSkiLBjrnG4eGAZe2SC6HS2Qtqm84qOn3+=QqNUyYw@mail.gmail.com>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/5ieuYwAQ-iZMTVr5gRPFLl1s9ck>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 23:27:35 -0000

On Fri, Jan 30, 2015 at 1:39 AM, Lorenzo Colitti <lorenzo@google.com> wrote:
> On Fri, Jan 30, 2015 at 4:27 PM, Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>>
>> > No, the conclusion was that there was no consensus to define the option.
>> > The draft was abandoned as a working group item and the corresponding
>> > bullet was removed from the charter.
>>
>> Both your statements are true, and compatible with each other.
>
>
> I do not recall that the conclusion was that this work should be taken up in
> 6man. Was this written down anywhere?

Sorry my bad. Frankly I don't remember what the conclusion was and I
don't think it was written anywhere.
Wojciech, the main author realized that the draft was not going
anywhere and abandoned the work.

After that mif started Multiple Provisioning Domain Architecture
development and related DHCP and ND support.

We started SADR work in 6man.

Maybe all these are related. Can we say that mif DHCP route options
work lead the way to these new avenues, so it was avant garde?

Regards,


Behcet


From nobody Fri Jan 30 15:29:01 2015
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D034B1A87D9 for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 15:28:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3iwvHnPTlhYN for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 15:28:57 -0800 (PST)
Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 769691A87D5 for <6man@ietf.org>; Fri, 30 Jan 2015 15:28:57 -0800 (PST)
Received: by mail-la0-f47.google.com with SMTP id hz20so26240754lab.6 for <6man@ietf.org>; Fri, 30 Jan 2015 15:28:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=SnVZ1ByPEa+LE2wTF5bF0nQ8s2v/M9CKVKuKd/IyJTM=; b=eIVSZpt50Aj+Ux0y3tJ2Glls3A+ZLgw8iSy5dUxGPQYiXYNk47G/8YUhQTgvnzh8tT BYG4c/FY+9FdmaB0KdXZ1y5lXgby+srQtCcPY89LjEsGzN0nZvXs5e0meUOknYauj8r2 61/axdlu7acWYZPA/we09QyxKAq/AwT7LNy3yFvSyuebYMxrac9ZL04koCmIWYKhh57Q sH3JFqpl92Jnt2bKynMawjabvKgA4l8u5Sid8LXnBQ5TYBiFnAJ8x+c+vkrzz0/k3719 4NUFSwNVqWL5EY2Y9TmtWT8yjNIeEtLnc2/zQZCxm0rVptbpAdbo/8STf730eqzMaIiC 9ATw==
MIME-Version: 1.0
X-Received: by 10.152.203.230 with SMTP id kt6mr8771373lac.38.1422660535986; Fri, 30 Jan 2015 15:28:55 -0800 (PST)
Received: by 10.114.80.231 with HTTP; Fri, 30 Jan 2015 15:28:55 -0800 (PST)
In-Reply-To: <021E64FECA7E5A4699562F4E66716481534A0512@XCH-PHX-503.sw.nos.boeing.com>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <54C9DCCD.4090802@globis.net> <54CAB84E.5030406@gmail.com> <8C665B1D-4063-4D14-A0CD-B4CA1EC1E7CE@globis.net> <021E64FECA7E5A4699562F4E66716481534A0512@XCH-PHX-503.sw.nos.boeing.com>
Date: Fri, 30 Jan 2015 17:28:55 -0600
Message-ID: <CAC8QAcfUBZqq3A-6a2vKGzAEXiTp16aGH9DL7menZzEVS0oYWw@mail.gmail.com>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/i29ZQUwtasBtRi6S-6j1cfGfFpU>
Cc: V6ops <v6ops@globis.net>, "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 23:28:59 -0000

Folks,
Mobility in home network is out of scope with this draft.
Maybe also that should be discussed in homenet.

Regards,

Behcet

On Fri, Jan 30, 2015 at 2:55 PM, Manfredi, Albert E
<albert.e.manfredi@boeing.com> wrote:
>> -----Original Message-----
>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of V6ops
>
>> It's much more serious than that. Someone turns on a microwave and one wifi
>> link drops, and another is preferred. Or radio propagation changes
>> marginally. So the node has to renumber and drop all existing sessions? That
>> ain't going to fly with consumers. Wifi roaming has been kludged in the
>> enterprise at L2.
>
> But that's not a kludge. WiFi APs were always meant to be L2 devices.
>
> Bert
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Fri Jan 30 15:33:40 2015
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C44E1A87E1; Fri, 30 Jan 2015 15:33:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.523
X-Spam-Level: 
X-Spam-Status: No, score=0.523 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_DBL_ABUSE_REDIR=0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lkv5L43QbAjE; Fri, 30 Jan 2015 15:33:35 -0800 (PST)
Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CCF51A8822; Fri, 30 Jan 2015 15:33:31 -0800 (PST)
Received: by mail-lb0-f169.google.com with SMTP id f15so38783562lbj.0; Fri, 30 Jan 2015 15:33:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wsCnZYD+YMdPr9rFZksBqBR0EH7Xsb30gh2WwIdNNl8=; b=i1Nz2tjmq4L/q6bpxsQ2G10UGAAFTkMzRumWWaFi77vXimcVSkHLsND30v4fsTyO4B cO1+I1I1LlpMTKFFqNJRh9qrGLbC/pKjyO+B76NmwQBjMkUCHArVUwZ7TCV0khzkjtdb lMzCV9osBDpmjqRMhmFHNhAUsiPS+FMSw/yuYV3sI8LJ/1+vpoR3buh5gCnZWvgKyugl oDImFx4xtYrl664NiAxdLnoeypDPyznV7s0mFHZjJ5kaa1YfAYHUIqCszMxVSHigGeom Z5En/scjf4fH6phmIw9xlG+AXLSsZkhuF8Ic6MSEs0ASl80zfAxrk/x6mB4ycWdDTgt6 xZpQ==
MIME-Version: 1.0
X-Received: by 10.112.162.226 with SMTP id yd2mr8933498lbb.1.1422660809879; Fri, 30 Jan 2015 15:33:29 -0800 (PST)
Received: by 10.25.39.129 with HTTP; Fri, 30 Jan 2015 15:33:29 -0800 (PST)
In-Reply-To: <7200.1421359216@sandelman.ca>
References: <7200.1421359216@sandelman.ca>
Date: Sat, 31 Jan 2015 01:33:29 +0200
Message-ID: <CAP+sJUdgHLwdSf6KV-Y6p3uHT1f_5P=nC5E6L5n=h2WjOuax2g@mail.gmail.com>
Subject: Re: [Roll] virtual interim meeting for ROLL: 2015-02-10, 15:00 UTC
From: Ines  Robles <mariainesrobles@googlemail.com>
To: roll <roll@ietf.org>
Content-Type: multipart/alternative; boundary=089e0112c86c35752a050de708cf
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/S0dbm3Lc9NpBdpkh63TXAI-m274>
Cc: "6tisch@ietf.org" <6tisch@ietf.org>, 6man@ietf.org, Brian Haberman <brian@innovationslab.net>, "6lo@ietf.org WG" <6lo@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 23:33:37 -0000

--089e0112c86c35752a050de708cf
Content-Type: text/plain; charset=UTF-8

Hi,

Please find a draft of the slides here
http://www.ietf.org/proceedings/interim/2015/02/10/roll/slides/slides-interim-2015-roll-1-0.pdf

Any comments are very welcome,

Thanks,

Michael and Ines

2015-01-16 0:00 GMT+02:00 Michael Richardson <mcr+ietf@sandelman.ca>:

>
> In accordance with:
> https://www.ietf.org/iesg/statement/interim-meetings.html
> the ROLL Working Group Chairs are announcing a virtual interim meeting for
> February 10, 2015, from 15:00 UTC to 18:00 UTC.
>       (please see: http://goo.gl/NVefsy to convert the time)
>
> The very draft agenda is in development, and can be seen at:
>
> http://www.ietf.org/proceedings/interim/2015/02/10/roll/agenda/agenda-interim-2015-roll-1
>
> The goal of this interim meeting is to do a deep technical dive into the
> different ways of optimizing the byte/power cost of the RFC6553 (RPI) and
> RFC6554 (RH3) options.  This could involve compression or recoding, or???
> We invite submissions on this.  Please post your -00 draft by January 23 if
> possible, or point us at your other drafts.
>
> We will use JITSI for audio, video and slides, with the following URL:
>      https://jitsi.tools.ietf.org/Roll20150210VirtualInterim
>   Participants are encouraged to visit this URL in advance to verify that
>   it works for them.  If you need another participant to help verify,
> please
>   email me.
>
> There will be a PSTN bridge for a backup, should things completely fail.
> We will have a dial-in phone number connected to the bridge for those that
> are unable to connect with a computer, but it won't be toll-free.
> The phone numbers involved will be posted to the agenda as it is finalized,
> and we expect to distribute slides by January 27, 2015.
>
> (BTW: we do not believe that ROLL will meet in Dallas/IETF92)
>
>
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/
>
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>
>

--089e0112c86c35752a050de708cf
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,=C2=A0<div><br></div><div>Please find a draft of the sl=
ides here=C2=A0<a href=3D"http://www.ietf.org/proceedings/interim/2015/02/1=
0/roll/slides/slides-interim-2015-roll-1-0.pdf">http://www.ietf.org/proceed=
ings/interim/2015/02/10/roll/slides/slides-interim-2015-roll-1-0.pdf</a></d=
iv><div><br></div><div>Any comments are very welcome,</div><div><br></div><=
div>Thanks,</div><div><br></div><div>Michael and Ines</div><div class=3D"gm=
ail_extra"><br><div class=3D"gmail_quote">2015-01-16 0:00 GMT+02:00 Michael=
 Richardson <span dir=3D"ltr">&lt;<a href=3D"mailto:mcr+ietf@sandelman.ca" =
target=3D"_blank">mcr+ietf@sandelman.ca</a>&gt;</span>:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex"><br>
In accordance with: <a href=3D"https://www.ietf.org/iesg/statement/interim-=
meetings.html" target=3D"_blank">https://www.ietf.org/iesg/statement/interi=
m-meetings.html</a><br>
the ROLL Working Group Chairs are announcing a virtual interim meeting for<=
br>
February 10, 2015, from 15:00 UTC to 18:00 UTC.<br>
=C2=A0 =C2=A0 =C2=A0 (please see: <a href=3D"http://goo.gl/NVefsy" target=
=3D"_blank">http://goo.gl/NVefsy</a> to convert the time)<br>
<br>
The very draft agenda is in development, and can be seen at:<br>
=C2=A0 <a href=3D"http://www.ietf.org/proceedings/interim/2015/02/10/roll/a=
genda/agenda-interim-2015-roll-1" target=3D"_blank">http://www.ietf.org/pro=
ceedings/interim/2015/02/10/roll/agenda/agenda-interim-2015-roll-1</a><br>
<br>
The goal of this interim meeting is to do a deep technical dive into the<br=
>
different ways of optimizing the byte/power cost of the RFC6553 (RPI) and<b=
r>
RFC6554 (RH3) options.=C2=A0 This could involve compression or recoding, or=
???<br>
We invite submissions on this.=C2=A0 Please post your -00 draft by January =
23 if<br>
possible, or point us at your other drafts.<br>
<br>
We will use JITSI for audio, video and slides, with the following URL:<br>
=C2=A0 =C2=A0 =C2=A0<a href=3D"https://jitsi.tools.ietf.org/Roll20150210Vir=
tualInterim" target=3D"_blank">https://jitsi.tools.ietf.org/Roll20150210Vir=
tualInterim</a><br>
=C2=A0 Participants are encouraged to visit this URL in advance to verify t=
hat<br>
=C2=A0 it works for them.=C2=A0 If you need another participant to help ver=
ify, please<br>
=C2=A0 email me.<br>
<br>
There will be a PSTN bridge for a backup, should things completely fail.<br=
>
We will have a dial-in phone number connected to the bridge for those that<=
br>
are unable to connect with a computer, but it won&#39;t be toll-free.<br>
The phone numbers involved will be posted to the agenda as it is finalized,=
<br>
and we expect to distribute slides by January 27, 2015.<br>
<br>
(BTW: we do not believe that ROLL will meet in Dallas/IETF92)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
<br>
--<br>
Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca">mcr+IETF@=
sandelman.ca</a>&gt;, Sandelman Software Works<br>
IETF ROLL WG co-chair.=C2=A0 =C2=A0 <a href=3D"http://datatracker.ietf.org/=
wg/roll/charter/" target=3D"_blank">http://datatracker.ietf.org/wg/roll/cha=
rter/</a><br>
<br>
</font></span><br>_______________________________________________<br>
Roll mailing list<br>
<a href=3D"mailto:Roll@ietf.org">Roll@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/roll" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/roll</a><br>
<br></blockquote></div><br></div></div>

--089e0112c86c35752a050de708cf--


From nobody Fri Jan 30 18:10:27 2015
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1F291A883A for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 18:10:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level: 
X-Spam-Status: No, score=-114.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i4DqT4xtH0Iv for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 18:10:24 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AA1E1A6F15 for <6man@ietf.org>; Fri, 30 Jan 2015 18:10:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1152; q=dns/txt; s=iport; t=1422670224; x=1423879824; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=NqA2MbQhNvcMGjx7MZDVq7CnRsv5tNw9PNc2o/VfFNc=; b=VICq9dpDZwKUwdGxnynmYYb7/SnX0VJzMoX6xyA1KYF0BsqjweeEcTvD +ZWFaNBJyC6xZEpjxRST4lnCm/68SbhFKaC2Xy7G+4yn+vAwTOno15EQh eoRbkkRi9hUS+0LmITiElbxBTe609Dlvo3n2yDq2/Md9G+4xv9/WFWTLN A=;
X-Files: signature.asc : 487
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A4BQBEOMxU/5RdJa1agwaBKwTKWwKBFkMBAQEBAX2EDAEBAQMBeQULAgEIGC4hESUCBA4FDogKAwkIz3kNhVIBAQEBAQEBAQEBAQEBAQEBAQEBARiNToIqB4MWgRMBBI8BgVSBK4RggUaMXYV8IoNub4FEfgEBAQ
X-IronPort-AV: E=Sophos;i="5.09,495,1418083200";  d="asc'?scan'208";a="119181208"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-1.cisco.com with ESMTP; 31 Jan 2015 02:10:23 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t0V2AN4M021021 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 31 Jan 2015 02:10:23 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.211]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0195.001; Fri, 30 Jan 2015 20:10:23 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: "sarikaya@ieee.org" <sarikaya@ieee.org>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
Thread-Topic: Source Address Dependent Routing and Source Address Selection for IPv6
Thread-Index: AQHQNcNADOrV3CAXwEuZ9Jr9dnzyvJzLywmAgAB6KgCAAjxiAIACkjOAgAObTACAAHVVgIAAOywAgAA9xACAAoJmAIAAZtyAgAAu9wCAAAM1gIABCOkAgAAtgIA=
Date: Sat, 31 Jan 2015 02:10:22 +0000
Message-ID: <4FC68E66-37E0-483F-B12E-EDFAE169FD83@cisco.com>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <1F17C514-D466-4069-9D1E-9EE15E59995F@darou.fr> <CAC8QAceabpe+bHPyQD7fJCXzS-kh17ESw-zoax_pJSKhbmz4Dw@mail.gmail.com> <CAKD1Yr0waXtgp3g2gcH64ygQ3zE_ktfi3mA+2tqpUYtAXujOzg@mail.gmail.com> <54C86618.4070505@gmail.com> <323EF2A4-9200-4382-953F-752ABBE29126@employees.org> <CAC8QAcfWAKWDwr9vxw-F04rrZA8cHbrpWdxfh1tJ52VTigL1WA@mail.gmail.com> <CAKD1Yr0-pQffp=0HLA2MaFaoUdiTLSPn6TqVkU2k8K3qcQUBxw@mail.gmail.com> <54CB3278.8040001@gmail.com> <CAKD1Yr0pOVWFJdT+yZMshAA6g1dh0UrG=P+Dd1RcA4t05zSxuQ@mail.gmail.com> <CAC8QAce9TSkiLBjrnG4eGAZe2SC6HS2Qtqm84qOn3+=QqNUyYw@mail.gmail.com>
In-Reply-To: <CAC8QAce9TSkiLBjrnG4eGAZe2SC6HS2Qtqm84qOn3+=QqNUyYw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.121]
Content-Type: multipart/signed; boundary="Apple-Mail=_DC14F279-A1CF-4D27-A0D9-EFFB9945DC6D"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Mb6daplR9eydHl_qJXmTE3wg4k0>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Jan 2015 02:10:25 -0000

--Apple-Mail=_DC14F279-A1CF-4D27-A0D9-EFFB9945DC6D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Jan 30, 2015, at 3:27 PM, Behcet Sarikaya <sarikaya2012@gmail.com> =
wrote:
>=20
> We started SADR work in 6man.

Why would routing not be done in the routing area?

--Apple-Mail=_DC14F279-A1CF-4D27-A0D9-EFFB9945DC6D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEVAwUBVMw5jZ9ieig10VPpAQJDWAgAonbg21JD+LNJCyqBQdhnTVSvKViXYSAp
WeoyXlJf8Yewugo+L0aXhl/F1aZMn+uTQTtihxzQtqs0ZQis7CnJpEM8HLGt+MKf
UqxfMX9igLjGKHMqNYrDCSH2ijuxVb15Qz9GbwAlCvVb3Lh+9/PtYdTWnekykjqh
cyc6c249Vk0MLINKVYhBzKU/BS/96hVWVVLphxxdNtlifgHLt0P4VkgTegumVdxM
JvdTK0p0BOMANQvnF8tpAKI/CNQIEZXpReGaURV45miXl0+P/N0mAiyeLSEossiI
qBl7SGRlIgP5jsI6xDZaLhuQ6sL/WYrqJ5yWHkNFi73jv37u7y2Lfw==
=LQPf
-----END PGP SIGNATURE-----

--Apple-Mail=_DC14F279-A1CF-4D27-A0D9-EFFB9945DC6D--


From nobody Fri Jan 30 18:36:05 2015
Return-Path: <iana-shared@icann.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 630C61A6FEF; Tue, 27 Jan 2015 11:14:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.19
X-Spam-Level: 
X-Spam-Status: No, score=-3.19 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Viv4AqnRnlWj; Tue, 27 Jan 2015 11:14:17 -0800 (PST)
Received: from smtp1.lax.icann.org (smtp01.icann.org [192.0.33.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B45B1A1BF9; Tue, 27 Jan 2015 11:14:17 -0800 (PST)
Received: from request3.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp1.lax.icann.org (8.13.8/8.13.8) with ESMTP id t0RJEG00028360;  Tue, 27 Jan 2015 19:14:16 GMT
Received: by request3.lax.icann.org (Postfix, from userid 48) id CF068C2054B; Tue, 27 Jan 2015 19:14:16 +0000 (UTC)
RT-Owner: pearl.liang
Subject: [IANA #804727] Last Call: <draft-ietf-6man-enhanced-dad-12.txt> (Enhanced Duplicate Address Detection) to Proposed Standard
From: "Pearl Liang via RT" <drafts-lastcall@iana.org>
In-Reply-To: <20150120145735.11874.48727.idtracker@ietfa.amsl.com>
References: <RT-Ticket-804727@icann.org> <20150120145735.11874.48727.idtracker@ietfa.amsl.com>
Message-ID: <rt-4.2.9-15761-1422386056-640.804727-7-0@icann.org>
X-RT-Loop-Prevention: IANA
X-RT-Ticket: IANA #804727
X-Managed-BY: RT 4.2.9 (http://www.bestpractical.com/rt/)
X-RT-Originator: pearl.liang@icann.org
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Precedence: bulk
Date: Tue, 27 Jan 2015 19:14:16 +0000
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/9ItNqQuSsaILKrT9FCbPgGrLR0A>
X-Mailman-Approved-At: Fri, 30 Jan 2015 18:36:00 -0800
Cc: 6man-chairs@tools.ietf.org, draft-ietf-6man-enhanced-dad.all@tools.ietf.org, ipv6@ietf.org, iesg@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: drafts-lastcall@iana.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jan 2015 19:14:19 -0000

(BEGIN IANA LAST CALL COMMENTS)

IESG/Authors/WG Chairs:

IANA has reviewed draft-ietf-6man-enhanced-dad-12 which is currently in Last Call, and has the following comments:

We understand that, upon approval of this document, there are no IANA Actions that need completion. 

While it is helpful for the IANA Considerations section of the document to remain in place upon publication, if the authors prefer to remove it, IANA doesn't object.

If this assessment is not accurate, please respond as soon as possible.

Thanks,

Pearl Liang
ICANN

(END IANA LAST CALL COMMENTS)


On Tue Jan 20 14:57:59 2015, iesg-secretary@ietf.org wrote:
> 
> The IESG has received a request from the IPv6 Maintenance WG (6man) to
> consider the following document:
> - 'Enhanced Duplicate Address Detection'
>   <draft-ietf-6man-enhanced-dad-12.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2015-02-03. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    IPv6 Loopback Suppression and Duplicate Address Detection (DAD) are
>    discussed in Appendix A of RFC4862.  That specification mentions a
>    hardware-assisted mechanism to detect looped back DAD messages.  If
>    hardware cannot suppress looped back DAD messages, a software
>    solution is required.  Several service provider communities have
>    expressed a need for automated detection of looped back Neighbor
>    Discovery (ND) messages used by DAD.  This document includes
>    mitigation techniques and outlines the Enhanced DAD algorithm to
>    automate the detection of looped back IPv6 ND messages used by DAD.
>    For network loopback tests, the Enhanced DAD algorithm allows IPv6 to
>    self-heal after a loopback is placed and removed.  Further, for
>    certain access networks the document automates resolving a specific
>    duplicate address conflict.  This document updates RFC4861, RFC4862,
>    and RFC4429.
> 
> 
> 
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-dad/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-dad/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 



From nobody Fri Jan 30 23:12:17 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABAB41A8889 for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 23:12:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hxFND21Irx7K for <ipv6@ietfa.amsl.com>; Fri, 30 Jan 2015 23:12:10 -0800 (PST)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05B611A6FFB for <6man@ietf.org>; Fri, 30 Jan 2015 23:12:10 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id rd3so61049790pab.3 for <6man@ietf.org>; Fri, 30 Jan 2015 23:12:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=y04x3DKNtAss0uQuux+HbofbPK54c2c3o4w7UZDKJPM=; b=Aao0cF9D0XXJ8zhsAT4EUNA3zirM+PeU40suwdKM/1rjxfdM6vEZP76xHYTvGt2Zey lmQP+PPxxmBDRX2EhbCDFbkcltK7fXJxfO6xThRyDemqx4unPKC0I2wBRtah5cDBcEIT sBfq+s1OuxgKcq81mzVl/vKLPC7PL9UmZeEqMF7r/Crfp2rlF7X7xzzWWKewkVBatmy8 mMhnBtYn3fpGkaj3hUT02rDCHI+nR1iczUqhxAssonFkJOHBUMUbUD0k9C8HJxThFHAN pDHgM2H+hJlEYpx1t0OjT3mxdX8255FgbG26GjAquVgGi8olDkZyhJBg46yJ5nYTxljz j4mw==
X-Received: by 10.68.233.232 with SMTP id tz8mr14070947pbc.166.1422688329278;  Fri, 30 Jan 2015 23:12:09 -0800 (PST)
Received: from [192.168.1.67] (210-86-2-198.adsl.xtra.co.nz. [210.86.2.198]) by mx.google.com with ESMTPSA id ak5sm12827480pad.44.2015.01.30.23.12.05 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Jan 2015 23:12:08 -0800 (PST)
Message-ID: <54CC804C.5000204@gmail.com>
Date: Sat, 31 Jan 2015 20:12:12 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>,  "sarikaya@ieee.org" <sarikaya@ieee.org>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <1F17C514-D466-4069-9D1E-9EE15E59995F@darou.fr> <CAC8QAceabpe+bHPyQD7fJCXzS-kh17ESw-zoax_pJSKhbmz4Dw@mail.gmail.com> <CAKD1Yr0waXtgp3g2gcH64ygQ3zE_ktfi3mA+2tqpUYtAXujOzg@mail.gmail.com> <54C86618.4070505@gmail.com> <323EF2A4-9200-4382-953F-752ABBE29126@employees.org> <CAC8QAcfWAKWDwr9vxw-F04rrZA8cHbrpWdxfh1tJ52VTigL1WA@mail.gmail.com> <CAKD1Yr0-pQffp=0HLA2MaFaoUdiTLSPn6TqVkU2k8K3qcQUBxw@mail.gmail.com> <54CB3278.8040001@gmail.com> <CAKD1Yr0pOVWFJdT+yZMshAA6g1dh0UrG=P+Dd1RcA4t05zSxuQ@mail.gmail.com> <CAC8QAce9TSkiLBjrnG4eGAZe2SC6HS2Qtqm84qOn3+=QqNUyYw@mail.gmail.com> <4FC68E66-37E0-483F-B12E-EDFAE169FD83@cisco.com>
In-Reply-To: <4FC68E66-37E0-483F-B12E-EDFAE169FD83@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/HkWzOYD_5KhovWI3qrMfV1W90a8>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Jan 2015 07:12:15 -0000

On 31/01/2015 15:10, Fred Baker (fred) wrote:
> 
>> On Jan 30, 2015, at 3:27 PM, Behcet Sarikaya <sarikaya2012@gmail.com> wrote:
>>
>> We started SADR work in 6man.
> 
> Why would routing not be done in the routing area?

I think that's a fair question, once we know we have a routing problem.
It seems to me that isn't clear yet, which is why I'd like to see
something approaching consenus about the scenario analysis.

   Brian


From nobody Sat Jan 31 01:17:44 2015
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 669E21A88FC for <ipv6@ietfa.amsl.com>; Sat, 31 Jan 2015 01:17:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level: 
X-Spam-Status: No, score=-114.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tzH4IHcQ4OnU for <ipv6@ietfa.amsl.com>; Sat, 31 Jan 2015 01:17:34 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C4801A88EF for <6man@ietf.org>; Sat, 31 Jan 2015 01:17:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1562; q=dns/txt; s=iport; t=1422695854; x=1423905454; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=pP5y7cL8xSfrb8EgapByLBjRBlGklZLxBZvsvHaXDFk=; b=TwpABYWb4uR6PKGf40o02JE64j0JmH3/vEyrQI1KRa3QrUNDXRYE6X8J MAFwPk7pexNt/+CKJon7RLcmFHCQQdhYLYefs7RKkmN11E2x/jsCEsJvd A4ECbKDKCkedRgq8eQTzzBE+gEJ6vErq3u/owN3EorntTsqszeLel8TQX s=;
X-Files: signature.asc : 487
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0A8BQB4nMxU/4gNJK1bgwZSWQTEbYVvAoEUQwEBAQEBfYQMAQEBAwF5BQsCAQgYLiERJQIEDgUOiAoDCQgNzSENhVIBAQEBAQEBAQEBAQEBAQEBAQEBAQETBI1OgioHgxaBEwWPAYFUgStPhBGBRoxfhXwig25vAYFDfgEBAQ
X-IronPort-AV: E=Sophos;i="5.09,496,1418083200";  d="asc'?scan'208";a="119286118"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-7.cisco.com with ESMTP; 31 Jan 2015 09:17:33 +0000
Received: from xhc-rcd-x09.cisco.com (xhc-rcd-x09.cisco.com [173.37.183.83]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t0V9HXdq021849 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 31 Jan 2015 09:17:33 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.211]) by xhc-rcd-x09.cisco.com ([173.37.183.83]) with mapi id 14.03.0195.001; Sat, 31 Jan 2015 03:17:33 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
Thread-Topic: Source Address Dependent Routing and Source Address Selection for IPv6
Thread-Index: AQHQNcNADOrV3CAXwEuZ9Jr9dnzyvJzLywmAgAB6KgCAAjxiAIACkjOAgAObTACAAHVVgIAAOywAgAA9xACAAoJmAIAAZtyAgAAu9wCAAAM1gIABCOkAgAAtgICAAFRWAIAAIwIA
Date: Sat, 31 Jan 2015 09:17:33 +0000
Message-ID: <4AFCD303-8D20-440D-AAA4-6A26C25F6996@cisco.com>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <1F17C514-D466-4069-9D1E-9EE15E59995F@darou.fr> <CAC8QAceabpe+bHPyQD7fJCXzS-kh17ESw-zoax_pJSKhbmz4Dw@mail.gmail.com> <CAKD1Yr0waXtgp3g2gcH64ygQ3zE_ktfi3mA+2tqpUYtAXujOzg@mail.gmail.com> <54C86618.4070505@gmail.com> <323EF2A4-9200-4382-953F-752ABBE29126@employees.org> <CAC8QAcfWAKWDwr9vxw-F04rrZA8cHbrpWdxfh1tJ52VTigL1WA@mail.gmail.com> <CAKD1Yr0-pQffp=0HLA2MaFaoUdiTLSPn6TqVkU2k8K3qcQUBxw@mail.gmail.com> <54CB3278.8040001@gmail.com> <CAKD1Yr0pOVWFJdT+yZMshAA6g1dh0UrG=P+Dd1RcA4t05zSxuQ@mail.gmail.com> <CAC8QAce9TSkiLBjrnG4eGAZe2SC6HS2Qtqm84qOn3+=QqNUyYw@mail.gmail.com> <4FC68E66-37E0-483F-B12E-EDFAE169FD83@cisco.com> <54CC804C.5000204@gmail.com>
In-Reply-To: <54CC804C.5000204@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.121]
Content-Type: multipart/signed; boundary="Apple-Mail=_16223EFD-9F83-43D2-A607-4F09FE4DEF5C"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/iZhD7QKY10hkn7S2ZrMU97FJ0Kc>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Jan 2015 09:17:36 -0000

--Apple-Mail=_16223EFD-9F83-43D2-A607-4F09FE4DEF5C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Jan 30, 2015, at 11:12 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> I think that's a fair question, once we know we have a routing =
problem.
> It seems to me that isn't clear yet, which is why I'd like to see
> something approaching consenus about the scenario analysis.

Well, in case it helps:

=
https://datatracker.ietf.org/doc/draft-baker-rtgwg-src-dst-routing-use-cas=
es
https://tools.ietf.org/html/draft-baker-rtgwg-src-dst-routing-use-cases
  "Requirements and Use Cases for Source/Destination Routing", Fred =
Baker,
  2014-10-21

--Apple-Mail=_16223EFD-9F83-43D2-A607-4F09FE4DEF5C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iQEVAwUBVMydqp9ieig10VPpAQKRpwf9HRQxfxfTvcCh8J/Et3lB7jK2QjSGOtSR
lSqGfqE4USz9IExEBx0EiV26I92BOHfqaxghfZEziBfZXm4th5k/Nqmd9fCu4nj9
XmvvrDcFMiNygnpTJReg8gXsT/jcNjvkV3JTf6K/miliwX/+xPYYrukHwuoGPTFU
voWUHgFYDSSV3FRPJDnTeZon5iONR6GmGos7kdMbAktpLNWCux/G21XoB9XMb//+
IOzMYUh7C5TBpU+foAwbflJf7qnQRgOzZLFEGfopP7CZrNb+KS9vWzcTaUU/ohAN
qiOQ2141/V9wT0MR20X59bYAuGq6EkcRIPQqnV4M8zNj4bSgxtUwyg==
=TYdg
-----END PGP SIGNATURE-----

--Apple-Mail=_16223EFD-9F83-43D2-A607-4F09FE4DEF5C--


From nobody Sat Jan 31 01:32:50 2015
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2098A1A8906 for <ipv6@ietfa.amsl.com>; Sat, 31 Jan 2015 01:32:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lJRh2gQJmeJe for <ipv6@ietfa.amsl.com>; Sat, 31 Jan 2015 01:32:48 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 435221A8905 for <6man@ietf.org>; Sat, 31 Jan 2015 01:32:48 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id CE0DE6205; Sat, 31 Jan 2015 01:32:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=SV8eBYNtogAu1RYRK5x1I01QfQw=; b=V7I3ScQpakWwakRvUK HzkKpyGrGlQeuhNnmF7qCUhAp5cKpifJfphEX7HpvdVolQZRFFahIHCeeKcks6Wv 7oBo7KP142bFjME6OY+VCozh1gThmzKXy2Lfu5YdcuNSHvvxuZTZytz2Vm3dHZPT aYXKqoZ3x8xsEU9SzM0+H5vs0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=WHWDRuNZ1nTXGqirJTJAs3KyJJ2uDLULudsrGBzvkPuzp6LChDz KGvVenLSG7RIW549o/+GxoZaS22AmwIn4X4XtJFirKFgBzHlf8YAOqKsSNB5p5L1 Lz9vxLI8erYsu6kB592/X+3V4uoIIaw6Ur9KYz8UfS0JGgTFXCxMb44c=
Received: from OTROAN-M-Q0RH.localdomain (unknown [195.159.234.46]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 69A9961F7; Sat, 31 Jan 2015 01:32:46 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by OTROAN-M-Q0RH.localdomain (Postfix) with ESMTP id 984C33DC16A6; Sat, 31 Jan 2015 10:32:43 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
From: Ole Troan <otroan@employees.org>
In-Reply-To: <4FC68E66-37E0-483F-B12E-EDFAE169FD83@cisco.com>
Date: Sat, 31 Jan 2015 10:32:43 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C1E188CF-9E30-4BA1-9A93-4BCF2EC6642E@employees.org>
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <1F17C514-D466-4069-9D1E-9EE15E59995F@darou.fr> <CAC8QAceabpe+bHPyQD7fJCXzS-kh17ESw-zoax_pJSKhbmz4Dw@mail.gmail.com> <CAKD1Yr0waXtgp3g2gcH64ygQ3zE_ktfi3mA+2tqpUYtAXujOzg@mail.gmail.com> <54C86618.4070505@gmail.com> <323EF2A4-9200-4382-953F-752ABBE29126@employees.org> <CAC8QAcfWAKWDwr9vxw-F04rrZA8cHbrpWdxfh1tJ52VTigL1WA@mail.gmail.com> <CAKD1Yr0-pQffp=0HLA2MaFaoUdiTLSPn6TqVkU2k8K3qcQUBxw@mail.gmail.com> <54CB3278.8040001@gmail.com> <CAKD1Yr0pOVWFJdT+yZMshAA6g1dh0UrG=P+Dd1RcA4t05zSxuQ@mail.gmail.com> <CAC8QAce9TSkiLBjrnG4eGAZe2SC6HS2Qtqm84qOn3+=QqNUyYw@mail.gmail.com> <4FC68E66-37E0-483F-B12E-EDFAE169FD83@cisco.com>
To: "Fred Baker (fred)" <fred@cisco.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/U7HDcN1z5B-31pKIwFYW_V_Xia8>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Jan 2015 09:32:49 -0000

Fred,

>> We started SADR work in 6man.
>=20
> Why would routing not be done in the routing area?

it would and I think it is.
as far as I remember this work was instigated both in homenet and in =
routing in parallel.

what I think has been discussed in 6man so far, and is in scope for =
6man, is possible host changes (or network to host signalling).

cheers,
Ole=


From nobody Sat Jan 31 07:57:12 2015
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DD911A03A3 for <ipv6@ietfa.amsl.com>; Sat, 31 Jan 2015 07:57:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id atDIi9ChT2Ss for <ipv6@ietfa.amsl.com>; Sat, 31 Jan 2015 07:57:06 -0800 (PST)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id D65EF1A039F for <6man@ietf.org>; Sat, 31 Jan 2015 07:57:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 3E76F8716F1; Sat, 31 Jan 2015 16:57:04 +0100 (CET)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rpJFWCHcFkkx; Sat, 31 Jan 2015 16:57:04 +0100 (CET)
Received: from Rays-iMac.local (unknown [IPv6:2001:470:1f15:73a:b56f:ba0a:672a:b30b]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id E91DE871612; Sat, 31 Jan 2015 16:57:03 +0100 (CET)
Message-ID: <54CCFB4E.2020605@globis.net>
Date: Sat, 31 Jan 2015 16:57:02 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: sarikaya@ieee.org
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <54C9DCCD.4090802@globis.net> <54CAB84E.5030406@gmail.com> <8C665B1D-4063-4D14-A0CD-B4CA1EC1E7CE@globis.net> <021E64FECA7E5A4699562F4E66716481534A0512@XCH-PHX-503.sw.nos.boeing.com> <CAC8QAcfUBZqq3A-6a2vKGzAEXiTp16aGH9DL7menZzEVS0oYWw@mail.gmail.com>
In-Reply-To: <CAC8QAcfUBZqq3A-6a2vKGzAEXiTp16aGH9DL7menZzEVS0oYWw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ivW3MWfUoFUKtyNwX5r-ky7LL9g>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Jan 2015 15:57:10 -0000

> Behcet Sarikaya <mailto:sarikaya2012@gmail.com>
> 31 January 2015 00:28
> Folks,
> Mobility in home network is out of scope with this draft.
> Maybe also that should be discussed in homenet.
>
> Regards,
>
> Behcet
>
> On Fri, Jan 30, 2015 at 2:55 PM, Manfredi, Albert E

RFC7084 only covers the situation of a single ISP customer edge router, 
so the described situation cannot occur in any existing 
IETF-standardised set ups. Only Homenet covers multiple ISP routers 
connected to one user LAN shared with end hosts.

So you seem to be suggesting creating a new RA or DHCPv6 option that has 
to be implemented in every single end-host operating system for the 
solution to be able to work, and it won't even solve the real 
operational problems that will occur in Homenet?

IMVHO a better solution to the problem described in this draft is that 
when a "mis-directed packet" arrives at a router performing BCP38 
filtering, if the router is SADR capable, and the device has learned a 
SADR route via another SADR router that includes the relevant source 
prefix, the receiving device should prefer the SADR route over the 
destination-based-only route and forward the packet to the other ISP 
router rather than via its own default route, and SADR-aware routers 
SHOULD NOT send an ICMPv6 redirect if that ICMPv6 redirect would only be 
triggered by the presence of SADR.

This to avoid filtering the packet on the egress interface to the ISP 
not delegating the source prefix, or causing incorrect ICMP redirection 
entries in end hosts. That may mean forwarding a packet back out on the 
inbound interface to another ISP router, but so what? This advised 
behaviour would only require an update to SADR aware routers to perform 
a form of policy based routing on ingress (nothing dramatically new here 
AFAICs), does not require updating any end hosts, and does not require 
any new standards or new RA/RIO/DHCPv6 options.

-- 
Regards,
RayH


From nobody Sat Jan 31 10:25:46 2015
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95F9B1A1A8F for <ipv6@ietfa.amsl.com>; Sat, 31 Jan 2015 10:25:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 55q8jzLjpq4k for <ipv6@ietfa.amsl.com>; Sat, 31 Jan 2015 10:25:43 -0800 (PST)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 272901A0103 for <6man@ietf.org>; Sat, 31 Jan 2015 10:25:43 -0800 (PST)
Received: by mail-pa0-f53.google.com with SMTP id kx10so65096789pab.12 for <6man@ietf.org>; Sat, 31 Jan 2015 10:25:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=9SzgcB8xPLAXWUAoiRnWTUL2RqrCblwbv4KYfN3Q2rs=; b=MHVrLXdBRMNeQc79LeVs7zyluprFaU8VmzADOtyX+tUL3n0g0CmFulTR58JpRkkRDD UOoLrQV+KCdT2owjNtmUAtR/rMvO+u05pIkfo9t7oyFbF9dxqScaWgat7FFATRyMxijr AaK8uJahnXW//M8PARB/W06dB/P3VAL/0EYfU8GaIqhaC/GMxFTII+OlTITk0UURjSrj zGitPDG0frc9KgKItQKpo+h/2Yc0nd/TcBebR8H80LUaw8kRGzE+dQ8PcCTtcZRNfi+p lFjXhVj7wys3cDfA1gC3SX965py7qOJuaYb426r3Y5/PPhqBr1fS2vVFP87KzFYj7bT6 yQQA==
X-Received: by 10.66.250.225 with SMTP id zf1mr17963984pac.31.1422728742464; Sat, 31 Jan 2015 10:25:42 -0800 (PST)
Received: from [192.168.1.67] (210-86-2-198.adsl.xtra.co.nz. [210.86.2.198]) by mx.google.com with ESMTPSA id in1sm14293747pbc.19.2015.01.31.10.25.39 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 31 Jan 2015 10:25:41 -0800 (PST)
Message-ID: <54CD1E1A.4070303@gmail.com>
Date: Sun, 01 Feb 2015 07:25:30 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: Source Address Dependent Routing and Source Address Selection for IPv6
References: <CAC8QAcdfLPW5-GZFo-eFZY=wXXzTgvNpKG_MgARGkb48HtPQsQ@mail.gmail.com> <CAKD1Yr0-64qTy7pSB0y0faJNJNb_epgm4BmrkULBuPPCZ5bmTA@mail.gmail.com> <50BA595E-F4D4-4BAD-BCCA-418A0857FA16@darou.fr> <CAC8QAcciYVb5xOPzR11keckimb3imtzNwkea7nSOGvYh7=c0kQ@mail.gmail.com> <1F17C514-D466-4069-9D1E-9EE15E59995F@darou.fr> <CAC8QAceabpe+bHPyQD7fJCXzS-kh17ESw-zoax_pJSKhbmz4Dw@mail.gmail.com> <CAKD1Yr0waXtgp3g2gcH64ygQ3zE_ktfi3mA+2tqpUYtAXujOzg@mail.gmail.com> <54C86618.4070505@gmail.com> <323EF2A4-9200-4382-953F-752ABBE29126@employees.org> <CAC8QAcfWAKWDwr9vxw-F04rrZA8cHbrpWdxfh1tJ52VTigL1WA@mail.gmail.com> <CAKD1Yr0-pQffp=0HLA2MaFaoUdiTLSPn6TqVkU2k8K3qcQUBxw@mail.gmail.com> <54CB3278.8040001@gmail.com> <CAKD1Yr0pOVWFJdT+yZMshAA6g1dh0UrG=P+Dd1RcA4t05zSxuQ@mail.gmail.com> <CAC8QAce9TSkiLBjrnG4eGAZe2SC6HS2Qtqm84qOn3+=QqNUyYw@mail.gmail.com> <4FC68E66-37E0-483F-B12E-EDFAE169FD83@cisco.com> <54CC804C.5000204@gmail.com> <4AFCD303-8D20-440D-AAA4-6A26C25F6996@cisco.com>
In-Reply-To: <4AFCD303-8D20-440D-AAA4-6A26C25F6996@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/xUN0F1dFVI9_ctmctYK51Jzn3-0>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Jan 2015 18:25:44 -0000

On 31/01/2015 22:17, Fred Baker (fred) wrote:
> 
>> On Jan 30, 2015, at 11:12 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>
>> I think that's a fair question, once we know we have a routing problem.
>> It seems to me that isn't clear yet, which is why I'd like to see
>> something approaching consenus about the scenario analysis.
> 
> Well, in case it helps:
> 
> https://datatracker.ietf.org/doc/draft-baker-rtgwg-src-dst-routing-use-cases
> https://tools.ietf.org/html/draft-baker-rtgwg-src-dst-routing-use-cases
>   "Requirements and Use Cases for Source/Destination Routing", Fred Baker,
>   2014-10-21

IMHO they do help and Behcet's draft specifically refers to them, but the
concern is about what should be shipped in all host stacks such that all
hosts will work in any of the possible scenarios.

   Brian

    Brian

