
From nobody Wed Dec  3 08:07:16 2014
Return-Path: <jonathan@hansfords.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58E4E1A3B9D for <homenet@ietfa.amsl.com>; Wed,  3 Dec 2014 08:07:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.101
X-Spam-Level: 
X-Spam-Status: No, score=0.101 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 X1vsoeEoaTIn for <homenet@ietfa.amsl.com>; Wed,  3 Dec 2014 08:07:06 -0800 (PST)
Received: from avasout04.plus.net (avasout04.plus.net [212.159.14.19]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CAC081A1B48 for <homenet@ietf.org>; Wed,  3 Dec 2014 08:07:05 -0800 (PST)
Received: from Vanguard ([84.92.149.4]) by avasout04 with smtp id P4721p00405w0Nk01473m3; Wed, 03 Dec 2014 16:07:04 +0000
X-CM-Score: 0.00
X-CNFS-Analysis: v=2.1 cv=ZuVjKrLG c=1 sm=1 tr=0 a=ay7+waBXjX2gYBYtdgtTjg==:117 a=ay7+waBXjX2gYBYtdgtTjg==:17 a=0Bzu9jTXAAAA:8 a=6bkCdLdQAAAA:8 a=DAwyPP_o2Byb1YXLmDAA:9 a=Zr7miEi8wWIA:10 a=cKsnjEOsciEA:10 a=2oeSqxxVzlsA:10 a=u70v44XJMRm-sT3miW0A:9 a=CjuIK1q_8ugA:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=HeGJdMf7AFQ1jVFe9lMA:9 a=0cuH1PP1yM9_49E7:21 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10
From: "Jonathan Hansford" <jonathan@hansfords.net>
To: <homenet@ietf.org>
Date: Wed, 3 Dec 2014 16:07:09 -0000
Message-ID: <019001d00f13$320db9e0$96292da0$@hansfords.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0191_01D00F13.320EA440"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AdAO6zCVQ0tsC2qQS7+4IaP4yoJQkA==
Content-Language: en-gb
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/90I7OCjBkEqjV10ccBPh2xdt-eE
Subject: [homenet] Comments on draft-ietf-homenet-hncp-02
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Dec 2014 16:07:10 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0191_01D00F13.320EA440
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

Hi,

 

I've just come to the homenet WG and have some questions and comments for
draft-ietf-homenet-hncp-02:

 

1.       I notice from the homenet charter the work is based on IPv6. Is
there anything in the HNCP protocol that precludes its use for IPv4? I am
looking for a similar capability for use within multiple IPv4 broadcast
domains with no IPv6 in the mix at all.

2.       What is a node? I presume it is a router.

3.       Section 1, 3rd paragraph: s/information how/information on how

4.       Section 3, set of TLV data: s/The set of TLVs have/The set of TLVs
has

5.       Section 4.2

a.       1st paragraph: s/as purely as/purely as

b.      "TLVs MUST or MAY be present" - is that a decision that can be made
per node, per link or across the implementation?

6.       Section 4.2.4, Network State TLV: s/every known node/every node
known

7.       Section 4.3, 2nd paragraph, last sentence: s/is not IPv6/is not an
IPv6

8.       Sections 4.4 to 5: The style feels more terse here. The text is
still readable, but there is a noticeable reduction in definite and
indefinite articles (e.g. s/Whenever multicast message/Whenever a multicast
message). 

9.       Section 4.4, 2nd sentence: Feels a little clumsy. How about "If
nothing (for example - no router advertisements, no HNCP traffic) is
received from that neighbor in Imax seconds, the neighbor is not in the
neighbor discovery cache, and no layer 2 indication of presence is
available, at least 3 attempts SHOULD be made to ping it using a request
network state message (Section 4.2.2), sent with increasing timeouts (e.g.
1, 2, 4 seconds)."?

10.   Section 4.5: Is the reference to "h(neighbor node identifier)" the
equivalent of H(x) in section 5?

11.   Section 5: 

a.       s/MUST be always/MUST always be

b.      "Encoding of type=123 ." and "Notation: ." feel as though they apply
to the preceding diagram rather than the encoding being an example and the
notation applying to the diagrams that follow.

12.   Section 6, as-hoc category: Excuse my ignorance, but what is meant by
non-transitive?

13.   Page 16, assigned prefix: s/using one TLVs/using one TLV

14.   Section 7: s/Following TLVs/The following TLVs

15.   Section 9, 1st paragraph: s/have rarely security/rarely have security

16.   Section 10: s/with following/with the following

 

Jonathan


------=_NextPart_000_0191_01D00F13.320EA440
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:518157182;
	mso-list-type:hybrid;
	mso-list-template-ids:-776405512 134807567 134807577 134807579 =
134807567 134807577 134807579 134807567 134807577 134807579;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB =
link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoNormal>Hi,<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>I&#8217;ve =
just come to the homenet WG and have some questions and comments for =
draft-ietf-homenet-hncp-02:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span><![endif]>I =
notice from the homenet charter the work is based on IPv6. Is there =
anything in the HNCP protocol that precludes its use for IPv4? I am =
looking for a similar capability for use within multiple IPv4 broadcast =
domains with no IPv6 in the mix at all.<o:p></o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>2.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>What is a node? I presume it is a =
router.<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>3.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Section 1, 3<sup>rd</sup> paragraph: =
s/information how/information on how<o:p></o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>4.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Section 3, set of TLV data: s/The set of TLVs =
have/The set of TLVs has<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>5.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Section 4.2<o:p></o:p></p><p =
class=3DMsoListParagraph =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>a.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>1<sup>st</sup> paragraph: s/as purely as/purely =
as<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>b.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>&#8220;TLVs MUST or MAY be present&#8221; =
&#8211; is that a decision that can be made per node, per link or across =
the implementation?<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>6.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Section 4.2.4, Network State TLV: s/every known =
node/every node known<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>7.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Section 4.3, 2<sup>nd</sup> paragraph, last =
sentence: s/is not IPv6/is not an IPv6<o:p></o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>8.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Sections 4.4 to 5: The style feels more terse =
here. The text is still readable, but there is a noticeable reduction in =
definite and indefinite articles (e.g. s/Whenever multicast =
message/Whenever a multicast message). <o:p></o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>9.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>Section 4.4, 2<sup>nd</sup> sentence: Feels a =
little clumsy. How about &#8220;If nothing (for example - no router =
advertisements, no HNCP traffic) is received from that neighbor in Imax =
seconds, the neighbor is not in the neighbor discovery cache, and no =
layer 2 indication of presence is available, at least 3 attempts SHOULD =
be made to ping it using a request network state message (Section =
4.2.2), sent with increasing timeouts (e.g. 1, 2, 4 =
seconds).&#8221;?<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>10.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></span><![endif]>Section 4.5: Is the reference to =
&#8220;h(neighbor node identifier)&#8221; the equivalent of H(x) in =
section 5?<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>11.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></span><![endif]>Section 5: <o:p></o:p></p><p =
class=3DMsoListParagraph =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>a.<span =
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>s/MUST be always/MUST always be<o:p></o:p></p><p =
class=3DMsoListParagraph =
style=3D'margin-left:72.0pt;text-indent:-18.0pt;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>b.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span><![endif]>&#8220;Encoding of type=3D123 &#8230;&#8221; and =
&#8220;Notation: &#8230;&#8221; feel as though they apply to the =
preceding diagram rather than the encoding being an example and the =
notation applying to the diagrams that follow.<o:p></o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>12.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></span><![endif]>Section 6, as-hoc category: Excuse my ignorance, =
but what is meant by non-transitive?<o:p></o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>13.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></span><![endif]>Page 16, assigned prefix: s/using one TLVs/using =
one TLV<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>14.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></span><![endif]>Section 7: s/Following TLVs/The following =
TLVs<o:p></o:p></p><p class=3DMsoListParagraph =
style=3D'text-indent:-18.0pt;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span style=3D'mso-list:Ignore'>15.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></span><![endif]>Section 9, 1<sup>st</sup> paragraph: s/have =
rarely security/rarely have security<o:p></o:p></p><p =
class=3DMsoListParagraph style=3D'text-indent:-18.0pt;mso-list:l0 level1 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>16.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp; =
</span></span><![endif]>Section 10: s/with following/with the =
following<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Jonathan<o:p></o:p></p></div></body></html>
------=_NextPart_000_0191_01D00F13.320EA440--


From nobody Fri Dec  5 05:30:05 2014
Return-Path: <markus.stenberg@iki.fi>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1FFE1ACE9A for <homenet@ietfa.amsl.com>; Fri,  5 Dec 2014 05:30:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.579
X-Spam-Level: *
X-Spam-Status: No, score=1.579 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] 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 XN0yfPf3rriO for <homenet@ietfa.amsl.com>; Fri,  5 Dec 2014 05:29:59 -0800 (PST)
Received: from jenni2.inet.fi (mta-out1.inet.fi [62.71.2.195]) by ietfa.amsl.com (Postfix) with ESMTP id B98D71ACE99 for <homenet@ietf.org>; Fri,  5 Dec 2014 05:29:57 -0800 (PST)
Received: from poro.lan (80.220.64.126) by jenni2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 546BDD5301E6C5F4; Fri, 5 Dec 2014 15:29:51 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <87ppcd60tb.wl-jch@pps.univ-paris-diderot.fr>
Date: Fri, 5 Dec 2014 15:29:51 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C3268A6-020A-46F8-8200-F1E6D4D24C3B@iki.fi>
References: <87sihiy8rr.wl-jch@pps.univ-paris-diderot.fr> <87ppcd60tb.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/_27-3hrHIbFlJQUMAhXMmVsoQWc
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] Stub-only implementation of Babel
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Dec 2014 13:30:01 -0000

On 23.11.2014, at 23.53, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>> sbabeld doesn't speak to the kernel itself, it execs the "ip" utility
>> instead.  That makes error handling somewhat random,
> Steven has fixed that -- sbabeld's error handling should be reasonably
> reliable now.  (And it=E2=80=99s also slightly smaller.)

Speaking of sizes.. Steven made following comparison of existing routing =
(or =E2=80=98routing=E2=80=99 in case of hnetd) protocol implementation =
candidates:

http://employees.org/~mstenber/201412-igp-implementations.pdf

I hope the cabal (aka =E2=80=98design team=E2=80=99 or whatever it is =
called today) writing the routing comparison document includes aspects =
like that, or even just spec size, as metrics for evaluation.=20

Cheers,

-Markus=


From nobody Fri Dec  5 05:41:35 2014
Return-Path: <acee@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 674591A0382 for <homenet@ietfa.amsl.com>; Fri,  5 Dec 2014 05:41:34 -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 E4VRJukiyLc5 for <homenet@ietfa.amsl.com>; Fri,  5 Dec 2014 05:41:33 -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 DCD3B1A01F6 for <homenet@ietf.org>; Fri,  5 Dec 2014 05:41:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1157; q=dns/txt; s=iport; t=1417786893; x=1418996493; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=9OCJltOJBi4VVmaONNRkKXWQVkpH+swhSK8qBgkNALs=; b=grMaDCL5eLWH6rPucpnNVWZqQ7XlsS6EhuAiSmnEdND2c4zCuQl3DM4n jSHzEmIfreGuO0eIJrxqo7xyd+/ZbMjypSbH6zv8H4RcJTSVlCY3gqEOD Wd2T59VLbUQrsU09zpr0JAVQ0bGvt0KcGzjp1GxxlMvtS3/jRYXL0ggJT I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AksFALq1gVStJA2K/2dsb2JhbABZFoJwUlgExWBeCoVETwKBHRYBAQEBAX2EAwEBAgIBAQFrCxACAQgYLicLJQIEAQ0FiDsN1msBAQEBAQEBAQEBAQEBAQEBAQEBAQEXkE8HhDYFj0aDfoYbgVaRaYNvb4FFfgEBAQ
X-IronPort-AV: E=Sophos;i="5.07,522,1413244800"; d="scan'208";a="102995011"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-7.cisco.com with ESMTP; 05 Dec 2014 13:41:32 +0000
Received: from xhc-rcd-x01.cisco.com (xhc-rcd-x01.cisco.com [173.37.183.75]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id sB5DfWsl024679 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 5 Dec 2014 13:41:32 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.58]) by xhc-rcd-x01.cisco.com ([173.37.183.75]) with mapi id 14.03.0195.001; Fri, 5 Dec 2014 07:41:32 -0600
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Markus Stenberg <markus.stenberg@iki.fi>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Thread-Topic: [homenet] Stub-only implementation of Babel
Thread-Index: AQHQEI+fILOsX1XXkk6XK3Ibb7CnBZyBEfqA
Date: Fri, 5 Dec 2014 13:41:31 +0000
Message-ID: <D0A71FC4.A234%acee@cisco.com>
References: <87sihiy8rr.wl-jch@pps.univ-paris-diderot.fr> <87ppcd60tb.wl-jch@pps.univ-paris-diderot.fr> <9C3268A6-020A-46F8-8200-F1E6D4D24C3B@iki.fi>
In-Reply-To: <9C3268A6-020A-46F8-8200-F1E6D4D24C3B@iki.fi>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.152.199]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <9353CF3373F47B47A42243AB643DD641@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/FT1CRtj0ZF2qSmpCPai0_NjfJGg
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Stub-only implementation of Babel
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Dec 2014 13:41:34 -0000

Who contributed the ISIS implementation in Erlang? I must admit I haven=B9t
followed it closely but I thought all the quagga work was C or C++?

On 12/5/14, 8:29 AM, "Markus Stenberg" <markus.stenberg@iki.fi> wrote:

>On 23.11.2014, at 23.53, Juliusz Chroboczek
><jch@pps.univ-paris-diderot.fr> wrote:
>>> sbabeld doesn't speak to the kernel itself, it execs the "ip" utility
>>> instead.  That makes error handling somewhat random,
>> Steven has fixed that -- sbabeld's error handling should be reasonably
>> reliable now.  (And it=B9s also slightly smaller.)
>
>Speaking of sizes.. Steven made following comparison of existing routing
>(or =8Crouting=B9 in case of hnetd) protocol implementation candidates:
>
>http://employees.org/~mstenber/201412-igp-implementations.pdf
>
>I hope the cabal (aka =8Cdesign team=B9 or whatever it is called today)
>writing the routing comparison document includes aspects like that, or
>even just spec size, as metrics for evaluation.
>
>Cheers,
>
>-Markus
>_______________________________________________
>homenet mailing list
>homenet@ietf.org
>https://www.ietf.org/mailman/listinfo/homenet


From nobody Fri Dec  5 05:43:55 2014
Return-Path: <markus.stenberg@iki.fi>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEDB21A0398 for <homenet@ietfa.amsl.com>; Fri,  5 Dec 2014 05:43:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779] 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 XtRpZQGKQkGs for <homenet@ietfa.amsl.com>; Fri,  5 Dec 2014 05:43:53 -0800 (PST)
Received: from jenni2.inet.fi (mta-out1.inet.fi [62.71.2.203]) by ietfa.amsl.com (Postfix) with ESMTP id AD9C71A0382 for <homenet@ietf.org>; Fri,  5 Dec 2014 05:43:52 -0800 (PST)
Received: from poro.lan (80.220.64.126) by jenni2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 546BDD5301E721A0; Fri, 5 Dec 2014 15:43:44 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <019001d00f13$320db9e0$96292da0$@hansfords.net>
Date: Fri, 5 Dec 2014 15:43:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8BF97502-E33B-4AFA-81D2-D5F0C6A6E491@iki.fi>
References: <019001d00f13$320db9e0$96292da0$@hansfords.net>
To: Jonathan Hansford <jonathan@hansfords.net>
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/JQoiDkT6_OyZ2UzSpbR3uK6zxV4
Cc: homenet@ietf.org, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] Comments on draft-ietf-homenet-hncp-02
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Dec 2014 13:43:54 -0000

> On 3.12.2014, at 18.07, Jonathan Hansford <jonathan@hansfords.net> =
wrote:
> I=E2=80=99ve just come to the homenet WG and have some questions and =
comments for draft-ietf-homenet-hncp-02:

Heya, and thanks for the review ;)
=20
> 1.       I notice from the homenet charter the work is based on IPv6. =
Is there anything in the HNCP protocol that precludes its use for IPv4? =
I am looking for a similar capability for use within multiple IPv4 =
broadcast domains with no IPv6 in the mix at all.

Do you need PA, SD, or just share some arbitrary TLVs? If last, you =
could use some existing routing link-state protocol, or possibly =
<unnamed thing we are generalizing out of HNCP>.

> 2.       What is a node? I presume it is a router.

Router/node is awfully mixed in hncp-02.. Router is a node, but not all =
nodes are routers..=20

Thanks also for corrections - I will incorporate them in the next =
version if they are still applicable (it seems the next iteration will =
be drastic, given what we have now in github (public development and =
all) but more on that later perhaps).

(Terms =E2=80=98link=E2=80=99, =E2=80=98router=E2=80=99, =E2=80=99node=E2=80=
=99 were horribly abused in the hncp-02. Sorry.)

> 3.       Section 1, 3rd paragraph: s/information how/information on =
how
>=20
> 4.       Section 3, set of TLV data: s/The set of TLVs have/The set of =
TLVs has
>=20
> 5.       Section 4.2
>=20
> a.       1st paragraph: s/as purely as/purely as
>=20
> b.      =E2=80=9CTLVs MUST or MAY be present=E2=80=9D =E2=80=93 is =
that a decision that can be made per node, per link or across the =
implementation?

Good point, have to specify that (if this thing even exists). MUST be =
ones obviously are always required, and MAY ones are local choice. (I =
think we got rid of the MAY ones in the next iteration though, but I =
have to double check to make sure.)

Cheers,

-Markus=


From nobody Fri Dec  5 05:48:15 2014
Return-Path: <markus.stenberg@iki.fi>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC4F91A039C for <homenet@ietfa.amsl.com>; Fri,  5 Dec 2014 05:48:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.212
X-Spam-Level: 
X-Spam-Status: No, score=0.212 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FRT_CLICK=1.333, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] 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 vU2ZR5Eep-tG for <homenet@ietfa.amsl.com>; Fri,  5 Dec 2014 05:48:13 -0800 (PST)
Received: from jenni2.inet.fi (mta-out1.inet.fi [62.71.2.195]) by ietfa.amsl.com (Postfix) with ESMTP id 638C51A0387 for <homenet@ietf.org>; Fri,  5 Dec 2014 05:48:13 -0800 (PST)
Received: from poro.lan (80.220.64.126) by jenni2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 546BDD5301E73FC0; Fri, 5 Dec 2014 15:48:07 +0200
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <D0A71FC4.A234%acee@cisco.com>
Date: Fri, 5 Dec 2014 15:48:07 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <62D88D1B-407A-4A20-A4AA-F4AA93779449@iki.fi>
References: <87sihiy8rr.wl-jch@pps.univ-paris-diderot.fr> <87ppcd60tb.wl-jch@pps.univ-paris-diderot.fr> <9C3268A6-020A-46F8-8200-F1E6D4D24C3B@iki.fi> <D0A71FC4.A234%acee@cisco.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/PG9cI__m00NozY5hWOA4h3j__pE
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Stub-only implementation of Babel
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Dec 2014 13:48:15 -0000

On 5.12.2014, at 15.41, Acee Lindem (acee) <acee@cisco.com> wrote:
> Who contributed the ISIS implementation in Erlang? I must admit I =
haven=B9t
> followed it closely but I thought all the quagga work was C or C++?

It is the most recent IS-IS for Quagga, not part of the mainline (not =
sure if there are plans for it either).

The built-in IS-IS in Quagga is not zeroconf, nor does it do source =
specific routing, so it is not an option. I am aware of two additional =
source-specific things on top of Quagga, one of them being that =
AutoISIS. (The other one was some prototype using Klick IIRC).

Of course, to be fair, we could probably include the built-in Quagga =
IS-IS footprint metric at some point too, but I think =91order of =
magnitude=92 more=92 is still the result.

(That said, link-state protocol implementation _does not_ have to be =
big, c.f. Bird=92s OSPF/OSPFv3 which is just ~thrice size of Babel.)

Cheers,

-Markus=


From nobody Fri Dec  5 06:17:20 2014
Return-Path: <jonathan@hansfords.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CA481A1A33 for <homenet@ietfa.amsl.com>; Fri,  5 Dec 2014 06:17:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 4TSaFlXFzd9c for <homenet@ietfa.amsl.com>; Fri,  5 Dec 2014 06:17:17 -0800 (PST)
Received: from avasout04.plus.net (avasout04.plus.net [212.159.14.19]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B78F01A1A29 for <homenet@ietf.org>; Fri,  5 Dec 2014 06:17:16 -0800 (PST)
Received: from Vanguard ([84.92.149.4]) by avasout04 with smtp id PqHC1p00105w0Nk01qHDok; Fri, 05 Dec 2014 14:17:14 +0000
X-CM-Score: 0.00
X-CNFS-Analysis: v=2.1 cv=ZuVjKrLG c=1 sm=1 tr=0 a=ay7+waBXjX2gYBYtdgtTjg==:117 a=ay7+waBXjX2gYBYtdgtTjg==:17 a=0Bzu9jTXAAAA:8 a=IkcTkHD0fZMA:10 a=6bkCdLdQAAAA:8 a=48vgC7mUAAAA:8 a=moVDaa8a8SCaulm3B08A:9 a=QEXdDO2ut3YA:10
From: "Jonathan Hansford" <jonathan@hansfords.net>
To: "'Markus Stenberg'" <markus.stenberg@iki.fi>
References: <019001d00f13$320db9e0$96292da0$@hansfords.net> <8BF97502-E33B-4AFA-81D2-D5F0C6A6E491@iki.fi>
In-Reply-To: <8BF97502-E33B-4AFA-81D2-D5F0C6A6E491@iki.fi>
Date: Fri, 5 Dec 2014 14:17:22 -0000
Message-ID: <00dd01d01096$30c7be80$92573b80$@hansfords.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQJUoDCFKDxI+/d8Y/Dp6un6JQWJzQHJXTfTm2mZ8BA=
Content-Language: en-gb
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/bA8BYtEeUILcDamKxs4HFRPle74
Cc: homenet@ietf.org
Subject: Re: [homenet] Comments on draft-ietf-homenet-hncp-02
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Dec 2014 14:17:19 -0000

> -----Original Message-----
> From: Markus Stenberg [mailto:markus.stenberg@iki.fi]
> Sent: 05 December 2014 13:44
> To: Jonathan Hansford
> Cc: Markus Stenberg; homenet@ietf.org
> Subject: Re: [homenet] Comments on draft-ietf-homenet-hncp-02
>=20
> > On 3.12.2014, at 18.07, Jonathan Hansford <jonathan@hansfords.net>
> wrote:
> > I=E2=80=99ve just come to the homenet WG and have some questions and
> comments for draft-ietf-homenet-hncp-02:
>=20
> Heya, and thanks for the review ;)
>=20
> > 1.       I notice from the homenet charter the work is based on =
IPv6. Is there
> anything in the HNCP protocol that precludes its use for IPv4? I am =
looking for
> a similar capability for use within multiple IPv4 broadcast domains =
with no
> IPv6 in the mix at all.
>=20
> Do you need PA, SD, or just share some arbitrary TLVs? If last, you =
could use
> some existing routing link-state protocol, or possibly <unnamed thing =
we are
> generalizing out of HNCP>.

I'm currently exploring using Zeroconf capabilities to establish a =
single broadcast domain from scratch within an "IP island" (i.e. =
initially isolated from any larger internet). However, I know there will =
be occasions when there will be multiple broadcast domains within the =
island and will therefore need to be able to move from link-local to =
private addresses so they can be routed between the domains. Also need =
to perform service discovery. The one anomaly is that I need to do this =
prior to receiving any information from "the outside world" (e.g. =
allocated prefixes), hence the use of private addresses. The network =
needs to "discover" itself whilst it is  an island, providing full =
service capability within that island prior to being connected to the =
internet.

>=20
> > 2.       What is a node? I presume it is a router.
>=20
> Router/node is awfully mixed in hncp-02.. Router is a node, but not =
all nodes
> are routers..
>=20
> Thanks also for corrections - I will incorporate them in the next =
version if they
> are still applicable (it seems the next iteration will be drastic, =
given what we
> have now in github (public development and all) but more on that later
> perhaps).
>=20
> (Terms =E2=80=98link=E2=80=99, =E2=80=98router=E2=80=99, =
=E2=80=99node=E2=80=99 were horribly abused in the hncp-02. Sorry.)
>=20
> > 3.       Section 1, 3rd paragraph: s/information how/information on =
how
> >
> > 4.       Section 3, set of TLV data: s/The set of TLVs have/The set =
of TLVs has
> >
> > 5.       Section 4.2
> >
> > a.       1st paragraph: s/as purely as/purely as
> >
> > b.      =E2=80=9CTLVs MUST or MAY be present=E2=80=9D =E2=80=93 is =
that a decision that can be made
> per node, per link or across the implementation?
>=20
> Good point, have to specify that (if this thing even exists). MUST be =
ones
> obviously are always required, and MAY ones are local choice. (I think =
we got
> rid of the MAY ones in the next iteration though, but I have to double =
check
> to make sure.)
>=20
> Cheers,
>=20
> -Markus


From nobody Wed Dec 10 10:45:36 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74C1A1A6F6F for <homenet@ietfa.amsl.com>; Wed, 10 Dec 2014 10:45:26 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 dLQysdLayzgw for <homenet@ietfa.amsl.com>; Wed, 10 Dec 2014 10:45:23 -0800 (PST)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA07B1A8A7A for <homenet@ietf.org>; Wed, 10 Dec 2014 10:44:00 -0800 (PST)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id sBAIhxaL024575 for <homenet@ietf.org>; Wed, 10 Dec 2014 18:43:59 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id sBAIhtFP024548 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO) for <homenet@ietf.org>; Wed, 10 Dec 2014 18:43:58 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <homenet@ietf.org>
References: <20141210182425.6387.29651.idtracker@ietfa.amsl.com>
In-Reply-To: <20141210182425.6387.29651.idtracker@ietfa.amsl.com>
Date: Wed, 10 Dec 2014 18:43:50 -0000
Message-ID: <010001d014a9$3f3830a0$bda891e0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGDspU+bH+68Bq5vmYqQRhEa360FJ0h7M2w
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-21166.001
X-TM-AS-Result: No--14.229-10.0-31-10
X-imss-scan-details: No--14.229-10.0-31-10
X-TMASE-MatchedRID: rXre1YwqJKL8E3ZqfFM6yjYTypjB3iDVuikHZcC6ceATVJPv0YKEKYtz mcNeATrLBavLVX8ZAjv3oP6UbDK0VdcUNjoF7YuVz4XVyhFFZHL6S5pTqlNeArV5fSMRD1zqX08 DX2bsZl5fgMIbirCKtUhxaJhuh0LPxw1EqT0VUfmCe7wQT5ayJToSfZud5+GgHMKI0y89bBLlnb BfOj9S74kcTkkZ+AATdMPtYLLwFHvB9SBfeVAw3O9VsdrlGzy3H181YDtIVark6rOQTf/DNm19g M1gDJGc4vM1YF6AJbZcLc3sLtjOt1ZFWWuOwo7w3QfwsVk0UbtuRXh7bFKB7vY4AkZnpboXUevm y3e1XlS/XCOTadrTrMEsOIPFjMc7XwjihSrlWBo=
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/p3ARSZKeHRTi7bhaeWTEq8WfjUM
Subject: [homenet] FW: Last Call: <draft-ietf-roll-admin-local-policy-02.txt> (MPL forwarder policy for multicast with admin-local scope) to Informational RFC
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 18:45:26 -0000

Hi,

The Homenet WG may be interested in this document that has just entered IETF
last call.

Adrian

> -----Original Message-----
> From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The
> IESG
> Sent: 10 December 2014 18:24
> To: IETF-Announce
> Cc: roll@ietf.org
> Subject: Last Call: <draft-ietf-roll-admin-local-policy-02.txt> (MPL forwarder
> policy for multicast with admin-local scope) to Informational RFC
> 
> 
> The IESG has received a request from the Routing Over Low power and Lossy
> networks WG (roll) to consider the following document:
> - 'MPL forwarder policy for multicast with admin-local scope'
>   <draft-ietf-roll-admin-local-policy-02.txt> as Informational RFC
> 
> 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 2014-12-24. 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
> 
>    The purpose of this document is to specify an automated policy for
>    the routing of MPL multicast messages with admin-local scope in a
>    border router.
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-roll-admin-local-policy/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-roll-admin-local-policy/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.


From nobody Wed Dec 17 06:16:24 2014
Return-Path: <dave.taht@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCAB21A1AFE for <homenet@ietfa.amsl.com>; Wed, 17 Dec 2014 06:16:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.7
X-Spam-Level: 
X-Spam-Status: No, score=0.7 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, 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 HB26UyuFXuas for <homenet@ietfa.amsl.com>; Wed, 17 Dec 2014 06:16:18 -0800 (PST)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D44541A1AA4 for <homenet@ietf.org>; Wed, 17 Dec 2014 06:16:17 -0800 (PST)
Received: by mail-ob0-f182.google.com with SMTP id wo20so3826364obc.13 for <homenet@ietf.org>; Wed, 17 Dec 2014 06:16:17 -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:cc:content-type :content-transfer-encoding; bh=nZxfEPgQxniBbZVmuOEyMlZOwVh7mLspPw5TDSH0Pl4=; b=nfldsgQJcwdZTOm2ERP1PQftkyolbBz3YZdRBrnIwxK8eefGiFAtGYqlcHeoUbrUcv U3UjN/R7qxj/TI+CC3WqCYgU3ynRWPqH+J+wRBvHRzzC2j8JXx68dzSt7irbZqQUdk0w ekiptk8MltxB3+roA4RJa7FDlAVPeeIRNpOqemG9mHz6GtBuuck5XG/mrFLYTuSedGHS BYzw4NRb/nIHLuym8rja1NBjo2a0Yy7TXP2R7hKG6GtU0GuJ3LQZcIIeI2lzeWsJGkO1 8xfYpzAoERyTaNmyu0WxPlNIP585TZ4hUaaNEKCT0+A6Ys/bph1mHA4wwGAHzU2hUO26 T3aA==
MIME-Version: 1.0
X-Received: by 10.182.245.130 with SMTP id xo2mr26351146obc.16.1418825777046;  Wed, 17 Dec 2014 06:16:17 -0800 (PST)
Received: by 10.202.227.77 with HTTP; Wed, 17 Dec 2014 06:16:16 -0800 (PST)
Date: Wed, 17 Dec 2014 06:16:16 -0800
Message-ID: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: HOMENET <homenet@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/IbsVORd_NcvrP55lxVx6vC4ecs8
Cc: dnsmasq-discuss <dnsmasq-discuss@lists.thekelleys.org.uk>, "babel-users@lists.alioth.debian.org" <babel-users@lists.alioth.debian.org>
Subject: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Dec 2014 14:16:21 -0000

I have been wrestling with prefix coloring, where choosing a "best"
prefix would be of use in (for example) reducing the problems induced
by happy eyeballs when more than one ipv6 prefix is present and
several other scenarios.

There are many parts to this - one is in addressing, the other in DNS,
and this is not dnsmasq specific but kind of general.

* gai.conf

Does anyone have a "better" gai.conf file or getaddrinfo implemention
"out there?

This is the closest I've found to what I sort of think I want.

http://biplane.com.au/blog/?p=3D122

* hints for addressing?

I will start with the complex scenario - I have three primary
connections to the internet (one is hardline, one is 5 hops away on a
source specific gateway to elsewhere, the last LTE), with slaac, dhcp,
and privacy addresses assigned for each, a ula for internal addressing
(with possibly slaac, dhcp, and privacy addresses), and a vpn (also on
a ula). What the heck, let's throw in a hip address, also. And... why
not? A legacy ipv6 tunnel from hurricane, a 2002:address for 6to4....

The ideal scenario is where the host app picks the "best" address for
each connection type, and I am a little vague on what actually
happens. What my backbrain (but not RFC 3484 - is there a later rfc
for what gai.conf should do?) says should happen is that the host
should pick the shortest prefix match between source and destination.
Well, it turns out this breaks down - my tunnel is a 2001::address,
and my native ipv6 connection is a 2600::address, and my destination
(being on the "legacy" internet), is a 2001::address, so things tend
to pick the tunnel rather than the native address. A differentiation
between these is that I have a different MTU for each. Another is how
these addresses are acquired - the main address comes from dhcpv6,
tunnel from a he speciifc script, the source specific gateway comes
from hnet, the lte address is pppoe....

And worse, the "best" address is dynamic and changes every week, and
on reboots, (this just happened to me and I went nuts flushing old
ipv6 addrs everywhere, since I lack hnetd) and caching it or using it
internally is a bad idea when a static ULA or more static tunnel addr
is available,

The LTE connection costs money to use, and is definately "secondary"
in intent, and I can see supplying that via ra as secondary. I can
also see treating almost all the others as "secondary" also, but it
probably would be nice to have the nearly equal cost hnetd supplied
prefix have a chance at being used occasionally.

and, sigh, the ip route command has no ability currently to set
secondary on an address.

* In terms of DNS

spitting all these into a single DNS record strikes me as insane.
However, having more than one visible address per dns entry strikes me
as desirable. Certainly a dhcp supplied address should end up in dns,
and dnsmasq also has a mechanism to put slaac assigned address into
dns.

putting the ULA in the local dns is actually desirable when you have split =
dns.

Perhaps having a subdomain per address type? dave.lte.home.lan
dave.slaac.home.lan dave.dhcp.home.lan?

I am not offering any solutions here, just sharing a headache. There
are some other basic problems like setting a default src address on a
default route in this scenario that are giving me headaches in the
source specific universe...

* In terms of being a host and selecting the

for example, I think linux presently choses the last assigned static
address as it's default source, and that can be overridden with stuff
like:

ip -6 route add default via 2001:db8::1 dev ethic src 2001:db8::abcd

but it is not done today, and is not always the correct thing. I add a
vpn address last in my case.

What I see happening now is distributing source specific routes to
hosts doesn't work, if you merely have

default from 2001:558:6045:bd:8dcc:5e18:dd54:b31c via
fe80::6eb0:ceff:fe0b:e2ab dev eth0  proto babel  metric 1024
default from 2601:9:3640::/60 via fe80::6eb0:ceff:fe0b:e2ab dev eth0
proto babel  metric 1024

and no broader default, the right thing doesn't happen for source
address selection on the host. You end up with no ipv6 connectivity at
all until you add something like this

default via fe80::6eb0:ceff:fe0b:e2ab dev eth0  metric 1024

or this

default from :: via fe80::4a1:51ff:fea3:1304 dev eth0.2  proto babel
metric 1024 (different machine)

to get something that works.


On Mon, Dec 1, 2014 at 2:17 PM, Simon Kelley <simon@thekelleys.org.uk> wrot=
e:
> On 01/12/14 18:49, Michael Gorbach wrote:
>> On Nov 30, 2014, at 11:17 AM, Simon Kelley <simon@thekelleys.org.uk>
>> wrote:
>>>
>>> On 29/11/14 19:18, Michael Gorbach wrote:
>>>> Hi All,
>>>>
>>>> I've got a question and potential enhancement request. It looks
>>>> like right now, the (very useful) interface-name feature pulls
>>>> all (global) addresses from the interface. One of my machines
>>>> uses IPv6 privacy extensions (known in Linux as use_tempaddr),
>>>> which means that in addition to link-local and permanent global
>>>> addresses, it has a rotating cast of ~ 5 temporary addresses. I
>>>> suggest that dnsmasq should detect those temporary addresses and
>>>> not return them for queries that would otherwise hit
>>>> interface-name. Returning them as it does now means > 5 AAAA
>>>> records for a single name, which causes repeated confusion due to
>>>> things like SSH warning about an unknown host because it has
>>>> suddenly picked a previously-unknown temporary address to connect
>>>> to. Thoughts?
>>>>
>>>
>>> Sounds like a sensible suggestion. This facility was added before I
>>> was really familiar with IPv6 and all its extra complications. Most
>>> of those 5 temporary addresses will be "deprecated" ie hanging
>>> around for the use of existing connections, but not used for new
>>> ones. They definitely shouldn't appear, but I'm pretty convinced,
>>> unless anyone can come up with a good reason why not, that all
>>> privacy addresses should be elided, without exception.
>>>
>>> I wonder, though, if that's only true for forward (ie AAAA)
>>> lookups. Should a reverse lookup on an old privacy address still
>>> yield the name of the host it belongs to?
>>
>> Thanks, Simon. I=E2=80=99d agree that all the temporary addresses should=
 be
>> skipped in forward resolution. In terms of reverse, I=E2=80=99d say ther=
e=E2=80=99s a
>> high amount of value in having at least the current temporary address
>> resolve to the correct host name. Temporary addresses are often
>> preferred for outbound connections, so if we don=E2=80=99t have reverse
>> resolution here then for example SSH is going to complain that it
>> can=E2=80=99t check reverse DNS. There=E2=80=99s probably some value in =
reverse
>> resolution for deprecated temporary addresses, for example if you
>> wanted to track down some client in your system logs from several
>> days ago, but it=E2=80=99s significantly lower. If that=E2=80=99s a larg=
e amount of
>> work, to me it=E2=80=99s something that wouldn=E2=80=99t be top-priority=
.
>
> Since all the addresses - permanent, current privacy, and deprecated
> privacy - are there now, it's just a question of filtering them, with a
> bit of extra complication to do it differently for forward and reverse
> queries. I think I've convinced myself that this won't bite anyone if we
> make it a simple change-of-behaviour, rather than some new configuration
> option to request this behaviour. I'd feel more confident if others had
> a think about it and convinced themselves too.
>
>
> Cheers,
>
> Simon.
>
>>
>> Yours, ~ M.
>>
>>>
>>>
>>>
>>> Cheers,
>>>
>>> Simon.
>>>
>>>
>>> _______________________________________________ Dnsmasq-discuss
>>> mailing list Dnsmasq-discuss@lists.thekelleys.org.uk
>>> <mailto:Dnsmasq-discuss@lists.thekelleys.org.uk>
>>> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
>>> <http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss>
>
>
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss@lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Thu Dec 18 07:08:41 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88C851A8A7F for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 07:08:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, T_TVD_MIME_NO_HEADERS=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 VEiQn6vCn1NN for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 07:08:35 -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 7C93F1A897C for <homenet@ietf.org>; Thu, 18 Dec 2014 07:08:01 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id D58F320012; Thu, 18 Dec 2014 10:12:12 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 0AB2E63745; Thu, 18 Dec 2014 10:07:59 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id EB1BA63743; Thu, 18 Dec 2014 10:07:59 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Dave Taht <dave.taht@gmail.com>
In-Reply-To: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.1
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, 18 Dec 2014 10:07:59 -0500
Message-ID: <24024.1418915279@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/0YQSIg0ggKohSGNYkdOE66cdPw0
Cc: dnsmasq-discuss <dnsmasq-discuss@lists.thekelleys.org.uk>, HOMENET <homenet@ietf.org>, "babel-users@lists.alioth.debian.org" <babel-users@lists.alioth.debian.org>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Dec 2014 15:08:37 -0000

--=-=-=


Dave,
my take is that applications, and the entire gai.conf/getaddrinfo() library
is broken.  Applications can neither be updated nor be trusted to know enough
about the system to be able to make a proper decision.

Somewhere, someone was working on a new connect(2) call that took FQDNs
rather than sockaddr's, such that the kernel could take ownership of this
problem. (Of course, actually solving the problem in a kernel is probably the
wrong answer).
What is necessary is some new infrastructure inside the box which becomes
standardized (like sockets API was), with some daemon that thinks about the
best source addresses is, and possibly gets involved with routing protocols.
(I'm told that OSX has a sophisticated state machine that combines DHCP and
1x, and wifi... it sounds like it could be the start of such a thing)

I think that shim6 and mptcp are answers in this equation.

shim6 has, I'm told, deployment issues which make me very very sad.
mptcp, I'm told, is likely to show up in Apple and Google products and
infrastructure, and my idea (and many others) is that you don't always have
to pick the perfect address for the SYN, just one that works, but rather one
can add better addresses as one discovers them.

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




--=-=-=
Content-Type: application/pgp-signature

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

iQEVAwUBVJLtz4CLcPvd0N1lAQJ56AgAwVuxsA8RCXCsoZ5SCOcBhOvXVPi0cgKV
5eFjp0joil+uRCqyE/Ma0OogouCrGL2Y0VQ3fW9irSt4sYFf2TXBIv6m5v0RthS9
/AjV/F8jrB32W79co2Er6xGBrOhEemsMyndZ9G5rdDwOrt3yOnPp1tkqq50wtHCo
5qXjfVxYpMKp5EwiOi5JGO+7iDVR7fQGK8pwmO3Za9nzywOitUiBRrGvs8GDdIoA
SgRDurfzh2kkz6k256qCRycDEx3FkVqhzGz9g9+VK895AkIuOV8t5hy7x9r/18m1
tOGlsoJRETVP2w5lG6inaOVdKS0ohZfJS0fKlKFdByBJvn6yhPbyrA==
=S4zR
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Dec 18 14:07:08 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D328C1A908F for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 14:06:57 -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 III7gUrHoc6J for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 14:06:46 -0800 (PST)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03EB01A8712 for <homenet@ietf.org>; Thu, 18 Dec 2014 14:06:41 -0800 (PST)
Received: by mail-pd0-f170.google.com with SMTP id v10so2266414pde.1 for <homenet@ietf.org>; Thu, 18 Dec 2014 14:06:40 -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=zBxBslsSq+eBRxx22k2pU4/Yu4ghEEHPBhTJxxkFHoc=; b=hVNptvpGRYRfzf6kfPXwgGH469DxiIiyGrkaAEe4KY4ZwurN47zGTbRyXXRouoPzcZ +Jp77Pp+X3LhlNXTG8P0QlfBv6wgZg2u0hy4un2smchorip1kbnDt73a5Taw4QjsbPzs PK8LRHG5p7T/1VO3uLufNoC1acn1SbNMuAFvtxlWO0RT5+kpQu1pgA5E+43hatHk+VNl 3Z1ur3/ZPs1iMAYMCf9NEVlF0iM8Z9rj3t9NlZacI5/CFsccctknSFijvzt6smmJZGAC P/2ULz+W1sZAWOGSiSio6mNthi0/TVCw5lhJVlO62phJrVHRZO94Jg0FnMvbTqgFesrx B1Vg==
X-Received: by 10.68.57.144 with SMTP id i16mr7191739pbq.86.1418940399364; Thu, 18 Dec 2014 14:06:39 -0800 (PST)
Received: from ?IPv6:2406:e007:74cb:1:28cc:dc4c:9703:6781? ([2406:e007:74cb:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id eo4sm7596953pbb.87.2014.12.18.14.06.35 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 18 Dec 2014 14:06:38 -0800 (PST)
Message-ID: <54934FF5.2050108@gmail.com>
Date: Fri, 19 Dec 2014 11:06:45 +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:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca>
In-Reply-To: <24024.1418915279@sandelman.ca>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/uH-omBG19kfhSTPOrTQtWXYacmQ
Cc: dnsmasq-discuss <dnsmasq-discuss@lists.thekelleys.org.uk>, HOMENET <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>, "babel-users@lists.alioth.debian.org" <babel-users@lists.alioth.debian.org>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Dec 2014 22:06:58 -0000

On 19/12/2014 04:07, Michael Richardson wrote:
> 
> Dave,
> my take is that applications, and the entire gai.conf/getaddrinfo() library
> is broken.  Applications can neither be updated nor be trusted to know enough
> about the system to be able to make a proper decision.
> 
> Somewhere, someone was working on a new connect(2) call that took FQDNs
> rather than sockaddr's, such that the kernel could take ownership of this
> problem. 

I suppose you are thinking of Name Based Sockets:
http://tools.ietf.org/html/draft-ubillos-name-based-sockets

It's dead, as far as I know.

> (Of course, actually solving the problem in a kernel is probably the
> wrong answer).
> What is necessary is some new infrastructure inside the box which becomes
> standardized (like sockets API was), with some daemon that thinks about the
> best source addresses is, and possibly gets involved with routing protocols.
> (I'm told that OSX has a sophisticated state machine that combines DHCP and
> 1x, and wifi... it sounds like it could be the start of such a thing)
> 
> I think that shim6 and mptcp are answers in this equation.
> 
> shim6 has, I'm told, deployment issues which make me very very sad.

Like, it cannot get through most firewalls.

> mptcp, I'm told, is likely to show up in Apple and Google products and
> infrastructure, and my idea (and many others) is that you don't always have
> to pick the perfect address for the SYN, just one that works, but rather one
> can add better addresses as one discovers them.

But bad luck if you need UDP.

Some form of intelligent probing does seem to be the answer,
but certainly that needs to be generic because we cannot expect
all apps developers to reinvent it. That's one reason we wrote
http://tools.ietf.org/html/draft-naderi-ipv6-probing recently.

   Brian


From nobody Thu Dec 18 14:23:01 2014
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 412BB1A90A5 for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 14:23:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] 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 4Yr7L5yhzXMO for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 14:22:58 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 1592D1A90A4 for <homenet@ietf.org>; Thu, 18 Dec 2014 14:22:57 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/46573) with ESMTP id sBIMMtYf000345; Thu, 18 Dec 2014 23:22:55 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 771EC1A85B; Thu, 18 Dec 2014 23:22:55 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id bxFlk7jycvpd; Thu, 18 Dec 2014 23:22:53 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 8D2A91A85A; Thu, 18 Dec 2014 23:22:52 +0100 (CET)
Date: Thu, 18 Dec 2014 23:22:55 +0100
Message-ID: <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <54934FF5.2050108@gmail.com>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Thu, 18 Dec 2014 23:22:55 +0100 (CET)
X-Miltered: at korolev with ID 549353BF.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 549353BF.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 549353BF.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/KFXkHlWVHlq2Ero1Cgn8Av9yo2U
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Dave Taht <dave.taht@gmail.com>, boutier@pps.univ-paris-diderot.fr, "babel-users@lists.alioth.debian.org" <babel-users@lists.alioth.debian.org>, HOMENET <homenet@ietf.org>, dnsmasq-discuss <dnsmasq-discuss@thekelleys.org.uk>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Dec 2014 22:23:00 -0000

Shouldn't we reduce the amount of cross-posting at some point?

>> mptcp, I'm told, is likely to show up in Apple and Google products and
>> infrastructure, and my idea (and many others) is that you don't always have
>> to pick the perfect address for the SYN, just one that works, but rather one
>> can add better addresses as one discovers them.

> But bad luck if you need UDP.

> Some form of intelligent probing does seem to be the answer,

I'd like to attract your attention to the work that Matthieu Boutier has
been doing on mosh, Keith Winstein's UDP-based ssh replacement:

  http://comments.gmane.org/gmane.network.mosh.devel/749

Boutier's version of mosh builds connections across all source/destination
pairs, and picks the one with lowest RTT.  It's a work in progress --
there are multiple versions, and Matthieu has yet to decide which
implementation he's going to submit for inclusion in mainline mosh.

We hope to write that stuff down when Matthieu has decided which is the
"right" version, but I'm not promising any hard deadlines -- we have a lot
of stuff that we want to write down.

> but certainly that needs to be generic because we cannot expect
> all apps developers to reinvent it.

Uh-huh.  But there's only one thing that's worse than generalising from
one example -- it's generalising from zero eexamples.

> http://tools.ietf.org/html/draft-naderi-ipv6-probing recently.

I'll have a look, thanks for the pointer.

-- Juliusz


From nobody Thu Dec 18 14:46:51 2014
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A3501A87BC for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 14:46:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_FR=0.35] 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 AljpoXIypBOc for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 14:46:48 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 EE4661A87BB for <homenet@ietf.org>; Thu, 18 Dec 2014 14:46:47 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/46573) with ESMTP id sBIMkjC6005192; Thu, 18 Dec 2014 23:46:45 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id BAE951A860; Thu, 18 Dec 2014 23:46:45 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id hoVpXo0eL4dx; Thu, 18 Dec 2014 23:46:44 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 520971A85A; Thu, 18 Dec 2014 23:46:44 +0100 (CET)
Date: Thu, 18 Dec 2014 23:46:47 +0100
Message-ID: <87tx0spodk.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Dave Taht <dave.taht@gmail.com>
In-Reply-To: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Thu, 18 Dec 2014 23:46:45 +0100 (CET)
X-Miltered: at korolev with ID 54935955.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54935955.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54935955.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/lZ4X6RjE-3Z8OFP7943xtuDzGks
Cc: HOMENET <homenet@ietf.org>, "babel-users@lists.alioth.debian.org" <babel-users@lists.alioth.debian.org>, dnsmasq-discuss <dnsmasq-discuss@thekelleys.org.uk>
Subject: Re: [homenet] [Babel-users] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Dec 2014 22:46:49 -0000

> The ideal scenario is where the host app picks the "best" address for
> each connection type, and I am a little vague on what actually
> happens. What my backbrain (but not RFC 3484 - is there a later rfc
> for what gai.conf should do?)

With ordinary next-hop routing, routing policy is entirely in the
routers -- the end hosts have no control whatsoever on the path taken.
The opposite of source routing, where the hosts have the ultimate control
on routing policy, and the routers merely provide a mechanism [1].

Now source-specific routing is an interesting compromise between the two:
it splits policy decisions between the routers (who distribute a set of
source-specific routes) and the hosts (who pick among one of the available
routes by specifying a given source address).  But even though the amount
of policy control given to hosts is fairly modest, it still requires that
some routing intelligence be implemented within the hosts -- and, as you
justly note, the available mechanisms are insufficient.

I think we're pretty much done with the routing part -- I'm fairly
confident now that we've got a reasonable understanding of source-specific
routing in edge networks [2,3].  On the other hand, we haven't done any
serious work on the host side of things -- if anyone understands how to
distribute source address selection policies in a way that is both fully
automated and flexible enough, they're not saying.  (And I'm pretty sure
that DNS is the wrong place to do that.)

[1] J. Saltzer, D. Reed, D. Clark.  Source-routing for Campus-wide
    Internet Transport.  1980.
    http://groups.csail.mit.edu/ana/Publications/PubPDFs/SourceRouting.html
[2] M. Boutier, J. Chroboczek.  Source-specific routing.  2014.
    https://hal.archives-ouvertes.fr/hal-00947234v3
    (Yes, it's a new version.)
[3] As opposed to core networks, where there's the ugly issue of routing
    table explosion -- please give Matthieu a core network to break)

-- Juliusz


From nobody Thu Dec 18 16:09:52 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA3231AC3A7 for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 16:09:49 -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 7qqVkJ4ua0CU for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 16:09:48 -0800 (PST)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e: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 D77951A9173 for <homenet@ietf.org>; Thu, 18 Dec 2014 16:09:47 -0800 (PST)
Received: by mail-pa0-f50.google.com with SMTP id bj1so2446401pad.9 for <homenet@ietf.org>; Thu, 18 Dec 2014 16:09:47 -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=p0ctGALMuMpPONCA0I2C/5KhJhFgQClWkO9p1y7Z6DY=; b=lzI/fB+UIJT+++3K/jXc8gDTJa1KD8RwCvQb482nu99NtfI3hqgQW3pkImsErv4NER uwyb5q3ebxtdsh13cR7rMKNdqV4miGj0N83EOszro6/IeynJlMKS0bfWxRWEypr4YYjL sf0v7YVAssSBrkykM2K5P9pVRQlWzVqbahmylCSKoVMXURv4wWx7PDs5PtZjZ61HsDw9 aBGTPLygTVuikAEoc8zV6vzeADnAjeSNPl3c0YLBvgAyT9dTWTn9mCtzYN52qHdCoUGA rgppQsX4YQ6in1r8JcMEpHJr27UlEAT8yaXuReo8TkU+6iSBIX5lsh3Z9ejVBiQnlCLE elkQ==
X-Received: by 10.70.131.78 with SMTP id ok14mr7836148pdb.112.1418947787118; Thu, 18 Dec 2014 16:09:47 -0800 (PST)
Received: from ?IPv6:2406:e007:74cb:1:28cc:dc4c:9703:6781? ([2406:e007:74cb:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id vf6sm7751403pbc.73.2014.12.18.16.09.44 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 18 Dec 2014 16:09:46 -0800 (PST)
Message-ID: <54936CD3.7040004@gmail.com>
Date: Fri, 19 Dec 2014 13:09:55 +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:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Dave Taht <dave.taht@gmail.com>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com>
In-Reply-To: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/3CCRorjk_rx6lJqx5uH9X9xGwwE
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 00:09:49 -0000

On 18/12/2014 03:16, Dave Taht wrote:

...
> The ideal scenario is where the host app picks the "best" address for
> each connection type, and I am a little vague on what actually
> happens. What my backbrain (but not RFC 3484 - is there a later rfc
> for what gai.conf should do?) 

Not sure if anyone else has responded to that:

Yes, it was obsoleted by RFC6724. It probably won't change anything
material for this thread, but it's very important for other reasons.

btw I strongly recommend the pages like this one:
http://www.rfc-editor.org/info/rfc3484
if you want to get Obsoleted by/Updated by/Errata information
for any RFC.

   Brian


From nobody Thu Dec 18 16:19:48 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3D9E1AC431 for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 16:19:47 -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 fxV_U6QX4tGA for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 16:19:46 -0800 (PST)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C81001AC43A for <homenet@ietf.org>; Thu, 18 Dec 2014 16:19:45 -0800 (PST)
Received: by mail-pd0-f175.google.com with SMTP id g10so8598pdj.6 for <homenet@ietf.org>; Thu, 18 Dec 2014 16:19:45 -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=1E6Zi+1DSIqUQS+e06ODf9Z/TnHtL1vmKOwL4SfrVAM=; b=deLSGgr/pLJX/E9bQuUIGFniP2OY/8CUdDR8wm4lWsISNhorrk6NICaLHrFGt/nD9R WWuA0T5e7FmD5jDOmjG8iY4BFxAphpKew6WS7L4DycQueqcchFO5nECHpD4Ibt56ibrA Agl+1J4qIBnd7j82C+4VLBEcw2lnnB+zMOeoptnaYvKMkxLWh7yWU9Ga8bXzgyGvwfNH GQfsxlaKtVKLdxIkJN35goakDlSNxjcIGZHh/KUccChXwOhK3+Dq3f9pNfFpLLCw4Pjm bqTxoHHLi+hUkr+Bo/dUhk0mRssCqa6OagILwdq/F6u5vx6QJ3XUnkW3fZm4j3gE6/Ej TcUA==
X-Received: by 10.66.140.76 with SMTP id re12mr7504552pab.147.1418948385109; Thu, 18 Dec 2014 16:19:45 -0800 (PST)
Received: from ?IPv6:2406:e007:74cb:1:28cc:dc4c:9703:6781? ([2406:e007:74cb:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id z5sm7737292pbt.89.2014.12.18.16.19.41 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 18 Dec 2014 16:19:44 -0800 (PST)
Message-ID: <54936F28.9070201@gmail.com>
Date: Fri, 19 Dec 2014 13:19: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:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/kUx76AidQ_o2h1bQfbGptw_XfXI
Cc: boutier@pps.univ-paris-diderot.fr, Michael Richardson <mcr+ietf@sandelman.ca>, HOMENET <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 00:19:48 -0000

On 19/12/2014 11:22, Juliusz Chroboczek wrote:
> Shouldn't we reduce the amount of cross-posting at some point?
>=20
>>> mptcp, I'm told, is likely to show up in Apple and Google products an=
d
>>> infrastructure, and my idea (and many others) is that you don't alway=
s have
>>> to pick the perfect address for the SYN, just one that works, but rat=
her one
>>> can add better addresses as one discovers them.
>=20
>> But bad luck if you need UDP.
>=20
>> Some form of intelligent probing does seem to be the answer,
>=20
> I'd like to attract your attention to the work that Matthieu Boutier ha=
s
> been doing on mosh, Keith Winstein's UDP-based ssh replacement:
>=20
>   http://comments.gmane.org/gmane.network.mosh.devel/749
>=20
> Boutier's version of mosh builds connections across all source/destinat=
ion
> pairs, and picks the one with lowest RTT. =20

Sounds interesting. In the ideal world, that would be a pluggable
policy algorithm. Lowest RTT may not always be the best choice.
NAROS* suggested distributing policy from a single source, for
example.

The point about shim6, of course, is that allows you to change
horses in midstream without bothering the transport layer.
It's a real shame we don't know how to deploy it, especially
for homenets where nobody manages the routing policy.

   Brian

* C. Launois, O. Bonaventure, and M. Lobelle. The NAROS approach for IPv6=

multihoming with traffic engineering. volume 2811 of Lecture Notes in
Computer
Science, pages 112=E2=80=93121. Springer Berlin Heidelberg, 2003.

> It's a work in progress --
> there are multiple versions, and Matthieu has yet to decide which
> implementation he's going to submit for inclusion in mainline mosh.
>=20
> We hope to write that stuff down when Matthieu has decided which is the=

> "right" version, but I'm not promising any hard deadlines -- we have a =
lot
> of stuff that we want to write down.
>=20
>> but certainly that needs to be generic because we cannot expect
>> all apps developers to reinvent it.
>=20
> Uh-huh.  But there's only one thing that's worse than generalising from=

> one example -- it's generalising from zero eexamples.
>=20
>> http://tools.ietf.org/html/draft-naderi-ipv6-probing recently.
>=20
> I'll have a look, thanks for the pointer.
>=20
> -- Juliusz
>=20


From nobody Thu Dec 18 16:39:10 2014
Return-Path: <gettysjim@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D9C91AC431 for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 16:39:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 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, HTML_MESSAGE=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 JF6Y4zS5QHUg for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 16:39:04 -0800 (PST)
Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6090A1A000B for <homenet@ietf.org>; Thu, 18 Dec 2014 16:39:04 -0800 (PST)
Received: by mail-ob0-f170.google.com with SMTP id wp18so8417009obc.1 for <homenet@ietf.org>; Thu, 18 Dec 2014 16:39:03 -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=Eeqlp8ovKIw6Tt9QLwmat9wm5frgjqknktfT2XyXF6Y=; b=LIzkmWZciNCKwmCZi7KUFtX9T8S7NIztWsFpU5OnTEwG2ATXNma3q/DYGlXnC68Pav Q18wP23GUackpzNPIn72qdM7velZvm2JjuWFSp2LTUr2U6FB/8AUjLJy6qw4eLQuVwom CmUpna8rH8IJtxNh0RDESep3G+fm02cgD5/ld3127Uo4QYGqcA52dpyOvkGiB5F3ZzYi tZ2Jt+fnPr3g0WrPKdVyMABzpC8oX0dlN4viqO94uf9ApNqiUSOgBGLifQLV0c1mJWAp aPH1bdtLTWbVSwo9TxBb+Jl+U9XZK4RVDXKY0+CJV3539rdWq3SpNUttFkE0AsGXr/H1 o1mQ==
MIME-Version: 1.0
X-Received: by 10.60.177.193 with SMTP id cs1mr3071438oec.55.1418949543669; Thu, 18 Dec 2014 16:39:03 -0800 (PST)
Sender: gettysjim@gmail.com
Received: by 10.76.194.73 with HTTP; Thu, 18 Dec 2014 16:39:03 -0800 (PST)
In-Reply-To: <54936F28.9070201@gmail.com>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com>
Date: Thu, 18 Dec 2014 19:39:03 -0500
X-Google-Sender-Auth: o0lszriY3IisIMRP36Rw0Kw4xRk
Message-ID: <CAGhGL2CBHoM9aKzmHAuos_ubMYazqyBMyx8Eo=hNhieD9H9zKQ@mail.gmail.com>
From: Jim Gettys <jg@freedesktop.org>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=089e010d8c2c813556050a86ef2c
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/xunRuLkhcnW9MFch2F7-DLA9MYg
Cc: Dave Taht <dave.taht@gmail.com>, Michael Richardson <mcr+ietf@sandelman.ca>, Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>, HOMENET <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 00:39:07 -0000

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

On Thu, Dec 18, 2014 at 7:19 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:
>
> On 19/12/2014 11:22, Juliusz Chroboczek wrote:
> > Shouldn't we reduce the amount of cross-posting at some point?
> >
> >>> mptcp, I'm told, is likely to show up in Apple and Google products an=
d
> >>> infrastructure, and my idea (and many others) is that you don't alway=
s
> have
> >>> to pick the perfect address for the SYN, just one that works, but
> rather one
> >>> can add better addresses as one discovers them.
> >
> >> But bad luck if you need UDP.
> >
> >> Some form of intelligent probing does seem to be the answer,
> >
> > I'd like to attract your attention to the work that Matthieu Boutier ha=
s
> > been doing on mosh, Keith Winstein's UDP-based ssh replacement:
> >
> >   http://comments.gmane.org/gmane.network.mosh.devel/749
> >
> > Boutier's version of mosh builds connections across all
> source/destination
> > pairs, and picks the one with lowest RTT.
>
> Sounds interesting. In the ideal world, that would be a pluggable
> policy algorithm. Lowest RTT may not always be the best choice.
> NAROS* suggested distributing policy from a single source, for
> example.
>
> The point about shim6, of course, is that allows you to change
> horses in midstream without bothering the transport layer.
> It's a real shame we don't know how to deploy it, especially
> for homenets where nobody manages the routing policy.
>

=E2=80=8B
What were the problems with getting shim6 deployed?

There appear to have been
=E2=80=8Ba Linux implementation, and if the idea now has merit, that is eno=
ugh of
the market (which is very responsive) =E2=80=8B
=E2=80=8Bto get significant deployment, and to do so quickly. (codel/fq_cod=
el went
from concept to shipping code is under 3 months, with wide test deployment
in a year, and now becoming default).  We aren't talking about 5 year
product cycles any more.

As to policy, the home routers themselves give us a place to enable people
to state the policy they want (e.g. only use the LTE upstream if the cheap
broadband service is unavailable...).
                                    - Jim


>    Brian
>
> * C. Launois, O. Bonaventure, and M. Lobelle. The NAROS approach for IPv6
> multihoming with traffic engineering. volume 2811 of Lecture Notes in
> Computer
> Science, pages 112=E2=80=93121. Springer Berlin Heidelberg, 2003.
>
> > It's a work in progress --
> > there are multiple versions, and Matthieu has yet to decide which
> > implementation he's going to submit for inclusion in mainline mosh.
> >
> > We hope to write that stuff down when Matthieu has decided which is the
> > "right" version, but I'm not promising any hard deadlines -- we have a
> lot
> > of stuff that we want to write down.
> >
> >> but certainly that needs to be generic because we cannot expect
> >> all apps developers to reinvent it.
> >
> > Uh-huh.  But there's only one thing that's worse than generalising from
> > one example -- it's generalising from zero eexamples.
> >
> >> http://tools.ietf.org/html/draft-naderi-ipv6-probing recently.
> >
> > I'll have a look, thanks for the pointer.
> >
> > -- Juliusz
> >
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, De=
c 18, 2014 at 7:19 PM, Brian E Carpenter <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpenter@gmai=
l.com</a>&gt;</span> wrote:<blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204=
);border-left-style:solid;padding-left:1ex"><span class=3D"">On 19/12/2014 =
11:22, Juliusz Chroboczek wrote:<br>
&gt; Shouldn&#39;t we reduce the amount of cross-posting at some point?<br>
&gt;<br>
&gt;&gt;&gt; mptcp, I&#39;m told, is likely to show up in Apple and Google =
products and<br>
&gt;&gt;&gt; infrastructure, and my idea (and many others) is that you don&=
#39;t always have<br>
&gt;&gt;&gt; to pick the perfect address for the SYN, just one that works, =
but rather one<br>
&gt;&gt;&gt; can add better addresses as one discovers them.<br>
&gt;<br>
&gt;&gt; But bad luck if you need UDP.<br>
&gt;<br>
&gt;&gt; Some form of intelligent probing does seem to be the answer,<br>
&gt;<br>
&gt; I&#39;d like to attract your attention to the work that Matthieu Bouti=
er has<br>
&gt; been doing on mosh, Keith Winstein&#39;s UDP-based ssh replacement:<br=
>
&gt;<br>
&gt;=C2=A0 =C2=A0<a href=3D"http://comments.gmane.org/gmane.network.mosh.de=
vel/749" target=3D"_blank">http://comments.gmane.org/gmane.network.mosh.dev=
el/749</a><br>
&gt;<br>
&gt; Boutier&#39;s version of mosh builds connections across all source/des=
tination<br>
&gt; pairs, and picks the one with lowest RTT.<br>
<br>
</span>Sounds interesting. In the ideal world, that would be a pluggable<br=
>
policy algorithm. Lowest RTT may not always be the best choice.<br>
NAROS* suggested distributing policy from a single source, for<br>
example.<br>
<br>
The point about shim6, of course, is that allows you to change<br>
horses in midstream without bothering the transport layer.<br>
It&#39;s a real shame we don&#39;t know how to deploy it, especially<br>
for homenets where nobody manages the routing policy.<br></blockquote><div>=
<br></div><div><div class=3D"gmail_default" style=3D"font-size:small;displa=
y:inline">=E2=80=8B</div>What were the problems with getting shim6 deployed=
?=C2=A0</div><div><br></div><div>There appear to have been=C2=A0<div class=
=3D"gmail_default" style=3D"font-size:small;display:inline">=E2=80=8Ba Linu=
x implementation, and if the idea now has merit, that is enough of the mark=
et (which is very responsive) =E2=80=8B</div><div class=3D"gmail_default" s=
tyle=3D"display:inline">=E2=80=8Bto get significant deployment, and to do s=
o quickly. (codel/fq_codel went from concept to shipping code is under 3 mo=
nths, with wide test deployment in a year, and now becoming default).=C2=A0=
 We aren&#39;t talking about 5 year product cycles any more.</div></div><di=
v><div class=3D"gmail_default" style=3D"display:inline"><br></div></div><di=
v><div class=3D"gmail_default" style=3D"display:inline">As to policy, the h=
ome routers themselves give us a place to enable people to state the policy=
 they want (e.g. only use the LTE upstream if the cheap broadband service i=
s unavailable...).</div></div><div><div class=3D"gmail_default" style=3D"di=
splay:inline">=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 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - Jim</d=
iv></div><div><div class=3D"gmail_default" style=3D"display:inline"><br></d=
iv></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-styl=
e:solid;padding-left:1ex">
<br>
=C2=A0 =C2=A0Brian<br>
<br>
* C. Launois, O. Bonaventure, and M. Lobelle. The NAROS approach for IPv6<b=
r>
multihoming with traffic engineering. volume 2811 of Lecture Notes in<br>
Computer<br>
Science, pages 112=E2=80=93121. Springer Berlin Heidelberg, 2003.<br>
<div class=3D""><div class=3D"h5"><br>
&gt; It&#39;s a work in progress --<br>
&gt; there are multiple versions, and Matthieu has yet to decide which<br>
&gt; implementation he&#39;s going to submit for inclusion in mainline mosh=
.<br>
&gt;<br>
&gt; We hope to write that stuff down when Matthieu has decided which is th=
e<br>
&gt; &quot;right&quot; version, but I&#39;m not promising any hard deadline=
s -- we have a lot<br>
&gt; of stuff that we want to write down.<br>
&gt;<br>
&gt;&gt; but certainly that needs to be generic because we cannot expect<br=
>
&gt;&gt; all apps developers to reinvent it.<br>
&gt;<br>
&gt; Uh-huh.=C2=A0 But there&#39;s only one thing that&#39;s worse than gen=
eralising from<br>
&gt; one example -- it&#39;s generalising from zero eexamples.<br>
&gt;<br>
&gt;&gt; <a href=3D"http://tools.ietf.org/html/draft-naderi-ipv6-probing" t=
arget=3D"_blank">http://tools.ietf.org/html/draft-naderi-ipv6-probing</a> r=
ecently.<br>
&gt;<br>
&gt; I&#39;ll have a look, thanks for the pointer.<br>
&gt;<br>
&gt; -- Juliusz<br>
&gt;<br>
<br>
_______________________________________________<br>
homenet mailing list<br>
<a href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/homenet" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/homenet</a><br>
</div></div></blockquote></div></div></div>

--089e010d8c2c813556050a86ef2c--


From nobody Thu Dec 18 16:47:22 2014
Return-Path: <joelja@bogus.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F79D1ACC86 for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 16:47: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, 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 A0A-Du-9qKA7 for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 16:47:19 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 027F51ACAD8 for <homenet@ietf.org>; Thu, 18 Dec 2014 16:47:18 -0800 (PST)
Received: from mbp.local (c-67-188-0-113.hsd1.ca.comcast.net [67.188.0.113]) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id sBJ0lHJq035465 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 19 Dec 2014 00:47:17 GMT (envelope-from joelja@bogus.com)
Message-ID: <54937592.7070601@bogus.com>
Date: Thu, 18 Dec 2014 16:47:14 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: Jim Gettys <jg@freedesktop.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com> <CAGhGL2CBHoM9aKzmHAuos_ubMYazqyBMyx8Eo=hNhieD9H9zKQ@mail.gmail.com>
In-Reply-To: <CAGhGL2CBHoM9aKzmHAuos_ubMYazqyBMyx8Eo=hNhieD9H9zKQ@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ddbCMe9BE2H0ExHMQnbPA8fSxs6eoKBDw"
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/URU9XyqBw4vWE_FTHdFWClBpaXY
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>, HOMENET <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 00:47:21 -0000

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

On 12/18/14 4:39 PM, Jim Gettys wrote:
>
>
> On Thu, Dec 18, 2014 at 7:19 PM, Brian E Carpenter
> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrot=
e:
>
>     On 19/12/2014 11:22, Juliusz Chroboczek wrote:
>     > Shouldn't we reduce the amount of cross-posting at some point?
>     >
>     >>> mptcp, I'm told, is likely to show up in Apple and Google
>     products and
>     >>> infrastructure, and my idea (and many others) is that you
>     don't always have
>     >>> to pick the perfect address for the SYN, just one that works,
>     but rather one
>     >>> can add better addresses as one discovers them.
>     >
>     >> But bad luck if you need UDP.
>     >
>     >> Some form of intelligent probing does seem to be the answer,
>     >
>     > I'd like to attract your attention to the work that Matthieu
>     Boutier has
>     > been doing on mosh, Keith Winstein's UDP-based ssh replacement:
>     >
>     >   http://comments.gmane.org/gmane.network.mosh.devel/749
>     >
>     > Boutier's version of mosh builds connections across all
>     source/destination
>     > pairs, and picks the one with lowest RTT.
>
>     Sounds interesting. In the ideal world, that would be a pluggable
>     policy algorithm. Lowest RTT may not always be the best choice.
>     NAROS* suggested distributing policy from a single source, for
>     example.
>
>     The point about shim6, of course, is that allows you to change
>     horses in midstream without bothering the transport layer.
>     It's a real shame we don't know how to deploy it, especially
>     for homenets where nobody manages the routing policy.
>
>
> =E2=80=8B
> What were the problems with getting shim6 deployed?=20
>
need a time machine

https://www.nanog.org/meetings/nanog35/presentations/schiller.pdf

> There appear to have been=20
> =E2=80=8Ba Linux implementation, and if the idea now has merit, that is=
 enough
> of the market (which is very responsive) =E2=80=8B
> =E2=80=8Bto get significant deployment, and to do so quickly. (codel/fq=
_codel
> went from concept to shipping code is under 3 months, with wide test
> deployment in a year, and now becoming default).  We aren't talking
> about 5 year product cycles any more.
>
> As to policy, the home routers themselves give us a place to enable
> people to state the policy they want (e.g. only use the LTE upstream
> if the cheap broadband service is unavailable...).
>                                     - Jim
>
>
>        Brian
>
>     * C. Launois, O. Bonaventure, and M. Lobelle. The NAROS approach
>     for IPv6
>     multihoming with traffic engineering. volume 2811 of Lecture Notes =
in
>     Computer
>     Science, pages 112=E2=80=93121. Springer Berlin Heidelberg, 2003.
>
>     > It's a work in progress --
>     > there are multiple versions, and Matthieu has yet to decide which=

>     > implementation he's going to submit for inclusion in mainline mos=
h.
>     >
>     > We hope to write that stuff down when Matthieu has decided which
>     is the
>     > "right" version, but I'm not promising any hard deadlines -- we
>     have a lot
>     > of stuff that we want to write down.
>     >
>     >> but certainly that needs to be generic because we cannot expect
>     >> all apps developers to reinvent it.
>     >
>     > Uh-huh.  But there's only one thing that's worse than
>     generalising from
>     > one example -- it's generalising from zero eexamples.
>     >
>     >> http://tools.ietf.org/html/draft-naderi-ipv6-probing recently.
>     >
>     > I'll have a look, thanks for the pointer.
>     >
>     > -- Juliusz
>     >
>
>     _______________________________________________
>     homenet mailing list
>     homenet@ietf.org <mailto:homenet@ietf.org>
>     https://www.ietf.org/mailman/listinfo/homenet
>
>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet



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

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

iEYEARECAAYFAlSTdZIACgkQ8AA1q7Z/VrJ7HQCZAfdQg0cdutXQ49HuQb/AjCPT
6Y4An3jFsbi58kJOVez2g+OKGRyM13za
=aHzT
-----END PGP SIGNATURE-----

--ddbCMe9BE2H0ExHMQnbPA8fSxs6eoKBDw--


From nobody Thu Dec 18 17:03:51 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98FA11A1B71 for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 17:03:49 -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 d_hVsI-DvpxZ for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 17:03:46 -0800 (PST)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C63E1A0045 for <homenet@ietf.org>; Thu, 18 Dec 2014 17:03:46 -0800 (PST)
Received: by mail-pa0-f52.google.com with SMTP id eu11so60605pac.25 for <homenet@ietf.org>; Thu, 18 Dec 2014 17:03:45 -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=FnbCh3jNWBbkpHIxsfBvLmrketScvXCg+A3tLKYJDI0=; b=Mom/6fXrYtUtbst36iP3y1sTeBxR+hVt3JVs810HDJp9NHoYH0WtITUI8xUChOkKhW R1EjVGOEq6VVfckxkK35TjbrvjAnDJKBVXVGNQK3lWXEKFv9Rk+tlogZz1XNFZrMLw/+ Bn3dCpn3mD1aN9k7Ly0b7SWrqjj2JDQiJY+72ZhzBWn/rKlJgMJpWnmHnKmLaFHg/p3n LXgrGs6vd83KMZIbsftX2Mo/rE33xWFbo3AtISjFf3WjQlMtr1ec/9hQ6qFn41KTuEOn OsFx/BU4CEPSZQ8FM7L12qEzT0RSj7taIktJ6II7swC3xZG9aR6cy6EjLi+USN48qQAa AJXA==
X-Received: by 10.68.224.6 with SMTP id qy6mr8092160pbc.35.1418951025705; Thu, 18 Dec 2014 17:03:45 -0800 (PST)
Received: from ?IPv6:2406:e007:74cb:1:28cc:dc4c:9703:6781? ([2406:e007:74cb:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id nh4sm7885003pdb.37.2014.12.18.17.03.41 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 18 Dec 2014 17:03:44 -0800 (PST)
Message-ID: <54937978.5050607@gmail.com>
Date: Fri, 19 Dec 2014 14:03: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:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com> <CAGhGL2CBHoM9aKzmHAuos_ubMYazqyBMyx8Eo=hNhieD9H9zKQ@mail.gmail.com> <54937592.7070601@bogus.com>
In-Reply-To: <54937592.7070601@bogus.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/qlU0Bvda-YnVrzbrDOF1uOIl6VU
Cc: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Michael Richardson <mcr+ietf@sandelman.ca>, Jim Gettys <jg@freedesktop.org>, Dave Taht <dave.taht@gmail.com>, Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>, HOMENET <homenet@ietf.org>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 01:03:49 -0000

On 19/12/2014 13:47, joel jaeggli wrote:
> On 12/18/14 4:39 PM, Jim Gettys wrote:
>>
>>
>> On Thu, Dec 18, 2014 at 7:19 PM, Brian E Carpenter
>> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wro=
te:
>>
>>     On 19/12/2014 11:22, Juliusz Chroboczek wrote:
>>     > Shouldn't we reduce the amount of cross-posting at some point?
>>     >
>>     >>> mptcp, I'm told, is likely to show up in Apple and Google
>>     products and
>>     >>> infrastructure, and my idea (and many others) is that you
>>     don't always have
>>     >>> to pick the perfect address for the SYN, just one that works,
>>     but rather one
>>     >>> can add better addresses as one discovers them.
>>     >
>>     >> But bad luck if you need UDP.
>>     >
>>     >> Some form of intelligent probing does seem to be the answer,
>>     >
>>     > I'd like to attract your attention to the work that Matthieu
>>     Boutier has
>>     > been doing on mosh, Keith Winstein's UDP-based ssh replacement:
>>     >
>>     >   http://comments.gmane.org/gmane.network.mosh.devel/749
>>     >
>>     > Boutier's version of mosh builds connections across all
>>     source/destination
>>     > pairs, and picks the one with lowest RTT.
>>
>>     Sounds interesting. In the ideal world, that would be a pluggable
>>     policy algorithm. Lowest RTT may not always be the best choice.
>>     NAROS* suggested distributing policy from a single source, for
>>     example.
>>
>>     The point about shim6, of course, is that allows you to change
>>     horses in midstream without bothering the transport layer.
>>     It's a real shame we don't know how to deploy it, especially
>>     for homenets where nobody manages the routing policy.
>>
>>
>> =E2=80=8B
>> What were the problems with getting shim6 deployed?=20
>>
> need a time machine
>=20
> https://www.nanog.org/meetings/nanog35/presentations/schiller.pdf

Well, let's not start that argument again. Shim6 was never intended to
address operator's concerns, so it didn't. The real world problems are
these:

1. Most firewalls drop packets containing the shim6 extension header.

2. When shim6 switches addresses, the packets get a big bigger and
that might reveal a PMTUD problem.

3. Absent SADR in the exit router, shim6 has a high chance of falling
victim to BCP38 filtering.

More details:
H. Naderi & B.E. Carpenter, Putting SHIM6 into Practice,
Australasian Telecommunication Networks and Applications Conference
(ATNAC 2014),
Melbourne (November 2014).
https://www.cs.auckland.ac.nz/~brian/Shim6-ATNAC14-subm.pdf

    Brian

>=20
>> There appear to have been=20
>> =E2=80=8Ba Linux implementation, and if the idea now has merit, that i=
s enough
>> of the market (which is very responsive) =E2=80=8B
>> =E2=80=8Bto get significant deployment, and to do so quickly. (codel/f=
q_codel
>> went from concept to shipping code is under 3 months, with wide test
>> deployment in a year, and now becoming default).  We aren't talking
>> about 5 year product cycles any more.
>>
>> As to policy, the home routers themselves give us a place to enable
>> people to state the policy they want (e.g. only use the LTE upstream
>> if the cheap broadband service is unavailable...).
>>                                     - Jim
>>
>>
>>        Brian
>>
>>     * C. Launois, O. Bonaventure, and M. Lobelle. The NAROS approach
>>     for IPv6
>>     multihoming with traffic engineering. volume 2811 of Lecture Notes=
 in
>>     Computer
>>     Science, pages 112=E2=80=93121. Springer Berlin Heidelberg, 2003.
>>
>>     > It's a work in progress --
>>     > there are multiple versions, and Matthieu has yet to decide whic=
h
>>     > implementation he's going to submit for inclusion in mainline mo=
sh.
>>     >
>>     > We hope to write that stuff down when Matthieu has decided which=

>>     is the
>>     > "right" version, but I'm not promising any hard deadlines -- we
>>     have a lot
>>     > of stuff that we want to write down.
>>     >
>>     >> but certainly that needs to be generic because we cannot expect=

>>     >> all apps developers to reinvent it.
>>     >
>>     > Uh-huh.  But there's only one thing that's worse than
>>     generalising from
>>     > one example -- it's generalising from zero eexamples.
>>     >
>>     >> http://tools.ietf.org/html/draft-naderi-ipv6-probing recently.
>>     >
>>     > I'll have a look, thanks for the pointer.
>>     >
>>     > -- Juliusz
>>     >
>>
>>     _______________________________________________
>>     homenet mailing list
>>     homenet@ietf.org <mailto:homenet@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/homenet
>>
>>
>>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>=20
>=20


From nobody Thu Dec 18 17:49:14 2014
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 855B81A8AC0 for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 17:49:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] 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 eRlJ4VNYOgrS for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 17:49:12 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 CB2501A7005 for <homenet@ietf.org>; Thu, 18 Dec 2014 17:49:11 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/46573) with ESMTP id sBJ1n993002587 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 19 Dec 2014 02:49:09 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/46573) with ESMTP id sBJ1n9IF004649; Fri, 19 Dec 2014 02:49:09 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 3E405199F3; Fri, 19 Dec 2014 02:49:09 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id z61ps0LLCOJ1; Fri, 19 Dec 2014 02:49:07 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 8662F1ABC8; Fri, 19 Dec 2014 02:49:07 +0100 (CET)
Date: Fri, 19 Dec 2014 02:49:10 +0100
Message-ID: <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <54936F28.9070201@gmail.com>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Fri, 19 Dec 2014 02:49:09 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Fri, 19 Dec 2014 02:49:09 +0100 (CET)
X-Miltered: at korolev with ID 54938415.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54938415.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54938415.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54938415.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54938415.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54938415.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/xMKN3kKIOpeJwKyPPZ43bEMHwHo
Cc: boutier@pps.univ-paris-diderot.fr, Michael Richardson <mcr+ietf@sandelman.ca>, HOMENET <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 01:49:13 -0000

>> Boutier's version of mosh builds connections across all source/destination
>> pairs, and picks the one with lowest RTT.  

> Sounds interesting. In the ideal world, that would be a pluggable
> policy algorithm. Lowest RTT may not always be the best choice.

It is, in our particular context.  That's the nice thing about working at
the application layer -- you are the application, so you have a pretty
good idea of what the desirable properties are.  Mosh is an interactive
shell, and in this particular context it's latency you want to optimise
for.

Once we gain some real-world experience from mosh, we can think about
making something more generic.  But I, at least, don't feel comfortable
about doing that.

-- Juliusz


From nobody Thu Dec 18 19:38:07 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CD981A00B9 for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 19:38:05 -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 5cppMMZi3JrY for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 19:38:04 -0800 (PST)
Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA8E61A9150 for <homenet@ietf.org>; Thu, 18 Dec 2014 19:38:03 -0800 (PST)
Received: by mail-pd0-f181.google.com with SMTP id v10so290379pde.40 for <homenet@ietf.org>; Thu, 18 Dec 2014 19:38:03 -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=cGs0gxHddPn4NdCI1OaXHe8eyFgINcapj20zdRr+CnE=; b=DmxiIkeZUt4MTQv7ii5fPcluDhfjBXKkip0R4Ewi7bfdcjx0Qn2SZQQ/eB4Eirxhs0 1yMcakIijpktLb3PGDxE1uaDgfcEvALZ4admazjInBzhLVcboSq8XQ82+QJePYRN+gcQ i4coDc1OtlJvbP2fuzhYLHZL0GzQdoPwg2XsoX2b/jDqcgu2TuSuNRonDdYh5f/QrVIg qPjCOGtQqikAsapEaGU8YOjsWtOh5pkU/XG0YTtQyF72nX8nsEdYAQDwtGrnnyRM+WKt Wy/3UokPG/S/R6xb9XzjYkOqnBCF4AA8rYs6nll1t+KVIdT5qgfGhkAewmD8JtsTXprn Q8gw==
X-Received: by 10.68.136.70 with SMTP id py6mr2553521pbb.91.1418960283211; Thu, 18 Dec 2014 19:38:03 -0800 (PST)
Received: from ?IPv6:2406:e007:74cb:1:28cc:dc4c:9703:6781? ([2406:e007:74cb:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id se3sm8098705pbc.24.2014.12.18.19.37.59 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 18 Dec 2014 19:38:02 -0800 (PST)
Message-ID: <54939DA2.60602@gmail.com>
Date: Fri, 19 Dec 2014 16:38:10 +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:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com> <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/RpM7jFvTH4tkBbSPCDidBLgmcQE
Cc: boutier@pps.univ-paris-diderot.fr, Michael Richardson <mcr+ietf@sandelman.ca>, HOMENET <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 03:38:05 -0000

On 19/12/2014 14:49, Juliusz Chroboczek wrote:
>>> Boutier's version of mosh builds connections across all source/destination
>>> pairs, and picks the one with lowest RTT.  
> 
>> Sounds interesting. In the ideal world, that would be a pluggable
>> policy algorithm. Lowest RTT may not always be the best choice.
> 
> It is, in our particular context.  That's the nice thing about working at
> the application layer -- you are the application, so you have a pretty
> good idea of what the desirable properties are.  Mosh is an interactive
> shell, and in this particular context it's latency you want to optimise
> for.

Are you sure? Suppose I open a file transfer window (which as a matter
of fact I do almost every time I use SSH these days). For large file
transfers
I might want to specify "cheapest" not "fastest".

> Once we gain some real-world experience from mosh, we can think about
> making something more generic.  But I, at least, don't feel comfortable
> about doing that.

Understood. But all I'm thinking is that you might make that bit a
self-contained
module.

    Brian


From nobody Thu Dec 18 21:39:47 2014
Return-Path: <dave.taht@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A02C1A9063 for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 21:39: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 68L1pMgDtzcl for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 21:39:42 -0800 (PST)
Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED14E1A8F48 for <homenet@ietf.org>; Thu, 18 Dec 2014 21:39:41 -0800 (PST)
Received: by mail-ob0-f171.google.com with SMTP id uz6so11067614obc.2 for <homenet@ietf.org>; Thu, 18 Dec 2014 21:39:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=XKAGUI33y313YSfxBf/VHQ3n5XkB1DgeWTwy3Br5caU=; b=nok81vYBpxG7TF2ZQLq2JZIxa1rL/knQLu/6p8/Xy9cp3d7joe+iJrVl6qcmBn47pl iXnxH8UgZ758jAzooF5o8mKqDJwmGiZu+h+7bbOES65Cn256B7U4a0NjMrk9KtRDCLTd yvzdRrUAPDhWKsWjqRbqHmx223zLIQ94+LAm9KS3tSx6DyXpboXWX+nFg8t1lnbM/D3w wiR52dG8PSdWmtk92eyjwddc6E5R3wOWbs3w9kgvXxHoIhFrk33K46KdRBAp5aiaBNA9 217XyRnCr+WiJ8ENaTis7EKrG1EBV5VCX+5EImge3UTVnQooZmlLoT2oLHlhafIcGQNo o3gw==
MIME-Version: 1.0
X-Received: by 10.182.245.130 with SMTP id xo2mr3751803obc.16.1418967581216; Thu, 18 Dec 2014 21:39:41 -0800 (PST)
Received: by 10.202.169.209 with HTTP; Thu, 18 Dec 2014 21:39:41 -0800 (PST)
In-Reply-To: <54939DA2.60602@gmail.com>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com> <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr> <54939DA2.60602@gmail.com>
Date: Thu, 18 Dec 2014 21:39:41 -0800
Message-ID: <CAA93jw6R=VbqQDJD2jVR7h4Z2072MeRLr6D8Z9vcxWEuaJ7ueQ@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/6IFYTYUypJ8Y6QHICyZR88DDTqs
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, HOMENET <homenet@ietf.org>, Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 05:39:44 -0000

On Thu, Dec 18, 2014 at 7:38 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> On 19/12/2014 14:49, Juliusz Chroboczek wrote:
>>>> Boutier's version of mosh builds connections across all source/destina=
tion
>>>> pairs, and picks the one with lowest RTT.
>>
>>> Sounds interesting. In the ideal world, that would be a pluggable
>>> policy algorithm. Lowest RTT may not always be the best choice.
>>
>> It is, in our particular context.  That's the nice thing about working a=
t
>> the application layer -- you are the application, so you have a pretty
>> good idea of what the desirable properties are.  Mosh is an interactive
>> shell, and in this particular context it's latency you want to optimise
>> for.
>
> Are you sure?

For mosh, which is a very low bandwidth, highly interactive application,
lowest RTT is the right choice.

> Suppose I open a file transfer window (which as a matter
> of fact I do almost every time I use SSH these days). For large file
> transfers
> I might want to specify "cheapest" not "fastest".

I would argue that a transfer over LTE (which is the most expensive option)=
,
would generally exhibit higher RTT over any other method.

lowest financial cost does not have a whole lot of meaning otherwise
along the edge. Highest bandwidth or least congested might be other
selectors...

But: in kicking off this thread, what I was mostly thinking about was
making a choice between 9 or more ipv6 addresses to choose from, what
to start with, and when to give up. (and which ones should end up in
DNS)

It seemed to me that I should longest prefix match, except when other
characteristics of the route interfered. As one example it made sense
to choose a native connection over a tunneled one. As another example,
when there was a vpn in play (with it's own address range) to try to
use the vpn rather than any public addresses that existed. And then
there is a choice to try and prefer stabler addresses (infinite
lifetime) over addresses with shorter lifetimes.

And then, in order to have a better choice of multi-path connectivity,
for an app like mosh or something using mptcp, to chose addresses that
are wildly different. I would argue for an app that wants multiple
forms of connectivity to pick 3-5 addresses total (and for mosh, to
ensure it did ipv4 and ipv6).

I tossed hip in there just to make things difficult, as arguably hip
addresses should only be used when trying to contact another device in
the hip address range ( 2001:10::/28 )

>> Once we gain some real-world experience from mosh, we can think about
>> making something more generic.  But I, at least, don't feel comfortable
>> about doing that.
>
> Understood. But all I'm thinking is that you might make that bit a
> self-contained
> module.

Well, I think I was seeking a new API here. But writing a select or
poll loop for 9 addresses is not much harder than 2.

>
>     Brian



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Fri Dec 19 09:32:23 2014
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 105441A904E for <homenet@ietfa.amsl.com>; Fri, 19 Dec 2014 09:32:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] 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 n2TiKdhsH61V for <homenet@ietfa.amsl.com>; Fri, 19 Dec 2014 09:32:13 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 E0CB41A909B for <homenet@ietf.org>; Fri, 19 Dec 2014 09:31:42 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/46573) with ESMTP id sBJHVejv024063 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 19 Dec 2014 18:31:40 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/46573) with ESMTP id sBJHVeie000935; Fri, 19 Dec 2014 18:31:40 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 276F51AE3B; Fri, 19 Dec 2014 18:31:40 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id FxAGSecV1kd9; Fri, 19 Dec 2014 18:31:38 +0100 (CET)
Received: from lanthane.pps.univ-paris-diderot.fr (unknown [172.23.36.54]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 390A31AE3E; Fri, 19 Dec 2014 18:31:38 +0100 (CET)
Received: from localhost ([::1] helo=lanthane.pps.univ-paris-diderot.fr) by lanthane.pps.univ-paris-diderot.fr with esmtp (Exim 4.84) (envelope-from <jch@pps.univ-paris-diderot.fr>) id 1Y21Or-0002et-SN; Fri, 19 Dec 2014 18:31:37 +0100
Date: Fri, 19 Dec 2014 18:31:37 +0100
Message-ID: <7izjajh7gm.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <54939DA2.60602@gmail.com>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com> <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr> <54939DA2.60602@gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Fri, 19 Dec 2014 18:31:40 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Fri, 19 Dec 2014 18:31:40 +0100 (CET)
X-Miltered: at korolev with ID 549460FC.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 549460FC.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 549460FC.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 549460FC.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 549460FC.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 549460FC.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/VbiYXwlpi2vbh1j-80Ze3w5rpJg
Cc: boutier@pps.univ-paris-diderot.fr, Michael Richardson <mcr+ietf@sandelman.ca>, HOMENET <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 17:32:16 -0000

>>> Sounds interesting. In the ideal world, that would be a pluggable
>>> policy algorithm. Lowest RTT may not always be the best choice.

>> It is, in our particular context.  That's the nice thing about working at
>> the application layer -- you are the application, so you have a pretty
>> good idea of what the desirable properties are.

> Are you sure?

This particular debate aside, I think we're in agreement about the
underlying issue -- source selection in networks with source-specific
routing is an interesting problem, and one that we haven't explored much
yet.

> But all I'm thinking is that you might make that bit a self-contained
> module.

Medium-term, yes.

-- Juliusz


From nobody Fri Dec 19 09:40:09 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92AF81A8A62 for <homenet@ietfa.amsl.com>; Fri, 19 Dec 2014 09:40: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 yso-nHXXOCQC for <homenet@ietfa.amsl.com>; Fri, 19 Dec 2014 09:39:57 -0800 (PST)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0FBB1A8A9B for <homenet@ietf.org>; Fri, 19 Dec 2014 09:39:55 -0800 (PST)
Received: by mail-wg0-f52.google.com with SMTP id x12so1929721wgg.25 for <homenet@ietf.org>; Fri, 19 Dec 2014 09:39:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=wSR01M6qw1TlNIgd7S8Z1qjI0B6YPsj9d23s/VaQyfY=; b=F9Go33I/SMwQUF1WwViJ2n2C8opA9tP2/aXNLkumuHZvqyZvwIEFyyaBhJ2N0z2anJ NK+ScuKFuTPcF363x/i3uWkSuffEqV6Erl859NxOFq7FDJjXL3GPhewTHGBoQVGKbfs5 FBm6DQgpR8XmqEN2+HTFRPiUVDWkuCuOcIzwRtCyMb1c5BwqeInPUA1Rvd1c1Y1o4LLO OBadMW7EvwXj1wLXGHmk56sHL4AcUQ8dovetonRb5y/PwoUCWNbTFo/ixwi+YKTsPnHP G6OKAr8oLE2tCgzr/gp1O1BG19Yk/x1rum6G7j9o8rYicauUAkmDvCZTUDT9dtjUnN+2 hP8Q==
X-Received: by 10.180.88.165 with SMTP id bh5mr7878070wib.77.1419010794577; Fri, 19 Dec 2014 09:39:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.10.66 with HTTP; Fri, 19 Dec 2014 09:39:34 -0800 (PST)
In-Reply-To: <7izjajh7gm.wl-jch@pps.univ-paris-diderot.fr>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com> <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr> <54939DA2.60602@gmail.com> <7izjajh7gm.wl-jch@pps.univ-paris-diderot.fr>
From: Henning Rogge <hrogge@gmail.com>
Date: Fri, 19 Dec 2014 18:39:34 +0100
Message-ID: <CAGnRvuqDTnyzH4ehKr9kizKM7H8J8y7=GTQxMJOcuBQyd8Nb5w@mail.gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/gFPUq-ANL5XOgBMGMiZdGC9VEY4
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>, HOMENET <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 17:40:07 -0000

On Fri, Dec 19, 2014 at 6:31 PM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
>>>> Sounds interesting. In the ideal world, that would be a pluggable
>>>> policy algorithm. Lowest RTT may not always be the best choice.
>
>>> It is, in our particular context.  That's the nice thing about working at
>>> the application layer -- you are the application, so you have a pretty
>>> good idea of what the desirable properties are.
>
>> Are you sure?
>
> This particular debate aside, I think we're in agreement about the
> underlying issue -- source selection in networks with source-specific
> routing is an interesting problem, and one that we haven't explored much
> yet.

You might also need to combine the features of the gateway with the
metric(s) of the path to the gateway.

Its not really useful to select a faster gateway if the path towards
the gateway goes over a slow wifi link.

Henning Rogge


From nobody Fri Dec 19 14:55:05 2014
Return-Path: <boutier@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 814741A908A for <homenet@ietfa.amsl.com>; Fri, 19 Dec 2014 14:55:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] 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 qiaJkGK3CVGH for <homenet@ietfa.amsl.com>; Fri, 19 Dec 2014 14:55:02 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 BC2471A9084 for <homenet@ietf.org>; Fri, 19 Dec 2014 14:55:01 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/46573) with ESMTP id sBJMswC6017695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 19 Dec 2014 23:54:58 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/46573) with ESMTP id sBJMswfR018256; Fri, 19 Dec 2014 23:54:58 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 790A41AE71; Fri, 19 Dec 2014 23:54:58 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id QSmHO6f8q0GV; Fri, 19 Dec 2014 23:54:57 +0100 (CET)
Received: from mac-matthieu.lan (AAubervilliers-652-1-202-228.w90-3.abo.wanadoo.fr [90.3.153.228]) (Authenticated sender: boutier) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id E85901AE70; Fri, 19 Dec 2014 23:54:55 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>
In-Reply-To: <CAGnRvuqDTnyzH4ehKr9kizKM7H8J8y7=GTQxMJOcuBQyd8Nb5w@mail.gmail.com>
Date: Fri, 19 Dec 2014 23:54:54 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <C72807F4-88D6-4040-8BF6-94BAD5B87AB0@pps.univ-paris-diderot.fr>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com> <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr> <54939DA2.60602@gmail.com> <7izjajh7gm.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqDTnyzH4ehKr9kizKM7H8J8y7=GTQxMJOcuBQyd8Nb5w@mail.gmail.com>
To: Henning Rogge <hrogge@gmail.com>
X-Mailer: Apple Mail (2.1283)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Fri, 19 Dec 2014 23:54:59 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Fri, 19 Dec 2014 23:54:58 +0100 (CET)
X-Miltered: at korolev with ID 5494ACC2.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 5494ACC2.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 5494ACC2.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<boutier@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 5494ACC2.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<boutier@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 5494ACC2.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 5494ACC2.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/4OSZnahK_gQZKc0UDzQgi-qbsJM
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, HOMENET <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 22:55:03 -0000

> You might also need to combine the features of the gateway with the
> metric(s) of the path to the gateway.
> 
> Its not really useful to select a faster gateway if the path towards
> the gateway goes over a slow wifi link.

I do end-to-end measurements in my mosh implementation, so we should
not have the problem.  The host selects a source address, in fact a
pair (src, dst), depending on the performances of the whole path
determined by this pair.

Matthieu


From nobody Sun Dec 21 04:17:34 2014
Return-Path: <gert@Space.Net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C85741A03A7 for <homenet@ietfa.amsl.com>; Sun, 21 Dec 2014 04:17:32 -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, 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 Yx2ApB04TrYU for <homenet@ietfa.amsl.com>; Sun, 21 Dec 2014 04:17:32 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (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 CB92D1A03A1 for <homenet@ietf.org>; Sun, 21 Dec 2014 04:17:31 -0800 (PST)
X-Original-To: homenet@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 2492A60A16 for <homenet@ietf.org>; Sun, 21 Dec 2014 13:17:30 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id ECF8460A11 for <homenet@ietf.org>; Sun, 21 Dec 2014 13:17:29 +0100 (CET)
Received: (qmail 14455 invoked by uid 1007); 21 Dec 2014 13:17:29 +0100
Date: Sun, 21 Dec 2014 13:17:29 +0100
From: Gert Doering <gert@space.net>
To: Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>
Message-ID: <20141221121729.GL28745@Space.Net>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com> <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr> <54939DA2.60602@gmail.com> <7izjajh7gm.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqDTnyzH4ehKr9kizKM7H8J8y7=GTQxMJOcuBQyd8Nb5w@mail.gmail.com> <C72807F4-88D6-4040-8BF6-94BAD5B87AB0@pps.univ-paris-diderot.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C72807F4-88D6-4040-8BF6-94BAD5B87AB0@pps.univ-paris-diderot.fr>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/Woy_UWkTma3GpHGkJxeYSQRQGEE
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, HOMENET <homenet@ietf.org>, Henning Rogge <hrogge@gmail.com>, Dave Taht <dave.taht@gmail.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Dec 2014 12:17:33 -0000

Hi,

On Fri, Dec 19, 2014 at 11:54:54PM +0100, Matthieu Boutier wrote:
> I do end-to-end measurements in my mosh implementation, so we should
> not have the problem.  The host selects a source address, in fact a
> pair (src, dst), depending on the performances of the whole path
> determined by this pair.

This is extremely cool (and quite likely one of the reasons why mosh
performs so well under adverse network conditions).

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From nobody Sun Dec 21 11:09:48 2014
Return-Path: <hrogge@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 975E61A6FEE for <homenet@ietfa.amsl.com>; Sun, 21 Dec 2014 11:09:45 -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 fLm4DUMbgrcc for <homenet@ietfa.amsl.com>; Sun, 21 Dec 2014 11:09:44 -0800 (PST)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CF311A1BDB for <homenet@ietf.org>; Sun, 21 Dec 2014 11:09:44 -0800 (PST)
Received: by mail-wg0-f43.google.com with SMTP id l18so5218023wgh.16 for <homenet@ietf.org>; Sun, 21 Dec 2014 11:09:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=jgZty2g2KDism0j5P99hH3M/l2XZ1gGI1cdmSKjmBcs=; b=zrKQUursQt+9zmVKnIWfPH57H4lTvdLu+3AwnpK4Kuc+PLNhrCJcRjTG0qyvsPp7XN pjxZm49XEh5NKZSJsPK3gYAAUeFyukmNdQKiltH9voBZFbxaXmxQDP5m+B40iQE2/hTf g+YxZRaDRbNaAO3LU4ZozRynTbDu5M1ry1oL++NirfhAG4Q0yZL0T5IpMa0IW7DLVh3y FUnJzcAq9F66IFPXEXLXzr1ydCtyyvb/7qDDEoX+xEkmzvjGekeHu6H0yuRILP66PHRp /NF+675go87E3qqrVS0PUV20WVHRZU//kyWlhsTd9bu54t7emyEbRG4N/PuelVhGJG5i 1wtw==
X-Received: by 10.194.222.98 with SMTP id ql2mr35393698wjc.36.1419188983045; Sun, 21 Dec 2014 11:09:43 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.10.66 with HTTP; Sun, 21 Dec 2014 11:09:22 -0800 (PST)
In-Reply-To: <C72807F4-88D6-4040-8BF6-94BAD5B87AB0@pps.univ-paris-diderot.fr>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com> <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr> <54939DA2.60602@gmail.com> <7izjajh7gm.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqDTnyzH4ehKr9kizKM7H8J8y7=GTQxMJOcuBQyd8Nb5w@mail.gmail.com> <C72807F4-88D6-4040-8BF6-94BAD5B87AB0@pps.univ-paris-diderot.fr>
From: Henning Rogge <hrogge@gmail.com>
Date: Sun, 21 Dec 2014 20:09:22 +0100
Message-ID: <CAGnRvuos29bkYMChXUaOGoxrtY2ZNiJFXDVu==SaiwiD-zw5xA@mail.gmail.com>
To: Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/Kv5YgJE6k49cxh-67QcFMGd99Tc
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, HOMENET <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Dec 2014 19:09:45 -0000

On Fri, Dec 19, 2014 at 11:54 PM, Matthieu Boutier
<boutier@pps.univ-paris-diderot.fr> wrote:
>> You might also need to combine the features of the gateway with the
>> metric(s) of the path to the gateway.
>>
>> Its not really useful to select a faster gateway if the path towards
>> the gateway goes over a slow wifi link.
>
> I do end-to-end measurements in my mosh implementation, so we should
> not have the problem.  The host selects a source address, in fact a
> pair (src, dst), depending on the performances of the whole path
> determined by this pair.

Does this really scale well?

If every application on every attached computer in the Homenet
measures the end-to-end performance through every gateway... that
could be a LOT of overhead for larger Homenet installations.

Henning Rogge


From nobody Sun Dec 21 11:44:14 2014
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD5521A7016 for <homenet@ietfa.amsl.com>; Sun, 21 Dec 2014 11:44:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] 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 X9Q2k5zwpdiI for <homenet@ietfa.amsl.com>; Sun, 21 Dec 2014 11:44:11 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 0879B1A6FCF for <homenet@ietf.org>; Sun, 21 Dec 2014 11:44:10 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/46573) with ESMTP id sBLJi8CC024528 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 21 Dec 2014 20:44:08 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/46573) with ESMTP id sBLJi7Bo008199; Sun, 21 Dec 2014 20:44:07 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id CD1C01B3BF; Sun, 21 Dec 2014 20:44:07 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id BEa5ApnKxa7K; Sun, 21 Dec 2014 20:44:06 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 6CE911B3BD; Sun, 21 Dec 2014 20:44:05 +0100 (CET)
Date: Sun, 21 Dec 2014 20:44:05 +0100
Message-ID: <87h9wou6t6.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Henning Rogge <hrogge@gmail.com>
In-Reply-To: <CAGnRvuos29bkYMChXUaOGoxrtY2ZNiJFXDVu==SaiwiD-zw5xA@mail.gmail.com>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com> <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr> <54939DA2.60602@gmail.com> <7izjajh7gm.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqDTnyzH4ehKr9kizKM7H8J8y7=GTQxMJOcuBQyd8Nb5w@mail.gmail.com> <C72807F4-88D6-4040-8BF6-94BAD5B87AB0@pps.univ-paris-diderot.fr> <CAGnRvuos29bkYMChXUaOGoxrtY2ZNiJFXDVu==SaiwiD-zw5xA@mail.gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Sun, 21 Dec 2014 20:44:08 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Sun, 21 Dec 2014 20:44:08 +0100 (CET)
X-Miltered: at korolev with ID 54972308.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54972307.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54972308.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54972307.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54972308.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54972307.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/dDZj-h-N4CP4R7bZLhV_v8JzK_I
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>, HOMENET <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Dec 2014 19:44:13 -0000

>>> You might also need to combine the features of the gateway with the
>>> metric(s) of the path to the gateway.

>> I do end-to-end measurements in my mosh implementation, so we should
>> not have the problem.

> Does this really scale well?

How well do we need it to scale?  Three addresses per host?  A dozen?
A hundred?  (Per host, mind you -- not per router.)

The probes Matthieu's code is sending are less than 90 bytes each.  This
means that if the client and the server have three addresses each, each
probing episode consists of a burst of 9 packets totalling less than one
full Ethernet frame.  (18 if you count the replies.)

On the other hand, if we end up having hundreds of addresses on every
host, the strategy will need to be rethought.  Dave is currently playing
with a network where each host has 10 addresses of different kinds, and
he's trying to work out heuristics to limit the number of probes.  I'd
personally prefer to gather some empirical data before we start optimising
things.

-- Juliusz



From nobody Sun Dec 21 12:07:54 2014
Return-Path: <dave.taht@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0885D1A8741 for <homenet@ietfa.amsl.com>; Sun, 21 Dec 2014 12:07:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.7
X-Spam-Level: 
X-Spam-Status: No, score=0.7 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, 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 MoTbBNouWvlt for <homenet@ietfa.amsl.com>; Sun, 21 Dec 2014 12:07:49 -0800 (PST)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE5D71A8743 for <homenet@ietf.org>; Sun, 21 Dec 2014 12:07:48 -0800 (PST)
Received: by mail-oi0-f49.google.com with SMTP id a141so7059976oig.8 for <homenet@ietf.org>; Sun, 21 Dec 2014 12:07:47 -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 :content-transfer-encoding; bh=wV+0vwpjtyNXHuYSRikMDXThuVI2rXkvBJ9vLoiteE4=; b=tstr6j4TBFWxmwBXIbUfNah/RiEKKMLFONPe3605GpogTk4CegIqbCOlY1yNdDAQyU Puqf4OUnnqzYy/sTI9as3QmGeZ3/IPybyTRZwjA1ar+NpBBZC7Sp+U7V2HdX0EC6a9YY fJ/ANNj1jKGYfwfTC2hlqG7kLMpInixgtaldjP7AwaQndXj65mj9D5ggRtIEshV1AyxP fnVI5r+uSNhr5oiaJN8tr9s9nzWQS38mzxieh8NcAtaZbbWq0dCbDxMeH9mwkS91u10H tLGGMFteDNiFXyQI0t2kyvIVSkjSTRf6oRmtt0ALuAU/HY/1jjF6Sfyc4XYnxZKb0LWq lPbQ==
MIME-Version: 1.0
X-Received: by 10.202.175.146 with SMTP id y140mr10476806oie.79.1419192467820;  Sun, 21 Dec 2014 12:07:47 -0800 (PST)
Received: by 10.202.169.209 with HTTP; Sun, 21 Dec 2014 12:07:47 -0800 (PST)
Date: Sun, 21 Dec 2014 12:07:47 -0800
Message-ID: <CAA93jw5+e0u=aHCjaBjwKrqdvhfwx5MbvG2yuKvBnOtHk_5jQg@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: HOMENET <homenet@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/LvQzfsTaQ2vcLFNQ6R5w8d8uHL0
Subject: [homenet] udp-lite support?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Dec 2014 20:07:51 -0000

I am growing concerned by the widespread adoption of udp as a baseline
transport for so many protocols (webrtc, bittorrent maelstrom, etc.)
Certainly a couple traceroutes alone could blow up my udp nat table on
a busy router with open udp ports as can something as simple as trying
to do reverse lookups on everything in a /64 - I long ago had to start
closing udp ports on the firewall in under 30 seconds - (dns over ipv6
fixes this thoroughly, thank ghu), but having thoroughly blown up my
world just now with mosh-multipath...

I see udplite support is mandated by some homenet rfc or another.

udp-lite, unlike sctp, it is simple enough to work everywhere, but a
lot of its original use case (unencrypted rtp) is gone.

What, if anything is it actually used for today? Are there any test
suites or large scale tests/testers that have gone and looked at its
actual routability over the ipv4 and ipv6 Internet?

anyway, udplite seemed like a good fit for a userspace vpn or
something like mosh, so (since I was unable to find any comprehensive
udplite test suites)  I went and implemented that as a test for fun...

https://plus.google.com/u/0/107942175615993706558/posts/LDNmr8PWkFg

and given how easy it is to hack in will probably try to add it to
netperf-wrapper. Over the holidays. Maybe.

--=20
Dave T=C3=A4ht

http://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talk


From nobody Sun Dec 21 12:24:47 2014
Return-Path: <dave.taht@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA7321A878E for <homenet@ietfa.amsl.com>; Sun, 21 Dec 2014 12:24: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 fc2a6CgtfdwE for <homenet@ietfa.amsl.com>; Sun, 21 Dec 2014 12:24:45 -0800 (PST)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D18D91A8788 for <homenet@ietf.org>; Sun, 21 Dec 2014 12:24:44 -0800 (PST)
Received: by mail-ob0-f178.google.com with SMTP id gq1so18798506obb.9 for <homenet@ietf.org>; Sun, 21 Dec 2014 12:24:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=3sm2/lI2yzWJIvnEg1xoaB/V46ZuvrgvEYuNxBCkq88=; b=yTTw8b4CRscDhMk338vq0JGB6p1Bqr+9PKWHdkzLY+oenodLjz0hH3puJlWp4rZIsr KE+Ro3LurKtpFJnoMryW7LFHif/msDp0UqexrcI1Slym2ey2WbOnRoncRhnqRNrGTs73 +JvgbHgdMmL5dkSHEAmNjE52bzIjjtd3VFvapCPUejRZbntWbGh4AxP/GC7yw0Daw4jI hy0AIvuDauVRV0QdEE18ODE5XQiUEfkZptQIk+SQQqqGq2NPsuUzeqjYWsJJHcRmQsSv WSHD7yLgSSwZHmuZo3Y3ekIlvqFfOLmlMkAgzjEybagog3DjbkWtEd5PhZk/PtLIPLbG +8DA==
MIME-Version: 1.0
X-Received: by 10.182.120.10 with SMTP id ky10mr11212182obb.68.1419193484113;  Sun, 21 Dec 2014 12:24:44 -0800 (PST)
Received: by 10.202.169.209 with HTTP; Sun, 21 Dec 2014 12:24:44 -0800 (PST)
In-Reply-To: <87h9wou6t6.wl-jch@pps.univ-paris-diderot.fr>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com> <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr> <54939DA2.60602@gmail.com> <7izjajh7gm.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqDTnyzH4ehKr9kizKM7H8J8y7=GTQxMJOcuBQyd8Nb5w@mail.gmail.com> <C72807F4-88D6-4040-8BF6-94BAD5B87AB0@pps.univ-paris-diderot.fr> <CAGnRvuos29bkYMChXUaOGoxrtY2ZNiJFXDVu==SaiwiD-zw5xA@mail.gmail.com> <87h9wou6t6.wl-jch@pps.univ-paris-diderot.fr>
Date: Sun, 21 Dec 2014 12:24:44 -0800
Message-ID: <CAA93jw4ZNtGFhzeXMm8oG+u+XAK50LWG28fJM3rBtAZZG2_xxQ@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/9OqVZpsEr93gKft_UlqU7HHsfac
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>, Henning Rogge <hrogge@gmail.com>, HOMENET <homenet@ietf.org>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 21 Dec 2014 20:24:46 -0000

On Sun, Dec 21, 2014 at 11:44 AM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
>>>> You might also need to combine the features of the gateway with the
>>>> metric(s) of the path to the gateway.
>
>>> I do end-to-end measurements in my mosh implementation, so we should
>>> not have the problem.
>
>> Does this really scale well?
>
> How well do we need it to scale?  Three addresses per host?  A dozen?
> A hundred?  (Per host, mind you -- not per router.)
>
> The probes Matthieu's code is sending are less than 90 bytes each.  This
> means that if the client and the server have three addresses each, each
> probing episode consists of a burst of 9 packets totalling less than one
> full Ethernet frame.  (18 if you count the replies.)
>
> On the other hand, if we end up having hundreds of addresses on every
> host, the strategy will need to be rethought.  Dave is currently playing
> with a network where each host has 10 addresses of different kinds, and
> he's trying to work out heuristics to limit the number of probes.  I'd
> personally prefer to gather some empirical data before we start optimisin=
g
> things.

That has been a very long, and interesting, private thread, and I should
summarize here but Ive been awake 24 hours hacking on this -

The particular test server I have is an 8 port rangeley router with 36
projected ip
addresses, connected to a test client with 12, which is rather a lot
of connections to
probe and sort through. Amazingly mosh-multipath, does, indeed, work
in this case.

(And mosh is the greatest thing since sliced bread already for a
beleagured sysadmin type that endures
frequent mobility events and periods of disconnectivity!)

...

I have been also hacking on odhcpd and hnetd and a few other end
products of this wg to see how far they are along.  (my testbed plan
was to have 5 source specific gateways working across about 70
routers)

I have had to file multiple bugs on all the dhcpv6 clients, and be
annoyed at comcast for sending ras under a minute intervals,
thoroughly break ubuntu and openwrt,  and work around various other
problems, but overall things are much better than they were last
month, and almost as fast as I file bugs, they get fixed.

see various open and closed bugs on https://github.com/sbyx/hnetd/issues/24
https://github.com/sbyx/odhcp6c/issues/27

and rants about it all and some of the tools I have been using on my g+

https://plus.google.com/u/0/107942175615993706558/posts/CsGyyJspjVK

But everything homenet-ish is looking very promising. I guess I have
to go compile a couple boxes with mptcp support soon.

so far babel has been dealing with failing over default gateways going
up and down and source specific routes through a very complex network
beautifully, even though only 1/3 the network is source specific
enabled. (and updating the parts remaining involves climbing a lot of
trees. in the rain. Preferably with a totally baked version of openwrt
chaos calmer)

> -- Juliusz
>
>



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Sun Dec 21 16:23:47 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EABB11A000E for <homenet@ietfa.amsl.com>; Sun, 21 Dec 2014 16:23:45 -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 BhHv1RkFKlHS for <homenet@ietfa.amsl.com>; Sun, 21 Dec 2014 16:23:44 -0800 (PST)
Received: from mail-pd0-x231.google.com (mail-pd0-x231.google.com [IPv6:2607:f8b0:400e:c02::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EB3A1A000D for <homenet@ietf.org>; Sun, 21 Dec 2014 16:23:44 -0800 (PST)
Received: by mail-pd0-f177.google.com with SMTP id ft15so4718876pdb.36 for <homenet@ietf.org>; Sun, 21 Dec 2014 16:23:43 -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=JfSWqpwjki3z/jm0byldck3VOakta9Aprcb0P/AMFBo=; b=MzZPLVXBEEzpK9Cc6NFktV2MW9if+kVcgDOy+C+5cSLRHmtTGodRP19VfM8orJ6QLz sG2ZrYpSQzX55CjIdHa2YLF9M7vuXQLLTaZ/kki044wo7nFFaDmXe2oWoXbjbcjmwwpN UoqRotEEu6nPNKsMixNEhgGwJ0Y5rjSLc5c5EQLjhnQffjOaRdRvhRkMS8Fq0R7+z2lb etnD8HkSov25aQIv1STbbxC2/4F8DKXg3TCoaU2cdQN/O9WbUbgRiIVJT2A0n4Gvagp4 iJFpVuLyrljbHhZDXEJVuDziFFkm3E3PntfZzsoemrKQYbfiPkiOO2jnkAF102SpHAdC TafQ==
X-Received: by 10.68.230.10 with SMTP id su10mr30401628pbc.129.1419207823712;  Sun, 21 Dec 2014 16:23:43 -0800 (PST)
Received: from ?IPv6:2406:e007:4f6a:1:28cc:dc4c:9703:6781? ([2406:e007:4f6a:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id vc6sm15478798pbc.66.2014.12.21.16.23.39 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 21 Dec 2014 16:23:42 -0800 (PST)
Message-ID: <54976489.8080400@gmail.com>
Date: Mon, 22 Dec 2014 13:23:37 +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:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com> <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr> <54939DA2.60602@gmail.com> <7izjajh7gm.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqDTnyzH4ehKr9kizKM7H8J8y7=GTQxMJOcuBQyd8Nb5w@mail.gmail.com> <C72807F4-88D6-4040-8BF6-94BAD5B87AB0@pps.univ-paris-diderot.fr> <CAGnRvuos29bkYMChXUaOGoxrtY2ZNiJFXDVu==SaiwiD-zw5xA@mail.gmail.com> <87h9wou6t6.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87h9wou6t6.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/aV0UuRRLL-WMeBDNpkwaCPoEfR0
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>, Henning Rogge <hrogge@gmail.com>, HOMENET <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Dec 2014 00:23:46 -0000

On 22/12/2014 08:44, Juliusz Chroboczek wrote:
>>>> You might also need to combine the features of the gateway with the
>>>> metric(s) of the path to the gateway.
> 
>>> I do end-to-end measurements in my mosh implementation, so we should
>>> not have the problem.
> 
>> Does this really scale well?
> 
> How well do we need it to scale?  Three addresses per host?  A dozen?
> A hundred?  (Per host, mind you -- not per router.)
> 
> The probes Matthieu's code is sending are less than 90 bytes each.  This
> means that if the client and the server have three addresses each, each
> probing episode consists of a burst of 9 packets totalling less than one
> full Ethernet frame.  (18 if you count the replies.)
> 
> On the other hand, if we end up having hundreds of addresses on every
> host, the strategy will need to be rethought.  Dave is currently playing
> with a network where each host has 10 addresses of different kinds, and
> he's trying to work out heuristics to limit the number of probes.  I'd
> personally prefer to gather some empirical data before we start optimising
> things.

A good thought. From the point of view of usefulness, more than two or
three addresses per host seems pretty pointless (that is at any rate
what draft-naderi-ipv6-probing told us). Probe results should probably
be cached for a while and interpreted per-prefix not per-address.

   Brian


From nobody Mon Dec 22 03:54:30 2014
Return-Path: <gert@Space.Net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 755591A8A61 for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 03:54:27 -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, 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 fsUn8XIVypb3 for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 03:54:25 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (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 EC1F81A0378 for <homenet@ietf.org>; Mon, 22 Dec 2014 03:54:23 -0800 (PST)
X-Original-To: homenet@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id F024A60A96 for <homenet@ietf.org>; Mon, 22 Dec 2014 12:54:20 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 98F8360A8F for <homenet@ietf.org>; Mon, 22 Dec 2014 12:54:20 +0100 (CET)
Received: (qmail 29823 invoked by uid 1007); 22 Dec 2014 12:54:20 +0100
Date: Mon, 22 Dec 2014 12:54:20 +0100
From: Gert Doering <gert@space.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <20141222115420.GP28745@Space.Net>
References: <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com> <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr> <54939DA2.60602@gmail.com> <7izjajh7gm.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqDTnyzH4ehKr9kizKM7H8J8y7=GTQxMJOcuBQyd8Nb5w@mail.gmail.com> <C72807F4-88D6-4040-8BF6-94BAD5B87AB0@pps.univ-paris-diderot.fr> <CAGnRvuos29bkYMChXUaOGoxrtY2ZNiJFXDVu==SaiwiD-zw5xA@mail.gmail.com> <87h9wou6t6.wl-jch@pps.univ-paris-diderot.fr> <54976489.8080400@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <54976489.8080400@gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/RviVXd00WWplw0dgiR3ylm86avg
Cc: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Michael Richardson <mcr+ietf@sandelman.ca>, Dave Taht <dave.taht@gmail.com>, Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>, Henning Rogge <hrogge@gmail.com>, HOMENET <homenet@ietf.org>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Dec 2014 11:54:27 -0000

Hi,

On Mon, Dec 22, 2014 at 01:23:37PM +1300, Brian E Carpenter wrote:
> Probe results should probably
> be cached for a while and interpreted per-prefix not per-address.

I agree in principle, just wonder how big the prefix boundary for 
"per-prefix" should be...  (and I can make cases for "a /32 should be
good enough" or "maybe /48 or even /64 level"...)

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From nobody Mon Dec 22 04:49:15 2014
Return-Path: <markus.stenberg@iki.fi>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D31EC1A8ACC for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 04:49:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] 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 AsNhKG-aT6HG for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 04:49:10 -0800 (PST)
Received: from jenni2.inet.fi (mta-out1.inet.fi [62.71.2.195]) by ietfa.amsl.com (Postfix) with ESMTP id 91F101A039D for <homenet@ietf.org>; Mon, 22 Dec 2014 04:49:09 -0800 (PST)
Received: from [192.168.43.129] (80.220.64.126) by jenni2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 546BDD5303D74CD7; Mon, 22 Dec 2014 14:48:55 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <20141222115420.GP28745@Space.Net>
Date: Mon, 22 Dec 2014 12:48:50 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <4221B7E1-C6EF-4A66-9AFD-7DAB9F4EF94B@iki.fi>
References: <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com> <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr> <54939DA2.60602@gmail.com> <7izjajh7gm.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqDTnyzH4ehKr9kizKM7H8J8y7=GTQxMJOcuBQyd8Nb5w@mail.gmail.com> <C72807F4-88D6-4040-8BF6-94BAD5B87AB0@pps.univ-paris-diderot.fr> <CAGnRvuos29bkYMChXUaOGoxrtY2ZNiJFXDVu==SaiwiD-zw5xA@mail.gmail.com> <87h9wou6t6.wl-jch@pps.univ-paris-diderot.fr> <54976489.8080400@gmail.com> <20141222115420.GP28745@Space.Net>
To: Gert Doering <gert@space.net>
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/TPL-NxU5JS7aRUW63kz-AnF0mD4
Cc: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Michael Richardson <mcr+ietf@sandelman.ca>, Markus Stenberg <markus.stenberg@iki.fi>, Dave Taht <dave.taht@gmail.com>, Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>, Henning Rogge <hrogge@gmail.com>, HOMENET <homenet@ietf.org>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Dec 2014 12:49:12 -0000

> On 22.12.2014, at 11.54, Gert Doering <gert@space.net> wrote:
> On Mon, Dec 22, 2014 at 01:23:37PM +1300, Brian E Carpenter wrote:
>> Probe results should probably
>> be cached for a while and interpreted per-prefix not per-address.
> I agree in principle, just wonder how big the prefix boundary for=20
> "per-prefix" should be...  (and I can make cases for "a /32 should be
> good enough=E2=80=9D or "maybe /48 or even /64 level"...)

I would say whatever the prefix length is that is advertised on the link =
(=3DSLAAC=3D/64 typically). Of course, you probably receive savings of =
only 2x by doing this (for example, temp + perm address). One _could_ =
argue for larger prefixes if you could somehow intuit that they are from =
same ISP and use same uplink, but what is preventing ISP from applying =
different traffic shaping on them if they for some reason give you =
multiple prefixes?

So for simplicity=E2=80=99s sake, I think that the =
per-prefix-on-link-granularity is the sane level.

I have been thinking about how to abstract this stuff from applications =
too; ultimately there are two semi-separate things that need to happen;

- SA selection
- DA selection (+IPv4/IPv6)

and in case of TCP apps, assuming you are willing to skip DA selection =
(for apps that do not care about it), you could easily enough make =
SA-choice-only ~HE that would work with every app, by doing simply =
multiple connections in the background and just using the one that =
succeeds connecting fastest. This could be patched inside C library (or =
overridden in the C library using LD_PRELOAD) to get it working on any =
app without app level changes. Of course bonus points for storing =
results for awhile so no need to probe on every connect().

For UDP, you seem need app support in any case.=20

For more ambitious TCP solutions, such as for multiple DA (or =
simultaneous multiple SA) you ultimately want mptcp anyway, and failing =
that, connect2() with DNS name argument + IPv4/IPv6 agnosticity. But =
changing SA/DA on the fly in TCP is not really an option, so you can do =
it only on per-connection basis probably which more or less sucks if you =
have long-lived connections. (Not so big problem in most web browsing I =
guess.)

Cheers,

-Markus=


From nobody Mon Dec 22 05:05:26 2014
Return-Path: <gert@Space.Net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7C611A8B84 for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 05:05:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 RldyL4W4uUuL for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 05:05:03 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (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 9484C1A8AE9 for <homenet@ietf.org>; Mon, 22 Dec 2014 05:05:02 -0800 (PST)
X-Original-To: homenet@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id CA02560A84 for <homenet@ietf.org>; Mon, 22 Dec 2014 14:04:58 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 74D4760A62 for <homenet@ietf.org>; Mon, 22 Dec 2014 14:04:58 +0100 (CET)
Received: (qmail 41495 invoked by uid 1007); 22 Dec 2014 14:04:58 +0100
Date: Mon, 22 Dec 2014 14:04:58 +0100
From: Gert Doering <gert@space.net>
To: Markus Stenberg <markus.stenberg@iki.fi>
Message-ID: <20141222130458.GR28745@Space.Net>
References: <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr> <54939DA2.60602@gmail.com> <7izjajh7gm.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqDTnyzH4ehKr9kizKM7H8J8y7=GTQxMJOcuBQyd8Nb5w@mail.gmail.com> <C72807F4-88D6-4040-8BF6-94BAD5B87AB0@pps.univ-paris-diderot.fr> <CAGnRvuos29bkYMChXUaOGoxrtY2ZNiJFXDVu==SaiwiD-zw5xA@mail.gmail.com> <87h9wou6t6.wl-jch@pps.univ-paris-diderot.fr> <54976489.8080400@gmail.com> <20141222115420.GP28745@Space.Net> <4221B7E1-C6EF-4A66-9AFD-7DAB9F4EF94B@iki.fi>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Oj0Uz+Jh7vTaw4cF"
Content-Disposition: inline
In-Reply-To: <4221B7E1-C6EF-4A66-9AFD-7DAB9F4EF94B@iki.fi>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/O8bKBE9BhN7XV6BLYLK3oi9f8uQ
Cc: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Michael Richardson <mcr+ietf@sandelman.ca>, Dave Taht <dave.taht@gmail.com>, Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>, Henning Rogge <hrogge@gmail.com>, HOMENET <homenet@ietf.org>, Gert Doering <gert@space.net>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Dec 2014 13:05:11 -0000

--Oj0Uz+Jh7vTaw4cF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Mon, Dec 22, 2014 at 12:48:50PM +0000, Markus Stenberg wrote:
> >> be cached for a while and interpreted per-prefix not per-address.
> > I agree in principle, just wonder how big the prefix boundary for=20
> > "per-prefix" should be...  (and I can make cases for "a /32 should be
> > good enough??? or "maybe /48 or even /64 level"...)
>=20
> I would say whatever the prefix length is that is advertised on the link =
(=3DSLAAC=3D/64 typically). Of course, you probably receive savings of only=
 2x by doing this (for example, temp + perm address). One _could_ argue for=
 larger prefixes if you could somehow intuit that they are from same ISP an=
d use same uplink, but what is preventing ISP from applying different traff=
ic shaping on them if they for some reason give you multiple prefixes?

I was actually looking the other way, destination space - if you know
that for, say, 2001:608::1 the path over ISP A is "better" (for whatever
local metric), everything else inside 2001:608::/32 will have the same
result for the same metric, as it's really a single network in a single
city with identical routing policy for all of the /32.

But this is just this particular ISP, while others might have vastly
different routing policyies for different /48s out of the same /32, like
"Akamai"...

> So for simplicity???s sake, I think that the per-prefix-on-link-granulari=
ty is the sane level.

I have the nagging suspicion that "permanent + temp addr" wasn't even on
Brian's radar here (and might not actually be relevant :-) - if you have te=
mp
addresses, you don't connect outbound from the permanent address in the=20
same prefix, no?).

> I have been thinking about how to abstract this stuff from applications t=
oo; ultimately there are two semi-separate things that need to happen;
>=20
> - SA selection
> - DA selection (+IPv4/IPv6)
>=20
> and in case of TCP apps, assuming you are willing to skip DA
> selection (for apps that do not care about it), you could easily
> enough make SA-choice-only ~HE that would work with every app, by
> doing simply multiple connections in the background and just using
> the one that succeeds connecting fastest.

Mmmh, interesting idea, yes.

Gert Doering
        -- NetMaster
--=20
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279

--Oj0Uz+Jh7vTaw4cF
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIVAwUBVJgW+t9WwGXkzn/FAQL73w/7BJYekaYbY5CRZaL9xQkico8PQzT9u7zE
g3atVEdEHJu7hjkLdPq3tM0q1M8PFnGbCOji49JrMJ0qNGo2Okz7dNPEiQ/3b6D8
PyGC92g81UPQpvomgBOfSVgLU0neZORGaBpndmzbqn70dCXqYv0fXgyzre/cMxhY
vpBvLoJmTmLT458F0zUJEokE2Ble8uHlnZoA/Faz0bbp2H1mIv+ggMLzSUFAVDOD
O3pFlpd0m00KzsmcaLddnrca7H3qp4SH8leFFj1T1WwrfNeQklk/wWzNobtkSjVC
7+rFDBaguQDJfvDBCogR0Qgwl6IkwFCF8X5E9vCHnpng4uAIU6QhTXWjLNHjYuQt
9/r87yeIZDD7xIUWMXX4VnNEiY5YNhlFc7KIFD2U8XuydoU8v4qfXmb11/bKCKqW
Z/vpnmQjCS3jgz9taXAi60yAzFGjBUcIZHvJY9YJpMrOf9No5VvyeVfMGcex9Rq6
+DjuQ1yt9b3aLuGNsbxzNRdKMJN+tNBF/YayMdrtcP964aBuYbI3AoLX/dbvhVEh
Qz3P3IRumyJedaN2xS6JjWDr1MH6xD6n8iyyB325qqq3mrflocGbV933oGxWh3Yb
zMZFrBa66s9t5xwBI2PYE8bKKyH4FUkSqLdGAUKhV4gqEN0nppojkdRAJGiJLkFQ
tjo4ycruO6Y=
=Pu7W
-----END PGP SIGNATURE-----

--Oj0Uz+Jh7vTaw4cF--


From nobody Mon Dec 22 05:13:45 2014
Return-Path: <markus.stenberg@iki.fi>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC1631A8AD2 for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 05:13:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] 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 EgFs1pRPatpf for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 05:13:42 -0800 (PST)
Received: from kirsi1.inet.fi (mta-out1.inet.fi [62.71.2.227]) by ietfa.amsl.com (Postfix) with ESMTP id 817DC1A03A7 for <homenet@ietf.org>; Mon, 22 Dec 2014 05:13:42 -0800 (PST)
Received: from [192.168.43.129] (80.220.64.126) by kirsi1.inet.fi (8.5.142.08) (authenticated as stenma-47) id 546BDD4B03D88CEE; Mon, 22 Dec 2014 15:13:31 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <20141222130458.GR28745@Space.Net>
Date: Mon, 22 Dec 2014 13:13:27 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <E490FDF9-56B8-47F0-B743-FAD9FD0F778E@iki.fi>
References: <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr> <54939DA2.60602@gmail.com> <7izjajh7gm.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqDTnyzH4ehKr9kizKM7H8J8y7=GTQxMJOcuBQyd8Nb5w@mail.gmail.com> <C72807F4-88D6-4040-8BF6-94BAD5B87AB0@pps.univ-paris-diderot.fr> <CAGnRvuos29bkYMChXUaOGoxrtY2ZNiJFXDVu==SaiwiD-zw5xA@mail.gmail.com> <87h9wou6t6.wl-jch@pps.univ-paris-diderot.fr> <54976489.8080400@gmail.com> <20141222115420.GP28745@Space.Net> <4221B7E1-C6EF-4A66-9AFD-7DAB9F4EF94B@iki.fi> <20141222130458.GR28745@Space.Net>
To: Gert Doering <gert@space.net>
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/9cRSABkcbFKws-y9CssEZJz37lM
Cc: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Michael Richardson <mcr+ietf@sandelman.ca>, Markus Stenberg <markus.stenberg@iki.fi>, Dave Taht <dave.taht@gmail.com>, Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>, Henning Rogge <hrogge@gmail.com>, HOMENET <homenet@ietf.org>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Dec 2014 13:13:44 -0000

> On 22.12.2014, at 13.04, Gert Doering <gert@space.net> wrote:
> I was actually looking the other way, destination space - if you know
> that for, say, 2001:608::1 the path over ISP A is "better" (for =
whatever
> local metric), everything else inside 2001:608::/32 will have the same
> result for the same metric, as it's really a single network in a =
single
> city with identical routing policy for all of the /32.
>=20
> But this is just this particular ISP, while others might have vastly
> different routing policyies for different /48s out of the same /32, =
like
> =E2=80=9CAkamai"...

Yeah, on DA side, I would not venture to aggregate any results _without_ =
local data to back it up. So what I would do there is basically gather =
(ideally on system level and not per application) statistics on =
difference in the relevant measures (rtt, jitter, bandwidth depending on =
what you care about) towards different addresses, and try to notice =
where there is significant change and guess meaningful DA prefix lengths =
for particular SA based on that.

It does not sound too fun either :)

>> So for simplicity???s sake, I think that the =
per-prefix-on-link-granularity is the sane level.
> I have the nagging suspicion that "permanent + temp addr" wasn't even =
on
> Brian's radar here (and might not actually be relevant :-) - if you =
have temp
> addresses, you don't connect outbound from the permanent address in =
the=20
> same prefix, no?).

Depends on how stupid (=3Dor portable and standard-API-abiding) =
applications you have. Typical stack (look at API in RFCs for example) =
does not expose address lifetimes or {permanent,temp} address type to =
applications, as the stack is =E2=80=98just supposed to do the SA=E2=80=99=
 on behalf of applications. Now that we are discussing either libraries =
or applications getting smarter, there are potential problems there.. :p

Sure you can get that with OS specific hackery, but the standardized API =
is woefully inadequate. And IETF is to blame here to some degree, as the =
IPv6 APIs come mostly from here.

(Yeah, I guess you can recognize temp/perm address by looking at the =
bits in the app but ugh..)

Cheers,

-Markus=


From nobody Mon Dec 22 05:50:25 2014
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C3231A8F3B for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 05:50:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] 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 3vKyhGwnNnaK for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 05:50:20 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 73DB01A8F38 for <homenet@ietf.org>; Mon, 22 Dec 2014 05:50:20 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/46573) with ESMTP id sBMDoHYx028524; Mon, 22 Dec 2014 14:50:17 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 57BC41B617; Mon, 22 Dec 2014 14:50:17 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id KhnJLh5n8v3r; Mon, 22 Dec 2014 14:50:16 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id DED481B62A; Mon, 22 Dec 2014 14:50:15 +0100 (CET)
Date: Mon, 22 Dec 2014 14:50:16 +0100
Message-ID: <87egrr94kn.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <54976489.8080400@gmail.com>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com> <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr> <54939DA2.60602@gmail.com> <7izjajh7gm.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqDTnyzH4ehKr9kizKM7H8J8y7=GTQxMJOcuBQyd8Nb5w@mail.gmail.com> <C72807F4-88D6-4040-8BF6-94BAD5B87AB0@pps.univ-paris-diderot.fr> <CAGnRvuos29bkYMChXUaOGoxrtY2ZNiJFXDVu==SaiwiD-zw5xA@mail.gmail.com> <87h9wou6t6.wl-jch@pps.univ-paris-diderot.fr> <54976489.8080400@gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Mon, 22 Dec 2014 14:50:17 +0100 (CET)
X-Miltered: at korolev with ID 54982199.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54982199.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54982199.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/a1ajIClL9ldjleuvfKLa7nPwt-A
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>, Henning Rogge <hrogge@gmail.com>, HOMENET <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Dec 2014 13:50:22 -0000

> Probe results should probably [be] interpreted per-prefix not per-address.

Hmm.  Interesting idea.

I can imagine some scenarios where it could break -- Ethernet bridged with
Wifi (OpenWRT style), mesh networks, or simply a congested, bufferbloated
interface.  I'm not sure how common such scenarios are.

(I'm also not sure how common it is for a host to connect to multiple
peers on the same subnet.)

Empirical data, anyone?

-- Juliusz


From nobody Mon Dec 22 06:11:38 2014
Return-Path: <dave.taht@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31AB11A6FB8 for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 06:11:37 -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 rhbbH4yI0BRY for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 06:11:35 -0800 (PST)
Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com [IPv6:2607:f8b0:4003:c06::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E1C51A883C for <homenet@ietf.org>; Mon, 22 Dec 2014 06:11:35 -0800 (PST)
Received: by mail-oi0-f52.google.com with SMTP id h136so9958127oig.11 for <homenet@ietf.org>; Mon, 22 Dec 2014 06:11:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=DW/XR8PIMOuA6o9/KApJhRn7hPaKrMYggrPHCoB4ACM=; b=poN5qzz6ccSLnARhGBJYn6HtqkLIp/b7hpeyiW090aj4YyKT4P12XJg/ccfiqohLUn 2LTagXyOP2iB/Q3LsLqtinCuhyO0tPFGRn/irFNx0Yx07sS7jJTK/kzKhomqYWyDmmtn U0DiUY6WQPkIsBZBLBYkUB04hTRrOVmrVHiAS2Oc1LpAACvXnUabYnk7cNnrWRzS4293 kNiIdEXy/gcPPdBPass9dtHA6gECrdROE6FRoQl7mGUzIAt+i58EwRk81ndNKlIAJ0z7 DpRThcZyI0rDxNjfuawhzPLfQPSGGM6YAEC/kbAMO90QUKzw7cOpHbOYxT6wz/1O6wSw TB9A==
MIME-Version: 1.0
X-Received: by 10.60.84.196 with SMTP id b4mr13137725oez.49.1419257494307; Mon, 22 Dec 2014 06:11:34 -0800 (PST)
Received: by 10.202.169.209 with HTTP; Mon, 22 Dec 2014 06:11:34 -0800 (PST)
In-Reply-To: <87egrr94kn.wl-jch@pps.univ-paris-diderot.fr>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com> <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr> <54939DA2.60602@gmail.com> <7izjajh7gm.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqDTnyzH4ehKr9kizKM7H8J8y7=GTQxMJOcuBQyd8Nb5w@mail.gmail.com> <C72807F4-88D6-4040-8BF6-94BAD5B87AB0@pps.univ-paris-diderot.fr> <CAGnRvuos29bkYMChXUaOGoxrtY2ZNiJFXDVu==SaiwiD-zw5xA@mail.gmail.com> <87h9wou6t6.wl-jch@pps.univ-paris-diderot.fr> <54976489.8080400@gmail.com> <87egrr94kn.wl-jch@pps.univ-paris-diderot.fr>
Date: Mon, 22 Dec 2014 06:11:34 -0800
Message-ID: <CAA93jw5GdG0=mNTEQkC58YW_9n22z8oLwp5bX2tO-4d0aJBKiQ@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/VS-plGnWW2uZw8JJ6z9CcEVQaPU
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>, Henning Rogge <hrogge@gmail.com>, HOMENET <homenet@ietf.org>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Dec 2014 14:11:37 -0000

On Mon, Dec 22, 2014 at 5:50 AM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
>> Probe results should probably [be] interpreted per-prefix not per-addres=
s.
>
> Hmm.  Interesting idea.

+1. Pick one of dhcp, slaac, or privacy within a prefix with the best
lifetime, maybe?

> I can imagine some scenarios where it could break -- Ethernet bridged wit=
h
> Wifi (OpenWRT style),

expound?

>mesh networks,

?

>or simply a congested, bufferbloated
> interface.

It depends on how you get to that interface.

> I'm not sure how common such scenarios are.
>
> (I'm also not sure how common it is for a host to connect to multiple
> peers on the same subnet.)
>
> Empirical data, anyone?

We are in a brave new world where some providers (or their modems) are
handing out prefix delegations with a dazzlingly short lifetime of
15sec, apparently...

https://github.com/sbyx/hnetd/issues/24



>
> -- Juliusz



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Mon Dec 22 06:18:55 2014
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C0681A6FB8 for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 06:18:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] 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 9SU9hHdrV86j for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 06:18:51 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 757FF1A03A7 for <homenet@ietf.org>; Mon, 22 Dec 2014 06:18:51 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/46573) with ESMTP id sBMEIn59007633; Mon, 22 Dec 2014 15:18:49 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 4DA501B632; Mon, 22 Dec 2014 15:18:49 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id Pou-dAeWUaYa; Mon, 22 Dec 2014 15:18:48 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 192DC1B62F; Mon, 22 Dec 2014 15:18:48 +0100 (CET)
Date: Mon, 22 Dec 2014 15:18:47 +0100
Message-ID: <87a92f9394.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Dave Taht <dave.taht@gmail.com>
In-Reply-To: <CAA93jw5GdG0=mNTEQkC58YW_9n22z8oLwp5bX2tO-4d0aJBKiQ@mail.gmail.com>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com> <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr> <54939DA2.60602@gmail.com> <7izjajh7gm.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqDTnyzH4ehKr9kizKM7H8J8y7=GTQxMJOcuBQyd8Nb5w@mail.gmail.com> <C72807F4-88D6-4040-8BF6-94BAD5B87AB0@pps.univ-paris-diderot.fr> <CAGnRvuos29bkYMChXUaOGoxrtY2ZNiJFXDVu==SaiwiD-zw5xA@mail.gmail.com> <87h9wou6t6.wl-jch@pps.univ-paris-diderot.fr> <54976489.8080400@gmail.com> <87egrr94kn.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw5GdG0=mNTEQkC58YW_9n22z8oLwp5bX2tO-4d0aJBKiQ@mail.gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Mon, 22 Dec 2014 15:18:49 +0100 (CET)
X-Miltered: at korolev with ID 54982849.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54982849.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54982849.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/0XjVw3mBp7LMLaLoTc_B0VZcnwg
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Dec 2014 14:18:52 -0000

>> I can imagine some scenarios where it could break -- Ethernet bridged with
>> Wifi (OpenWRT style),

If you have two hosts connected to an OpenWRT router, one over Wifi and
one over Ethernet, they could have very different performance
characteristics while being on the same prefix.

> expound?
>
>> mesh networks,
>
> ?

If you have two hosts connected at different places to the same mesh
network, they could have very different performance characteristics while
having addresses from the same /64.

-- Juliusz


From nobody Mon Dec 22 06:22:59 2014
Return-Path: <gert@Space.Net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 535171A8F4A for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 06:22:57 -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, 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 s2kXmVUWF5xH for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 06:22:55 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (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 230BE1A8F4C for <homenet@ietf.org>; Mon, 22 Dec 2014 06:22:55 -0800 (PST)
X-Original-To: homenet@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 6F26560A62 for <homenet@ietf.org>; Mon, 22 Dec 2014 15:22:53 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 362A26010D for <homenet@ietf.org>; Mon, 22 Dec 2014 15:22:53 +0100 (CET)
Received: (qmail 55398 invoked by uid 1007); 22 Dec 2014 15:22:53 +0100
Date: Mon, 22 Dec 2014 15:22:53 +0100
From: Gert Doering <gert@space.net>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Message-ID: <20141222142253.GX28745@Space.Net>
References: <54939DA2.60602@gmail.com> <7izjajh7gm.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqDTnyzH4ehKr9kizKM7H8J8y7=GTQxMJOcuBQyd8Nb5w@mail.gmail.com> <C72807F4-88D6-4040-8BF6-94BAD5B87AB0@pps.univ-paris-diderot.fr> <CAGnRvuos29bkYMChXUaOGoxrtY2ZNiJFXDVu==SaiwiD-zw5xA@mail.gmail.com> <87h9wou6t6.wl-jch@pps.univ-paris-diderot.fr> <54976489.8080400@gmail.com> <87egrr94kn.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw5GdG0=mNTEQkC58YW_9n22z8oLwp5bX2tO-4d0aJBKiQ@mail.gmail.com> <87a92f9394.wl-jch@pps.univ-paris-diderot.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87a92f9394.wl-jch@pps.univ-paris-diderot.fr>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/oxPUgEI8QZ_NPTdPQu-ZBpCF2Nw
Cc: HOMENET <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Dec 2014 14:22:57 -0000

Hi,

On Mon, Dec 22, 2014 at 03:18:47PM +0100, Juliusz Chroboczek wrote:
> If you have two hosts connected at different places to the same mesh
> network, they could have very different performance characteristics while
> having addresses from the same /64.

Indeed, that's the other end of the diversity spectrum (vs. "all hosts in
our /32 have roughly the same network characteristics").

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From nobody Mon Dec 22 11:07:53 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D7A41A1BD6 for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 11:07:51 -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 w60taf3dPuLH for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 11:07:50 -0800 (PST)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 218631A1EFD for <homenet@ietf.org>; Mon, 22 Dec 2014 11:07:49 -0800 (PST)
Received: by mail-pd0-f170.google.com with SMTP id v10so6336662pde.15 for <homenet@ietf.org>; Mon, 22 Dec 2014 11:07:48 -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=tld6y9Fuv+UPos2skbn0yA3n9+fiI9PTKCWiti4CwGs=; b=QckX4UR5C4Yn7xze7Zo4STfBN4vJp6WeNsg6QUyrt2aP5c09PFpcstSezycb3etKSp F2hOkf7HeP/14VrbmfNL/hlG7I6eHB6RzHed5kFh9CigZ9Lk1m32MixKEDb4gYZOs9xO oogY273tFS+/7AcLZ8GFa+0C0wGGD1AAdJCrcRERl1KrtEo4X2eCnGO6xq4feOnxZdDI Pa604RNycbMtDoF5dUIx6wucUglvzu0d39WhHIxRLhXszpkF55DqqGsX/CR7IlJoL3el 8EEOJFgBIGZV/0+8m6sd+vZPi6++kLkup4b0OdAqln0Fuycb0yNHQSPYToHOe6PyKw1f +/JQ==
X-Received: by 10.66.242.238 with SMTP id wt14mr37525778pac.60.1419275268334;  Mon, 22 Dec 2014 11:07:48 -0800 (PST)
Received: from ?IPv6:2406:e007:59db:1:28cc:dc4c:9703:6781? ([2406:e007:59db:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id oi5sm17948608pbb.7.2014.12.22.11.07.45 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 22 Dec 2014 11:07:47 -0800 (PST)
Message-ID: <54986C01.1070703@gmail.com>
Date: Tue, 23 Dec 2014 08:07:45 +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:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Gert Doering <gert@space.net>
References: <54939DA2.60602@gmail.com> <7izjajh7gm.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqDTnyzH4ehKr9kizKM7H8J8y7=GTQxMJOcuBQyd8Nb5w@mail.gmail.com> <C72807F4-88D6-4040-8BF6-94BAD5B87AB0@pps.univ-paris-diderot.fr> <CAGnRvuos29bkYMChXUaOGoxrtY2ZNiJFXDVu==SaiwiD-zw5xA@mail.gmail.com> <87h9wou6t6.wl-jch@pps.univ-paris-diderot.fr> <54976489.8080400@gmail.com> <87egrr94kn.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw5GdG0=mNTEQkC58YW_9n22z8oLwp5bX2tO-4d0aJBKiQ@mail.gmail.com> <87a92f9394.wl-jch@pps.univ-paris-diderot.fr> <20141222142253.GX28745@Space.Net>
In-Reply-To: <20141222142253.GX28745@Space.Net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/AKXnOK2Vc_eD26zIfllLk5svbcU
Cc: HOMENET <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Dec 2014 19:07:51 -0000

On 23/12/2014 03:22, Gert Doering wrote:
> Hi,
> 
> On Mon, Dec 22, 2014 at 03:18:47PM +0100, Juliusz Chroboczek wrote:
>> If you have two hosts connected at different places to the same mesh
>> network, they could have very different performance characteristics while
>> having addresses from the same /64.
> 
> Indeed, that's the other end of the diversity spectrum (vs. "all hosts in
> our /32 have roughly the same network characteristics").

Yes. But this whole thing is a heuristic anyway; I could imagine
quite sophisticated algorithms, or something fairly simple such
as "cache results for a pair of /64s; if that gives inconsistent
RTTs, cache results for individual pairs of /128s".

   Brian


From nobody Mon Dec 22 16:12:53 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 985D81A88DD for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 16:12:50 -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 zrgoAWg4bAcA for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 16:12:48 -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 550191A1B8B for <homenet@ietf.org>; Mon, 22 Dec 2014 16:12:48 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 85EE420098; Mon, 22 Dec 2014 19:17:13 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 31148637FE; Mon, 22 Dec 2014 19:12:45 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 0DE3D637EA; Mon, 22 Dec 2014 19:12:45 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <54976489.8080400@gmail.com>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com> <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr> <54939DA2.60602@gmail.com> <7izjajh7gm.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqDTnyzH4ehKr9kizKM7H8J8y7=GTQxMJOcuBQyd8Nb5w@mail.gmail.com> <C72807F4-88D6-4040-8BF6-94BAD5B87AB0@pps.univ-paris-diderot.fr> <CAGnRvuos29bkYMChXUaOGoxrtY2ZNiJFXDVu==SaiwiD-zw5xA@mail.gmail.com> <87h9wou6t6.wl-jch@pps.univ-paris-diderot.fr> <54976489.8080400@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
Date: Mon, 22 Dec 2014 19:12:45 -0500
Message-ID: <3184.1419293565@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/_oMuMCgDFLM44G_VqgFTZtBCg58
Cc: Dave Taht <dave.taht@gmail.com>, Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>, Henning Rogge <hrogge@gmail.com>, HOMENET <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Dec 2014 00:12:50 -0000

Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
    >> On the other hand, if we end up having hundreds of addresses on every
    >> host, the strategy will need to be rethought.  Dave is currently playing
    >> with a network where each host has 10 addresses of different kinds, and
    >> he's trying to work out heuristics to limit the number of probes.  I'd
    >> personally prefer to gather some empirical data before we start optimising
    >> things.

    > A good thought. From the point of view of usefulness, more than two or
    > three addresses per host seems pretty pointless (that is at any rate
    > what draft-naderi-ipv6-probing told us). Probe results should probably
    > be cached for a while and interpreted per-prefix not per-address.

While I would agree that 2-3 makes sense for average desktop system, having
at least one IPv6 address per virtual (http,ftp,smtp,..) host makes lots of
sense, and there could be hundreds.
The host system still needs to pick the right address for outgoing connections.

While light-weight containers likely will put context on the many addresses,
in some container implementations the superuser ("dom0") container sees all
addresses anyway.

I've also observed some systems with dozens of privacy addresses; now I
think that many were marked as deprecated, they ought not be considered, but
as long as something has a socket open, they remain. (HTTP 1.1, ssh
connections...)  I think this will be increasingly common.

--
]               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    [



From nobody Mon Dec 22 16:22:25 2014
Return-Path: <dave.taht@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7949A1A8932 for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 16:22:23 -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 DeihaMQKyWUl for <homenet@ietfa.amsl.com>; Mon, 22 Dec 2014 16:22:21 -0800 (PST)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4358F1A88A3 for <homenet@ietf.org>; Mon, 22 Dec 2014 16:22:21 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id va8so23454846obc.3 for <homenet@ietf.org>; Mon, 22 Dec 2014 16:22:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=rMX/V5iMJNNUZsYayhEEVbP1gdb1upAjiWsW7imi9Mc=; b=UqHn0uzSgR6Uh1goc0/JzIS+P3utVSU8S9rZVKncaNzx+ZXkOgWET+SlIcHdtnpQLN 8O1lwBHdgcD6zfWF5IEy9qodH/vyfYF3/q0bm+2I/VDNAuiTA/a9BD6GGkbHaSittDns 5oOtIB/v+Op9AVdQfzDPOWpvd+K1UXkNrnA/+rcVf5s657nBTTPJoPjHIw/cHrJfVO6L UWi0/PapMxaxeq+KZPbD41aP3nkYZOyN2loTNHssKgnk3UPmtWLKBktTauIxwL2RwUQZ KSkOiivZP3mTtiVguGn0ZFM6L6dY4ZM6SRzOwjIB4XoRH4tjdgbikAUzew6rY6UVEIBW gkbw==
MIME-Version: 1.0
X-Received: by 10.60.84.196 with SMTP id b4mr14696892oez.49.1419294140469; Mon, 22 Dec 2014 16:22:20 -0800 (PST)
Received: by 10.202.169.209 with HTTP; Mon, 22 Dec 2014 16:22:20 -0800 (PST)
In-Reply-To: <54934FF5.2050108@gmail.com>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com>
Date: Mon, 22 Dec 2014 16:22:20 -0800
Message-ID: <CAA93jw7YGtOzC0px8eVGz+njrq7TNzoCUpamm2yeqZ--u_dTxQ@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/JsAXzN9bVRXmGfoR2krvKxk-JS4
Cc: dnsmasq-discuss <dnsmasq-discuss@lists.thekelleys.org.uk>, Michael Richardson <mcr+ietf@sandelman.ca>, HOMENET <homenet@ietf.org>, "babel-users@lists.alioth.debian.org" <babel-users@lists.alioth.debian.org>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Dec 2014 00:22:23 -0000

On Thu, Dec 18, 2014 at 2:06 PM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> On 19/12/2014 04:07, Michael Richardson wrote:

I am way behind on my mail (this thread) and will be away for the holidays.

Merry Christmas, everyone, and to all a happy new year!

>> Dave,
>> my take is that applications, and the entire gai.conf/getaddrinfo() libr=
ary
>> is broken.  Applications can neither be updated nor be trusted to know e=
nough
>> about the system to be able to make a proper decision.

I concur. Also other apis dating from the 70s, like sendmsg,getmsg,
and the new sendmmsg,getmmsg are a real pita to use, but increasingly
of interest to the webrtc, quic, and brave new post-tcp udp-only
world.

>> Somewhere, someone was working on a new connect(2) call that took FQDNs
>> rather than sockaddr's, such that the kernel could take ownership of thi=
s
>> problem.
>
> I suppose you are thinking of Name Based Sockets:
> http://tools.ietf.org/html/draft-ubillos-name-based-sockets
>
> It's dead, as far as I know.

It's not dead, it's resting!

The kernel work is not that out of date (3 years). Why did progress stop?

https://github.com/namebasedsockets

I for one would really like names to get more closely tied to numbers...

>
>> (Of course, actually solving the problem in a kernel is probably the
>> wrong answer).
>> What is necessary is some new infrastructure inside the box which become=
s
>> standardized (like sockets API was), with some daemon that thinks about =
the
>> best source addresses is, and possibly gets involved with routing protoc=
ols.
>> (I'm told that OSX has a sophisticated state machine that combines DHCP =
and
>> 1x, and wifi... it sounds like it could be the start of such a thing)

Openwrt had to go to very tightly integrated internal messaging API in
order to get all of the newly mandated dynamicsm in ipv6 sort of taken
care of, and that still isn't quite working right.

Yes, looking over OSX would be a good idea.

>>
>> I think that shim6 and mptcp are answers in this equation.
>>
>> shim6 has, I'm told, deployment issues which make me very very sad.
>
> Like, it cannot get through most firewalls.

I would like to test it against modern firewalls.

>
>> mptcp, I'm told, is likely to show up in Apple and Google products and
>> infrastructure, and my idea (and many others) is that you don't always h=
ave
>> to pick the perfect address for the SYN, just one that works, but rather=
 one
>> can add better addresses as one discovers them.
>
> But bad luck if you need UDP.

Meh. The world is seemingly moving to userspace networking anyway.

>
> Some form of intelligent probing does seem to be the answer,
> but certainly that needs to be generic because we cannot expect
> all apps developers to reinvent it. That's one reason we wrote
> http://tools.ietf.org/html/draft-naderi-ipv6-probing recently.
>
>    Brian
>



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Sat Dec 27 01:52:57 2014
Return-Path: <v6ops@globis.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C6771AD4BC for <homenet@ietfa.amsl.com>; Sat, 27 Dec 2014 01:52:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.012
X-Spam-Level: 
X-Spam-Status: No, score=-0.012 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, 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 S6eB3rZts6SL for <homenet@ietfa.amsl.com>; Sat, 27 Dec 2014 01:52:54 -0800 (PST)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id D7DD01AD4B8 for <homenet@ietf.org>; Sat, 27 Dec 2014 01:52:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 7EFC1871612; Sat, 27 Dec 2014 10:52:52 +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 LfUUM-q388ER; Sat, 27 Dec 2014 10:52:52 +0100 (CET)
Received: from [192.168.0.17] (cpc1-lanc6-2-0-cust213.3-3.cable.virginm.net [86.5.68.214]) (Authenticated sender: v6ops@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id 4CF46870067; Sat, 27 Dec 2014 10:52:52 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
From: V6ops <v6ops@globis.net>
X-Mailer: iPad Mail (12B440)
In-Reply-To: <CAA93jw7YGtOzC0px8eVGz+njrq7TNzoCUpamm2yeqZ--u_dTxQ@mail.gmail.com>
Date: Sat, 27 Dec 2014 09:52:51 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <62BCA13A-7526-4D4B-9ACC-C100120F4C53@globis.net>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <CAA93jw7YGtOzC0px8eVGz+njrq7TNzoCUpamm2yeqZ--u_dTxQ@mail.gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/6-PIRVHZdLIEPumMEeyMtrKh0mg
Cc: dnsmasq-discuss <dnsmasq-discuss@lists.thekelleys.org.uk>, Michael Richardson <mcr+ietf@sandelman.ca>, HOMENET <homenet@ietf.org>, "babel-users@lists.alioth.debian.org" <babel-users@lists.alioth.debian.org>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Dec 2014 09:52:56 -0000

Sent from my iThing

> On 23 Dec 2014, at 00:22, Dave Taht <dave.taht@gmail.com> wrote:
>=20
> On Thu, Dec 18, 2014 at 2:06 PM, Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>> On 19/12/2014 04:07, Michael Richardson wrote:
>=20
> I am way behind on my mail (this thread) and will be away for the holidays=
.
>=20
> Merry Christmas, everyone, and to all a happy new year!
>=20
>>> Dave,
>>> my take is that applications, and the entire gai.conf/getaddrinfo() libr=
ary
>>> is broken.  Applications can neither be updated nor be trusted to know e=
nough
>>> about the system to be able to make a proper decision.
>=20
> I concur. Also other apis dating from the 70s, like sendmsg,getmsg,
> and the new sendmmsg,getmmsg are a real pita to use, but increasingly
> of interest to the webrtc, quic, and brave new post-tcp udp-only
> world.
>=20
>>> Somewhere, someone was working on a new connect(2) call that took FQDNs
>>> rather than sockaddr's, such that the kernel could take ownership of thi=
s
>>> problem.
>>=20
>> I suppose you are thinking of Name Based Sockets:
>> http://tools.ietf.org/html/draft-ubillos-name-based-sockets
>>=20
>> It's dead, as far as I know.
>=20
> It's not dead, it's resting!
>=20
> The kernel work is not that out of date (3 years). Why did progress stop?
>=20
> https://github.com/namebasedsockets
>=20
> I for one would really like names to get more closely tied to numbers...
>=20
>>=20
>>> (Of course, actually solving the problem in a kernel is probably the
>>> wrong answer).
>>> What is necessary is some new infrastructure inside the box which become=
s
>>> standardized (like sockets API was), with some daemon that thinks about t=
he
>>> best source addresses is, and possibly gets involved with routing protoc=
ols.
>>> (I'm told that OSX has a sophisticated state machine that combines DHCP a=
nd
>>> 1x, and wifi... it sounds like it could be the start of such a thing)
>=20
> Openwrt had to go to very tightly integrated internal messaging API in
> order to get all of the newly mandated dynamicsm in ipv6 sort of taken
> care of, and that still isn't quite working right.
>=20
> Yes, looking over OSX would be a good idea.
>=20
>>>=20
>>> I think that shim6 and mptcp are answers in this equation.
>>>=20
>>> shim6 has, I'm told, deployment issues which make me very very sad.
>>=20
>> Like, it cannot get through most firewalls.
>=20
> I would like to test it against modern firewalls.
>=20
>>=20
>>> mptcp, I'm told, is likely to show up in Apple and Google products and
>>> infrastructure, and my idea (and many others) is that you don't always h=
ave
>>> to pick the perfect address for the SYN, just one that works, but rather=
 one
>>> can add better addresses as one discovers them.
>>=20
>> But bad luck if you need UDP.
>=20
> Meh. The world is seemingly moving to userspace networking anyway.
>=20
>>=20
>> Some form of intelligent probing does seem to be the answer,
>> but certainly that needs to be generic because we cannot expect
>> all apps developers to reinvent it. That's one reason we wrote
>> http://tools.ietf.org/html/draft-naderi-ipv6-probing recently.
>>=20
>>   Brian
>>=20
>=20
>=20
>=20
> --=20
> Dave T=C3=A4ht
>=20
> thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
>=20
Another potential solution would be to follow current practice in router man=
agement. I know Homenet does not wish to change hosts, but it may result in t=
he best solution.

We could:
- create one of more additional software loopback interfaces that are always=
 up and used as source and destination for binding for all (legacy) apps.
- a software interface would have one single /64 prefix from each delegated H=
omenet prefix, reducing the number of potential sources and sinks.
- allow the end nodes to take part in HNCP as multi-homed stub devices that d=
o not forward packets between hardware interfaces.
- use stub mode of Babel to learn outbound routes, and to originate a return=
 route to the software loopback interface.

That might also solve the conundrum of how to handle roaming beween multiple=
 routed wireless interfaces running on multiple Homenet routers, and should a=
lso greatly simplify the namespace, as the AAAA record of the device could b=
e invariant and independent of the attachment point to the Homenet.=


From nobody Sat Dec 27 09:02:21 2014
Return-Path: <jch@pps.univ-paris-diderot.fr>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B12D91A904F for <homenet@ietfa.amsl.com>; Sat, 27 Dec 2014 09:02:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] 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 QYEzBjU2YGNv for <homenet@ietfa.amsl.com>; Sat, 27 Dec 2014 09:02:10 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 93B1E1A9060 for <homenet@ietf.org>; Sat, 27 Dec 2014 09:02:09 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/46573) with ESMTP id sBRH26Lg032356 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 27 Dec 2014 18:02:06 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/46573) with ESMTP id sBRH26DJ030380; Sat, 27 Dec 2014 18:02:06 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 51F821C510; Sat, 27 Dec 2014 18:02:06 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id GW5y-SISnCrw; Sat, 27 Dec 2014 18:02:05 +0100 (CET)
Received: from pirx.pps.jussieu.fr (dra38-1-82-225-44-56.fbx.proxad.net [82.225.44.56]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 793541C509; Sat, 27 Dec 2014 18:02:03 +0100 (CET)
Date: Sat, 27 Dec 2014 18:02:03 +0100
Message-ID: <873881gh6c.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: V6ops <v6ops@globis.net>
In-Reply-To: <62BCA13A-7526-4D4B-9ACC-C100120F4C53@globis.net>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <CAA93jw7YGtOzC0px8eVGz+njrq7TNzoCUpamm2yeqZ--u_dTxQ@mail.gmail.com> <62BCA13A-7526-4D4B-9ACC-C100120F4C53@globis.net>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Sat, 27 Dec 2014 18:02:06 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Sat, 27 Dec 2014 18:02:06 +0100 (CET)
X-Miltered: at korolev with ID 549EE60E.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 549EE60E.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 549EE60E.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 549EE60E.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 549EE60E.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 549EE60E.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/KSxgEnuo33JxU-7kvYH5FQLCSv4
Cc: HOMENET <homenet@ietf.org>, "babel-users@lists.alioth.debian.org" <babel-users@lists.alioth.debian.org>, dnsmasq-discuss <dnsmasq-discuss@thekelleys.org.uk>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Dec 2014 17:02:13 -0000

> - create one of more additional software loopback interfaces that are
>   always up and used as source and destination for binding for all
>   (legacy) apps.
> - a software interface would have one single /64 prefix from each
>   delegated Homenet prefix, reducing the number of potential sources and
>   sinks.
> - allow the end nodes to take part in HNCP as multi-homed stub devices
>   that do not forward packets between hardware interfaces.
> - use stub mode of Babel to learn outbound routes, and to originate
>   a return route to the software loopback interface.

Yes, that's more or less what we're doing with hosts connected to
a AHCP/Babel mesh right now.  That's also what I suggested we do when
people were arguing in favour of TRILL (giggle) in order to have roaming.

That's certainly something I'm planning to experiment with when I have the
time and energy to replace AHCP with HNCP in our Babel mesh.  (Not before
February, I fear.)

> That might also solve the conundrum of how to handle roaming beween
> multiple routed wireless interfaces running on multiple Homenet routers,

Yes.

> and should also greatly simplify the namespace, as the AAAA record of
> the device could be invariant and independent of the attachment point to
> the Homenet.

Almost -- any given IPv6 might go away when an ISP goes down.  So either
you include all of your ISPs in DNS (in which case you need probing) or
you renumber whenever you change addresses (in which case you need to wait
for DNS to propagate).

In short, it looks like something needs to give.  Unless I'm missing
something (in which case please do tell), multihoming requires one of the
following:

  - hosts perform e2e probing (shim6, MPTCP, or at the application layer); or
  - DNS becomes more dynamic and propagates faster than it does now; or
  - you use PI addresses, with the table bloat that this entails.

I'm not very keen on putting extra load on DNS, and PI seems out of the
question, so it looks like we're stuck with probing.  Or am I missing
something?

-- Juliusz


From nobody Tue Dec 30 07:55:34 2014
Return-Path: <mark@townsley.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 008FC1A01E1 for <homenet@ietfa.amsl.com>; Tue, 30 Dec 2014 07:55:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.723
X-Spam-Level: 
X-Spam-Status: No, score=0.723 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 hlrSQ63jSpxh for <homenet@ietfa.amsl.com>; Tue, 30 Dec 2014 07:55:30 -0800 (PST)
Received: from mail-la0-f49.google.com (mail-la0-f49.google.com [209.85.215.49]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3392F1A01D8 for <homenet@ietf.org>; Tue, 30 Dec 2014 07:55:30 -0800 (PST)
Received: by mail-la0-f49.google.com with SMTP id hs14so12876738lab.36 for <homenet@ietf.org>; Tue, 30 Dec 2014 07:55:28 -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=VFcxJHiJgMO9W5lIq9vHhb8HAvuBe1BKTxkW1HMUbtY=; b=h2Kf0udmatV7naaQ9EYh2jTXqeh2wqq55X/F5oiRZyUT9XzaIBTV/fCPXjTaz2C2NI Amw3CnZBcWTL9J/tjIKDCZfOmq65becSxMZX9x3vrug8eCD31YloZI+jqoKr/hTH17wf RVrDEocCVWwMHj3YODlGfJB9fECbKGGddYyM6maIUN/TiYmzJdxUGVGEgbs74XhHev6a XhQQMbLeiYIlzbbGQe09UlKH+DfUZc2qG9C7LEfUsTuiStf4agU9x2l0yE+JQ/3o8BeT f3tlT0ajQEKmG6Jp77rM78gAFTNKwqd76KLlOcqXSjAkhyfVLLf+ZMli/CVcj0K6h80l UORA==
X-Gm-Message-State: ALoCoQnLDofsU1a4C/KA54caGQtQ0G2Gh24h285THDP12dwRa354crng+/6vQ31SEDbnQ6LY8Oa7
MIME-Version: 1.0
X-Received: by 10.152.30.6 with SMTP id o6mr63396872lah.64.1419954928343; Tue, 30 Dec 2014 07:55:28 -0800 (PST)
Received: by 10.112.72.40 with HTTP; Tue, 30 Dec 2014 07:55:28 -0800 (PST)
In-Reply-To: <CAESTAVtBfD8A8iDCKV-+7eaxL3SDvajHw2eY0W7XbDbZ5P4mMQ@mail.gmail.com>
References: <CAESTAVtBfD8A8iDCKV-+7eaxL3SDvajHw2eY0W7XbDbZ5P4mMQ@mail.gmail.com>
Date: Tue, 30 Dec 2014 16:55:28 +0100
Message-ID: <CAESTAVuNE7qOwmaEoitp3JvKF=Qfvhq3u=X+vC_gDvU5DyMyjg@mail.gmail.com>
From: Mark Townsley <mark@townsley.net>
To: "homenet@ietf.org Group" <homenet@ietf.org>
Content-Type: multipart/alternative; boundary=089e0160b4541a1503050b71051a
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/044QM3-ZbFz1Cbq4YqawOxrMuM8
Subject: [homenet] Fwd: Homenet draft reorg and generalization
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Dec 2014 15:55:32 -0000

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

Dear WG,

To help organize the work Homenet has done thus far, Ray and I worked with
our document authors at the last IETF (and since) to come up with a
document and protocol organization that should help advance the more stable
work that we have completed thus far and also enable Homenet's work to be
used in other WGs as required. Here's the result:

These two WG documents:

draft-ietf-homenet-prefix-assignment-01
draft-ietf-homenet-hncp-02

Become these three WG documents:

draft-ietf-homenet-prefix-assignment-02
draft-ietf-homenet-dncp-00
draft-ietf-homenet-hncp-03

The three new documents inherit directly from the two existing in a
criss-cross pattern, along with some security-related text taken
from draft-barth-homenet-hncp-security-trust-01 (which, as pointed out by
Ray before, should have simply been part of the hncp-02 draft to begin with
rather than separated out).

*draft-prefix-assignment-02 *will become even more generic, allowing it to
be more readily used as a normative reference within other work.
prefix-assignment-02 will include more text regarding the mathematical
proof of the algorithm itself, and all homenet specific text will be moved
to draft-ietf-homenet-hncp-03.

*draft-ietf-homenet-dncp-00 *(Dynamic Network Consensus Protocol) will
include generalized parts of draft-ietf-homenet-hncp-02. As above, homenet
specifics will be included in draft-ietf-homenet-hncp-03.

*draft-ietf-homenet-hncp-03* thus becomes the base document for how to
apply draft-ietf-homenet-prefix-assignment and draft-ietf-homenet-dncp
(with normative references to each) in a homenet context, as well as any
other homenet-specific work (including possibly what we end up deciding for
routing).

We'll leave details of what section goes where for the editors/authors to
work out, we believe at least some of this work is already underway so
hopefully we will see some results soon. Many thanks for all of the hard
editing work as we know doc reorg is painful. Also thanks for all the
recent reviews, there have been a lot of eyeballs on these documents of
late and we expect the next set of revisions published to be improved
accordingly.

- Mark & Ray

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

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr"><br><div>Dear =
WG,<br></div><div><br></div><div>To help organize the work Homenet has done=
 thus far, Ray and I worked with our document authors at the last IETF (and=
 since) to come up with a document and protocol organization that should he=
lp advance the more stable work that we have completed thus far and also en=
able Homenet&#39;s work to be used in other WGs as required. Here&#39;s the=
 result:<br></div><div><br></div><div>These two WG documents:<br></div><div=
><br></div><div><div>draft-ietf-homenet-prefix-assignment-01<br></div><div>=
draft-ietf-homenet-hncp-02=C2=A0</div><div><br></div><div>Become these thre=
e WG documents:</div><div><br></div><div>draft-ietf-homenet-prefix-assignme=
nt-02</div><div>draft-ietf-homenet-dncp-00=C2=A0</div><div>draft-ietf-homen=
et-hncp-03=C2=A0</div><div><br></div><div>The three new documents inherit d=
irectly from the two existing in a criss-cross pattern, along with some sec=
urity-related text taken from=C2=A0draft-barth-homenet-hncp-security-trust-=
01 (which, as pointed out by Ray before, should have simply been part of th=
e hncp-02 draft to begin with rather than separated out).<br></div><div><br=
></div><div><b>draft-prefix-assignment-02=C2=A0</b>will become even more ge=
neric, allowing it to be more readily used as a normative reference within =
other work. prefix-assignment-02 will include more text regarding the mathe=
matical proof of the algorithm itself, and all homenet specific text will b=
e moved to draft-ietf-homenet-hncp-03.=C2=A0</div><div><br></div><div><b>dr=
aft-ietf-homenet-dncp-00 </b>(Dynamic Network Consensus Protocol) will incl=
ude generalized parts of draft-ietf-homenet-hncp-02. As above, homenet spec=
ifics will be included in draft-ietf-homenet-hncp-03.</div><div><br></div><=
div><b>draft-ietf-homenet-hncp-03</b>=C2=A0thus becomes the base document f=
or how to apply draft-ietf-homenet-prefix-assignment and draft-ietf-homenet=
-dncp (with normative references to each) in a homenet context, as well as =
any other homenet-specific work (including possibly what we end up deciding=
 for routing).=C2=A0</div></div><div><br></div><div>We&#39;ll leave details=
 of what section goes where for the editors/authors to work out, we believe=
 at least some of this work is already underway so hopefully we will see so=
me results soon. Many thanks for all of the hard editing work as we know do=
c reorg is painful. Also thanks for all the recent reviews, there have been=
 a lot of eyeballs on these documents of late and we expect the next set of=
 revisions published to be improved accordingly.=C2=A0</div><div><br></div>=
<div>- Mark &amp; Ray</div><div><br></div><div><br></div><div><br></div><di=
v><br></div><div><br></div><div><br></div><div><br></div><div><br></div><di=
v><br></div><div><br></div></div>
</div><br></div>

--089e0160b4541a1503050b71051a--


From nobody Tue Dec 30 08:20:55 2014
Return-Path: <mark@townsley.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79DD51A000C for <homenet@ietfa.amsl.com>; Tue, 30 Dec 2014 08:20:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.078
X-Spam-Level: 
X-Spam-Status: No, score=-0.078 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 iNiB2TG5wdOv for <homenet@ietfa.amsl.com>; Tue, 30 Dec 2014 08:20:51 -0800 (PST)
Received: from mail-la0-f43.google.com (mail-la0-f43.google.com [209.85.215.43]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2441D1A000B for <homenet@ietf.org>; Tue, 30 Dec 2014 08:20:50 -0800 (PST)
Received: by mail-la0-f43.google.com with SMTP id s18so12846042lam.30 for <homenet@ietf.org>; Tue, 30 Dec 2014 08:20:48 -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:cc:content-type; bh=+zxW7+Pp8MKlcwRHYPQwREDW1VRx/kwD3lJaBBKR1aA=; b=Dw2GlQLpdXg/JScGboXFZQNUJzIHsEf8mW9Q2HuwA2nhNk9jk4ajCpP9rYTpdEgFeW G0brW2yYBmqa8GMWUO3BZKCIQm0TcuLYGIvWp5C5q9CtW2lmP9WE8hEswY86bilG9cw1 CqyAb8+3lpIxpeDO84e9uOfhb4UOn+sQhlUW9FFEvnG329ySJoKmIBZ16v+OWXmfvK5p fmz3QHWWKvd9uOMf++kj6z48qKMVbjU3jOwOUh6CYM8VpfUd5jiA/qChd9KjGocRjQFj U7uTyssz7x8bAq5UDEI7g/UfWQ2+eyWFYGypDuXVmtvfZpQQ/A0gBrkmuGaS2I9m9NfA i4rg==
X-Gm-Message-State: ALoCoQlMoBgZ3llT0fibLlt64+bIiBlcZ1YeTKPcpydrSd/RDWhiAKyMnAAJOk97fiRQBe1fvEcN
MIME-Version: 1.0
X-Received: by 10.112.185.101 with SMTP id fb5mr19579806lbc.12.1419956448467;  Tue, 30 Dec 2014 08:20:48 -0800 (PST)
Received: by 10.112.72.40 with HTTP; Tue, 30 Dec 2014 08:20:48 -0800 (PST)
In-Reply-To: <CAA93jw5+e0u=aHCjaBjwKrqdvhfwx5MbvG2yuKvBnOtHk_5jQg@mail.gmail.com>
References: <CAA93jw5+e0u=aHCjaBjwKrqdvhfwx5MbvG2yuKvBnOtHk_5jQg@mail.gmail.com>
Date: Tue, 30 Dec 2014 17:20:48 +0100
Message-ID: <CAESTAVvqhdbujnh-uQVB7oQ4fnx70aD17Q9zaFy4b39t_oq7hA@mail.gmail.com>
From: Mark Townsley <mark@townsley.net>
To: Dave Taht <dave.taht@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c3c516b53670050b715f4c
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/HGbauy8Xi4gn_mZVSbQCUXtQ7mc
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] udp-lite support?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Dec 2014 16:20:53 -0000

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

On Sun, Dec 21, 2014 at 9:07 PM, Dave Taht <dave.taht@gmail.com> wrote:

> I am growing concerned by the widespread adoption of udp as a baseline
> transport for so many protocols (webrtc, bittorrent maelstrom, etc.)
> Certainly a couple traceroutes alone could blow up my udp nat table on
> a busy router with open udp ports as can something as simple as trying
> to do reverse lookups on everything in a /64 - I long ago had to start
> closing udp ports on the firewall in under 30 seconds - (dns over ipv6
> fixes this thoroughly, thank ghu), but having thoroughly blown up my
> world just now with mosh-multipath...
>
> I see udplite support is mandated by some homenet rfc or another.
>

Hi Dave,

I could have missed it, but I don't recall UDP-Lite coming up before...
Which Homenet document are you referring to?


>
> udp-lite, unlike sctp, it is simple enough to work everywhere, but a
> lot of its original use case (unencrypted rtp) is gone.
>
> What, if anything is it actually used for today?


I am not aware any significant deployment.

- Mark


> Are there any test
> suites or large scale tests/testers that have gone and looked at its
> actual routability over the ipv4 and ipv6 Internet?
>
> anyway, udplite seemed like a good fit for a userspace vpn or
> something like mosh, so (since I was unable to find any comprehensive
> udplite test suites)  I went and implemented that as a test for fun...
>
> https://plus.google.com/u/0/107942175615993706558/posts/LDNmr8PWkFg
>
> and given how easy it is to hack in will probably try to add it to
> netperf-wrapper. Over the holidays. Maybe.
>
> --
> Dave T=C3=A4ht
>
> http://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talk
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Sun, Dec 21, 2014 at 9:07 PM, Dave Taht <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:dave.taht@gmail.com" target=3D"_blank">dave.taht@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">I am growing concerned =
by the widespread adoption of udp as a baseline<br>
transport for so many protocols (webrtc, bittorrent maelstrom, etc.)<br>
Certainly a couple traceroutes alone could blow up my udp nat table on<br>
a busy router with open udp ports as can something as simple as trying<br>
to do reverse lookups on everything in a /64 - I long ago had to start<br>
closing udp ports on the firewall in under 30 seconds - (dns over ipv6<br>
fixes this thoroughly, thank ghu), but having thoroughly blown up my<br>
world just now with mosh-multipath...<br>
<br>
I see udplite support is mandated by some homenet rfc or another.<br></bloc=
kquote><div><br></div><div>Hi Dave,</div><div><br></div><div>I could have m=
issed it, but I don&#39;t recall UDP-Lite coming up before... Which Homenet=
 document are you referring to?</div><div>=C2=A0<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
<br>
udp-lite, unlike sctp, it is simple enough to work everywhere, but a<br>
lot of its original use case (unencrypted rtp) is gone.<br>
<br>
What, if anything is it actually used for today? </blockquote><div><br></di=
v><div>I am not aware any significant deployment.=C2=A0</div><div><br></div=
><div>- Mark</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Are ther=
e any test<br>
suites or large scale tests/testers that have gone and looked at its<br>
actual routability over the ipv4 and ipv6 Internet?<br>
<br>
anyway, udplite seemed like a good fit for a userspace vpn or<br>
something like mosh, so (since I was unable to find any comprehensive<br>
udplite test suites)=C2=A0 I went and implemented that as a test for fun...=
<br>
<br>
<a href=3D"https://plus.google.com/u/0/107942175615993706558/posts/LDNmr8PW=
kFg" target=3D"_blank">https://plus.google.com/u/0/107942175615993706558/po=
sts/LDNmr8PWkFg</a><br>
<br>
and given how easy it is to hack in will probably try to add it to<br>
netperf-wrapper. Over the holidays. Maybe.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Dave T=C3=A4ht<br>
<br>
<a href=3D"http://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talk" ta=
rget=3D"_blank">http://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Tal=
k</a><br>
<br>
_______________________________________________<br>
homenet mailing list<br>
<a href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/homenet" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/homenet</a><br>
</font></span></blockquote></div><br></div></div>

--001a11c3c516b53670050b715f4c--


From nobody Tue Dec 30 11:44:03 2014
Return-Path: <dave.taht@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D94081A1B44 for <homenet@ietfa.amsl.com>; Tue, 30 Dec 2014 11:44:01 -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 piJxOQ-RBwEX for <homenet@ietfa.amsl.com>; Tue, 30 Dec 2014 11:44:00 -0800 (PST)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8B1E1A1B37 for <homenet@ietf.org>; Tue, 30 Dec 2014 11:43:59 -0800 (PST)
Received: by mail-oi0-f42.google.com with SMTP id v63so33476540oia.1 for <homenet@ietf.org>; Tue, 30 Dec 2014 11:43:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=eaw0BEshX+AoTMTo3f0WTPGgcZzjDDxV54UvVpET9zE=; b=FAp9+21vqDXOsejTx8RNQhREgsLrFmbrRoJaq0qadpTaQn+DmyM6O0FCiFbGzuOCKS 1Edo+LzX7vMf0C/B6spT6c/8hooryagNQSBQ+gnov/WRiV5sJQaZE/sW3CnumGG+8rxy 1bBCoj7mtjxCt2Y1w10DnzTNwFZCNo2ytEIGzs2Y75BWMOhY8unuEnxxHBTD0SmPxcb8 tDxueCS9WIrOvsnylS4c+RB4DobpwL2R688Ns6SJf74dDpcvChNkmtG/Jub4JAW5HQ8C TSCri6NVDhP++5dsUbiBxd/AXdB5r9DPA8+ozIyUfctv5GL7jwbwO2fw29DSzy+WMIlr rSaQ==
MIME-Version: 1.0
X-Received: by 10.182.22.198 with SMTP id g6mr4985264obf.16.1419968639210; Tue, 30 Dec 2014 11:43:59 -0800 (PST)
Received: by 10.202.169.209 with HTTP; Tue, 30 Dec 2014 11:43:59 -0800 (PST)
In-Reply-To: <CAESTAVvqhdbujnh-uQVB7oQ4fnx70aD17Q9zaFy4b39t_oq7hA@mail.gmail.com>
References: <CAA93jw5+e0u=aHCjaBjwKrqdvhfwx5MbvG2yuKvBnOtHk_5jQg@mail.gmail.com> <CAESTAVvqhdbujnh-uQVB7oQ4fnx70aD17Q9zaFy4b39t_oq7hA@mail.gmail.com>
Date: Tue, 30 Dec 2014 11:43:59 -0800
Message-ID: <CAA93jw4unwJR2XCyNRDhS2yWJwFGL6XKqdh4dc3HaZ2AQFn42w@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Mark Townsley <mark@townsley.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/Jr7vR3e4osE1G1WYP1-2oqM7NsI
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] udp-lite support?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Dec 2014 19:44:02 -0000

On Tue, Dec 30, 2014 at 8:20 AM, Mark Townsley <mark@townsley.net> wrote:
>
>
> On Sun, Dec 21, 2014 at 9:07 PM, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> I am growing concerned by the widespread adoption of udp as a baseline
>> transport for so many protocols (webrtc, bittorrent maelstrom, etc.)
>> Certainly a couple traceroutes alone could blow up my udp nat table on
>> a busy router with open udp ports as can something as simple as trying
>> to do reverse lookups on everything in a /64 - I long ago had to start
>> closing udp ports on the firewall in under 30 seconds - (dns over ipv6
>> fixes this thoroughly, thank ghu), but having thoroughly blown up my
>> world just now with mosh-multipath...
>>
>> I see udplite support is mandated by some homenet rfc or another.
>
>
> Hi Dave,
>
> I could have missed it, but I don't recall UDP-Lite coming up before...
> Which Homenet document are you referring to?

Sorry, the rfcs I was mentally referring to were not homenet:

https://tools.ietf.org/html/rfc6092

and:

https://tools.ietf.org/html/rfc6936#section-2.2

>>
>>
>> udp-lite, unlike sctp, it is simple enough to work everywhere, but a
>> lot of its original use case (unencrypted rtp) is gone.
>>
>> What, if anything is it actually used for today?
>
>
> I am not aware any significant deployment.

Well, I just tested it a little bit on v6 (with full checksum coverage). Wo=
rked.
ENOTIME to pursue it further.

CAPWAP was called out in the latter RFC above as a use case.

>
> - Mark
>
>>
>> Are there any test
>> suites or large scale tests/testers that have gone and looked at its
>> actual routability over the ipv4 and ipv6 Internet?
>>
>> anyway, udplite seemed like a good fit for a userspace vpn or
>> something like mosh, so (since I was unable to find any comprehensive
>> udplite test suites)  I went and implemented that as a test for fun...
>>
>> https://plus.google.com/u/0/107942175615993706558/posts/LDNmr8PWkFg
>>
>> and given how easy it is to hack in will probably try to add it to
>> netperf-wrapper. Over the holidays. Maybe.
>>
>> --
>> Dave T=C3=A4ht
>>
>> http://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talk
>>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>
>



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks

