
From nobody Mon Feb  1 11:17:57 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 611AC1B34E2 for <ipv6@ietfa.amsl.com>; Mon,  1 Feb 2016 11:17:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.103
X-Spam-Level: 
X-Spam-Status: No, score=-0.103 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-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 Cd-tpAWvcxd0 for <ipv6@ietfa.amsl.com>; Mon,  1 Feb 2016 11:17:54 -0800 (PST)
Received: from cowbell.employees.org (cowbell.employees.org [IPv6:2001:1868:a000:17::142]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11C9A1B34A6 for <ipv6@ietf.org>; Mon,  1 Feb 2016 11:17:54 -0800 (PST)
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id C0BB3D7887; Mon,  1 Feb 2016 11:17:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :content-type:subject:date:message-id:cc:to:mime-version; s= selector1; bh=LxighsMmgtNerlo0SQNG7NjphAM=; b=aX/f24yM8caNDig4XT tS5sBT/7KwRYbfs4BEoKTFZH9pP7VgeDLFYyvtz5G2jp1jW9o3Ras+cw4CM9X8rE 0hjtxcUxKE0qdhG0+KbmOYl5zk/R77HnVdInju6nOu8XNIsaBKQai8hasfdw90Xk WDgihvnRnyu+TJdXYDupFYnEA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :content-type:subject:date:message-id:cc:to:mime-version; q=dns; s=selector1; b=nTORURG+DLgggtn2o7oqO5cnX1haB0d0o5yYOvwgZPGZ7Jgc VGkAyMiaKOVZQ1CiOHmKJVa/Ko4/yoRory/ML5PJqJVjCe/epuSm23Z20IlLxJWH /c+dQuowaj4GtVNdzHrUTyvZDiNbipilXry2X7gKOqUjIEtvWbpYHvgOGfo=
Received: from h.hanazo.no (unknown [195.159.234.46]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 3D8E5D7885; Mon,  1 Feb 2016 11:17:52 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id C448EFBE978; Mon,  1 Feb 2016 20:17:48 +0100 (CET)
From: otroan@employees.org
X-Pgp-Agent: GPGMail 2.6b2
Content-Type: multipart/signed; boundary="Apple-Mail=_50FF771E-219D-469A-96D2-3FD1153A10D7"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: 6MAN document shepherding experiment 
Date: Mon, 1 Feb 2016 20:17:47 +0100
Message-Id: <541F8542-83C0-4FEE-B702-50ED543DB346@employees.org>
To: 6man WG <ipv6@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/hOJCjfdyliuJL-nw-ats00kTtyc>
Cc: int-ads@tools.ietf.org, bob.hinden@gmail.com, Suresh Krishnan <suresh.krishnan@ericsson.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Feb 2016 19:17:55 -0000

--Apple-Mail=_50FF771E-219D-469A-96D2-3FD1153A10D7
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

The 6MAN working group chairs together with the Internet ADs are
proposing the following changes to how documents are handled in the
working group.  We propose this initially as an experiment to gather
experience. We will evaluate the experiment continuously as documents are
progressed.

The purpose of the proposal is to involve more working group participants
in the document process.

Expand the document shepherding process, so that the document shepherd
takes a more involved role in the whole lifecycle of the document from
working group draft until RFC.

The idea is:

o A document shepherd is a volunteer chosen by the chairs, ideally as
  soon as the document is adopted, but no later than the working group
  last call. It cannot be the document authors.

o The shepherd is responsible for the document from that point onwards.

    - Follow the document all the way through working group last call
      to RFC Editor publishing
    - Main channel between IESG and working group.
    - Involved in all discussions about edits and changes. (No direct
      IESG AD + author/editor channel without shepherd (and WG
      involvement)
    - Follow the IESG telechats for this document.
    - Administer and follow up with IESG members, authors and working
      group to ensure swift progress.

o The working group chairs are still responsible for determining
  consensus, and are responsible for the functioning of the shepherding
  role.

More information about the shepherding role is available:

 http://ietf.org/edu/tutorials/document-editing-sheparding.pdf
 https://tools.ietf.org/html/rfc4858
 https://www.ietf.org/iesg/statement/document-shepherds.html

This change comes in addition to the existing process of requiring two
volunteer reviews during WGLC. We propose to put this process into effect
immediately for new documents.

Please send us your comments on this proposed experiment, and if you
would be willing to be a document shepherd.  If there are no volunteers
then it will a short experiment!

Best regards,
Bob, Ole

--Apple-Mail=_50FF771E-219D-469A-96D2-3FD1153A10D7
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIcBAEBCgAGBQJWr69cAAoJEL7aWKiYQt92+b4QAM21eY1XJ7mIC3Pu//QUpZnM
uF1LqxUREaJ72FY6WSaMUNEY51MWBrjXEWeH9OXjoo5bmaEAwxZAs792Wzhb3WeZ
pdJhPPtZkBB74T+wSeeofQ+6Ntsrj65ecXe4xYBKYIAx+lx0skjd/LkqJ+M1OTOn
oV1l1Ly9CkQw5lacKC6XlDeRWXoCfv1BTkbSXeOh07qP15kM4Y6eO8xhr0fI2L08
bvFUEZ3hGCrzouKTS8veqQYRYv7Nvwpx7VUy5RLaKXKX4SOSDaP6/szDlq2XJOJn
v3pEgPydAFSykbg25LawbgMttEyhgu16CVjCtMLAZW+5ioiUqGvoUEKJbGbxWS1S
r07NnRk07AaK9a9Im726ZL510TdKTTo0X/UpS+SFG2UB6aNbH+iWTB1atgdXiAD9
3VDXZ1B/ehqNxzLdBnIC1xsGWHcsxMLeJ8DF1SCKYcSK2PJaC93jlmo8xozntd87
yWBuGQE4B4lxlYnVtnVAM7mCveAfY++5fYD7Cc8L4tTI8TnNtCv7DqnB2uXZZ3FC
xUMBmXC/dOT/u1y75G7pwQcSloSD5+ymUhRy2k0BtN4qVQBrYOpacmf3/64GI3vD
ennXbfFA3cRyAzdNbtBfp2xq/mi0rloSuttRs+p3a84Es4ulcIqkrN82NW+fV8Ux
LQdougGs8sk0UfdVmBqH
=wa6C
-----END PGP SIGNATURE-----

--Apple-Mail=_50FF771E-219D-469A-96D2-3FD1153A10D7--


From nobody Mon Feb  1 19:49:39 2016
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 096EE1ACDFA; Mon,  1 Feb 2016 19:49:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.502
X-Spam-Level: 
X-Spam-Status: No, score=-114.502 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AsKtAFx6lL_A; Mon,  1 Feb 2016 19:49:36 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 86DD01ACDF6; Mon,  1 Feb 2016 19:49:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3339; q=dns/txt; s=iport; t=1454384976; x=1455594576; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=KOj6kmKAY4KUfzRC7x9cR/SAkh6uBJuTRsi6+uH3MzE=; b=eqAEYRXcwok0Q7iaYUiQPvZl6ONU2ldAbHVcilzJasxfwPzTF8pOyDbP wG4HANdZOs4cctA5DKcXyx2EKJ0BgSVhLXP1a7veMRWIm1ZpmO6xPArMc L9GFX3VpIv0b+MNzXhRFllh0zbv3LTuvh/MtnQT3uIvfi7TfAfwMW+/9V 8=;
X-Files: signature.asc : 833
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CyAgD9JbBW/5hdJa1egzpSbQaIU7FfD?= =?us-ascii?q?oFkGAqFbQKBNTgUAQEBAQEBAYEKhEEBAQEDAQEBAWsLBQkCAgEIGC4bDAslAgQ?= =?us-ascii?q?OBQ6IBQgOvgQBAQEBAQEBAQEBAQEBAQEBAQEBAQENBAQEh3iCSoddgQ8FlnEBg?= =?us-ascii?q?nmBY4hugVuNFYpsg1EBHgFDg2xqAYhufAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.22,383,1449532800";  d="asc'?scan'208";a="233236157"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Feb 2016 03:49:35 +0000
Received: from XCH-RCD-012.cisco.com (xch-rcd-012.cisco.com [173.37.102.22]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u123nZcZ012197 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 2 Feb 2016 03:49:35 GMT
Received: from xch-rcd-013.cisco.com (173.37.102.23) by XCH-RCD-012.cisco.com (173.37.102.22) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 1 Feb 2016 21:49:34 -0600
Received: from xch-rcd-013.cisco.com ([173.37.102.23]) by XCH-RCD-013.cisco.com ([173.37.102.23]) with mapi id 15.00.1104.009; Mon, 1 Feb 2016 21:49:34 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Mark Andrews <marka@isc.org>
Subject: Re: [v6ops] State of play
Thread-Topic: [v6ops] State of play
Thread-Index: AQHRXWy7WKRnV1axq0Cue0ZfkN2Y9w==
Date: Tue, 2 Feb 2016 03:49:34 +0000
Message-ID: <61DE78D0-8B8D-4BD3-B6B4-5275B118D6F5@cisco.com>
References: <201602011400.u11E0Hsd009385@irp-lnx1.cisco.com> <20160201231151.25706414D77A@rock.dv.isc.org>
In-Reply-To: <20160201231151.25706414D77A@rock.dv.isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3112)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.4.81]
Content-Type: multipart/signed; boundary="Apple-Mail=_99008B0B-2380-47D5-A518-D24FACDEAD89"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ZSsPm8LBIuEKB74TN4TnR_zrnTk>
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IPv6 IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2016 03:49:38 -0000

--Apple-Mail=_99008B0B-2380-47D5-A518-D24FACDEAD89
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

When you say "v6man", I assume you mean "6man".

I'm a little lost. I don't see the words "chair" or "question" in the =
draft. Could you be more specific about what your question is?

> On Feb 1, 2016, at 3:11 PM, Mark Andrews <marka@isc.org> wrote:
>=20
>=20
> draft-andrews-tcp-and-ipv6-use-minmtu-04 has an open question directed
> at the v6man and v6ops chairs - should this be a v6man or v6ops?  It
> needs to be fixed and I don't care in which forum it gets done but it
> needs to be done.
>=20
> Mark
>=20
> In message <201602011400.u11E0Hsd009385@irp-lnx1.cisco.com>, =
fred@cisco.com writes:
>> RFC Editor: AUTH48
>> 	2015-11-23	draft-ietf-v6ops-reducing-ra-energy-consumption
>> 	2015-10-26	draft-ietf-v6ops-siit-dc
>> 	2015-10-26	draft-ietf-v6ops-siit-dc-2xlat
>> 	2015-10-26	draft-ietf-v6ops-siit-eam
>>=20
>> RFC Editor: In ISE Review
>> 	2016-01-20	draft-ietf-v6ops-mobile-device-profile
>>=20
>> IESG: AD Evaluation
>> 	2016-01-31	draft-bao-v6ops-rfc6145bis
>>=20
>> IESG: In Last Call
>> 	2016-01-28	draft-ietf-v6ops-ipv6-ehs-in-real-world
>>=20
>> WG: Unupdated WG Document
>> 	2015-10-19	draft-ietf-v6ops-design-choices
>>=20
>> WG: Updated WG Document
>> 	2016-01-21	draft-ietf-v6ops-unique-ipv6-prefix-per-host
>> 	2016-01-03	draft-ietf-v6ops-host-addr-availability
>>=20
>> Individual Submission: Unupdated
>> 	2015-10-19	draft-xu-v6ops-dslite-redundancy
>> 	2015-10-15	draft-gont-v6ops-ipv6-ehs-packet-drops
>> 	2015-09-21	draft-ybai-v6ops-ipv6-for-openstack
>>=20
>> Individual Submission: Updated
>> 	2016-01-05	draft-templin-v6ops-pdhost
>> 	2016-01-03	draft-xcf-v6ops-chinatelecom-deployment
>> 	2016-01-03	draft-xli-v6ops-cernet-deployment
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


--Apple-Mail=_99008B0B-2380-47D5-A518-D24FACDEAD89
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIVAwUBVrAnTkayAOS/EQ8MAQL9Ug//e/6aNfv+AC2Iv2qAp6MjcIYyRcqRZLew
hhXABkYFTk+/FPHe57xZ4W7h4eEpJ7L8Fha+M+tEzB1ydNc/n/3NsThP6iZCsIYE
lemKravU5zMVEvGLeWoaj9YUdKXzlqgIT6TjcE/0wuyUS6a5MotVMXqLKNkwbwg5
IIX1lZNeSWmc7dtWUIeh9/UzgzlGap9Nd0+MhQVoWvPXgNv4Xvq9AhFSOZsz3r1L
dtiOGn6cwypfrNleDt7D62jtWpmtyM/R7CjDBVhEhDVXyEiEt5/BfPnfB8e5+Ozt
+PvIPw7rPe3Y6tg37kZLTySOiHiJ0UDPCwk7B3KQtYlnfKjFmQ0w8aad+I9Gw7x6
FtUuMZZn5GDzkzR1dpBMr9J2KGjtwO7szDo8C/ZONEfwzTkXwepvxfZoW8eQuTIu
E09eFvtUmmpE5w3K9sU/8ku8h+rtNf85GO5rozDwGBlflZAnRHpE61UZZqHAenBm
HZIdLBxpZ56RQYzCN+ifrjR4ELTIfI0tUWVJSUWuW34hTpYfLFxWvi+BLLwnDbyC
brKIPmBtpks6HKctM/D4YBDiLC0/ZvvsmlWnzCX1ZxdkzZNm0Ah0rSvSP7I/wICA
x6tcJPMrUehuA13koaI++2SE7mI87wZb8DygbnxobCgwRwKJz2JgjATFPoV3Asyz
whJD47Pn2t8=
=0jdz
-----END PGP SIGNATURE-----

--Apple-Mail=_99008B0B-2380-47D5-A518-D24FACDEAD89--


From nobody Mon Feb  1 19:56:28 2016
Return-Path: <marka@isc.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 744E11A6F0E; Mon,  1 Feb 2016 19:55:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 pigOEC5K4yY5; Mon,  1 Feb 2016 19:55:27 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C07E01A6F0B; Mon,  1 Feb 2016 19:55:27 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx.ams1.isc.org (Postfix) with ESMTPS id F04B31FCAD4; Tue,  2 Feb 2016 03:55:23 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id C8F6216004B; Tue,  2 Feb 2016 03:55:40 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id BC38416004A; Tue,  2 Feb 2016 03:55:40 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 6hMTg9nFbU-l; Tue,  2 Feb 2016 03:55:40 +0000 (UTC)
Received: from rock.dv.isc.org (c122-106-161-187.carlnfd1.nsw.optusnet.com.au [122.106.161.187]) by zmx1.isc.org (Postfix) with ESMTPSA id 41F54160047; Tue,  2 Feb 2016 03:55:40 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 9932E415A9C9; Tue,  2 Feb 2016 14:55:20 +1100 (EST)
To: "Fred Baker (fred)" <fred@cisco.com>
From: Mark Andrews <marka@isc.org>
References: <201602011400.u11E0Hsd009385@irp-lnx1.cisco.com> <20160201231151.25706414D77A@rock.dv.isc.org> <61DE78D0-8B8D-4BD3-B6B4-5275B118D6F5@cisco.com>
Subject: Re: [v6ops] State of play
In-reply-to: Your message of "Tue, 02 Feb 2016 03:49:34 -0000." <61DE78D0-8B8D-4BD3-B6B4-5275B118D6F5@cisco.com>
Date: Tue, 02 Feb 2016 14:55:20 +1100
Message-Id: <20160202035520.9932E415A9C9@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/3FGuUn0l6HzR4_mWDt_oQ872pAo>
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IPv6 IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2016 03:55:34 -0000

In message <61DE78D0-8B8D-4BD3-B6B4-5275B118D6F5@cisco.com>, "Fred Baker (fred)
" writes:
> 
> When you say "v6man", I assume you mean "6man".

yep.
 
> I'm a little lost. I don't see the words "chair" or "question" in the =
> draft. Could you be more specific about what your question is?

Which WG should take ownership of the problem space in this draft?

Mark

> > On Feb 1, 2016, at 3:11 PM, Mark Andrews <marka@isc.org> wrote:
> >=20
> >=20
> > draft-andrews-tcp-and-ipv6-use-minmtu-04 has an open question directed
> > at the v6man and v6ops chairs - should this be a v6man or v6ops?  It
> > needs to be fixed and I don't care in which forum it gets done but it
> > needs to be done.
> >=20
> > Mark
> >=20
> > In message <201602011400.u11E0Hsd009385@irp-lnx1.cisco.com>, =
> fred@cisco.com writes:
> >> RFC Editor: AUTH48
> >> 	2015-11-23	draft-ietf-v6ops-reducing-ra-energy-consumption
> >> 	2015-10-26	draft-ietf-v6ops-siit-dc
> >> 	2015-10-26	draft-ietf-v6ops-siit-dc-2xlat
> >> 	2015-10-26	draft-ietf-v6ops-siit-eam
> >>=20
> >> RFC Editor: In ISE Review
> >> 	2016-01-20	draft-ietf-v6ops-mobile-device-profile
> >>=20
> >> IESG: AD Evaluation
> >> 	2016-01-31	draft-bao-v6ops-rfc6145bis
> >>=20
> >> IESG: In Last Call
> >> 	2016-01-28	draft-ietf-v6ops-ipv6-ehs-in-real-world
> >>=20
> >> WG: Unupdated WG Document
> >> 	2015-10-19	draft-ietf-v6ops-design-choices
> >>=20
> >> WG: Updated WG Document
> >> 	2016-01-21	draft-ietf-v6ops-unique-ipv6-prefix-per-host
> >> 	2016-01-03	draft-ietf-v6ops-host-addr-availability
> >>=20
> >> Individual Submission: Unupdated
> >> 	2015-10-19	draft-xu-v6ops-dslite-redundancy
> >> 	2015-10-15	draft-gont-v6ops-ipv6-ehs-packet-drops
> >> 	2015-09-21	draft-ybai-v6ops-ipv6-for-openstack
> >>=20
> >> Individual Submission: Updated
> >> 	2016-01-05	draft-templin-v6ops-pdhost
> >> 	2016-01-03	draft-xcf-v6ops-chinatelecom-deployment
> >> 	2016-01-03	draft-xli-v6ops-cernet-deployment
> >>=20
> >> _______________________________________________
> >> v6ops mailing list
> >> v6ops@ietf.org
> >> https://www.ietf.org/mailman/listinfo/v6ops
> > --
> > Mark Andrews, ISC
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
> 
> 
> --Apple-Mail=_99008B0B-2380-47D5-A518-D24FACDEAD89
> Content-Transfer-Encoding: 7bit
> Content-Disposition: attachment; filename="signature.asc"
> Content-Type: application/pgp-signature; name="signature.asc"
> Content-Description: Message signed with OpenPGP using GPGMail
> 
> -----BEGIN PGP SIGNATURE-----
> Comment: GPGTools - http://gpgtools.org
> 
> iQIVAwUBVrAnTkayAOS/EQ8MAQL9Ug//e/6aNfv+AC2Iv2qAp6MjcIYyRcqRZLew
> hhXABkYFTk+/FPHe57xZ4W7h4eEpJ7L8Fha+M+tEzB1ydNc/n/3NsThP6iZCsIYE
> lemKravU5zMVEvGLeWoaj9YUdKXzlqgIT6TjcE/0wuyUS6a5MotVMXqLKNkwbwg5
> IIX1lZNeSWmc7dtWUIeh9/UzgzlGap9Nd0+MhQVoWvPXgNv4Xvq9AhFSOZsz3r1L
> dtiOGn6cwypfrNleDt7D62jtWpmtyM/R7CjDBVhEhDVXyEiEt5/BfPnfB8e5+Ozt
> +PvIPw7rPe3Y6tg37kZLTySOiHiJ0UDPCwk7B3KQtYlnfKjFmQ0w8aad+I9Gw7x6
> FtUuMZZn5GDzkzR1dpBMr9J2KGjtwO7szDo8C/ZONEfwzTkXwepvxfZoW8eQuTIu
> E09eFvtUmmpE5w3K9sU/8ku8h+rtNf85GO5rozDwGBlflZAnRHpE61UZZqHAenBm
> HZIdLBxpZ56RQYzCN+ifrjR4ELTIfI0tUWVJSUWuW34hTpYfLFxWvi+BLLwnDbyC
> brKIPmBtpks6HKctM/D4YBDiLC0/ZvvsmlWnzCX1ZxdkzZNm0Ah0rSvSP7I/wICA
> x6tcJPMrUehuA13koaI++2SE7mI87wZb8DygbnxobCgwRwKJz2JgjATFPoV3Asyz
> whJD47Pn2t8=
> =0jdz
> -----END PGP SIGNATURE-----
> 
> --Apple-Mail=_99008B0B-2380-47D5-A518-D24FACDEAD89--
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Mon Feb  1 20:11:57 2016
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61EA21A6F57; Mon,  1 Feb 2016 20:11:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.502
X-Spam-Level: 
X-Spam-Status: No, score=-114.502 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CishmxmrqkX6; Mon,  1 Feb 2016 20:10:54 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 887371A6F61; Mon,  1 Feb 2016 20:10:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5327; q=dns/txt; s=iport; t=1454386254; x=1455595854; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=rKi1783Vq9rh696lnOH00aZJnCI9RnSiSPkyZ0UkSPI=; b=WutFRvguxOp7MIeNLgjnkm/mbgBTLhYeDKmbArRHpZn5U27sMjtbR/ss 9hkDF2XvRzHolvbXeNSgHv0oZwTKKd6M9+iHBkjTC+VMI8GLNDRsih9Ve +N5VLu6Ie0/+W8D6naDZivpBO6TvXkquhfcqmYqytZDAY7o2EzaQrnSbl Y=;
X-Files: signature.asc : 833
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CyAgB0K7BW/4sNJK1egzpSbQaIU7FfD?= =?us-ascii?q?oFkGAqFbQKBNjgUAQEBAQEBAYEKhEEBAQEDAQEBAWsLBQkCAgEIGC4bDAslAgQ?= =?us-ascii?q?KBAUOiAUIDr14AQEBAQEBAQEBAQEBAQEBAQEBAQEBDQgEh3gIgkKEEwEBW4Jtg?= =?us-ascii?q?Q8FjSWJTAGCeYFjaogEgVtKjEuKbINRAR4BQ4NsagGIOjR8AQEB?=
X-IronPort-AV: E=Sophos;i="5.22,383,1449532800";  d="asc'?scan'208";a="69151054"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 02 Feb 2016 04:10:53 +0000
Received: from XCH-RCD-012.cisco.com (xch-rcd-012.cisco.com [173.37.102.22]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u124ArxG011943 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 2 Feb 2016 04:10:53 GMT
Received: from xch-rcd-013.cisco.com (173.37.102.23) by XCH-RCD-012.cisco.com (173.37.102.22) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Mon, 1 Feb 2016 22:10:52 -0600
Received: from xch-rcd-013.cisco.com ([173.37.102.23]) by XCH-RCD-013.cisco.com ([173.37.102.23]) with mapi id 15.00.1104.009; Mon, 1 Feb 2016 22:10:52 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Mark Andrews <marka@isc.org>
Subject: Re: [v6ops] State of play
Thread-Topic: [v6ops] State of play
Thread-Index: AQHRXWy7WKRnV1axq0Cue0ZfkN2Y9w==
Date: Tue, 2 Feb 2016 04:10:52 +0000
Message-ID: <D8D6B933-5786-48A2-8C4C-7A38BCC14B41@cisco.com>
References: <201602011400.u11E0Hsd009385@irp-lnx1.cisco.com> <20160201231151.25706414D77A@rock.dv.isc.org> <61DE78D0-8B8D-4BD3-B6B4-5275B118D6F5@cisco.com> <20160202035520.9932E415A9C9@rock.dv.isc.org>
In-Reply-To: <20160202035520.9932E415A9C9@rock.dv.isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3112)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.4.81]
Content-Type: multipart/signed; boundary="Apple-Mail=_C3A52B19-0A1F-40FC-8A7D-B9FD9111C660"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/O9AKqOxUT_P44v7DhJ6vDZzitaE>
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, IPv6 IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2016 04:11:03 -0000

--Apple-Mail=_C3A52B19-0A1F-40FC-8A7D-B9FD9111C660
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I would guess it belongs in 6man, but I'll let the 6man chairs decide =
whether they agree.

> On Feb 1, 2016, at 7:55 PM, Mark Andrews <marka@isc.org> wrote:
>=20
>=20
> In message <61DE78D0-8B8D-4BD3-B6B4-5275B118D6F5@cisco.com>, "Fred =
Baker (fred)
> " writes:
>>=20
>> When you say "v6man", I assume you mean "6man".
>=20
> yep.
>=20
>> I'm a little lost. I don't see the words "chair" or "question" in the =
=3D
>> draft. Could you be more specific about what your question is?
>=20
> Which WG should take ownership of the problem space in this draft?
>=20
> Mark
>=20
>>> On Feb 1, 2016, at 3:11 PM, Mark Andrews <marka@isc.org> wrote:
>>> =3D20
>>> =3D20
>>> draft-andrews-tcp-and-ipv6-use-minmtu-04 has an open question =
directed
>>> at the v6man and v6ops chairs - should this be a v6man or v6ops?  It
>>> needs to be fixed and I don't care in which forum it gets done but =
it
>>> needs to be done.
>>> =3D20
>>> Mark
>>> =3D20
>>> In message <201602011400.u11E0Hsd009385@irp-lnx1.cisco.com>, =3D
>> fred@cisco.com writes:
>>>> RFC Editor: AUTH48
>>>> 	2015-11-23	draft-ietf-v6ops-reducing-ra-energy-consumption
>>>> 	2015-10-26	draft-ietf-v6ops-siit-dc
>>>> 	2015-10-26	draft-ietf-v6ops-siit-dc-2xlat
>>>> 	2015-10-26	draft-ietf-v6ops-siit-eam
>>>> =3D20
>>>> RFC Editor: In ISE Review
>>>> 	2016-01-20	draft-ietf-v6ops-mobile-device-profile
>>>> =3D20
>>>> IESG: AD Evaluation
>>>> 	2016-01-31	draft-bao-v6ops-rfc6145bis
>>>> =3D20
>>>> IESG: In Last Call
>>>> 	2016-01-28	draft-ietf-v6ops-ipv6-ehs-in-real-world
>>>> =3D20
>>>> WG: Unupdated WG Document
>>>> 	2015-10-19	draft-ietf-v6ops-design-choices
>>>> =3D20
>>>> WG: Updated WG Document
>>>> 	2016-01-21	draft-ietf-v6ops-unique-ipv6-prefix-per-host
>>>> 	2016-01-03	draft-ietf-v6ops-host-addr-availability
>>>> =3D20
>>>> Individual Submission: Unupdated
>>>> 	2015-10-19	draft-xu-v6ops-dslite-redundancy
>>>> 	2015-10-15	draft-gont-v6ops-ipv6-ehs-packet-drops
>>>> 	2015-09-21	draft-ybai-v6ops-ipv6-for-openstack
>>>> =3D20
>>>> Individual Submission: Updated
>>>> 	2016-01-05	draft-templin-v6ops-pdhost
>>>> 	2016-01-03	draft-xcf-v6ops-chinatelecom-deployment
>>>> 	2016-01-03	draft-xli-v6ops-cernet-deployment
>>>> =3D20
>>>> _______________________________________________
>>>> v6ops mailing list
>>>> v6ops@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>> --
>>> Mark Andrews, ISC
>>> 1 Seymour St., Dundas Valley, NSW 2117, Australia
>>> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>>=20
>>=20
>> --Apple-Mail=3D_99008B0B-2380-47D5-A518-D24FACDEAD89
>> Content-Transfer-Encoding: 7bit
>> Content-Disposition: attachment; filename=3D"signature.asc"
>> Content-Type: application/pgp-signature; name=3D"signature.asc"
>> Content-Description: Message signed with OpenPGP using GPGMail
>>=20
>> -----BEGIN PGP SIGNATURE-----
>> Comment: GPGTools - http://gpgtools.org
>>=20
>> iQIVAwUBVrAnTkayAOS/EQ8MAQL9Ug//e/6aNfv+AC2Iv2qAp6MjcIYyRcqRZLew
>> hhXABkYFTk+/FPHe57xZ4W7h4eEpJ7L8Fha+M+tEzB1ydNc/n/3NsThP6iZCsIYE
>> lemKravU5zMVEvGLeWoaj9YUdKXzlqgIT6TjcE/0wuyUS6a5MotVMXqLKNkwbwg5
>> IIX1lZNeSWmc7dtWUIeh9/UzgzlGap9Nd0+MhQVoWvPXgNv4Xvq9AhFSOZsz3r1L
>> dtiOGn6cwypfrNleDt7D62jtWpmtyM/R7CjDBVhEhDVXyEiEt5/BfPnfB8e5+Ozt
>> +PvIPw7rPe3Y6tg37kZLTySOiHiJ0UDPCwk7B3KQtYlnfKjFmQ0w8aad+I9Gw7x6
>> FtUuMZZn5GDzkzR1dpBMr9J2KGjtwO7szDo8C/ZONEfwzTkXwepvxfZoW8eQuTIu
>> E09eFvtUmmpE5w3K9sU/8ku8h+rtNf85GO5rozDwGBlflZAnRHpE61UZZqHAenBm
>> HZIdLBxpZ56RQYzCN+ifrjR4ELTIfI0tUWVJSUWuW34hTpYfLFxWvi+BLLwnDbyC
>> brKIPmBtpks6HKctM/D4YBDiLC0/ZvvsmlWnzCX1ZxdkzZNm0Ah0rSvSP7I/wICA
>> x6tcJPMrUehuA13koaI++2SE7mI87wZb8DygbnxobCgwRwKJz2JgjATFPoV3Asyz
>> whJD47Pn2t8=3D
>> =3D0jdz
>> -----END PGP SIGNATURE-----
>>=20
>> --Apple-Mail=3D_99008B0B-2380-47D5-A518-D24FACDEAD89--
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


--Apple-Mail=_C3A52B19-0A1F-40FC-8A7D-B9FD9111C660
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIVAwUBVrAsS0ayAOS/EQ8MAQKmUxAAn2dICp04V9RurE2NarL2QdKwWDhGcK0+
q0OoEYxOl1YbLWZzHwuNEBRPL3Xg/HtPMKRYkT5ARheT5d5h9tAInR5ztZ0LYD/9
+xqMlfZBDXYEXAW8HHw+gCtKQCrWN414uUTJc3ITOwO/86nCnSWO4mPE3ZpYs9pB
HnY//keYgoMf20v0cMWOo1nhKQY0Tbt73sNCYgz/GFY/ffXABd3KtmrL4w2wJ/Mt
XQskls7oGBNrkBc1RLxNpFYKtV1+2x9wwOfefkm1JYCj59FnIsRji2Bz0qrTX0kG
cgCpHF5+BO/SZHw76je/u7KSPlv7ZE315Vuye73X+2hZ9wS6AWbxak+OlpytjWj3
IIzmhe+vjAm5QfSjAixtt1jJxpt0sxHxiCoSkSKi0bUMmDIYXbsfG+NcXgW2nMb/
zfXw3tRvJCgq0J9gizPEJQtnK0SGWr3/ag1oZG9fCOkG9aJ2d21JCSeRyINo83Kn
lQfuBeOMo3BsTQip6P1JXp7Y4TesACxQjH5mst0e2bVtkIxrNwePZRj0lzfFVXsW
s7exSjK0pdnAhVOoaEMfkWaWeIDETbl6KP99ZHVc620TIeBwlTTSIWGb32WK8mha
cgiDu9N9FJxhZ40eWtcFmNBGH34bKha+ksElBzqrj1YNZBSB9ZWJQWzbiBK2PwFD
ZPJ4x07ybS8=
=XrJS
-----END PGP SIGNATURE-----

--Apple-Mail=_C3A52B19-0A1F-40FC-8A7D-B9FD9111C660--


From nobody Tue Feb  2 00:38:16 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 274FC1AC3CD; Tue,  2 Feb 2016 00:36:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-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 QBLn0DqrxOkF; Tue,  2 Feb 2016 00:36:07 -0800 (PST)
Received: from cowbell.employees.org (cowbell.employees.org [IPv6:2001:1868:a000:17::142]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B79221AC3CC; Tue,  2 Feb 2016 00:36:07 -0800 (PST)
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id F36E3D7884; Tue,  2 Feb 2016 00:36:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=MseW3nzPW1TKnPG9gx8hJSGO+2o=; b= ENxSOrfYSmGAn+lGnJbviA7Ccfpoc2op1AVPlfodqBvyZKzQRwRtl8rhbH8lWIC4 LuZGaoE/NLYhPITivCq+MPpAFwUqcxxnlqoAUFvtOBSNXh4r3j7unpDTY00+byQ4 scd3vhcBkhUT9AkTFeZljqRBro8JNPkAlhQhoZ6dxYs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=jLevplR6VBrhWZmdhIFthXa3Tk RFzVzzJo4Hdsv/mdpwtCBVPGI13NXRBGhvu/1m60WMOQrnjT1eT3QklolS22h3j4 F3dmfDRrrENXf+YJD7PHZ9EGB3UEH/n1N8FsPdknvdEAb18vASVxoee++mu/ThY4 Y2fzXrEAOJt5pmRSo=
Received: from h.hanazo.no (unknown [173.38.220.53]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 8376CD7882; Tue,  2 Feb 2016 00:36:05 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 00E65FC74D8; Tue,  2 Feb 2016 09:36:02 +0100 (CET)
Subject: Re: [v6ops] State of play
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Content-Type: multipart/signed; boundary="Apple-Mail=_19273F70-E38D-4231-BB1C-CF5BDAE3F7EC"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <20160202035520.9932E415A9C9@rock.dv.isc.org>
Date: Tue, 2 Feb 2016 09:36:02 +0100
Message-Id: <FD36029E-14CD-40EC-9A59-68CDFE7DB56F@employees.org>
References: <201602011400.u11E0Hsd009385@irp-lnx1.cisco.com> <20160201231151.25706414D77A@rock.dv.isc.org> <61DE78D0-8B8D-4BD3-B6B4-5275B118D6F5@cisco.com> <20160202035520.9932E415A9C9@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/gvKAMpj_tDq19a-4uYxDvIQgpDI>
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2016 08:36:10 -0000

--Apple-Mail=_19273F70-E38D-4231-BB1C-CF5BDAE3F7EC
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Mark,

>> When you say "v6man", I assume you mean "6man".
> 
> yep.
> 
>> I'm a little lost. I don't see the words "chair" or "question" in the =
>> draft. Could you be more specific about what your question is?
> 
> Which WG should take ownership of the problem space in this draft?

is this an implementation bug, specification bug or both?

Best regards,
Ole

> 
>>> On Feb 1, 2016, at 3:11 PM, Mark Andrews <marka@isc.org> wrote:
>>> =20
>>> =20
>>> draft-andrews-tcp-and-ipv6-use-minmtu-04 has an open question directed
>>> at the v6man and v6ops chairs - should this be a v6man or v6ops?  It
>>> needs to be fixed and I don't care in which forum it gets done but it
>>> needs to be done.
>>> =20
>>> Mark
>>> =20
>>> In message <201602011400.u11E0Hsd009385@irp-lnx1.cisco.com>, =
>> fred@cisco.com writes:
>>>> RFC Editor: AUTH48
>>>> 	2015-11-23	draft-ietf-v6ops-reducing-ra-energy-consumption
>>>> 	2015-10-26	draft-ietf-v6ops-siit-dc
>>>> 	2015-10-26	draft-ietf-v6ops-siit-dc-2xlat
>>>> 	2015-10-26	draft-ietf-v6ops-siit-eam
>>>> =20
>>>> RFC Editor: In ISE Review
>>>> 	2016-01-20	draft-ietf-v6ops-mobile-device-profile
>>>> =20
>>>> IESG: AD Evaluation
>>>> 	2016-01-31	draft-bao-v6ops-rfc6145bis
>>>> =20
>>>> IESG: In Last Call
>>>> 	2016-01-28	draft-ietf-v6ops-ipv6-ehs-in-real-world
>>>> =20
>>>> WG: Unupdated WG Document
>>>> 	2015-10-19	draft-ietf-v6ops-design-choices
>>>> =20
>>>> WG: Updated WG Document
>>>> 	2016-01-21	draft-ietf-v6ops-unique-ipv6-prefix-per-host
>>>> 	2016-01-03	draft-ietf-v6ops-host-addr-availability
>>>> =20
>>>> Individual Submission: Unupdated
>>>> 	2015-10-19	draft-xu-v6ops-dslite-redundancy
>>>> 	2015-10-15	draft-gont-v6ops-ipv6-ehs-packet-drops
>>>> 	2015-09-21	draft-ybai-v6ops-ipv6-for-openstack
>>>> =20
>>>> Individual Submission: Updated
>>>> 	2016-01-05	draft-templin-v6ops-pdhost
>>>> 	2016-01-03	draft-xcf-v6ops-chinatelecom-deployment
>>>> 	2016-01-03	draft-xli-v6ops-cernet-deployment
>>>> =20
>>>> _______________________________________________
>>>> v6ops mailing list
>>>> v6ops@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/v6ops
>>> --
>>> Mark Andrews, ISC
>>> 1 Seymour St., Dundas Valley, NSW 2117, Australia
>>> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>> 
>> 
>> --Apple-Mail=_99008B0B-2380-47D5-A518-D24FACDEAD89
>> Content-Transfer-Encoding: 7bit
>> Content-Disposition: attachment; filename="signature.asc"
>> Content-Type: application/pgp-signature; name="signature.asc"
>> Content-Description: Message signed with OpenPGP using GPGMail
>> 
>> -----BEGIN PGP SIGNATURE-----
>> Comment: GPGTools - http://gpgtools.org
>> 
>> iQIVAwUBVrAnTkayAOS/EQ8MAQL9Ug//e/6aNfv+AC2Iv2qAp6MjcIYyRcqRZLew
>> hhXABkYFTk+/FPHe57xZ4W7h4eEpJ7L8Fha+M+tEzB1ydNc/n/3NsThP6iZCsIYE
>> lemKravU5zMVEvGLeWoaj9YUdKXzlqgIT6TjcE/0wuyUS6a5MotVMXqLKNkwbwg5
>> IIX1lZNeSWmc7dtWUIeh9/UzgzlGap9Nd0+MhQVoWvPXgNv4Xvq9AhFSOZsz3r1L
>> dtiOGn6cwypfrNleDt7D62jtWpmtyM/R7CjDBVhEhDVXyEiEt5/BfPnfB8e5+Ozt
>> +PvIPw7rPe3Y6tg37kZLTySOiHiJ0UDPCwk7B3KQtYlnfKjFmQ0w8aad+I9Gw7x6
>> FtUuMZZn5GDzkzR1dpBMr9J2KGjtwO7szDo8C/ZONEfwzTkXwepvxfZoW8eQuTIu
>> E09eFvtUmmpE5w3K9sU/8ku8h+rtNf85GO5rozDwGBlflZAnRHpE61UZZqHAenBm
>> HZIdLBxpZ56RQYzCN+ifrjR4ELTIfI0tUWVJSUWuW34hTpYfLFxWvi+BLLwnDbyC
>> brKIPmBtpks6HKctM/D4YBDiLC0/ZvvsmlWnzCX1ZxdkzZNm0Ah0rSvSP7I/wICA
>> x6tcJPMrUehuA13koaI++2SE7mI87wZb8DygbnxobCgwRwKJz2JgjATFPoV3Asyz
>> whJD47Pn2t8=
>> =0jdz
>> -----END PGP SIGNATURE-----
>> 
>> --Apple-Mail=_99008B0B-2380-47D5-A518-D24FACDEAD89--
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_19273F70-E38D-4231-BB1C-CF5BDAE3F7EC
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIcBAEBCgAGBQJWsGpyAAoJEL7aWKiYQt92O7sQAJzx6xjmS0K7pNjzzU1WoSxT
/PCAbCin7vnDMqbk8758z16l6F1pbZ1gWNkIPagiCMHbgAkSwkGU1Fj+j4qEWvcY
EeF/1rcCbQNcWqGQZuopabI9uEHxMbvVKpPPmRwLPwq9UUIgimpYn2cyYg1umZU9
3stWAq/XrYH7BND96Pyb8hbFI660UqyfJJrmyRVxH+SrGboEF5JyI+sGEgFIqe3b
RzY/6tJWtyFqtTlaq8ooqWQsNcWsaz0opbM5dvYY8/VshznSbKSEPxcCDq98hSnm
kZKYJYG+ttWpkhTVwMAM6jso/WGw5eaSdzf5jpu1atZE69+IXYa60/aIbjpwaKQg
KjA13wd59mywEqwr+R2HcjNDCU3x2twkV6vWXlIjh933TusOjYsloFcPX3U9rtwZ
1k3Nlc61Gl2uXd7B3RT5hnHli2BaWV7WYdwWeAxVdlzn18lf/dXVnGvDlWQ8cTDu
VInpjJtloXitwd0Cp7m6P+j2BevlFceYRw/H2GP7yeviuRl5q8o9/43ZA/nxsvRg
G+j2ZGrXTw9QzeP/QeKdvxncPh2rZdxS5iVo8k6c3eld1/TwLoYnrvkhL0NkmknD
60ZPNIjpktABM6zDM3Qosky6JyAWP4Bn7NIDlkHgl3IjsWmCHQCvHj6B8bzblfQb
aiwCeoX2d+QQgd6eIYJu
=UHdx
-----END PGP SIGNATURE-----

--Apple-Mail=_19273F70-E38D-4231-BB1C-CF5BDAE3F7EC--


From nobody Tue Feb  2 00:46:47 2016
Return-Path: <marka@isc.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E65661AC400; Tue,  2 Feb 2016 00:46:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 RS9UX9InjmAw; Tue,  2 Feb 2016 00:46:42 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22A901AC3F9; Tue,  2 Feb 2016 00:46:42 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx.pao1.isc.org (Postfix) with ESMTPS id BD3AA34930F; Tue,  2 Feb 2016 08:46:40 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 9826B160043; Tue,  2 Feb 2016 08:46:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 877E016005C; Tue,  2 Feb 2016 08:46:59 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id HuIuds2IJF44; Tue,  2 Feb 2016 08:46:59 +0000 (UTC)
Received: from rock.dv.isc.org (c122-106-161-187.carlnfd1.nsw.optusnet.com.au [122.106.161.187]) by zmx1.isc.org (Postfix) with ESMTPSA id 1BB7D160043; Tue,  2 Feb 2016 08:46:59 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 296134160605; Tue,  2 Feb 2016 19:46:37 +1100 (EST)
To: otroan@employees.org
From: Mark Andrews <marka@isc.org>
References: <201602011400.u11E0Hsd009385@irp-lnx1.cisco.com> <20160201231151.25706414D77A@rock.dv.isc.org> <61DE78D0-8B8D-4BD3-B6B4-5275B118D6F5@cisco.com> <20160202035520.9932E415A9C9@rock.dv.isc.org> <FD36029E-14CD-40EC-9A59-68CDFE7DB56F@employees.org>
Subject: Re: [v6ops] State of play
In-reply-to: Your message of "Tue, 02 Feb 2016 09:36:02 +0100." <FD36029E-14CD-40EC-9A59-68CDFE7DB56F@employees.org>
Date: Tue, 02 Feb 2016 19:46:37 +1100
Message-Id: <20160202084637.296134160605@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/SmNDBtVm1KY4bs7R3YUvGkRcKc4>
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2016 08:46:44 -0000

In message <FD36029E-14CD-40EC-9A59-68CDFE7DB56F@employees.org>, otroan@employees.org writes:
> 
> Mark,
> 
> >> When you say "v6man", I assume you mean "6man".
> > 
> > yep.
> > 
> >> I'm a little lost. I don't see the words "chair" or "question" in the =
> >> draft. Could you be more specific about what your question is?
> > 
> > Which WG should take ownership of the problem space in this draft?
> 
> is this an implementation bug, specification bug or both?

Possibly both as implementers failed to apply the simple logic of
if the mtu is limited then the tcp segment size also limited.  If
limit is applied prior to the MSS negotiation then that too is also
limited.

It's all a matter of how much hand holding should there be which
is a judgement call.

Mark

> Best regards,
> Ole
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Feb  2 07:33:43 2016
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7103C1B2C63; Tue,  2 Feb 2016 07:33:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.502
X-Spam-Level: 
X-Spam-Status: No, score=-114.502 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JyFjnXj_9ZBk; Tue,  2 Feb 2016 07:33:40 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F311D1B2C62; Tue,  2 Feb 2016 07:33:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2746; q=dns/txt; s=iport; t=1454427220; x=1455636820; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=ojPjOxx85GbR8NdHGqoEfB9pv4Fp9f3rf1E2xG9AMuY=; b=KG2dr3NUFHxcqlpmb5BFqUzL0NjZYEjpwCcVHo+KCKdrLTziTUFa6e6M LauJHoBgSsz/TBrnSY4HVBQXgRKmbVG6vr5Sv++EL1xlwV+4MpTaSDEqZ 2T28kWn2ZEAktiZOqSvdcuWs1546Zho7oiIvNH7PGGro3ojkxs6yPpYdW g=;
X-Files: signature.asc : 833
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DDAgBzy7BW/4oNJK1egzqBPwaIU7FsD?= =?us-ascii?q?oFkhg0CgUU4FAEBAQEBAQGBCoRCAQEEeRACAQgYLjIlAgQOBQ6IDb5oAQEBAQE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBAQEBDQiHfIJKh12BDwWWcQGCeYFjiG6BW4dohS6OPgEeA?= =?us-ascii?q?UODZGqIb3wBAQE?=
X-IronPort-AV: E=Sophos;i="5.22,385,1449532800";  d="asc'?scan'208";a="72204171"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 02 Feb 2016 15:33:39 +0000
Received: from XCH-RCD-015.cisco.com (xch-rcd-015.cisco.com [173.37.102.25]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u12FXdao025625 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 2 Feb 2016 15:33:39 GMT
Received: from xch-rcd-013.cisco.com (173.37.102.23) by XCH-RCD-015.cisco.com (173.37.102.25) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 2 Feb 2016 09:33:38 -0600
Received: from xch-rcd-013.cisco.com ([173.37.102.23]) by XCH-RCD-013.cisco.com ([173.37.102.23]) with mapi id 15.00.1104.009; Tue, 2 Feb 2016 09:33:38 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Mark Andrews <marka@isc.org>
Subject: Re: [v6ops] State of play
Thread-Topic: [v6ops] State of play
Thread-Index: AQHRXc8WWKRnV1axq0Cue0ZfkN2Y9w==
Date: Tue, 2 Feb 2016 15:33:38 +0000
Message-ID: <F0944BE4-7A56-4E1E-A27D-680339DC4F02@cisco.com>
References: <201602011400.u11E0Hsd009385@irp-lnx1.cisco.com> <20160201231151.25706414D77A@rock.dv.isc.org>
In-Reply-To: <20160201231151.25706414D77A@rock.dv.isc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3112)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.51.158]
Content-Type: multipart/signed; boundary="Apple-Mail=_7EC40467-66AA-40E0-82A3-F4EBF66B4D46"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/YlNb4humJaK0ugD5z6PYYTPQdmM>
Cc: v6ops list <v6ops@ietf.org>, IPv6 IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Feb 2016 15:33:41 -0000

--Apple-Mail=_7EC40467-66AA-40E0-82A3-F4EBF66B4D46
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Feb 1, 2016, at 3:11 PM, Mark Andrews <marka@isc.org> wrote:
> draft-andrews-tcp-and-ipv6-use-minmtu-04 has an open question directed
> at the v6man and v6ops chairs - should this be a v6man or v6ops?  It
> needs to be fixed and I don't care in which forum it gets done but it
> needs to be done.

OK, I have now actually read the draft, rather than looking through it =
for what you described as an open question to the chairs embedded in it.

I suspect you might actually be looking at intarea.

In any event, I disagree with the proposal in the draft, which is that =
TCP should look at whether "use min MTU" is set. Yes, if it is set, that =
should be observed; I'm not sure why an implementation would offer the =
flag without considering it. However, if I understand the question, the =
key point is that the Maximum Segment Size offered in the TCP MSS should =
be a size that can be sent on the interface in question using the IP =
variant selected, and any options or extension headers that need to be =
present, not whether a given flag is set in a not-actually-standard API. =
If folks are offering an MSS value that can't be supported, they have an =
implementation bug, regardless of whether they are checking for the =
flag.

Can you describe the implementation? Is this Apple, Microsoft, Linux, =
FreeBSD, Android, something else? Give us a test for reproducing the =
fault?

--Apple-Mail=_7EC40467-66AA-40E0-82A3-F4EBF66B4D46
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIVAwUBVrDMUUayAOS/EQ8MAQIBhRAAhWMoZEryg3/o87/3SxFBG4Xkq+R+XcNU
KbaiwFbuf7zKaUDo32ubP1ZgXghOvvUEVbuKKN/VoVN4RUF4apZclj7WV0Kq+rXV
o9DEHWbp5OojfPJxJyvXV0eXm3aN0nuCEY7gBxw2CUnMKcjhdxTnYsPnuISG8OdI
YjwzRWxZF3leI1t8ScX7fHKW2ssEuZ7n/b9btrRmbv+2CYIegyQvbj6wjZi+oUxj
XyVrXtTZKpMP1c0mi6PrFdLbinKtxuVn2wmzEihrvHzYj79eV/nbdj93Tu2K9bcn
/hELdBeedYzbO74lg/tsf/6gYa8ada8qCeekB98hPH7tt4WRALozYtkE/P+kSpnn
FKP42+lDshW9DOUjapnXcVqyFNOP1S7c77TTQyML29HIGofD4yDujkBTgoqoDxm6
jwlw273Cb6EhmqKh+VjiH1W94Ya0Sg7P1pjXo5zXO/chXWiQZD0/8OooaTLW1EFX
0WMZhOFs4QbGn5kydVm8qOy5yjmdhJrh8DoB32oUSvOQYbrkHwxDuehTTmQF+fFc
TzLsSTLkuirIWxsDw+X1P6urr4KT9faD8Zd8YqjqkwQ3X/PdTb7xKjcexoZJaNmF
UZ6PK8AuB8wnhlGaGrdtoPrvqwP+OnttDguUEu37meHFl5CpftzAmZPc0gR6FYA8
tj0x7VAKKzQ=
=Btvy
-----END PGP SIGNATURE-----

--Apple-Mail=_7EC40467-66AA-40E0-82A3-F4EBF66B4D46--


From nobody Tue Feb  2 17:58:09 2016
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AB271B3170; Tue,  2 Feb 2016 17:58:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level: 
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 LTRIro3xZJlE; Tue,  2 Feb 2016 17:58:06 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1675F1B3154; Tue,  2 Feb 2016 17:58:06 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id EABC618046A; Tue,  2 Feb 2016 17:57:54 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7739 on Security Implications of Predictable Fragment Identification Values
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160203015754.EABC618046A@rfc-editor.org>
Date: Tue,  2 Feb 2016 17:57:54 -0800 (PST)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/0WrHOOV85vNPcGxDZiZJFaaoJ_Q>
Cc: drafts-update-ref@iana.org, ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2016 01:58:07 -0000

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

        
        RFC 7739

        Title:      Security Implications of Predictable Fragment 
                    Identification Values 
        Author:     F. Gont
        Status:     Informational
        Stream:     IETF
        Date:       February 2016
        Mailbox:    fgont@si6networks.com
        Pages:      20
        Characters: 46433
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-6man-predictable-fragment-id-10.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7739

IPv6 specifies the Fragment Header, which is employed for the
fragmentation and reassembly mechanisms.  The Fragment Header
contains an "Identification" field that, together with the IPv6
Source Address and the IPv6 Destination Address of a packet,
identifies fragments that correspond to the same original datagram,
such that they can be reassembled together by the receiving host.
The only requirement for setting the Identification field is that the
corresponding value must be different than that employed for any
other fragmented datagram sent recently with the same Source Address
and Destination Address.  Some implementations use a simple global
counter for setting the Identification field, thus leading to
predictable Identification values.  This document analyzes the
security implications of predictable Identification values, and
provides implementation guidance for setting the Identification field
of the Fragment Header, such that the aforementioned security
implications are mitigated.

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


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

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

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

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


The RFC Editor Team
Association Management Solutions, LLC



From nobody Wed Feb  3 12:25:58 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4FEF1B2C6F for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 12:25:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-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 j9U3GH5AsKYu for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 12:25:55 -0800 (PST)
Received: from cowbell.employees.org (cowbell.employees.org [IPv6:2001:1868:a000:17::142]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 065C51B2BF8 for <ipv6@ietf.org>; Wed,  3 Feb 2016 12:25:55 -0800 (PST)
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id A8017D7884; Wed,  3 Feb 2016 12:25:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :content-type:subject:date:message-id:cc:to:mime-version; s= selector1; bh=8hbwOzMf3rAc4YzfgqT+7+vIFKE=; b=TXQs/FEwj5Jh5e6dtt kcqwDY9KEAvmHLvujFxIhp+FkkYUYfjT6c+LKkrYWKYYgqv5GJSgCZmwOAUWekTj zC9VsQRX1MkPbSxfMnKMmAhW07zY+6RJ5kWaVjtGs0qUfZVDUIO3W//0I5yUC/Em oPdgbF1uYG1HqPZWMB+VcUxL4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :content-type:subject:date:message-id:cc:to:mime-version; q=dns; s=selector1; b=NC2Bvzh+d0CJ/gcoaXh/TdjlMxtpfmIDwdQixP3w0RFORGpP z71xDTaoHaNOdMQVZ7ojicWQOjCMz1XdJCiGDp68JJBKLONbGOOLrSOT/joNPK4j KqkrjxRUdX94mgO6PRGkuCIKB7P/i68iu0KuFnZN/9ZMfu8P9QS441W8gNw=
Received: from h.hanazo.no (unknown [195.159.234.46]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 783D1D7881; Wed,  3 Feb 2016 12:25:53 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 197C8FEC81A; Wed,  3 Feb 2016 21:25:51 +0100 (CET)
From: otroan@employees.org
X-Pgp-Agent: GPGMail 2.6b2
Content-Type: multipart/signed; boundary="Apple-Mail=_F3994F2C-7F60-4F51-980E-A6EC59DEE940"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Date: Wed, 3 Feb 2016 21:25:50 +0100
Message-Id: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org>
To: 6man WG <ipv6@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/oBPAJHYdxTSgpKK1h_1y1UY5x2Y>
Cc: bob.hinden@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2016 20:25:56 -0000

--Apple-Mail=_F3994F2C-7F60-4F51-980E-A6EC59DEE940
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

This message starts a two week 6MAN call on adopting:

Name:	draft-hinden-6man-rfc1981bis-01
Title:	Path MTU Discovery for IP version 6
Document date:	2015-12-01
Pages:	16
URL:         =
https://datatracker.ietf.org/doc/draft-hinden-6man-rfc1981bis/
Htmlized:  https://tools.ietf.org/html/draft-hinden-6man-rfc1981bis-01
Diff:          =
https://tools.ietf.org/rfcdiff?url2=3Ddraft-hinden-6man-rfc1981bis-01.txt

as a working group item. Substantive comments and statements of support
for adopting this document should be directed to the mailing
list. Editorial suggestions can be sent to the authors.

This document is part of the working group=E2=80=99s ongoing work on =
advancing the
 core IPv6 standards to Internet Standard.

This adoption call will end on February 17th, 2016.

Regards,

Bob Hinden & Ole Tr=C3=B8an


--Apple-Mail=_F3994F2C-7F60-4F51-980E-A6EC59DEE940
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIcBAEBCgAGBQJWsmJOAAoJEL7aWKiYQt921rkP/ir0mYnH5PS9aAQUT2h2DXkP
oDA7JlL0TIdxnc+PhgMVpHHzYjzbiLnIoOcZxPcU+GgJDa94r1hVkvWbFYJU7dQM
0ODM9SPmi3892e+D1nVDX2T8ijfKZ7+vPLEZ+m6qwkNNvhf9EX3Z3CwIKk7RZ/CI
uMzIxg8rvhMF+vavr3aMwFN37sIWt0wy9ouvi8OzeDvgR2zn18llm+Dh/IxSFA3N
5Y+8NMkKgs6AvwlTdWcnhP01Pi6xmoCduD1ip1btLo9DTZuaWqL9HVg6PdDTYlyG
bjqMVjQkDpP/IYJkcl9KkdOtS4Uh8eHgkHJADhb99LcE1ysybJ1nT9YotJvtgUhP
Mtb6oYl9vOHmPYlqXe/g0LkC3W1vGoDqMPkWLLuK7iXq9/8+YUwwQ8pZjBg3BcGp
8VDORMeKNsYKSfv9yLhB/3IKtGsLCkE8mWjJU9AHIejxZ0F4dpYe/Jw/3LMDa305
83qLnKIA7mcHESjhuxxoGRCeZWin9iuqdPnnG8+54WRZHNEsrjnlTkgfMQKUVC0F
SeEVz1AbOEaddXzRUT5WE/tVWEdWve+EtPrt4CpdiHYgHC/mqjUAbVmZpvOzzoZ+
samXrN0eFQFr0yt3GYdVf4sNosd5q6ESK8VR38Zez8xxGoU0Fpwg/CN/ohDxxKSR
7gTD86xDcX4APFKqF9C8
=2yky
-----END PGP SIGNATURE-----

--Apple-Mail=_F3994F2C-7F60-4F51-980E-A6EC59DEE940--


From nobody Wed Feb  3 12:54:24 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E22B51B2CB7 for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 12:54:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 Q2r6pdwg0FLF for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 12:54:21 -0800 (PST)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) (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 49B5B1B2CB6 for <ipv6@ietf.org>; Wed,  3 Feb 2016 12:54:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u13KsJD9001892; Wed, 3 Feb 2016 14:54:19 -0600
Received: from XCH-BLV-101.nw.nos.boeing.com (xch-blv-101.nw.nos.boeing.com [130.247.25.116]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u13KsGAx001870 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 3 Feb 2016 14:54:16 -0600
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-BLV-101.nw.nos.boeing.com ([169.254.1.207]) with mapi id 14.03.0235.001; Wed, 3 Feb 2016 12:54:15 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "otroan@employees.org" <otroan@employees.org>, 6man WG <ipv6@ietf.org>
Subject: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AQHRXsEg80dfpGCQDUCIhA2edhybgJ8ay9Ow
Date: Wed, 3 Feb 2016 20:54:15 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395D25D@XCH-BLV-105.nw.nos.boeing.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org>
In-Reply-To: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Gf9g7swGLTx6txCsmNSBE8E-FK4>
Cc: "bob.hinden@gmail.com" <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2016 20:54:23 -0000

SGkgT2xlLA0KDQpPbmUgcXVlc3Rpb24gb24gdGhlIGF1dGhvcnNoaXAgLSBJIGNhbiBzYXkgd2l0
aCBzb21lIGNlcnRhaW50eSB0aGF0IEphY2sgTWNDYW5uDQphbmQgSmVmZiBNb2d1bCBhcmUgbm8g
bG9uZ2VyIHdpdGggRGlnaXRhbCBFcXVpcG1lbnQgQ29ycG9yYXRpb24uIFdvdWxkIHRoZXkgIGJl
DQphY3RpdmVseSBpbnZvbHZlZCBpbiB0aGlzIHdvcmsgaWYgaXQgaXMgYWNjZXB0ZWQgYXMgYSB3
b3JraW5nIGdyb3VwIGl0ZW0/DQoNClRoYW5rcyAtIEZyZWQNCg0KPiAtLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KPiBGcm9tOiBpcHY2IFttYWlsdG86aXB2Ni1ib3VuY2VzQGlldGYub3JnXSBP
biBCZWhhbGYgT2Ygb3Ryb2FuQGVtcGxveWVlcy5vcmcNCj4gU2VudDogV2VkbmVzZGF5LCBGZWJy
dWFyeSAwMywgMjAxNiAxMjoyNiBQTQ0KPiBUbzogNm1hbiBXRw0KPiBDYzogYm9iLmhpbmRlbkBn
bWFpbC5jb20NCj4gU3ViamVjdDogNk1BTjogQWRvcHRpb24gY2FsbCBvbiBkcmFmdC1oaW5kZW4t
Nm1hbi1yZmMxOTgxYmlzLTAxDQo+IA0KPiBUaGlzIG1lc3NhZ2Ugc3RhcnRzIGEgdHdvIHdlZWsg
Nk1BTiBjYWxsIG9uIGFkb3B0aW5nOg0KPiANCj4gTmFtZToJZHJhZnQtaGluZGVuLTZtYW4tcmZj
MTk4MWJpcy0wMQ0KPiBUaXRsZToJUGF0aCBNVFUgRGlzY292ZXJ5IGZvciBJUCB2ZXJzaW9uIDYN
Cj4gRG9jdW1lbnQgZGF0ZToJMjAxNS0xMi0wMQ0KPiBQYWdlczoJMTYNCj4gVVJMOiAgICAgICAg
IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWhpbmRlbi02bWFuLXJmYzE5
ODFiaXMvDQo+IEh0bWxpemVkOiAgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWhp
bmRlbi02bWFuLXJmYzE5ODFiaXMtMDENCj4gRGlmZjogICAgICAgICAgaHR0cHM6Ly90b29scy5p
ZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtaGluZGVuLTZtYW4tcmZjMTk4MWJpcy0wMS50eHQN
Cj4gDQo+IGFzIGEgd29ya2luZyBncm91cCBpdGVtLiBTdWJzdGFudGl2ZSBjb21tZW50cyBhbmQg
c3RhdGVtZW50cyBvZiBzdXBwb3J0DQo+IGZvciBhZG9wdGluZyB0aGlzIGRvY3VtZW50IHNob3Vs
ZCBiZSBkaXJlY3RlZCB0byB0aGUgbWFpbGluZw0KPiBsaXN0LiBFZGl0b3JpYWwgc3VnZ2VzdGlv
bnMgY2FuIGJlIHNlbnQgdG8gdGhlIGF1dGhvcnMuDQo+IA0KPiBUaGlzIGRvY3VtZW50IGlzIHBh
cnQgb2YgdGhlIHdvcmtpbmcgZ3JvdXDigJlzIG9uZ29pbmcgd29yayBvbiBhZHZhbmNpbmcgdGhl
DQo+ICBjb3JlIElQdjYgc3RhbmRhcmRzIHRvIEludGVybmV0IFN0YW5kYXJkLg0KPiANCj4gVGhp
cyBhZG9wdGlvbiBjYWxsIHdpbGwgZW5kIG9uIEZlYnJ1YXJ5IDE3dGgsIDIwMTYuDQo+IA0KPiBS
ZWdhcmRzLA0KPiANCj4gQm9iIEhpbmRlbiAmIE9sZSBUcsO4YW4NCg0K


From nobody Wed Feb  3 13:32:50 2016
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F1101B2D75 for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 13:32:48 -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 Mfk3EmJ_U6hu for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 13:32:47 -0800 (PST)
Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1ECF1B2D71 for <ipv6@ietf.org>; Wed,  3 Feb 2016 13:32:46 -0800 (PST)
Received: by mail-io0-x235.google.com with SMTP id d63so71468412ioj.2 for <ipv6@ietf.org>; Wed, 03 Feb 2016 13:32:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=3gnwwcGsiNvK4B6ZDGR3igKzMKkcIyVLR5Af3oXUFVI=; b=xg5KWJR6Ic2TTPXSaNo2UNUPNg8j1o5hTzIztH4Q00N5QXTnxTD7kEcSL3ETqi0GLJ d759S7R7EQ9XDEgcicrnM9x19K+BdRQKrIj2FZwkLB+mz0tpwYeOQQ76pHz1Y61ZqJ9d dz5H1A+epYddW+aTJnfKQO3pN8GthR9EZNVD8vm9pPOQsKWrU0oFhLHqWNF9KP9xXzJU zaqZSyxhHplaWd4h+yDSavI8jKONT2Ywi/tgUFgFotyqb2Q4BqyvzqkKFXt0ormkChPU GVkgx9BsQFyeqoct8wox8sHEaFnW2+WC36S1FpihxqTiJruAorFc8GFRC15uopOHly51 ZQiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=3gnwwcGsiNvK4B6ZDGR3igKzMKkcIyVLR5Af3oXUFVI=; b=EFC8EWtID9YMYO9E+RWdl9EnEX2bMx9qmnr3VstEq6TmeaGkirbx2HwBvYuHDxC2Or Ie7epFRl5rkZL3EwZ8tPfRX9ugO9dRUT8yTosppYAT4Fl28JtU2aC7oMN2LjZ9mMxnY7 +Xc0pSkqmsBwln2u9j41FCuq+wXPjy1TAKAbo0mZjNyF2iI+JHH12HYB0vCV9AcKYVC1 U0IVlR3S2gi1VtsThfVsqMWT9bsDJjCu/OxQaOb6DBAMq7uEVeTkxyecPEuFA+7Yv656 d/JTb0VA4JHqAonTyQcr3NQWw0+CfrDKOmiiL4Whsbt43Ltcv/mSi2WKcrgLrEkn6V0/ a2uQ==
X-Gm-Message-State: AG10YOTfNEZk0jXVTiCa/Iphf2k0oABvt1NGz9xukHlVPkSYLJrpn7asYqr/ccIwOL9CNw==
X-Received: by 10.107.164.15 with SMTP id n15mr5150704ioe.148.1454535166282; Wed, 03 Feb 2016 13:32:46 -0800 (PST)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id l94sm3660072iod.13.2016.02.03.13.32.45 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 03 Feb 2016 13:32:45 -0800 (PST)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_E7C8E4E1-B132-4078-8C08-7B52F5F58008"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <2134F8430051B64F815C691A62D983183395D25D@XCH-BLV-105.nw.nos.boeing.com>
Date: Wed, 3 Feb 2016 13:32:43 -0800
Message-Id: <7A64F952-7BD8-4111-B3E7-93D164DA8A20@gmail.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <2134F8430051B64F815C691A62D983183395D25D@XCH-BLV-105.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/zrQoLeVFwAJMkGWHfNWRa8LCBGk>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2016 21:32:48 -0000

--Apple-Mail=_E7C8E4E1-B132-4078-8C08-7B52F5F58008
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Fred,

> On Feb 3, 2016, at 12:54 PM, Templin, Fred L =
<Fred.L.Templin@boeing.com> wrote:
>=20
> Hi Ole,
>=20
> One question on the authorship - I can say with some certainty that =
Jack McCann
> and Jeff Mogul are no longer with Digital Equipment Corporation. Would =
they  be
> actively involved in this work if it is accepted as a working group =
item?

I have emailed Jack and he is happy keeping his Digital Equipment =
Corporation affiliation on the draft as that is where he is when he did =
the work (and not including an email address).  I am still waiting to =
hear from Jeff Mogul.

I was planning to add myself as an editor because I found out the data =
tracker get=E2=80=99s can=E2=80=99t deal with the case of not having any =
current email addresses in the draft.

Bob



>=20
> Thanks - Fred
>=20
>> -----Original Message-----
>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of =
otroan@employees.org
>> Sent: Wednesday, February 03, 2016 12:26 PM
>> To: 6man WG
>> Cc: bob.hinden@gmail.com
>> Subject: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
>>=20
>> This message starts a two week 6MAN call on adopting:
>>=20
>> Name:	draft-hinden-6man-rfc1981bis-01
>> Title:	Path MTU Discovery for IP version 6
>> Document date:	2015-12-01
>> Pages:	16
>> URL:         =
https://datatracker.ietf.org/doc/draft-hinden-6man-rfc1981bis/
>> Htmlized:  =
https://tools.ietf.org/html/draft-hinden-6man-rfc1981bis-01
>> Diff:          =
https://tools.ietf.org/rfcdiff?url2=3Ddraft-hinden-6man-rfc1981bis-01.txt
>>=20
>> as a working group item. Substantive comments and statements of =
support
>> for adopting this document should be directed to the mailing
>> list. Editorial suggestions can be sent to the authors.
>>=20
>> This document is part of the working group=E2=80=99s ongoing work on =
advancing the
>> core IPv6 standards to Internet Standard.
>>=20
>> This adoption call will end on February 17th, 2016.
>>=20
>> Regards,
>>=20
>> Bob Hinden & Ole Tr=C3=B8an
>=20


--Apple-Mail=_E7C8E4E1-B132-4078-8C08-7B52F5F58008
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJWsnH8AAoJEK7rdBF357uo5XMH/2p5guUMesTrrM5Ggm8NgZSE
hXiQ9cc8c5XL7/aXIFvgvj+/GrbK7DOuufE9pjBtz+uYRyBHDA5hnJ9yO6F5Ce8v
EMRfspux2Zx0i4dIwABpIPG69MGmIVCVF+kKAgDxISupDhzI1Nzt+16B6egGNJP0
sLRQzcAbXgdHiEozOgWdAWVPZzD0xiuD7tCHxfONkHWPPBZ0Z6NnsBZ+CTd24wTw
ys2MLmib/kFkIWuMo5Qz8KTrRaxQTAtJ3Vn+P65wU/pKfOtNy7+mdxWRUkEC1Bxk
VokG/T8fBhXdqxr1T+A4PDFYG1I1ZZ55xfSCY13RNEBYzcCtEGFZ95hzWTM05iA=
=ZNS8
-----END PGP SIGNATURE-----

--Apple-Mail=_E7C8E4E1-B132-4078-8C08-7B52F5F58008--


From nobody Wed Feb  3 14:13:14 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97F971B35B5 for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 14:13:12 -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 XmoaYLxGnWA2 for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 14:13:11 -0800 (PST)
Received: from mail-pf0-x22b.google.com (mail-pf0-x22b.google.com [IPv6:2607:f8b0:400e:c00::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B22A1B35B2 for <ipv6@ietf.org>; Wed,  3 Feb 2016 14:13:11 -0800 (PST)
Received: by mail-pf0-x22b.google.com with SMTP id 65so20779588pfd.2 for <ipv6@ietf.org>; Wed, 03 Feb 2016 14:13:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=IGnhQJA8mf2jI4zDB8QBi79hZ24RSlQ0Kt/oN3AFiUw=; b=m1aAGcYAjKqiAYLzRd4eGw48mARkBZrivax5qQGg09PAEFJwcWJRrT1iITf7cL7c9g STZix/Q/Ze33WVWTxQdBMByWNk9wTEhSdDnLnzDylCJjFLv031kHWdmwc7Y+HDMg8LIq IoGsCkdoU1zpXUctZBt/HU/cP/z0wcyTUN/9jsSwSZuwo5E8sd/HWLSxoKP87rB9vnp0 y6PQF5+xwW1/oOET3tvXVqtyCV7Yhmt7M4pDKDNyO8JDQq5L0XqqKPe+g1K0DPG88BsP tbkimDBgBBTg1PEb9JZMW/26NAPe4SlZrhDYiuqXLmm35MF7E50rIutyt73TxNIscy3h c9Cg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=IGnhQJA8mf2jI4zDB8QBi79hZ24RSlQ0Kt/oN3AFiUw=; b=YqJg01J82OET5D+AaLxpytUM17I2695ip16d0E7gkNz/UniZrouT3iiK7o305PB6hr /AF08hxKI/t3YZkfunB/7fB22I35ZWxin3d/6jrQLZ0eAW0TzUSxZJ0rhY8RF70po4Dc AZCgYlBeLoHf/kstfLekyjMOmuTdIq64MiIcysE8KFPGUkriBQJo12haJVV8nLvZlNMv x0/Rz14CY2novzIFD9tJUAlEr/o2f1P430IJQ9nugfs1Zg8J+3CDYKj63CMyD+/IQALg Oo+VVn2jlOjBsa4nsLfaYtxOGWQmAs7X1xSRgK0CnZugLx04YdN0CveNZjMDWbIXqyKA CtCg==
X-Gm-Message-State: AG10YORG6ZnkaqTxBgBiQadFgLGS1lr9m4kM0KEpaA+WtcpzvBMR3inLenbqhe3bkMY4aw==
X-Received: by 10.98.74.202 with SMTP id c71mr6119556pfj.25.1454537591013; Wed, 03 Feb 2016 14:13:11 -0800 (PST)
Received: from ?IPv6:2406:e007:65a9:1:28cc:dc4c:9703:6781? ([2406:e007:65a9:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id f27sm12145296pfj.0.2016.02.03.14.13.07 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 03 Feb 2016 14:13:09 -0800 (PST)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
To: otroan@employees.org, 6man WG <ipv6@ietf.org>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56B27B7A.7010400@gmail.com>
Date: Thu, 4 Feb 2016 11:13:14 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/KH_0SZCK7ZFvlTZP4SLhZsDJa4s>
Cc: bob.hinden@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2016 22:13:12 -0000

Yes, we should adopt this.

Regards
   Brian


From nobody Wed Feb  3 14:18:07 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D70981B35C4 for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 14:18:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 yVEb5xvJ3oIi for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 14:18:00 -0800 (PST)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) (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 304CA1B35C2 for <ipv6@ietf.org>; Wed,  3 Feb 2016 14:18:00 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u13MHvA7007637; Wed, 3 Feb 2016 16:17:57 -0600
Received: from XCH-PHX-209.sw.nos.boeing.com (xch-phx-209.sw.nos.boeing.com [130.247.25.29]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u13MHqGL007626 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 3 Feb 2016 16:17:52 -0600
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-PHX-209.sw.nos.boeing.com ([169.254.9.211]) with mapi id 14.03.0235.001; Wed, 3 Feb 2016 14:17:53 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AQHRXsEg80dfpGCQDUCIhA2edhybgJ8ay9OwgACRm4D//4SDIA==
Date: Wed, 3 Feb 2016 22:17:52 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395D40B@XCH-BLV-105.nw.nos.boeing.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <2134F8430051B64F815C691A62D983183395D25D@XCH-BLV-105.nw.nos.boeing.com> <7A64F952-7BD8-4111-B3E7-93D164DA8A20@gmail.com>
In-Reply-To: <7A64F952-7BD8-4111-B3E7-93D164DA8A20@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/b5fCSfIvr98wg1ZcKSghOKwfCTE>
Cc: IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2016 22:18:07 -0000

VGhhbmtzIEJvYiwNCg0KSGF2ZSB5b3UgZ2l2ZW4gYW55IGZ1cnRoZXIgdGhvdWdodCB0byBteSBw
cm9wb3NhbCBmcm9tIGJhY2sgaW4gRGVjZW1iZXI/DQoNCmh0dHBzOi8vbWFpbGFyY2hpdmUuaWV0
Zi5vcmcvYXJjaC9tc2cvaXB2Ni9zSDZLN0Y0Y2dhNXNYX1QzaGdvWnpkanpTU0ENCg0KVGhhbmtz
IC0gRnJlZA0KZnJlZC5sLnRlbXBsaW5AYm9laW5nLmNvbQ0KDQo+IC0tLS0tT3JpZ2luYWwgTWVz
c2FnZS0tLS0tDQo+IEZyb206IEJvYiBIaW5kZW4gW21haWx0bzpib2IuaGluZGVuQGdtYWlsLmNv
bV0NCj4gU2VudDogV2VkbmVzZGF5LCBGZWJydWFyeSAwMywgMjAxNiAxOjMzIFBNDQo+IFRvOiBU
ZW1wbGluLCBGcmVkIEwNCj4gQ2M6IEJvYiBIaW5kZW47IE9sZSBUcsO4YW47IElQdjYgTGlzdA0K
PiBTdWJqZWN0OiBSZTogNk1BTjogQWRvcHRpb24gY2FsbCBvbiBkcmFmdC1oaW5kZW4tNm1hbi1y
ZmMxOTgxYmlzLTAxDQo+IA0KPiBGcmVkLA0KPiANCj4gPiBPbiBGZWIgMywgMjAxNiwgYXQgMTI6
NTQgUE0sIFRlbXBsaW4sIEZyZWQgTCA8RnJlZC5MLlRlbXBsaW5AYm9laW5nLmNvbT4gd3JvdGU6
DQo+ID4NCj4gPiBIaSBPbGUsDQo+ID4NCj4gPiBPbmUgcXVlc3Rpb24gb24gdGhlIGF1dGhvcnNo
aXAgLSBJIGNhbiBzYXkgd2l0aCBzb21lIGNlcnRhaW50eSB0aGF0IEphY2sgTWNDYW5uDQo+ID4g
YW5kIEplZmYgTW9ndWwgYXJlIG5vIGxvbmdlciB3aXRoIERpZ2l0YWwgRXF1aXBtZW50IENvcnBv
cmF0aW9uLiBXb3VsZCB0aGV5ICBiZQ0KPiA+IGFjdGl2ZWx5IGludm9sdmVkIGluIHRoaXMgd29y
ayBpZiBpdCBpcyBhY2NlcHRlZCBhcyBhIHdvcmtpbmcgZ3JvdXAgaXRlbT8NCj4gDQo+IEkgaGF2
ZSBlbWFpbGVkIEphY2sgYW5kIGhlIGlzIGhhcHB5IGtlZXBpbmcgaGlzIERpZ2l0YWwgRXF1aXBt
ZW50IENvcnBvcmF0aW9uIGFmZmlsaWF0aW9uIG9uIHRoZSBkcmFmdCBhcyB0aGF0IGlzIHdoZXJl
IGhlIGlzIHdoZW4gaGUNCj4gZGlkIHRoZSB3b3JrIChhbmQgbm90IGluY2x1ZGluZyBhbiBlbWFp
bCBhZGRyZXNzKS4gIEkgYW0gc3RpbGwgd2FpdGluZyB0byBoZWFyIGZyb20gSmVmZiBNb2d1bC4N
Cj4gDQo+IEkgd2FzIHBsYW5uaW5nIHRvIGFkZCBteXNlbGYgYXMgYW4gZWRpdG9yIGJlY2F1c2Ug
SSBmb3VuZCBvdXQgdGhlIGRhdGEgdHJhY2tlciBnZXTigJlzIGNhbuKAmXQgZGVhbCB3aXRoIHRo
ZSBjYXNlIG9mIG5vdCBoYXZpbmcgYW55IGN1cnJlbnQNCj4gZW1haWwgYWRkcmVzc2VzIGluIHRo
ZSBkcmFmdC4NCj4gDQo+IEJvYg0KPiANCj4gDQo+IA0KPiA+DQo+ID4gVGhhbmtzIC0gRnJlZA0K
PiA+DQo+ID4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4+IEZyb206IGlwdjYgW21h
aWx0bzppcHY2LWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBvdHJvYW5AZW1wbG95ZWVz
Lm9yZw0KPiA+PiBTZW50OiBXZWRuZXNkYXksIEZlYnJ1YXJ5IDAzLCAyMDE2IDEyOjI2IFBNDQo+
ID4+IFRvOiA2bWFuIFdHDQo+ID4+IENjOiBib2IuaGluZGVuQGdtYWlsLmNvbQ0KPiA+PiBTdWJq
ZWN0OiA2TUFOOiBBZG9wdGlvbiBjYWxsIG9uIGRyYWZ0LWhpbmRlbi02bWFuLXJmYzE5ODFiaXMt
MDENCj4gPj4NCj4gPj4gVGhpcyBtZXNzYWdlIHN0YXJ0cyBhIHR3byB3ZWVrIDZNQU4gY2FsbCBv
biBhZG9wdGluZzoNCj4gPj4NCj4gPj4gTmFtZToJZHJhZnQtaGluZGVuLTZtYW4tcmZjMTk4MWJp
cy0wMQ0KPiA+PiBUaXRsZToJUGF0aCBNVFUgRGlzY292ZXJ5IGZvciBJUCB2ZXJzaW9uIDYNCj4g
Pj4gRG9jdW1lbnQgZGF0ZToJMjAxNS0xMi0wMQ0KPiA+PiBQYWdlczoJMTYNCj4gPj4gVVJMOiAg
ICAgICAgIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWhpbmRlbi02bWFu
LXJmYzE5ODFiaXMvDQo+ID4+IEh0bWxpemVkOiAgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1s
L2RyYWZ0LWhpbmRlbi02bWFuLXJmYzE5ODFiaXMtMDENCj4gPj4gRGlmZjogICAgICAgICAgaHR0
cHM6Ly90b29scy5pZXRmLm9yZy9yZmNkaWZmP3VybDI9ZHJhZnQtaGluZGVuLTZtYW4tcmZjMTk4
MWJpcy0wMS50eHQNCj4gPj4NCj4gPj4gYXMgYSB3b3JraW5nIGdyb3VwIGl0ZW0uIFN1YnN0YW50
aXZlIGNvbW1lbnRzIGFuZCBzdGF0ZW1lbnRzIG9mIHN1cHBvcnQNCj4gPj4gZm9yIGFkb3B0aW5n
IHRoaXMgZG9jdW1lbnQgc2hvdWxkIGJlIGRpcmVjdGVkIHRvIHRoZSBtYWlsaW5nDQo+ID4+IGxp
c3QuIEVkaXRvcmlhbCBzdWdnZXN0aW9ucyBjYW4gYmUgc2VudCB0byB0aGUgYXV0aG9ycy4NCj4g
Pj4NCj4gPj4gVGhpcyBkb2N1bWVudCBpcyBwYXJ0IG9mIHRoZSB3b3JraW5nIGdyb3Vw4oCZcyBv
bmdvaW5nIHdvcmsgb24gYWR2YW5jaW5nIHRoZQ0KPiA+PiBjb3JlIElQdjYgc3RhbmRhcmRzIHRv
IEludGVybmV0IFN0YW5kYXJkLg0KPiA+Pg0KPiA+PiBUaGlzIGFkb3B0aW9uIGNhbGwgd2lsbCBl
bmQgb24gRmVicnVhcnkgMTd0aCwgMjAxNi4NCj4gPj4NCj4gPj4gUmVnYXJkcywNCj4gPj4NCj4g
Pj4gQm9iIEhpbmRlbiAmIE9sZSBUcsO4YW4NCj4gPg0KDQo=


From nobody Wed Feb  3 14:20:46 2016
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 279611B2D1C for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 14:20: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 DdcXiQsDCybh for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 14:20:38 -0800 (PST)
Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AF881B35C9 for <ipv6@ietf.org>; Wed,  3 Feb 2016 14:20:09 -0800 (PST)
Received: by mail-qg0-x22b.google.com with SMTP id u30so27504759qge.1 for <ipv6@ietf.org>; Wed, 03 Feb 2016 14:20:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=mT8jQqOPGnN7lEw+IdPqQYHfUwDuLU0SdVvcq95phkQ=; b=qLRbkIstrRLhyMTv0kpodSHVdHDNZnvxfrhdQhMOmCktbj+DATCSHBcpIzm1WjdB2I pA0zoRsn8t6vcIBnOnmam9hCuquVmLbwunOgczNw7s2m3V1ycSBDjfLtMe0hu3RtvHza H+w8sHKAYK1r5pMhNZ+soqsmdD+VYOu0EfiYD8sJQx7BMP+AHU4xFfjj9uaqQDy3BakY HcGEr32WD6gu/+nBiPKLSpvJIQVxH3Zqnvz99Zpk+7a4/VlfeVmkQRKW0VaVpVK4Y9WW 2dSfNdU/nyLxKiRHe0PNSEIQUKaFrvQN+0VI68sUIywO2fpNGBH4mCOif1E1r1ML/zLb ltrA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=mT8jQqOPGnN7lEw+IdPqQYHfUwDuLU0SdVvcq95phkQ=; b=ZPlvmFHDQLFYZ4pI4FHKNlmn7A3CaL0+hvxSzJxbzhIudQiKUcLqI46TTVCHQ1S8zv EkMS6XFssfTRcUzmChQJ68zL+TP/QsXXvngSu1f8+KNIkWI+RMM7/zlPHKSGC4qhowPD YGvBvbBj66Lh2Vck4SsgkLJVBB31WI12UNYnnpPnOQiLkF+tRBbUtBwONeJ3yQnzwh+r kFd3jJApoVzSPkSReQbV3x8wIsxdxWks+Xm73nUeCvc7Xbxlsy+EDiAs+Y/E0bbBK4z9 H/unJhgZ4HgLWTJE/E9bpf+yaHzzP9FV/EIdzOyzU3D9adcLJfOwxTUedwvGhSkM0YsX k8+Q==
X-Gm-Message-State: AG10YORVydqtdUrH8/juiEode84L38Xj26BzxDfxBgi1CZYVUINYPO6QUT6PD6AuukopaA==
X-Received: by 10.140.96.84 with SMTP id j78mr935441qge.93.1454538008490; Wed, 03 Feb 2016 14:20:08 -0800 (PST)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id z82sm3450245qhd.26.2016.02.03.14.20.07 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 03 Feb 2016 14:20:07 -0800 (PST)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_27BF91B6-A7F9-4C23-BB32-5AF9573A2938"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <2134F8430051B64F815C691A62D983183395D40B@XCH-BLV-105.nw.nos.boeing.com>
Date: Wed, 3 Feb 2016 14:20:05 -0800
Message-Id: <49D29662-5F18-40F1-8413-FD7E10355DCD@gmail.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <2134F8430051B64F815C691A62D983183395D25D@XCH-BLV-105.nw.nos.boeing.com> <7A64F952-7BD8-4111-B3E7-93D164DA8A20@gmail.com> <2134F8430051B64F815C691A62D983183395D40B@XCH-BLV-105.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/9qLk2iFaUBsSnSv4YCEomxuzN28>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2016 22:20:45 -0000

--Apple-Mail=_27BF91B6-A7F9-4C23-BB32-5AF9573A2938
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Fred,

> On Feb 3, 2016, at 2:17 PM, Templin, Fred L =
<Fred.L.Templin@boeing.com> wrote:
>=20
> Thanks Bob,
>=20
> Have you given any further thought to my proposal from back in =
December?
>=20
> https://mailarchive.ietf.org/arch/msg/ipv6/sH6K7F4cga5sX_T3hgoZzdjzSSA

I am still not sure it is necessary (and prefer to keep this update very =
simple), but would like to hear more from the w.g.

Thanks,
Bob

>=20
> Thanks - Fred
> fred.l.templin@boeing.com
>=20
>> -----Original Message-----
>> From: Bob Hinden [mailto:bob.hinden@gmail.com]
>> Sent: Wednesday, February 03, 2016 1:33 PM
>> To: Templin, Fred L
>> Cc: Bob Hinden; Ole Tr=C3=B8an; IPv6 List
>> Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
>>=20
>> Fred,
>>=20
>>> On Feb 3, 2016, at 12:54 PM, Templin, Fred L =
<Fred.L.Templin@boeing.com> wrote:
>>>=20
>>> Hi Ole,
>>>=20
>>> One question on the authorship - I can say with some certainty that =
Jack McCann
>>> and Jeff Mogul are no longer with Digital Equipment Corporation. =
Would they  be
>>> actively involved in this work if it is accepted as a working group =
item?
>>=20
>> I have emailed Jack and he is happy keeping his Digital Equipment =
Corporation affiliation on the draft as that is where he is when he
>> did the work (and not including an email address).  I am still =
waiting to hear from Jeff Mogul.
>>=20
>> I was planning to add myself as an editor because I found out the =
data tracker get=E2=80=99s can=E2=80=99t deal with the case of not =
having any current
>> email addresses in the draft.
>>=20
>> Bob
>>=20
>>=20
>>=20
>>>=20
>>> Thanks - Fred
>>>=20
>>>> -----Original Message-----
>>>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of =
otroan@employees.org
>>>> Sent: Wednesday, February 03, 2016 12:26 PM
>>>> To: 6man WG
>>>> Cc: bob.hinden@gmail.com
>>>> Subject: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
>>>>=20
>>>> This message starts a two week 6MAN call on adopting:
>>>>=20
>>>> Name:	draft-hinden-6man-rfc1981bis-01
>>>> Title:	Path MTU Discovery for IP version 6
>>>> Document date:	2015-12-01
>>>> Pages:	16
>>>> URL:         =
https://datatracker.ietf.org/doc/draft-hinden-6man-rfc1981bis/
>>>> Htmlized:  =
https://tools.ietf.org/html/draft-hinden-6man-rfc1981bis-01
>>>> Diff:          =
https://tools.ietf.org/rfcdiff?url2=3Ddraft-hinden-6man-rfc1981bis-01.txt
>>>>=20
>>>> as a working group item. Substantive comments and statements of =
support
>>>> for adopting this document should be directed to the mailing
>>>> list. Editorial suggestions can be sent to the authors.
>>>>=20
>>>> This document is part of the working group=E2=80=99s ongoing work =
on advancing the
>>>> core IPv6 standards to Internet Standard.
>>>>=20
>>>> This adoption call will end on February 17th, 2016.
>>>>=20
>>>> Regards,
>>>>=20
>>>> Bob Hinden & Ole Tr=C3=B8an
>>>=20
>=20


--Apple-Mail=_27BF91B6-A7F9-4C23-BB32-5AF9573A2938
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJWsn0VAAoJEK7rdBF357uo270IAMAR7r8v4rmwYE4ePfDrIPsG
AV89TuYlKpvrcNA8MzVhQtQQhhBXAt18mGl6yzNebImY8CSxumq/SW3wWAxFxXNJ
3vPpKUwlkqyBKzCfFtceKJebeTygvLNx83680W9cJ6yDOAZZbhUZoZFoAvRpLV7X
PlDnQI5UpmDFAb95b5SVBVCffBVeMIL0kwt/eS9Ksa7PvVJUZWA2fFG+GAeS8nbY
t2Sq1FkcgsDbSpr2tEe4AxOZW4292RqvtQxzZLkteEejHrKcsHN3t9IIriJSEB4U
5l1c/COGXmOjNslwwRbCl7brhvsfvmqGQXceByympgqGXkQUEVcgf76pq2/sMuw=
=gwx7
-----END PGP SIGNATURE-----

--Apple-Mail=_27BF91B6-A7F9-4C23-BB32-5AF9573A2938--


From nobody Wed Feb  3 14:28:18 2016
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA8A81B35AD for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 14:28:15 -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 jRk7Czfiilnf for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 14:28:09 -0800 (PST)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C9951B3584 for <ipv6@ietf.org>; Wed,  3 Feb 2016 14:28:09 -0800 (PST)
Received: by mail-io0-x22c.google.com with SMTP id d63so72976074ioj.2 for <ipv6@ietf.org>; Wed, 03 Feb 2016 14:28:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:subject:date:message-id:cc:to:mime-version;  bh=o2fTyE+S5ZE0JCWS1zepdthuJ7864yODlKodj5IrJdM=; b=G4ZRPyW2lsx7S6yZW0yCeMpWgjdfhUJ+CU2NGjbRQ33p7WenuYiDXn2qZj4o26IB7G 63kaBF0JeQ4VbFg0m4hjUbYwUONy0Ds2ufCAIIxJ1P4N1RhD8LMfUsdd+sXp60pC4+HV bwlh7vumVMV8S2l1OwvptdpRVO6N435klZsdgi4pRV29sob7AbdGKEdTSVm5DCh7h/WY tn4vE92/lP+k3kVxoXjQtBMbHufrkL+oWjrTd0It/6dWxuhEgmvhdZTQl/XWBfE1LhQQ PhMT9CyYmycFn4SLGoBJRJJpkJTCkenYx+NfhdheXyxMZbF5ZzOu1wmN8WZxnmR8+rs1 OH2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:subject:date:message-id:cc:to :mime-version; bh=o2fTyE+S5ZE0JCWS1zepdthuJ7864yODlKodj5IrJdM=; b=F9tAVmH3nnOpxZ5qq6QziX+YbjYHXnC9UhUTFRreYAATOfzS6UhLtpbMh58lXeFrEc sikfWV75zik1Oq5R8AhNGO8oL2wCqkrmYSKpzRHffU93po4DZy4kWDVRCvkByrLbcLCB zs/r3jcgU8j6jtFRx+5z98dFDzYghGi1lUADD7iKlkLAKToOHyi0ZIBWBPR/T5E2LtK3 Km/gSSIhYOJfj5zMiNBhhuK4gOP9XNyl0LbUUt8H5zAsXmhTwSz9M4eyw952/N9u7IUZ P2gla6ce7c7sTBUDvOe1JuH5qpeirfVYKbYIKe/FGrhKSfOqnKMVHAanSyASvRiaUoJJ AUag==
X-Gm-Message-State: AG10YOR9uCrBIErSAXi4yjzXbNy82xj752K6DW7QZFa7RCcSIVKSEBXdvRPwbNRGyzE/rQ==
X-Received: by 10.107.38.5 with SMTP id m5mr5930759iom.15.1454538488958; Wed, 03 Feb 2016 14:28:08 -0800 (PST)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id m6sm8817328ige.3.2016.02.03.14.28.08 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 03 Feb 2016 14:28:08 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
X-Pgp-Agent: GPGMail 2.5.2
Content-Type: multipart/signed; boundary="Apple-Mail=_DAE83033-0893-4DDD-B271-3CD5283C5068"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: 6MAN WG Last Call - draft-ietf-6man-multi-homed-host-03.txt
Date: Wed, 3 Feb 2016 14:28:07 -0800
Message-Id: <2052A806-4D40-4A17-9892-90E39B67C65C@gmail.com>
To: IPv6 List <ipv6@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/yI96U3W4PwixNwP3j8O3T1jdkb8>
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2016 22:28:16 -0000

--Apple-Mail=_DAE83033-0893-4DDD-B271-3CD5283C5068
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

This message starts a two week 6MAN Working Group Last Call on =
advancing:

       Title           : Routing packets from hosts in a multi-prefix =
network
       Authors         : Fred Baker
                         Brian Carpenter
       Filename        : draft-ietf-6man-multi-homed-host-03.txt
       Pages           : 13
       Date            : 2015-12-16

   https://tools.ietf.org/html/draft-ietf-6man-multi-homed-host-03

as a Proposed Standard.  Substantive comments and statements of support =
for publishing this document should be directed to the mailing list.  =
Editorial suggestions can be sent to the authors.  This last call will =
end on 17 February 2016.

Best regards,
Ole & Bob



--Apple-Mail=_DAE83033-0893-4DDD-B271-3CD5283C5068
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJWsn73AAoJEK7rdBF357uoYD8H/3tbQW4CTVxQGy2MJ8t1MXdg
/hxlJm0u2TAFt9fjooeYm0talx4mHxdNCen8UYAEcIkNmfAUra+VlgvHv/v4vK+e
ZmpeYIg3G6JVHdqVUN6DB6wWCFMakyaaTl4z2+p0AH35MchTlxbkcA1V6zQq2nMB
yQyPKT8bUKIUluB999SVd1liv4VG29fZ8DTE/3KMlkkyMRKltyJ/lYUmH9KJNoxb
IH8oKjidTy3pM7S2uMA7Idjp2dDKqPgzcGmo97p7p9J0Z+Xq4eQy+LrxWXzSGrpD
+4AMY+4Ds7sKtWS828R6KSKLd/KEjsX348QpYB8ztacI+K3B7JTcIVJMZXcS72g=
=HfAU
-----END PGP SIGNATURE-----

--Apple-Mail=_DAE83033-0893-4DDD-B271-3CD5283C5068--


From nobody Wed Feb  3 14:46:39 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E053C1B3611 for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 14:46:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 e4pcD1tGen12 for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 14:46:35 -0800 (PST)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) (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 995341B3610 for <ipv6@ietf.org>; Wed,  3 Feb 2016 14:46:35 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u13Mkfnb026297; Wed, 3 Feb 2016 14:46:42 -0800
Received: from XCH-BLV-508.nw.nos.boeing.com (xch-blv-508.nw.nos.boeing.com [130.247.25.198]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u13MkTpY025714 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 3 Feb 2016 14:46:29 -0800
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-BLV-508.nw.nos.boeing.com ([169.254.8.155]) with mapi id 14.03.0235.001; Wed, 3 Feb 2016 14:46:21 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AQHRXsEg80dfpGCQDUCIhA2edhybgJ8ay9OwgACRm4D//4SDIIAAiLmA//+AbiA=
Date: Wed, 3 Feb 2016 22:46:21 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395D48A@XCH-BLV-105.nw.nos.boeing.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <2134F8430051B64F815C691A62D983183395D25D@XCH-BLV-105.nw.nos.boeing.com> <7A64F952-7BD8-4111-B3E7-93D164DA8A20@gmail.com> <2134F8430051B64F815C691A62D983183395D40B@XCH-BLV-105.nw.nos.boeing.com> <49D29662-5F18-40F1-8413-FD7E10355DCD@gmail.com>
In-Reply-To: <49D29662-5F18-40F1-8413-FD7E10355DCD@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/9a2TstswOirm0ezmN_jDdxd35aM>
Cc: IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2016 22:46:38 -0000

SGkgQm9iLA0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IEJvYiBIaW5k
ZW4gW21haWx0bzpib2IuaGluZGVuQGdtYWlsLmNvbV0NCj4gU2VudDogV2VkbmVzZGF5LCBGZWJy
dWFyeSAwMywgMjAxNiAyOjIwIFBNDQo+IFRvOiBUZW1wbGluLCBGcmVkIEwNCj4gQ2M6IEJvYiBI
aW5kZW47IE9sZSBUcsO4YW47IElQdjYgTGlzdA0KPiBTdWJqZWN0OiBSZTogNk1BTjogQWRvcHRp
b24gY2FsbCBvbiBkcmFmdC1oaW5kZW4tNm1hbi1yZmMxOTgxYmlzLTAxDQo+IA0KPiBGcmVkLA0K
PiANCj4gPiBPbiBGZWIgMywgMjAxNiwgYXQgMjoxNyBQTSwgVGVtcGxpbiwgRnJlZCBMIDxGcmVk
LkwuVGVtcGxpbkBib2VpbmcuY29tPiB3cm90ZToNCj4gPg0KPiA+IFRoYW5rcyBCb2IsDQo+ID4N
Cj4gPiBIYXZlIHlvdSBnaXZlbiBhbnkgZnVydGhlciB0aG91Z2h0IHRvIG15IHByb3Bvc2FsIGZy
b20gYmFjayBpbiBEZWNlbWJlcj8NCj4gPg0KPiA+IGh0dHBzOi8vbWFpbGFyY2hpdmUuaWV0Zi5v
cmcvYXJjaC9tc2cvaXB2Ni9zSDZLN0Y0Y2dhNXNYX1QzaGdvWnpkanpTU0ENCj4gDQo+IEkgYW0g
c3RpbGwgbm90IHN1cmUgaXQgaXMgbmVjZXNzYXJ5IChhbmQgcHJlZmVyIHRvIGtlZXAgdGhpcyB1
cGRhdGUgdmVyeSBzaW1wbGUpLCBidXQgd291bGQgbGlrZSB0byBoZWFyIG1vcmUgZnJvbSB0aGUg
dy5nLg0KDQpZZXMsIEkgYWdyZWUgdGhhdCB3ZSBzaG91bGQgaGVhciBmcm9tIHRoZSB3b3JraW5n
IGdyb3VwLiBJIHdvdWxkIGxpa2UgdG8NCm5vdGUgaG93ZXZlciB0aGF0IHRoZSBQTVRVRCBpc3N1
ZSBoYXMgYmVlbiB1bmRlciBpbnZlc3RpZ2F0aW9uIGZvcg0KZGVjYWRlcyBhbmQgSU1ITyB3ZSBu
b3cgaGF2ZSBhbiBvcHBvcnR1bml0eSB0byBwdXQgaXQgdG8gcmVzdCBpbiBqdXN0DQp0d28gc2Vu
dGVuY2VzIGFkZGVkIHRvIHRoaXMgZG9jdW1lbnQuIFNvLCBJIHRoaW5rIGl0IHdvdWxkIGJlIHdv
cnRoIGl0Lg0KDQpUaGFua3MgLSBGcmVkDQpmcmVkLmwudGVtcGxpbkBiZW9pbmcuY29tDQoNCj4g
VGhhbmtzLA0KPiBCb2INCj4gDQo+ID4NCj4gPiBUaGFua3MgLSBGcmVkDQo+ID4gZnJlZC5sLnRl
bXBsaW5AYm9laW5nLmNvbQ0KPiA+DQo+ID4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+
ID4+IEZyb206IEJvYiBIaW5kZW4gW21haWx0bzpib2IuaGluZGVuQGdtYWlsLmNvbV0NCj4gPj4g
U2VudDogV2VkbmVzZGF5LCBGZWJydWFyeSAwMywgMjAxNiAxOjMzIFBNDQo+ID4+IFRvOiBUZW1w
bGluLCBGcmVkIEwNCj4gPj4gQ2M6IEJvYiBIaW5kZW47IE9sZSBUcsO4YW47IElQdjYgTGlzdA0K
PiA+PiBTdWJqZWN0OiBSZTogNk1BTjogQWRvcHRpb24gY2FsbCBvbiBkcmFmdC1oaW5kZW4tNm1h
bi1yZmMxOTgxYmlzLTAxDQo+ID4+DQo+ID4+IEZyZWQsDQo+ID4+DQo+ID4+PiBPbiBGZWIgMywg
MjAxNiwgYXQgMTI6NTQgUE0sIFRlbXBsaW4sIEZyZWQgTCA8RnJlZC5MLlRlbXBsaW5AYm9laW5n
LmNvbT4gd3JvdGU6DQo+ID4+Pg0KPiA+Pj4gSGkgT2xlLA0KPiA+Pj4NCj4gPj4+IE9uZSBxdWVz
dGlvbiBvbiB0aGUgYXV0aG9yc2hpcCAtIEkgY2FuIHNheSB3aXRoIHNvbWUgY2VydGFpbnR5IHRo
YXQgSmFjayBNY0Nhbm4NCj4gPj4+IGFuZCBKZWZmIE1vZ3VsIGFyZSBubyBsb25nZXIgd2l0aCBE
aWdpdGFsIEVxdWlwbWVudCBDb3Jwb3JhdGlvbi4gV291bGQgdGhleSAgYmUNCj4gPj4+IGFjdGl2
ZWx5IGludm9sdmVkIGluIHRoaXMgd29yayBpZiBpdCBpcyBhY2NlcHRlZCBhcyBhIHdvcmtpbmcg
Z3JvdXAgaXRlbT8NCj4gPj4NCj4gPj4gSSBoYXZlIGVtYWlsZWQgSmFjayBhbmQgaGUgaXMgaGFw
cHkga2VlcGluZyBoaXMgRGlnaXRhbCBFcXVpcG1lbnQgQ29ycG9yYXRpb24gYWZmaWxpYXRpb24g
b24gdGhlIGRyYWZ0IGFzIHRoYXQgaXMgd2hlcmUgaGUgaXMgd2hlbiBoZQ0KPiA+PiBkaWQgdGhl
IHdvcmsgKGFuZCBub3QgaW5jbHVkaW5nIGFuIGVtYWlsIGFkZHJlc3MpLiAgSSBhbSBzdGlsbCB3
YWl0aW5nIHRvIGhlYXIgZnJvbSBKZWZmIE1vZ3VsLg0KPiA+Pg0KPiA+PiBJIHdhcyBwbGFubmlu
ZyB0byBhZGQgbXlzZWxmIGFzIGFuIGVkaXRvciBiZWNhdXNlIEkgZm91bmQgb3V0IHRoZSBkYXRh
IHRyYWNrZXIgZ2V04oCZcyBjYW7igJl0IGRlYWwgd2l0aCB0aGUgY2FzZSBvZiBub3QgaGF2aW5n
IGFueQ0KPiBjdXJyZW50DQo+ID4+IGVtYWlsIGFkZHJlc3NlcyBpbiB0aGUgZHJhZnQuDQo+ID4+
DQo+ID4+IEJvYg0KPiA+Pg0KPiA+Pg0KPiA+Pg0KPiA+Pj4NCj4gPj4+IFRoYW5rcyAtIEZyZWQN
Cj4gPj4+DQo+ID4+Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPj4+PiBGcm9tOiBp
cHY2IFttYWlsdG86aXB2Ni1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2Ygb3Ryb2FuQGVt
cGxveWVlcy5vcmcNCj4gPj4+PiBTZW50OiBXZWRuZXNkYXksIEZlYnJ1YXJ5IDAzLCAyMDE2IDEy
OjI2IFBNDQo+ID4+Pj4gVG86IDZtYW4gV0cNCj4gPj4+PiBDYzogYm9iLmhpbmRlbkBnbWFpbC5j
b20NCj4gPj4+PiBTdWJqZWN0OiA2TUFOOiBBZG9wdGlvbiBjYWxsIG9uIGRyYWZ0LWhpbmRlbi02
bWFuLXJmYzE5ODFiaXMtMDENCj4gPj4+Pg0KPiA+Pj4+IFRoaXMgbWVzc2FnZSBzdGFydHMgYSB0
d28gd2VlayA2TUFOIGNhbGwgb24gYWRvcHRpbmc6DQo+ID4+Pj4NCj4gPj4+PiBOYW1lOglkcmFm
dC1oaW5kZW4tNm1hbi1yZmMxOTgxYmlzLTAxDQo+ID4+Pj4gVGl0bGU6CVBhdGggTVRVIERpc2Nv
dmVyeSBmb3IgSVAgdmVyc2lvbiA2DQo+ID4+Pj4gRG9jdW1lbnQgZGF0ZToJMjAxNS0xMi0wMQ0K
PiA+Pj4+IFBhZ2VzOgkxNg0KPiA+Pj4+IFVSTDogICAgICAgICBodHRwczovL2RhdGF0cmFja2Vy
LmlldGYub3JnL2RvYy9kcmFmdC1oaW5kZW4tNm1hbi1yZmMxOTgxYmlzLw0KPiA+Pj4+IEh0bWxp
emVkOiAgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWhpbmRlbi02bWFuLXJmYzE5
ODFiaXMtMDENCj4gPj4+PiBEaWZmOiAgICAgICAgICBodHRwczovL3Rvb2xzLmlldGYub3JnL3Jm
Y2RpZmY/dXJsMj1kcmFmdC1oaW5kZW4tNm1hbi1yZmMxOTgxYmlzLTAxLnR4dA0KPiA+Pj4+DQo+
ID4+Pj4gYXMgYSB3b3JraW5nIGdyb3VwIGl0ZW0uIFN1YnN0YW50aXZlIGNvbW1lbnRzIGFuZCBz
dGF0ZW1lbnRzIG9mIHN1cHBvcnQNCj4gPj4+PiBmb3IgYWRvcHRpbmcgdGhpcyBkb2N1bWVudCBz
aG91bGQgYmUgZGlyZWN0ZWQgdG8gdGhlIG1haWxpbmcNCj4gPj4+PiBsaXN0LiBFZGl0b3JpYWwg
c3VnZ2VzdGlvbnMgY2FuIGJlIHNlbnQgdG8gdGhlIGF1dGhvcnMuDQo+ID4+Pj4NCj4gPj4+PiBU
aGlzIGRvY3VtZW50IGlzIHBhcnQgb2YgdGhlIHdvcmtpbmcgZ3JvdXDigJlzIG9uZ29pbmcgd29y
ayBvbiBhZHZhbmNpbmcgdGhlDQo+ID4+Pj4gY29yZSBJUHY2IHN0YW5kYXJkcyB0byBJbnRlcm5l
dCBTdGFuZGFyZC4NCj4gPj4+Pg0KPiA+Pj4+IFRoaXMgYWRvcHRpb24gY2FsbCB3aWxsIGVuZCBv
biBGZWJydWFyeSAxN3RoLCAyMDE2Lg0KPiA+Pj4+DQo+ID4+Pj4gUmVnYXJkcywNCj4gPj4+Pg0K
PiA+Pj4+IEJvYiBIaW5kZW4gJiBPbGUgVHLDuGFuDQo+ID4+Pg0KPiA+DQoNCg==


From nobody Wed Feb  3 15:06:57 2016
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DBCA1B3637 for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 15:06:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.502
X-Spam-Level: 
X-Spam-Status: No, score=-114.502 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fQGzln6htYqp for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 15:06:54 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A9E81B3636 for <ipv6@ietf.org>; Wed,  3 Feb 2016 15:06:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3651; q=dns/txt; s=iport; t=1454540814; x=1455750414; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=eHEOiltloeLEXa0JvsjdypmlTBr9OgmjdeA2tuKEicc=; b=BmCY7vFSO51rK5oaR1dSxgbBMHDf7WbBycMk2WK2r7n8P5qaklfWrB8r r0UQhOFQkIY1hpFrnndwECuUXk0VAErhr3U850yByKNlHfL9oPghOOYeG g60E7O0kigUBVcXILMUjatZen6Bzhf+tssz8ap2jEzd74fd50nHyXbl/j s=;
X-Files: signature.asc : 833
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0C7AgDWh7JW/5tdJa1egzqBPwaIVbEaD?= =?us-ascii?q?oFmhg0CgUE4FAEBAQEBAQGBCoRBAQEBAwEjVgULAgEIGCoCAiERJQIEDgUOh3g?= =?us-ascii?q?DCgixZIpEDYQ/AQEBAQEBAQEBAQEBAQEBAQEBAQEBDQiHfwiCQoI3gVWDJiuBD?= =?us-ascii?q?wWWcQGCe4FjhnuBc4Fbh2iFLoVwgQ+HQAEeAUODZGqIMj18AQEB?=
X-IronPort-AV: E=Sophos;i="5.22,392,1449532800";  d="asc'?scan'208";a="67750183"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Feb 2016 23:06:41 +0000
Received: from XCH-RCD-014.cisco.com (xch-rcd-014.cisco.com [173.37.102.24]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id u13N6fOt016367 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 3 Feb 2016 23:06:41 GMT
Received: from xch-rcd-013.cisco.com (173.37.102.23) by XCH-RCD-014.cisco.com (173.37.102.24) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 3 Feb 2016 17:06:41 -0600
Received: from xch-rcd-013.cisco.com ([173.37.102.23]) by XCH-RCD-013.cisco.com ([173.37.102.23]) with mapi id 15.00.1104.009; Wed, 3 Feb 2016 17:06:41 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: 6MAN WG Last Call - draft-ietf-6man-multi-homed-host-03.txt
Thread-Topic: 6MAN WG Last Call - draft-ietf-6man-multi-homed-host-03.txt
Thread-Index: AQHRXtMz+oGF3eRmbkuVf5Gu7fEtVp8bVgKA
Date: Wed, 3 Feb 2016 23:06:40 +0000
Message-ID: <42523014-C715-428A-9549-B16FA3AC470B@cisco.com>
References: <2052A806-4D40-4A17-9892-90E39B67C65C@gmail.com> <CA38FB16-7B79-4708-9EB1-3D761C5871E2@gmail.com>
In-Reply-To: <CA38FB16-7B79-4708-9EB1-3D761C5871E2@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3112)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.248.216]
Content-Type: multipart/signed; boundary="Apple-Mail=_0E337A64-7B6E-40AB-B61E-F04D4BC1C46E"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/SH1-dzSt7TUDFxUKhots5FDICzU>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Feb 2016 23:06:56 -0000

--Apple-Mail=_0E337A64-7B6E-40AB-B61E-F04D4BC1C46E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Feb 3, 2016, at 2:35 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
>=20
> Brian, Fred,
>=20
> I started the w.g. last call.  I read the draft again, looks fine =
overall.  I think it would helpful if it was clearer as to what the =
update is for RFC4861.  Having done some updates a few times recently, =
it better to be very clear what the change is.
>=20
> I like the =E2=80=9CBob=E2=80=9D and =E2=80=9CAlice=E2=80=9D host =
names.  Maybe it should be =E2=80=9COle=E2=80=9D and =E2=80=9CBob=E2=80=9D=
 :-)

The text in question is, at least,

   Note that, apart from ensuring that a message with a given source
   address is given to a first-hop router that appears to know about the
   prefix in question, this specification is consistent with [RFC4861].
   Nevertheless, implementers of Sections 5.2, 6.2.3, 6.3.4 and 8 of RFC
   4861 will need to extend their implementations accordingly.  This
   specification is fully consistent with [RFC6724] and implementers
   will need to add support for its Rule 5.5.  Hosts that do not support
   these features may fail to communicate in the presence of filters as
   described above.

Section 5.2 basically says that on-link prefixes should result in local =
traffic ("the next hop address is the destination address") and off-link =
prefixes operate as described in 6.3.6. Based on that, I think this =
draft is primarily proposing an inserted step in 6.3.6:

0) IF the source address is a member of a prefix being advertised to the =
host in an RA, the set of routers being considered as possible next hops =
is limited to the set of routers advertising the prefix, as opposed to =
"all neighboring routers".

(which there may be a better way of wording)

Regarding 6.2.3 and 6.2.4, I need to defer to my co-author; I'm not sure =
what he had in mind. It may have to do with the RIO/PIO/DIO =
considerations in the draft.

In Section 8, there is a limitation on the set of routers a router might =
redirect to: it MUST be among the set of routers advertising the =
indicated prefix in its RA, or the redirecting router must in some other =
way know that it has the information necessary for SADR routing.

If putting words directly into draft-ietf-6man-multi-homed-host would =
help you with a 4861bis, we can do that.


--Apple-Mail=_0E337A64-7B6E-40AB-B61E-F04D4BC1C46E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIVAwUBVrKIAEayAOS/EQ8MAQJhERAAqR3m6c9l7MabbiTbBkrEzpGDscxXWbq6
FJflnt09qp3lsvFVo7yVOQ7/NcTnrss+JbvMbLs/HhHfUfO5ZrZzKSlzf3eumzHR
x2aKk/hHqqIvaX8FmrZMqNI2+4CYpSHDdPRnh3N5PbBC+wUDf4B3YnDnzOwUIE7V
FnEvhiCU4HZy5/wlp894dGgX1AM/N+/F6MusAEBM7Th1ahf/f57dn6SI6DmsOOkj
NIDpotRI+X89eo2+ZZdnLmBWuok2oXgUwLQ70F0xSh9azFbi0TrZbQlZZ+ysjDba
lalJ87n+Y1wKTL0cl9KrjsWrA70r05H2o6VhVzITTFxe+R8ztB2MvhpMCK26m06O
bvnHtDUaiVbPcdpP8vW+SgIdc2gA+5bfQWekNcng1lW5Dx0V3LIDu+y1gTCGTeRe
r7gsQ5toasNmwZ8hSE8P6sV4zZ3jZLeazNMSZ/wkHY8Jul2oXcot4cQIsr5u/UGa
u+OrOCGHXkn9cfdCp8uy2ODIuqqMMUU+saZx3FEAyr7a/WeIWLsjX3FadoXd+eHa
icBkIyi8Lw1+0BW2J6CgNFdek11Vx7viYvTNEcN/QasJjiZgO7bm/UfeBQ8Gov0V
1hlXlg3lPkIX2UroUsGY0+XLWaX2FuSxio7v1Sl+0yd+Dljps67Cm2VwVYiRasHQ
aN2NhIc8DK4=
=kuSU
-----END PGP SIGNATURE-----

--Apple-Mail=_0E337A64-7B6E-40AB-B61E-F04D4BC1C46E--


From nobody Wed Feb  3 16:24:21 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F34A51B3763 for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 16:24:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kHB5Seiw3q2L for <ipv6@ietfa.amsl.com>; Wed,  3 Feb 2016 16:24:18 -0800 (PST)
Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 308AD1B3762 for <ipv6@ietf.org>; Wed,  3 Feb 2016 16:24:18 -0800 (PST)
Received: by mail-pf0-x229.google.com with SMTP id 65so23869070pfd.2 for <ipv6@ietf.org>; Wed, 03 Feb 2016 16:24:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=Ao5DI49+eRvGK0LWFTPQhYn5hvW0Rtt/mtpdgZo7XQE=; b=oHiU068zbtR2Euo90mAnS3ASqgl+ow8UfCnFX9nkjpwmi3dJwn8h1821t4oOzcVOzV VgTEkkAec3tBAiw7EmzzNjigiBQi7cFcsN80XC3bI3KQkpyr9+7vGt76i2Vo1jWaL20n yhocKmpvw8GqOxlTEn9S4WCxjdd0IuAFffAW7ZVmeNzW3oaaNenhIUMBxiMllrjS9lQh 6MLUnVd9d9hrWGVIzlkLR4b+QeuNwvo00S1j4buG2idaRSvVb6JDhNZQXiqfarCebMAs 7Ie1rAs37ouC8+HzJb8RGk4e1D2PU3FFSg7xqWcGnB0izWdFQd3Tj5zTMwGOjHxNjsMJ tV7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=Ao5DI49+eRvGK0LWFTPQhYn5hvW0Rtt/mtpdgZo7XQE=; b=U91QYNKRgL6CiyHKcSsJKkl77MWjpLe3UhKCVjYtu8soNCLTTLXHSB2Js6zNUtVTLV 2xkO+2Pc6RK6EnQq17L6qmfS6EblWitO6/sVGsCax/54EOhEooH8Q8RbbUBkMb3Cf1o3 UwZO5wfItUxr8t0xW5QrT4Wg6CkA1xaBGq3pPY+KBPOS+g7UAOs0ttptIPGp3ZB1IFNo 4nfcUfBWXHLkroxqOrhYKn0MnmZROS9DcfPV6hYONQR6DXMY7TdBDY2eR5V5meYiCQJN 4wMSp7GXZEHSccY+BUPwO/ALcERqYG7xTOq4e/8gDYLDATbqh5iihhAkzB6iNjAgtTY7 r8zA==
X-Gm-Message-State: AG10YOStvKmZS3SshyuoAZ5JMciAp7GPoObPOhHs7RpubGUR9V3D9QPbuW1nx0/PjriEuA==
X-Received: by 10.66.140.44 with SMTP id rd12mr6752888pab.86.1454545457736; Wed, 03 Feb 2016 16:24:17 -0800 (PST)
Received: from ?IPv6:2406:e007:65a9:1:28cc:dc4c:9703:6781? ([2406:e007:65a9:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id c13sm12460017pat.8.2016.02.03.16.24.13 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 03 Feb 2016 16:24:15 -0800 (PST)
Subject: Re: 6MAN WG Last Call - draft-ietf-6man-multi-homed-host-03.txt
To: "Fred Baker (fred)" <fred@cisco.com>, Bob Hinden <bob.hinden@gmail.com>
References: <2052A806-4D40-4A17-9892-90E39B67C65C@gmail.com> <CA38FB16-7B79-4708-9EB1-3D761C5871E2@gmail.com> <42523014-C715-428A-9549-B16FA3AC470B@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56B29A32.50002@gmail.com>
Date: Thu, 4 Feb 2016 13:24:18 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <42523014-C715-428A-9549-B16FA3AC470B@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Ar2-pAyohd9_460p-CtmRpJy1DA>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 00:24:20 -0000

On 04/02/2016 12:06, Fred Baker (fred) wrote:
>=20
>> On Feb 3, 2016, at 2:35 PM, Bob Hinden <bob.hinden@gmail.com> wrote:
>>
>> Brian, Fred,
>>
>> I started the w.g. last call.  I read the draft again, looks fine over=
all.  I think it would helpful if it was clearer as to what the update is=
 for RFC4861.  Having done some updates a few times recently, it better t=
o be very clear what the change is.
>>
>> I like the =E2=80=9CBob=E2=80=9D and =E2=80=9CAlice=E2=80=9D host name=
s.  Maybe it should be =E2=80=9COle=E2=80=9D and =E2=80=9CBob=E2=80=9D :-=
)
>=20
> The text in question is, at least,
>=20
>    Note that, apart from ensuring that a message with a given source
>    address is given to a first-hop router that appears to know about th=
e
>    prefix in question, this specification is consistent with [RFC4861].=

>    Nevertheless, implementers of Sections 5.2, 6.2.3, 6.3.4 and 8 of RF=
C
>    4861 will need to extend their implementations accordingly.  This
>    specification is fully consistent with [RFC6724] and implementers
>    will need to add support for its Rule 5.5.  Hosts that do not suppor=
t
>    these features may fail to communicate in the presence of filters as=

>    described above.
>=20
> Section 5.2 basically says that on-link prefixes should result in local=
 traffic ("the next hop address is the destination address") and off-link=
 prefixes operate as described in 6.3.6. Based on that, I think this draf=
t is primarily proposing an inserted step in 6.3.6:
>=20
> 0) IF the source address is a member of a prefix being advertised to th=
e host in an RA, the set of routers being considered as possible next hop=
s is limited to the set of routers advertising the prefix, as opposed to =
"all neighboring routers".

Yes, that seems right.

>=20
> (which there may be a better way of wording)
>=20
> Regarding 6.2.3 and 6.2.4, I need to defer to my co-author; I'm not sur=
e what he had in mind. It may have to do with the RIO/PIO/DIO considerati=
ons in the draft.

The point is that solicited and unsolicited RAs should be sent and handle=
d
even if both L and A are zero. I think it was Jinmei who pointed out that=

some devices would not do this without a code update. That's the last par=
agraph
on https://tools.ietf.org/html/draft-ietf-6man-multi-homed-host-03#page-6=


Do we need to add more?

    Brian

>=20
> In Section 8, there is a limitation on the set of routers a router migh=
t redirect to: it MUST be among the set of routers advertising the indica=
ted prefix in its RA, or the redirecting router must in some other way kn=
ow that it has the information necessary for SADR routing.
>=20
> If putting words directly into draft-ietf-6man-multi-homed-host would h=
elp you with a 4861bis, we can do that.
>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20


From nobody Thu Feb  4 03:34:46 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6E9D1ACF17 for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 03:34:44 -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] 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 TnyLYW-39xcy for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 03:34:43 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A03681ACF57 for <ipv6@ietf.org>; Thu,  4 Feb 2016 03:34:43 -0800 (PST)
Received: from [192.168.2.101] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id F2DCA206ABF; Thu,  4 Feb 2016 12:34:34 +0100 (CET)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
To: otroan@employees.org, 6man WG <ipv6@ietf.org>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <56B336CC.6090608@si6networks.com>
Date: Thu, 4 Feb 2016 08:32:28 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ebqVJOXldEdoxWoL37_EJho-lFQ>
Cc: bob.hinden@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 11:34:45 -0000

On 02/03/2016 05:25 PM, otroan@employees.org wrote:
> This message starts a two week 6MAN call on adopting:
> 
> Name:	draft-hinden-6man-rfc1981bis-01
> Title:	Path MTU Discovery for IP version 6
> Document date:	2015-12-01
> Pages:	16
> URL:         https://datatracker.ietf.org/doc/draft-hinden-6man-rfc1981bis/
> Htmlized:  https://tools.ietf.org/html/draft-hinden-6man-rfc1981bis-01
> Diff:          https://tools.ietf.org/rfcdiff?url2=draft-hinden-6man-rfc1981bis-01.txt
> 
> as a working group item. Substantive comments and statements of support
> for adopting this document should be directed to the mailing
> list. Editorial suggestions can be sent to the authors.
> 
> This document is part of the working group’s ongoing work on advancing the
>  core IPv6 standards to Internet Standard.
> 
> This adoption call will end on February 17th, 2016.

I support adoption of this document as a wg item.

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





From nobody Thu Feb  4 04:42:13 2016
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 982591B2E42 for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 04:42:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.222
X-Spam-Level: 
X-Spam-Status: No, score=-1.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, 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 QjnS5Fbg6JYO for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 04:42:11 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 572E01B2E3C for <ipv6@ietf.org>; Thu,  4 Feb 2016 04:42:11 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u14Cg3pW002926; Thu, 4 Feb 2016 12:42:03 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u14Cg3pW002926
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1454589724; bh=2sszQHGlleWP5VHNnIMjPlvUC6U=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=BL38eqoyHamK+wIXRWH+zPEgHlTttSsiRUaqJIvlxbnIv34cK3O9Z7HGGNkRmz2Hu I22i6WAC6P4/tHUzGEPa/HwRmgghuoxp9YSXQbd6U4JH86GBr/wdl9yDDjTDI0E4Fo r09sRaEWWDWmuvaVYW6o5mWD1kpQ3Pwj0D9++jfM=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s13Cg31791807541PD ret-id none; Thu, 04 Feb 2016 12:42:03 +0000
Received: from [192.168.0.10] (tchowndsl.claranet.co.uk [212.188.254.49]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u14Cejah032130 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Feb 2016 12:40:45 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org>
Date: Thu, 4 Feb 2016 12:40:44 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|b1c34681698e78c2c2059a787bb4d28es13Cg303tjc|ecs.soton.ac.uk|9D2E6F68-2FFA-42A3-B122-65C1D5757657@ecs.soton.ac.uk>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <9D2E6F68-2FFA-42A3-B122-65C1D5757657@ecs.soton.ac.uk>
To: otroan@employees.org
X-Mailer: Apple Mail (2.3112)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s13Cg3179180754100; tid=s13Cg31791807541PD; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u14Cg3pW002926
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/XT-wL3vjL2pCig1u1g16_zY3yIs>
Cc: bob.hinden@gmail.com, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 12:42:12 -0000

> On 3 Feb 2016, at 20:25, otroan@employees.org wrote:
>=20
> This message starts a two week 6MAN call on adopting:
>=20
> Name:	draft-hinden-6man-rfc1981bis-01
> Title:	Path MTU Discovery for IP version 6
> Document date:	2015-12-01
> Pages:	16
> URL:         =
https://datatracker.ietf.org/doc/draft-hinden-6man-rfc1981bis/
> Htmlized:  https://tools.ietf.org/html/draft-hinden-6man-rfc1981bis-01
> Diff:          =
https://tools.ietf.org/rfcdiff?url2=3Ddraft-hinden-6man-rfc1981bis-01.txt
>=20
> as a working group item. Substantive comments and statements of =
support
> for adopting this document should be directed to the mailing
> list. Editorial suggestions can be sent to the authors.
>=20
> This document is part of the working group=E2=80=99s ongoing work on =
advancing the
> core IPv6 standards to Internet Standard.
>=20
> This adoption call will end on February 17th, 2016.

I support adoption.

Tim=


From nobody Thu Feb  4 05:16:20 2016
Return-Path: <twinters@iol.unh.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B40FA1B2ECD for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 05:16:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 526HV66AnrJe for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 05:16:17 -0800 (PST)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E02D61B2E84 for <ipv6@ietf.org>; Thu,  4 Feb 2016 05:16:16 -0800 (PST)
Received: by mail-io0-x234.google.com with SMTP id g73so92069104ioe.3 for <ipv6@ietf.org>; Thu, 04 Feb 2016 05:16:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=DsHfpSnGcdN0J5h9cj/nICw5y3c0ceSitB/SXaEBJfQ=; b=ZYLGkzwCpYfa+hjeG7DW75sfcK0tM6DCy+u8N1iipeZ0T5JTuWOW+bPJq0kQuYivcC TVjPC60wH5YyDbeB/MAsf77mkZUdoNDzAdg0q4eNv7l+39m5lrl+v34u27is6P8kJZYv 9PEnBq6u+G2qZZ8tmrclTAGDYylzfc7cfG7pg=
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=DsHfpSnGcdN0J5h9cj/nICw5y3c0ceSitB/SXaEBJfQ=; b=fOEcSy3g1V6H868fR9h+AtlAu4VtTGFZrJc++cfsqbdGRFe+KhH0wO8qbn2KsOro8f X+vsEVuWB8InhPZMpAZDYS6kxPb6tpccUcYzLpGIPFj3ph59xSGBtsvyXushve90RDg+ oD7r3wwc0pGZEHjWM1HL9OTLXX2gr2I9Xg+tAToKlh6q3hLKElYVHArN7iQJUe1PvFDo r4GMHNfXkUkD0QM+cBcvNw3XbXSHWPJr83LhdZo3Ajj9bMncnqyTt9RBXI6mSC0whpwA sQoFmfvjha2Lz6TPFSGyI5um+QbETum1Atgg4bo3FsluMgxI3AgY01XMbKbQDX/JZt9h yVMg==
X-Gm-Message-State: AG10YOQNl1Uy8415ujAuTZH9B7ob05M2Tiz5a/dkkXdZBOGRrrQZc5g+mq3r8TpEUi9NvcrckX6lUQXX2GECyrY/
MIME-Version: 1.0
X-Received: by 10.107.7.37 with SMTP id 37mr9262208ioh.17.1454591776188; Thu, 04 Feb 2016 05:16:16 -0800 (PST)
Received: by 10.64.146.103 with HTTP; Thu, 4 Feb 2016 05:16:16 -0800 (PST)
In-Reply-To: <EMEW3|b1c34681698e78c2c2059a787bb4d28es13Cg303tjc|ecs.soton.ac.uk|9D2E6F68-2FFA-42A3-B122-65C1D5757657@ecs.soton.ac.uk>
References: <9D2E6F68-2FFA-42A3-B122-65C1D5757657@ecs.soton.ac.uk> <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <EMEW3|b1c34681698e78c2c2059a787bb4d28es13Cg303tjc|ecs.soton.ac.uk|9D2E6F68-2FFA-42A3-B122-65C1D5757657@ecs.soton.ac.uk>
Date: Thu, 4 Feb 2016 08:16:16 -0500
Message-ID: <CAOSSMjVbvfeAwXpdhr=jLVje3Kj=vPb_wQbJ+Y4wOGXNXAEuCw@mail.gmail.com>
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
From: Timothy Winters <twinters@iol.unh.edu>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary=001a113ed1841d0f49052af18a8f
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/8RPMlGmrSL1GuS_TXV1Vg-5alhs>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 13:16:18 -0000

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

I support adoption.

~Tim

On Thu, Feb 4, 2016 at 7:40 AM, Tim Chown <tjc@ecs.soton.ac.uk> wrote:

> > On 3 Feb 2016, at 20:25, otroan@employees.org wrote:
> >
> > This message starts a two week 6MAN call on adopting:
> >
> > Name: draft-hinden-6man-rfc1981bis-01
> > Title:        Path MTU Discovery for IP version 6
> > Document date:        2015-12-01
> > Pages:        16
> > URL:
> https://datatracker.ietf.org/doc/draft-hinden-6man-rfc1981bis/
> > Htmlized:  https://tools.ietf.org/html/draft-hinden-6man-rfc1981bis-01
> > Diff:
> https://tools.ietf.org/rfcdiff?url2=3Ddraft-hinden-6man-rfc1981bis-01.txt
> >
> > as a working group item. Substantive comments and statements of support
> > for adopting this document should be directed to the mailing
> > list. Editorial suggestions can be sent to the authors.
> >
> > This document is part of the working group=E2=80=99s ongoing work on ad=
vancing
> the
> > core IPv6 standards to Internet Standard.
> >
> > This adoption call will end on February 17th, 2016.
>
> I support adoption.
>
> Tim
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>



--=20

Timothy Winters
UNH-IOL Senior Executive, Software and IP Networking
*Please note we've moved!*
21 Madbury Rd, Suite 100, Durham, NH 03824
603-421-4987

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

<div dir=3D"ltr">I support adoption.<div><br></div><div>~Tim</div></div><di=
v class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Feb 4, 2016 =
at 7:40 AM, Tim Chown <span dir=3D"ltr">&lt;<a href=3D"mailto:tjc@ecs.soton=
.ac.uk" target=3D"_blank">tjc@ecs.soton.ac.uk</a>&gt;</span> wrote:<br><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><span class=3D"">&gt; On 3 Feb 2016, at 20:25, <=
a href=3D"mailto:otroan@employees.org">otroan@employees.org</a> wrote:<br>
&gt;<br>
&gt; This message starts a two week 6MAN call on adopting:<br>
&gt;<br>
&gt; Name: draft-hinden-6man-rfc1981bis-01<br>
&gt; Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 Path MTU Discovery for IP version 6<=
br>
&gt; Document date:=C2=A0 =C2=A0 =C2=A0 =C2=A0 2015-12-01<br>
&gt; Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 16<br>
&gt; URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.i=
etf.org/doc/draft-hinden-6man-rfc1981bis/" rel=3D"noreferrer" target=3D"_bl=
ank">https://datatracker.ietf.org/doc/draft-hinden-6man-rfc1981bis/</a><br>
&gt; Htmlized:=C2=A0 <a href=3D"https://tools.ietf.org/html/draft-hinden-6m=
an-rfc1981bis-01" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.o=
rg/html/draft-hinden-6man-rfc1981bis-01</a><br>
&gt; Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://tools.ietf.=
org/rfcdiff?url2=3Ddraft-hinden-6man-rfc1981bis-01.txt" rel=3D"noreferrer" =
target=3D"_blank">https://tools.ietf.org/rfcdiff?url2=3Ddraft-hinden-6man-r=
fc1981bis-01.txt</a><br>
&gt;<br>
&gt; as a working group item. Substantive comments and statements of suppor=
t<br>
&gt; for adopting this document should be directed to the mailing<br>
&gt; list. Editorial suggestions can be sent to the authors.<br>
&gt;<br>
&gt; This document is part of the working group=E2=80=99s ongoing work on a=
dvancing the<br>
&gt; core IPv6 standards to Internet Standard.<br>
&gt;<br>
&gt; This adoption call will end on February 17th, 2016.<br>
<br>
</span>I support adoption.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Tim<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5">---------------------=
-----------------------------------------------<br>
IETF IPv6 working group mailing list<br>
<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listinfo/i=
pv6" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/list=
info/ipv6</a><br>
--------------------------------------------------------------------<br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div class=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div =
dir=3D"ltr"><div dir=3D"ltr">







<p><span style=3D"font-family:georgia,serif;font-size:x-small">Timothy Wint=
ers<br></span><span style=3D"font-family:georgia,serif;font-size:x-small">U=
NH-IOL Senior Executive, Software and IP Networking</span><span style=3D"fo=
nt-family:georgia,serif;font-size:x-small"><br></span><span style=3D"font-f=
amily:georgia,serif;font-size:x-small"><b>Please note we&#39;ve moved!</b><=
br></span><span style=3D"font-family:georgia,serif;font-size:x-small">21 Ma=
dbury Rd, Suite 100, Durham, NH 03824<br></span><span style=3D"font-family:=
georgia,serif;font-size:x-small">603-421-4987</span></p></div></div></div><=
/div></div></div>
</div>

--001a113ed1841d0f49052af18a8f--


From nobody Thu Feb  4 06:27:30 2016
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C89AD1B303E for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 06:27:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] 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 EB8hLx0isA_1 for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 06:27:27 -0800 (PST)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 590281B303D for <ipv6@ietf.org>; Thu,  4 Feb 2016 06:27:26 -0800 (PST)
X-AuditID: c618062d-f79d16d000001b1c-c0-56b35c99449c
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usplmg20.ericsson.net (Symantec Mail Security) with SMTP id 03.64.06940.99C53B65; Thu,  4 Feb 2016 15:13:46 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.03.0248.002; Thu, 4 Feb 2016 09:27:25 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: "otroan@employees.org" <otroan@employees.org>, 6man WG <ipv6@ietf.org>
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AQHRXsM/D3XasOnkKEKtLs0MEiZpcQ==
Date: Thu, 4 Feb 2016 14:27:24 +0000
Message-ID: <E87B771635882B4BA20096B589152EF63AB5D6BF@eusaamb107.ericsson.se>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrBLMWRmVeSWpSXmKPExsUyuXSPt+6smM1hBvP/81tsfb+PzeLl2fdM FpPbVrA5MHscPPaR0WPnrLvsHkuW/GQKYI7isklJzcksSy3St0vgyri90qjgO3vFg6MnGBsY T7B1MXJySAiYSFzYeYIFwhaTuHBvPVCci0NI4AijxISGS1DOMkaJ888vg3WwAXVs2PmZCcQW EfCSuLpoAzuIzSxgKPHq8VSwuLCAs8SqKW1sEDUuEm+fdwHFOYBsPYkdEItZBFQk+s53sILY vAK+En29TWCtQgIOEp3nH4DVMAId9P3UGiaI8eISt57MZ4I4VEBiyZ7zzBC2qMTLx/9YIWwl iTmvrzFD1BtIvD83H8rWlli28DUzxC5BiZMzn7BMYBSdhWTsLCQts5C0zELSsoCRZRUjR2lx QU5uupHBJkZgfByTYNPdwXh/uuchRgEORiUeXgO/TWFCrIllxZW5hxglOJiVRHiXRWwOE+JN SaysSi3Kjy8qzUktPsQozcGiJM671GF9mJBAemJJanZqakFqEUyWiYNTqoExWPsv49EnX6oM Z/B1yUVObCyfb3tV7H3MlqCW/rVsD121jzysEr8Q+3vGuopHPEuXefoE8EjlnGwN+eH1gFf3 LWN/SqLT0kszXnw1+8YSXzHLjHGbl4hZ+ZQE3QDZRJdDT9ODHH8Gc2w7KLmp1vuW1tWAAylP UlOn9+wpF87RKup+t2n6gzVKLMUZiYZazEXFiQDsbkT+iwIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/59XRksJQ2SP1ou9J-vHDEsxpNXw>
Cc: "bob.hinden@gmail.com" <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 14:27:29 -0000

On 02/03/2016 03:41 PM, otroan@employees.org wrote:=0A=
> This message starts a two week 6MAN call on adopting:=0A=
> =0A=
> Name:	draft-hinden-6man-rfc1981bis-01=0A=
> Title:	Path MTU Discovery for IP version 6=0A=
> Document date:	2015-12-01=0A=
> Pages:	16=0A=
> URL:         https://datatracker.ietf.org/doc/draft-hinden-6man-rfc1981bi=
s/=0A=
> Htmlized:  https://tools.ietf.org/html/draft-hinden-6man-rfc1981bis-01=0A=
> Diff:          https://tools.ietf.org/rfcdiff?url2=3Ddraft-hinden-6man-rf=
c1981bis-01.txt=0A=
> =0A=
> as a working group item. Substantive comments and statements of support=
=0A=
> for adopting this document should be directed to the mailing=0A=
> list. Editorial suggestions can be sent to the authors.=0A=
> =0A=
> This document is part of the working group=92s ongoing work on advancing =
the=0A=
>  core IPv6 standards to Internet Standard.=0A=
=0A=
I have read the draft and I support its adoption as a 6man wg item.=0A=
=0A=
Thanks=0A=
Suresh=0A=
=0A=


From nobody Thu Feb  4 08:45:06 2016
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E9581B331B for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 08:45:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.502
X-Spam-Level: 
X-Spam-Status: No, score=-114.502 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ntqvvCntKRZv for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 08:45:03 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E90F1B32E5 for <ipv6@ietf.org>; Thu,  4 Feb 2016 08:44:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4866; q=dns/txt; s=iport; t=1454604282; x=1455813882; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=dDuJEnill9j1F0EdXKeN2JYWZnAx+yUUL2dP+p+IDMw=; b=e78qWbLcEgGhZZGd+/NX5I6tjwnLL3dZMvnWdLlko4/916k2FsAw5H4G OsjdMWXm+6J17Gt2D/+AZAQ76ufLQhubeLrKyBGpj/qzCb6PZ3PwfeyuI NtRUyRRAorf9HrfYcDileMHlajEzykyOncQwKzlhNE6DeCT6JkfuSyE2d Q=;
X-Files: signature.asc : 833
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0C5AgCgf7NW/4cNJK1egzpSbQaIVbEBD?= =?us-ascii?q?oFmIYVsAoE+OBQBAQEBAQEBgQqEQQEBAQMBI0sLBQsCAQgYKgICMiUCBA4FDog?= =?us-ascii?q?FCA6xY48hAQEBAQEBAQEBAQEBAQEBAQEBAQEBDQQEh38IgkKHMiuBDwWNJYVHh?= =?us-ascii?q?AUBgn2BY2qIBIFbh2iFLo4/AR4BQ4NkagGHLXwBAQE?=
X-IronPort-AV: E=Sophos;i="5.22,396,1449532800";  d="asc'?scan'208";a="72981403"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 04 Feb 2016 16:44:40 +0000
Received: from XCH-ALN-011.cisco.com (xch-aln-011.cisco.com [173.36.7.21]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id u14GiU04031311 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 4 Feb 2016 16:44:40 GMT
Received: from xch-rcd-013.cisco.com (173.37.102.23) by XCH-ALN-011.cisco.com (173.36.7.21) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 4 Feb 2016 10:44:33 -0600
Received: from xch-rcd-013.cisco.com ([173.37.102.23]) by XCH-RCD-013.cisco.com ([173.37.102.23]) with mapi id 15.00.1104.009; Thu, 4 Feb 2016 10:44:33 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AQHRX2tTSDlY+6HQH0uuyx8Jsd7k2Q==
Date: Thu, 4 Feb 2016 16:44:33 +0000
Message-ID: <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org>
In-Reply-To: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3112)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.6.80]
Content-Type: multipart/signed; boundary="Apple-Mail=_1378F994-A2AA-4F2C-8C43-C6F8470D08B6"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/onWuqj0OXaYpj6-fznySj5E8NxU>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 16:45:05 -0000

--Apple-Mail=_1378F994-A2AA-4F2C-8C43-C6F8470D08B6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Feb 3, 2016, at 12:25 PM, otroan@employees.org wrote:
>=20
> This message starts a two week 6MAN call on adopting:
>=20
> Name:	draft-hinden-6man-rfc1981bis-01
> Title:	Path MTU Discovery for IP version 6
> Document date:	2015-12-01
> Pages:	16
> URL:         =
https://datatracker.ietf.org/doc/draft-hinden-6man-rfc1981bis/
> Htmlized:  https://tools.ietf.org/html/draft-hinden-6man-rfc1981bis-01
> Diff:          =
https://tools.ietf.org/rfcdiff?url2=3Ddraft-hinden-6man-rfc1981bis-01.txt
>=20
> as a working group item. Substantive comments and statements of =
support
> for adopting this document should be directed to the mailing
> list. Editorial suggestions can be sent to the authors.
>=20
> This document is part of the working group=E2=80=99s ongoing work on =
advancing the
> core IPv6 standards to Internet Standard.
>=20
> This adoption call will end on February 17th, 2016.
>=20
> Regards,
>=20
> Bob Hinden & Ole Tr=C3=B8an

I am in favor of adoption.

I have read through the diffs against RFC 1981 and the thread. I agree =
with the removal of the paragraph regarding reducing the MTU below a =
certain bound, and laud the mention of RFC 4821. I tend to think that, =
in a world that has issues with ICMP, RFC 4821 is an excellent =
suggestion. I do have one quibble with the wording, which seems to =
suggest that the host has to make a choice - it first, perhaps, tries =
traditional PMTU, and then "in the absence of ICMP messages" (the =
session is not making progress but it is getting no ICMP messages, =
perhaps?) does something different. I would rather simply say that RFC =
4821 suggests an approach for use in environments in which =
administrative policy or other factors prevents the delivery of ICMP to =
the host. Perhaps:

OLD:
   An extension to Path MTU Discovery defined in this document can be
   found in [RFC4821].  It defines a method for Packetization Layer Path
   MTU Discovery (PLPMTUD).  In the absence of ICMP messages, the proper
   MTU is determined by starting with small packets and probing with
   successively larger packets.  The bulk of the algorithm is
   implemented above IP, in the transport layer (e.g., TCP) or other
   "Packetization Protocol" that is responsible for determining packet
   boundaries.
NEW:
   An extension to Path MTU Discovery defined in this document can be
   found in [RFC4821].  It defines a method for Packetization Layer Path
   MTU Discovery (PLPMTUD) designed for use in environments in which
   delivery of ICMP messages to a host are not assured.  In this =
algorithm,
   the proper
   MTU is determined by starting with small packets and probing with
   successively larger packets.  The bulk of the algorithm is
   implemented above IP, in the transport layer (e.g., TCP) or other
   "Packetization Protocol" that is responsible for determining packet
   boundaries.

Most of the diffs seem to have to do with the bibliography or details of =
the definitions. I'm not sure what the changes in definitions actually =
added, but saw nothing pernicious in that.

Regarding the point Fred Templin has raised (a stronger recommendation =
for RFC 4821), I worry just a bit about the level of experience we have =
with it. Like Fred, I really like the concept. I know it is implemented =
in Linux, but its use by an application in optional, and AFAIK no =
applications actually use it. The authors might have more to say, but I =
don't think we're ready for a recommendation.

--Apple-Mail=_1378F994-A2AA-4F2C-8C43-C6F8470D08B6
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIVAwUBVrN/8EayAOS/EQ8MAQJQPw/6AnQ0dnwbrNq216KHraEJYdb5aV3IDdWl
bRnPZWVnSQx5LWVzs841RBImXClmCnMua8sfbv8iwEkxpIyWdAiPSJkGRIHqlSjJ
SWlTi49JmQ21f5ZGcxrkRRwNSA/jnzPaGa9jul/0mOaNi4WQgvgkVKB2BHVFzwhe
4wXnKjTdg9uUmC1qFtaF1Wsj7bIZNJjBxh8Kc2H2adwcAlB2gWmtSSB+SwZe259M
mWCq52YFs+ikiR04WBV71Wzn1zwlOONOXsWe6Cgf5fy98JJI0Vqm2pbcUUsC7mOT
kihP/RQzx/TTmyjbQ/SYVpG8/bN2Xhk0Mb0wAwoyr7twVVMzoA3KWvkRDlC4GVSQ
n6asMWrOzXMMYmKmhGfzhgev+Vkg0W+VLsrcAjkWR9to/N/RpKqqrIiRY9ViLJkc
fm9gLtC3CHuFco9/JWdTfk0GVm26ZFP2fogKN//TX89gfapexgBTVVfPgvBqtkGS
KUnBviZFCC2TbHFlYRFTmhGdDGS2n5aiIYaK310HcSuS+v4KYwaqeoWPAYmTptGO
SWJ3PFZHoJ5LwTdfCCZ4vfgPVozlVPlW26j7cCnwiyfzfznZCb2hAYGoKSIGVwJo
WTSlFEGFY5CmbkdwkL0L34rLksCX5qyRmayk/+45VGS4OK/7+Poaoxo3OqxCgtub
ao6gwoKn0Ds=
=HfC/
-----END PGP SIGNATURE-----

--Apple-Mail=_1378F994-A2AA-4F2C-8C43-C6F8470D08B6--


From nobody Thu Feb  4 08:57:41 2016
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53AB61B32E8 for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 08:57:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g24HbYVS_q2F for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 08:57:36 -0800 (PST)
Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACE671B32DD for <ipv6@ietf.org>; Thu,  4 Feb 2016 08:57:36 -0800 (PST)
Received: by mail-qg0-x232.google.com with SMTP id o11so46284398qge.2 for <ipv6@ietf.org>; Thu, 04 Feb 2016 08:57:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=eJz2b1jqGLgLYH3AX78Wt36Rw73OBKGA3JUQw6MAgtA=; b=iI95W7g+Hzzz5nTvwBVeqdwCbxU/pMfSwsXI6WxxGFjS9g1Ekr7m67FGFACN4dQbzh XbwqRiOKB+urznCL80ZkCwe06wVkvMpUvEMH1S+4an8YeoB+aGyZdsMPfsLlBxSgEHDe oqLaaMtbD6TYrMBrmj238CqDr+1Nf9YEXKGau+BasVWrw3uvt9cGm0S2K8iCkVuMBEtP j9M7sYCvtrECrluvR6VWQn8R5qrCnLBnnb1oDoCtqED5wnnT5VODtrrXJNlZTYNB0Rpi cExvkOVMeX+Tmlx4m/Xs1qoiCdD6cC3nT1qPr2RqPrt0FTLVwwp5H+S6rJEitACl1bZI bMgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=eJz2b1jqGLgLYH3AX78Wt36Rw73OBKGA3JUQw6MAgtA=; b=XMtuiqDNXGUGhTbrTz4pWollYIA/IM1hDiWcSJ9AjvoV70erYFlzgtI5s6lES7Z73b 7ztKtsA+ygdJjQstFBbVBejzsnkUAg43wdv5iv08UbO+h6Js4y8uOegiPoXcbIP1SL6L 5rPAWCHGPgM9R8BRYqLhhjgPj9eyROr5oiiAl4BnTwLUkFrrpmAbwQm8M2M0MMpgcBF8 NdBafTzfUN8PwCUcF9yHFBAWh8OLlJuxz4TfmA8zO4odvzuraQ3ai0A2xpyOfOFu246K /NgnxCL2X2bQNp3fMYKAmLg1OJCHAZVEJ/AdegHlWNhR88UAc88vWh7jJ9w2R/m3VJ5r 5eJg==
X-Gm-Message-State: AG10YOSUo9UUxU1jE9jgGOefA781Hm/aqZPcSKThAVVnYZe0zLhWA4X7Jl4LdNPTceTFyQ==
X-Received: by 10.140.96.117 with SMTP id j108mr8748482qge.63.1454605055735; Thu, 04 Feb 2016 08:57:35 -0800 (PST)
Received: from [10.0.0.24] (c-71-202-19-53.hsd1.ca.comcast.net. [71.202.19.53]) by smtp.gmail.com with ESMTPSA id j75sm2835726qge.41.2016.02.04.08.57.33 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 04 Feb 2016 08:57:33 -0800 (PST)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_67684B0F-20A7-4B12-9253-6809264447DD"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com>
Date: Thu, 4 Feb 2016 08:57:31 -0800
Message-Id: <2FC8254F-F177-4662-B678-6936E96080D3@gmail.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com>
To: "Fred Baker (fred)" <fred@cisco.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/q6A3u6VSg5E8yodQK7W3Qjk_Spw>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 16:57:39 -0000

--Apple-Mail=_67684B0F-20A7-4B12-9253-6809264447DD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Fred,

> On Feb 4, 2016, at 8:44 AM, Fred Baker (fred) <fred@cisco.com> wrote:
>=20
>=20
>> On Feb 3, 2016, at 12:25 PM, otroan@employees.org wrote:
>>=20
>> This message starts a two week 6MAN call on adopting:
>>=20
>> Name:	draft-hinden-6man-rfc1981bis-01
>> Title:	Path MTU Discovery for IP version 6
>> Document date:	2015-12-01
>> Pages:	16
>> URL:         =
https://datatracker.ietf.org/doc/draft-hinden-6man-rfc1981bis/
>> Htmlized:  =
https://tools.ietf.org/html/draft-hinden-6man-rfc1981bis-01
>> Diff:          =
https://tools.ietf.org/rfcdiff?url2=3Ddraft-hinden-6man-rfc1981bis-01.txt
>>=20
>> as a working group item. Substantive comments and statements of =
support
>> for adopting this document should be directed to the mailing
>> list. Editorial suggestions can be sent to the authors.
>>=20
>> This document is part of the working group=E2=80=99s ongoing work on =
advancing the
>> core IPv6 standards to Internet Standard.
>>=20
>> This adoption call will end on February 17th, 2016.
>>=20
>> Regards,
>>=20
>> Bob Hinden & Ole Tr=C3=B8an
>=20
> I am in favor of adoption.
>=20
> I have read through the diffs against RFC 1981 and the thread. I agree =
with the removal of the paragraph regarding reducing the MTU below a =
certain bound, and laud the mention of RFC 4821. I tend to think that, =
in a world that has issues with ICMP, RFC 4821 is an excellent =
suggestion. I do have one quibble with the wording, which seems to =
suggest that the host has to make a choice - it first, perhaps, tries =
traditional PMTU, and then "in the absence of ICMP messages" (the =
session is not making progress but it is getting no ICMP messages, =
perhaps?) does something different. I would rather simply say that RFC =
4821 suggests an approach for use in environments in which =
administrative policy or other factors prevents the delivery of ICMP to =
the host. Perhaps:
>=20
> OLD:
>   An extension to Path MTU Discovery defined in this document can be
>   found in [RFC4821].  It defines a method for Packetization Layer =
Path
>   MTU Discovery (PLPMTUD).  In the absence of ICMP messages, the =
proper
>   MTU is determined by starting with small packets and probing with
>   successively larger packets.  The bulk of the algorithm is
>   implemented above IP, in the transport layer (e.g., TCP) or other
>   "Packetization Protocol" that is responsible for determining packet
>   boundaries.
> NEW:
>   An extension to Path MTU Discovery defined in this document can be
>   found in [RFC4821].  It defines a method for Packetization Layer =
Path
>   MTU Discovery (PLPMTUD) designed for use in environments in which
>   delivery of ICMP messages to a host are not assured.  In this =
algorithm,
>   the proper
>   MTU is determined by starting with small packets and probing with
>   successively larger packets.  The bulk of the algorithm is
>   implemented above IP, in the transport layer (e.g., TCP) or other
>   "Packetization Protocol" that is responsible for determining packet
>   boundaries.

The =E2=80=9COLD=E2=80=9D text above was taken almost exactly from the =
Introduction from RFC4821.  I think you =E2=80=9CNEW=E2=80=9D text is =
fine and unless some objects I will included this in the next version of =
the draft.

>=20
> Most of the diffs seem to have to do with the bibliography or details =
of the definitions. I'm not sure what the changes in definitions =
actually added, but saw nothing pernicious in that.
>=20
> Regarding the point Fred Templin has raised (a stronger recommendation =
for RFC 4821), I worry just a bit about the level of experience we have =
with it. Like Fred, I really like the concept. I know it is implemented =
in Linux, but its use by an application in optional, and AFAIK no =
applications actually use it. The authors might have more to say, but I =
don't think we're ready for a recommendation.

I agree, especially for going to Internet Standard.

Thanks,
Bob



--Apple-Mail=_67684B0F-20A7-4B12-9253-6809264447DD
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJWs4L7AAoJEK7rdBF357uo+6EH/0kSWa/0Wpw7pDQyxr7m1iEy
wQ5qP1LzMZq6+vdD+yYArLAlFRLYheuc1vIWmeLjCBNm1m3eZ3oFNsiNaNO6JACF
SQqC5kCI2sgYcYuFvbdRcQsAS2TMCduMgvVf/T9R+lGZM3du1LVAqN6GT5NClhWZ
LZE0YiBbRhMHTu16VyrF5+ncR9+jRnY2SJNa+unzjWD5K/V/KVzfrJds8PqowXCX
m75Bj2O4OqyKHa5YqpFgklcpuxqFtI4rlFJbs67Gh/p6vRKaJDFxwDBP+z2f0FNb
tfK2i5b1MwToPiXQeDLko/y5p/sJGPXGrshi57XsxFuRoHFOz5xjx0Ev77gv7nw=
=JOmd
-----END PGP SIGNATURE-----

--Apple-Mail=_67684B0F-20A7-4B12-9253-6809264447DD--


From nobody Thu Feb  4 09:54:05 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EFCC1A8988 for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 09:54:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 jWMqlkxP7GvP for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 09:54:01 -0800 (PST)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) (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 B50A11A8992 for <ipv6@ietf.org>; Thu,  4 Feb 2016 09:53:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u14Hrt2C029658; Thu, 4 Feb 2016 11:53:55 -0600
Received: from XCH-PHX-111.sw.nos.boeing.com (xch-phx-111.sw.nos.boeing.com [130.247.25.132]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u14HriY2029613 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 4 Feb 2016 11:53:44 -0600
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-PHX-111.sw.nos.boeing.com ([169.254.11.183]) with mapi id 14.03.0235.001;  Thu, 4 Feb 2016 09:53:44 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Fred Baker (fred)" <fred@cisco.com>, Bob Hinden <bob.hinden@gmail.com>
Subject: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AQHRX2tT80dfpGCQDUCIhA2edhybgJ8cKO6Q
Date: Thu, 4 Feb 2016 17:53:43 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com>
In-Reply-To: <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/gWTQ7sP6pDOyaTEAocz6OVvl_-I>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 17:54:03 -0000

SGkgRnJlZCBCLiwNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBpcHY2
IFttYWlsdG86aXB2Ni1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgRnJlZCBCYWtlciAo
ZnJlZCkNCj4gU2VudDogVGh1cnNkYXksIEZlYnJ1YXJ5IDA0LCAyMDE2IDg6NDUgQU0NCj4gVG86
IEJvYiBIaW5kZW4NCj4gQ2M6IDZtYW4gV0cNCj4gU3ViamVjdDogUmU6IDZNQU46IEFkb3B0aW9u
IGNhbGwgb24gZHJhZnQtaGluZGVuLTZtYW4tcmZjMTk4MWJpcy0wMQ0KPiANCj4gDQo+ID4gT24g
RmViIDMsIDIwMTYsIGF0IDEyOjI1IFBNLCBvdHJvYW5AZW1wbG95ZWVzLm9yZyB3cm90ZToNCj4g
Pg0KPiA+IFRoaXMgbWVzc2FnZSBzdGFydHMgYSB0d28gd2VlayA2TUFOIGNhbGwgb24gYWRvcHRp
bmc6DQo+ID4NCj4gPiBOYW1lOglkcmFmdC1oaW5kZW4tNm1hbi1yZmMxOTgxYmlzLTAxDQo+ID4g
VGl0bGU6CVBhdGggTVRVIERpc2NvdmVyeSBmb3IgSVAgdmVyc2lvbiA2DQo+ID4gRG9jdW1lbnQg
ZGF0ZToJMjAxNS0xMi0wMQ0KPiA+IFBhZ2VzOgkxNg0KPiA+IFVSTDogICAgICAgICBodHRwczov
L2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1oaW5kZW4tNm1hbi1yZmMxOTgxYmlzLw0K
PiA+IEh0bWxpemVkOiAgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWhpbmRlbi02
bWFuLXJmYzE5ODFiaXMtMDENCj4gPiBEaWZmOiAgICAgICAgICBodHRwczovL3Rvb2xzLmlldGYu
b3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1oaW5kZW4tNm1hbi1yZmMxOTgxYmlzLTAxLnR4dA0KPiA+
DQo+ID4gYXMgYSB3b3JraW5nIGdyb3VwIGl0ZW0uIFN1YnN0YW50aXZlIGNvbW1lbnRzIGFuZCBz
dGF0ZW1lbnRzIG9mIHN1cHBvcnQNCj4gPiBmb3IgYWRvcHRpbmcgdGhpcyBkb2N1bWVudCBzaG91
bGQgYmUgZGlyZWN0ZWQgdG8gdGhlIG1haWxpbmcNCj4gPiBsaXN0LiBFZGl0b3JpYWwgc3VnZ2Vz
dGlvbnMgY2FuIGJlIHNlbnQgdG8gdGhlIGF1dGhvcnMuDQo+ID4NCj4gPiBUaGlzIGRvY3VtZW50
IGlzIHBhcnQgb2YgdGhlIHdvcmtpbmcgZ3JvdXDigJlzIG9uZ29pbmcgd29yayBvbiBhZHZhbmNp
bmcgdGhlDQo+ID4gY29yZSBJUHY2IHN0YW5kYXJkcyB0byBJbnRlcm5ldCBTdGFuZGFyZC4NCj4g
Pg0KPiA+IFRoaXMgYWRvcHRpb24gY2FsbCB3aWxsIGVuZCBvbiBGZWJydWFyeSAxN3RoLCAyMDE2
Lg0KPiA+DQo+ID4gUmVnYXJkcywNCj4gPg0KPiA+IEJvYiBIaW5kZW4gJiBPbGUgVHLDuGFuDQo+
IA0KPiBJIGFtIGluIGZhdm9yIG9mIGFkb3B0aW9uLg0KPiANCj4gSSBoYXZlIHJlYWQgdGhyb3Vn
aCB0aGUgZGlmZnMgYWdhaW5zdCBSRkMgMTk4MSBhbmQgdGhlIHRocmVhZC4gSSBhZ3JlZSB3aXRo
IHRoZSByZW1vdmFsIG9mIHRoZSBwYXJhZ3JhcGggcmVnYXJkaW5nIHJlZHVjaW5nIHRoZSBNVFUN
Cj4gYmVsb3cgYSBjZXJ0YWluIGJvdW5kLCBhbmQgbGF1ZCB0aGUgbWVudGlvbiBvZiBSRkMgNDgy
MS4gSSB0ZW5kIHRvIHRoaW5rIHRoYXQsIGluIGEgd29ybGQgdGhhdCBoYXMgaXNzdWVzIHdpdGgg
SUNNUCwgUkZDIDQ4MjEgaXMgYW4NCj4gZXhjZWxsZW50IHN1Z2dlc3Rpb24uIEkgZG8gaGF2ZSBv
bmUgcXVpYmJsZSB3aXRoIHRoZSB3b3JkaW5nLCB3aGljaCBzZWVtcyB0byBzdWdnZXN0IHRoYXQg
dGhlIGhvc3QgaGFzIHRvIG1ha2UgYSBjaG9pY2UgLSBpdCBmaXJzdCwNCj4gcGVyaGFwcywgdHJp
ZXMgdHJhZGl0aW9uYWwgUE1UVSwgYW5kIHRoZW4gImluIHRoZSBhYnNlbmNlIG9mIElDTVAgbWVz
c2FnZXMiICh0aGUgc2Vzc2lvbiBpcyBub3QgbWFraW5nIHByb2dyZXNzIGJ1dCBpdCBpcyBnZXR0
aW5nIG5vDQo+IElDTVAgbWVzc2FnZXMsIHBlcmhhcHM/KSBkb2VzIHNvbWV0aGluZyBkaWZmZXJl
bnQuIEkgd291bGQgcmF0aGVyIHNpbXBseSBzYXkgdGhhdCBSRkMgNDgyMSBzdWdnZXN0cyBhbiBh
cHByb2FjaCBmb3IgdXNlIGluDQo+IGVudmlyb25tZW50cyBpbiB3aGljaCBhZG1pbmlzdHJhdGl2
ZSBwb2xpY3kgb3Igb3RoZXIgZmFjdG9ycyBwcmV2ZW50cyB0aGUgZGVsaXZlcnkgb2YgSUNNUCB0
byB0aGUgaG9zdC4gUGVyaGFwczoNCj4gDQo+IE9MRDoNCj4gICAgQW4gZXh0ZW5zaW9uIHRvIFBh
dGggTVRVIERpc2NvdmVyeSBkZWZpbmVkIGluIHRoaXMgZG9jdW1lbnQgY2FuIGJlDQo+ICAgIGZv
dW5kIGluIFtSRkM0ODIxXS4gIEl0IGRlZmluZXMgYSBtZXRob2QgZm9yIFBhY2tldGl6YXRpb24g
TGF5ZXIgUGF0aA0KPiAgICBNVFUgRGlzY292ZXJ5IChQTFBNVFVEKS4gIEluIHRoZSBhYnNlbmNl
IG9mIElDTVAgbWVzc2FnZXMsIHRoZSBwcm9wZXINCj4gICAgTVRVIGlzIGRldGVybWluZWQgYnkg
c3RhcnRpbmcgd2l0aCBzbWFsbCBwYWNrZXRzIGFuZCBwcm9iaW5nIHdpdGgNCj4gICAgc3VjY2Vz
c2l2ZWx5IGxhcmdlciBwYWNrZXRzLiAgVGhlIGJ1bGsgb2YgdGhlIGFsZ29yaXRobSBpcw0KPiAg
ICBpbXBsZW1lbnRlZCBhYm92ZSBJUCwgaW4gdGhlIHRyYW5zcG9ydCBsYXllciAoZS5nLiwgVENQ
KSBvciBvdGhlcg0KPiAgICAiUGFja2V0aXphdGlvbiBQcm90b2NvbCIgdGhhdCBpcyByZXNwb25z
aWJsZSBmb3IgZGV0ZXJtaW5pbmcgcGFja2V0DQo+ICAgIGJvdW5kYXJpZXMuDQo+IE5FVzoNCj4g
ICAgQW4gZXh0ZW5zaW9uIHRvIFBhdGggTVRVIERpc2NvdmVyeSBkZWZpbmVkIGluIHRoaXMgZG9j
dW1lbnQgY2FuIGJlDQo+ICAgIGZvdW5kIGluIFtSRkM0ODIxXS4gIEl0IGRlZmluZXMgYSBtZXRo
b2QgZm9yIFBhY2tldGl6YXRpb24gTGF5ZXIgUGF0aA0KPiAgICBNVFUgRGlzY292ZXJ5IChQTFBN
VFVEKSBkZXNpZ25lZCBmb3IgdXNlIGluIGVudmlyb25tZW50cyBpbiB3aGljaA0KPiAgICBkZWxp
dmVyeSBvZiBJQ01QIG1lc3NhZ2VzIHRvIGEgaG9zdCBhcmUgbm90IGFzc3VyZWQuICBJbiB0aGlz
IGFsZ29yaXRobSwNCj4gICAgdGhlIHByb3Blcg0KPiAgICBNVFUgaXMgZGV0ZXJtaW5lZCBieSBz
dGFydGluZyB3aXRoIHNtYWxsIHBhY2tldHMgYW5kIHByb2Jpbmcgd2l0aA0KPiAgICBzdWNjZXNz
aXZlbHkgbGFyZ2VyIHBhY2tldHMuICBUaGUgYnVsayBvZiB0aGUgYWxnb3JpdGhtIGlzDQo+ICAg
IGltcGxlbWVudGVkIGFib3ZlIElQLCBpbiB0aGUgdHJhbnNwb3J0IGxheWVyIChlLmcuLCBUQ1Ap
IG9yIG90aGVyDQo+ICAgICJQYWNrZXRpemF0aW9uIFByb3RvY29sIiB0aGF0IGlzIHJlc3BvbnNp
YmxlIGZvciBkZXRlcm1pbmluZyBwYWNrZXQNCj4gICAgYm91bmRhcmllcy4NCg0KVGhhdCBpcyBl
c3NlbnRpYWxseSB3aGF0IEkgd2FzIHNheWluZyB3aGVuIEkgc2FpZCB0aGF0Og0KDQogICAgIkl0
IGlzIHJlY29tbWVuZGVkIHRoYXQgSVB2NiBub2RlcyB0aGF0IHNlbmQgcGFja2V0cyBsYXJnZXIg
dGhhbiAxMjgwIGJ5dGVzDQogICAgdG8gSW50ZXJuZXQgZGVzdGluYXRpb25zIHVzZSBQTFBNVFVE
IHRvIG92ZXJjb21lIHNpbGVudCBmYWlsdXJlcyBvZiBzdGFuZGFyZA0KICAgIFBhdGggTVRVIGRp
c2NvdmVyeS4iDQoNCndoZXJlICJJbnRlcm5ldCBkZXN0aW5hdGlvbnMiIHJlZmVycyB0byBkZXN0
aW5hdGlvbnMgb3V0c2lkZSBvZiB0aGUgc291cmNlDQpub2RlJ3MgYWRtaW5pc3RyYXRpdmUgZG9t
YWluIHNpbmNlIHN0YW5kYXJkIFBNVFVEIHByZXN1bWFibHkgd29ya3MNCndpdGhpbiBhIHdlbGwt
bWFuYWdlZCBhZG1pbmlzdHJhdGl2ZSBkb21haW4uDQoNCldlIG5lZWQgdG8gYWxzbyBtYWtlIGl0
IGNsZWFyIHRoYXQgc3RhbmRhcmQgUE1UVUQgcGVyIElDTVAgbWVzc2FnaW5nDQppcyB0aGUgcHJl
ZmVycmVkIG9wdGlvbiB3aGVuIGl0IGNhbiBiZSB0cnVzdGVkIC0gb3RoZXJ3aXNlLCB3ZSBzaG91
bGQgYmUNCmRlcHJlY2F0aW5nIFJGQzE5ODEgaW5zdGVhZCBvZiBtYWtpbmcgaXQgYSBzdGFuZGFy
ZC4NCg0KVGhhbmtzIC0gRnJlZA0KZnJlZC5sLnRlbXBsaW5AYm9laW5nLmNvbQ0KDQo+IE1vc3Qg
b2YgdGhlIGRpZmZzIHNlZW0gdG8gaGF2ZSB0byBkbyB3aXRoIHRoZSBiaWJsaW9ncmFwaHkgb3Ig
ZGV0YWlscyBvZiB0aGUgZGVmaW5pdGlvbnMuIEknbSBub3Qgc3VyZSB3aGF0IHRoZSBjaGFuZ2Vz
IGluIGRlZmluaXRpb25zDQo+IGFjdHVhbGx5IGFkZGVkLCBidXQgc2F3IG5vdGhpbmcgcGVybmlj
aW91cyBpbiB0aGF0Lg0KPiANCj4gUmVnYXJkaW5nIHRoZSBwb2ludCBGcmVkIFRlbXBsaW4gaGFz
IHJhaXNlZCAoYSBzdHJvbmdlciByZWNvbW1lbmRhdGlvbiBmb3IgUkZDIDQ4MjEpLCBJIHdvcnJ5
IGp1c3QgYSBiaXQgYWJvdXQgdGhlIGxldmVsIG9mDQo+IGV4cGVyaWVuY2Ugd2UgaGF2ZSB3aXRo
IGl0LiBMaWtlIEZyZWQsIEkgcmVhbGx5IGxpa2UgdGhlIGNvbmNlcHQuIEkga25vdyBpdCBpcyBp
bXBsZW1lbnRlZCBpbiBMaW51eCwgYnV0IGl0cyB1c2UgYnkgYW4gYXBwbGljYXRpb24gaW4NCj4g
b3B0aW9uYWwsIGFuZCBBRkFJSyBubyBhcHBsaWNhdGlvbnMgYWN0dWFsbHkgdXNlIGl0LiBUaGUg
YXV0aG9ycyBtaWdodCBoYXZlIG1vcmUgdG8gc2F5LCBidXQgSSBkb24ndCB0aGluayB3ZSdyZSBy
ZWFkeSBmb3IgYQ0KPiByZWNvbW1lbmRhdGlvbi4NCg==


From nobody Thu Feb  4 10:37:37 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EF181ACD00 for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 10:37:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 GaIX_ZyIEOcq for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 10:37:33 -0800 (PST)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) (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 283FE1ACD12 for <ipv6@ietf.org>; Thu,  4 Feb 2016 10:37:19 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u14IbPp4027268; Thu, 4 Feb 2016 10:37:25 -0800
Received: from XCH-BLV-306.nw.nos.boeing.com (xch-blv-306.nw.nos.boeing.com [130.247.25.218]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u14IbKLD027083 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 4 Feb 2016 10:37:20 -0800
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-BLV-306.nw.nos.boeing.com ([169.254.6.160]) with mapi id 14.03.0235.001; Thu, 4 Feb 2016 10:37:14 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Fred Baker (fred)" <fred@cisco.com>, Bob Hinden <bob.hinden@gmail.com>
Subject: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AQHRX2tT80dfpGCQDUCIhA2edhybgJ8cKO6QgAAMGWA=
Date: Thu, 4 Feb 2016 18:37:13 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395DEF3@XCH-BLV-105.nw.nos.boeing.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com> <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/hCFqRLR7HMlikI_qyqZWGUI88Bo>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 18:37:36 -0000

SGkgRnJlZCBCLiwNCg0KT25lIG90aGVyIHRoaW5nIHRoYXQgYm90aCB5b3VyIGFuZCBteSB0ZXh0
IGZhaWxzIHRvIGNhcHR1cmUgaXMgdGhhdCB0aGVyZQ0KYXJlIHR3byBmYWlsdXJlIG1vZGVzIHRv
IGNvbnNpZGVyOg0KDQogIDEpIGxvc3Mgb2YgbmVjZXNzYXJ5IElDTVAgUFRCcw0KICAyKSByZWNl
aXB0IG9mIGJvZ3VzIElDTVAgUFRCcw0KDQpZb3UgYW5kIEkgaGF2ZSB0YWxrZWQgYWJvdXQgY2Fz
ZSAxKSwgYnV0IHRoZSB0ZXh0IG5lZWRzIHRvIGJlIG1vZGlmaWVkDQp0byBhZGRyZXNzIGNhc2Ug
MikuIE15IHRleHQgY291bGQgYmUgbW9kaWZpZWQgYnkgc2ltcGx5IGRlbGV0aW5nIHRoZQ0Kd29y
ZCAic2lsZW50IiBhcyBmb2xsb3dzOg0KDQogICJJdCBpcyByZWNvbW1lbmRlZCB0aGF0IElQdjYg
bm9kZXMgdGhhdCBzZW5kIHBhY2tldHMgbGFyZ2VyIHRoYW4gMTI4MCBieXRlcw0KICAgdG8gSW50
ZXJuZXQgZGVzdGluYXRpb25zIHVzZSBQTFBNVFVEIHRvIG92ZXJjb21lIGZhaWx1cmVzIG9mIHN0
YW5kYXJkDQogICBQYXRoIE1UVSBkaXNjb3ZlcnkuIg0KDQpZb3VyIHRleHQgY291bGQgYmUgbW9k
aWZpZWQgYnkgc2ltcGx5IGFkZGluZyB0aGUgd29yZCAiYWNjdXJhdGUiIGFzIGZvbGxvd3M6DQoN
CiAgIkl0IGRlZmluZXMgYSBtZXRob2QgZm9yIFBhY2tldGl6YXRpb24gTGF5ZXIgUGF0aCBNVFUg
RGlzY292ZXJ5IChQTFBNVFVEKQ0KICAgIGRlc2lnbmVkIGZvciB1c2UgaW4gZW52aXJvbm1lbnRz
IGluIHdoaWNoIGRlbGl2ZXJ5IG9mIGFjY3VyYXRlIElDTVAgbWVzc2FnZXMNCiAgICB0byBhIGhv
c3QgYXJlIG5vdCBhc3N1cmVkLiINCg0KVGhhbmtzIC0gRnJlZA0KZnJlZC5sLnRlbXBsaW5AYm9l
aW5nLmNvbQ0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IGlwdjYgW21h
aWx0bzppcHY2LWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBUZW1wbGluLCBGcmVkIEwN
Cj4gU2VudDogVGh1cnNkYXksIEZlYnJ1YXJ5IDA0LCAyMDE2IDk6NTQgQU0NCj4gVG86IEZyZWQg
QmFrZXIgKGZyZWQpOyBCb2IgSGluZGVuDQo+IENjOiA2bWFuIFdHDQo+IFN1YmplY3Q6IFJFOiA2
TUFOOiBBZG9wdGlvbiBjYWxsIG9uIGRyYWZ0LWhpbmRlbi02bWFuLXJmYzE5ODFiaXMtMDENCj4g
DQo+IEhpIEZyZWQgQi4sDQo+IA0KPiA+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4g
RnJvbTogaXB2NiBbbWFpbHRvOmlwdjYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEZy
ZWQgQmFrZXIgKGZyZWQpDQo+ID4gU2VudDogVGh1cnNkYXksIEZlYnJ1YXJ5IDA0LCAyMDE2IDg6
NDUgQU0NCj4gPiBUbzogQm9iIEhpbmRlbg0KPiA+IENjOiA2bWFuIFdHDQo+ID4gU3ViamVjdDog
UmU6IDZNQU46IEFkb3B0aW9uIGNhbGwgb24gZHJhZnQtaGluZGVuLTZtYW4tcmZjMTk4MWJpcy0w
MQ0KPiA+DQo+ID4NCj4gPiA+IE9uIEZlYiAzLCAyMDE2LCBhdCAxMjoyNSBQTSwgb3Ryb2FuQGVt
cGxveWVlcy5vcmcgd3JvdGU6DQo+ID4gPg0KPiA+ID4gVGhpcyBtZXNzYWdlIHN0YXJ0cyBhIHR3
byB3ZWVrIDZNQU4gY2FsbCBvbiBhZG9wdGluZzoNCj4gPiA+DQo+ID4gPiBOYW1lOglkcmFmdC1o
aW5kZW4tNm1hbi1yZmMxOTgxYmlzLTAxDQo+ID4gPiBUaXRsZToJUGF0aCBNVFUgRGlzY292ZXJ5
IGZvciBJUCB2ZXJzaW9uIDYNCj4gPiA+IERvY3VtZW50IGRhdGU6CTIwMTUtMTItMDENCj4gPiA+
IFBhZ2VzOgkxNg0KPiA+ID4gVVJMOiAgICAgICAgIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5v
cmcvZG9jL2RyYWZ0LWhpbmRlbi02bWFuLXJmYzE5ODFiaXMvDQo+ID4gPiBIdG1saXplZDogIGh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1oaW5kZW4tNm1hbi1yZmMxOTgxYmlzLTAx
DQo+ID4gPiBEaWZmOiAgICAgICAgICBodHRwczovL3Rvb2xzLmlldGYub3JnL3JmY2RpZmY/dXJs
Mj1kcmFmdC1oaW5kZW4tNm1hbi1yZmMxOTgxYmlzLTAxLnR4dA0KPiA+ID4NCj4gPiA+IGFzIGEg
d29ya2luZyBncm91cCBpdGVtLiBTdWJzdGFudGl2ZSBjb21tZW50cyBhbmQgc3RhdGVtZW50cyBv
ZiBzdXBwb3J0DQo+ID4gPiBmb3IgYWRvcHRpbmcgdGhpcyBkb2N1bWVudCBzaG91bGQgYmUgZGly
ZWN0ZWQgdG8gdGhlIG1haWxpbmcNCj4gPiA+IGxpc3QuIEVkaXRvcmlhbCBzdWdnZXN0aW9ucyBj
YW4gYmUgc2VudCB0byB0aGUgYXV0aG9ycy4NCj4gPiA+DQo+ID4gPiBUaGlzIGRvY3VtZW50IGlz
IHBhcnQgb2YgdGhlIHdvcmtpbmcgZ3JvdXDigJlzIG9uZ29pbmcgd29yayBvbiBhZHZhbmNpbmcg
dGhlDQo+ID4gPiBjb3JlIElQdjYgc3RhbmRhcmRzIHRvIEludGVybmV0IFN0YW5kYXJkLg0KPiA+
ID4NCj4gPiA+IFRoaXMgYWRvcHRpb24gY2FsbCB3aWxsIGVuZCBvbiBGZWJydWFyeSAxN3RoLCAy
MDE2Lg0KPiA+ID4NCj4gPiA+IFJlZ2FyZHMsDQo+ID4gPg0KPiA+ID4gQm9iIEhpbmRlbiAmIE9s
ZSBUcsO4YW4NCj4gPg0KPiA+IEkgYW0gaW4gZmF2b3Igb2YgYWRvcHRpb24uDQo+ID4NCj4gPiBJ
IGhhdmUgcmVhZCB0aHJvdWdoIHRoZSBkaWZmcyBhZ2FpbnN0IFJGQyAxOTgxIGFuZCB0aGUgdGhy
ZWFkLiBJIGFncmVlIHdpdGggdGhlIHJlbW92YWwgb2YgdGhlIHBhcmFncmFwaCByZWdhcmRpbmcg
cmVkdWNpbmcgdGhlDQo+IE1UVQ0KPiA+IGJlbG93IGEgY2VydGFpbiBib3VuZCwgYW5kIGxhdWQg
dGhlIG1lbnRpb24gb2YgUkZDIDQ4MjEuIEkgdGVuZCB0byB0aGluayB0aGF0LCBpbiBhIHdvcmxk
IHRoYXQgaGFzIGlzc3VlcyB3aXRoIElDTVAsIFJGQyA0ODIxIGlzIGFuDQo+ID4gZXhjZWxsZW50
IHN1Z2dlc3Rpb24uIEkgZG8gaGF2ZSBvbmUgcXVpYmJsZSB3aXRoIHRoZSB3b3JkaW5nLCB3aGlj
aCBzZWVtcyB0byBzdWdnZXN0IHRoYXQgdGhlIGhvc3QgaGFzIHRvIG1ha2UgYSBjaG9pY2UgLSBp
dCBmaXJzdCwNCj4gPiBwZXJoYXBzLCB0cmllcyB0cmFkaXRpb25hbCBQTVRVLCBhbmQgdGhlbiAi
aW4gdGhlIGFic2VuY2Ugb2YgSUNNUCBtZXNzYWdlcyIgKHRoZSBzZXNzaW9uIGlzIG5vdCBtYWtp
bmcgcHJvZ3Jlc3MgYnV0IGl0IGlzIGdldHRpbmcgbm8NCj4gPiBJQ01QIG1lc3NhZ2VzLCBwZXJo
YXBzPykgZG9lcyBzb21ldGhpbmcgZGlmZmVyZW50LiBJIHdvdWxkIHJhdGhlciBzaW1wbHkgc2F5
IHRoYXQgUkZDIDQ4MjEgc3VnZ2VzdHMgYW4gYXBwcm9hY2ggZm9yIHVzZSBpbg0KPiA+IGVudmly
b25tZW50cyBpbiB3aGljaCBhZG1pbmlzdHJhdGl2ZSBwb2xpY3kgb3Igb3RoZXIgZmFjdG9ycyBw
cmV2ZW50cyB0aGUgZGVsaXZlcnkgb2YgSUNNUCB0byB0aGUgaG9zdC4gUGVyaGFwczoNCj4gPg0K
PiA+IE9MRDoNCj4gPiAgICBBbiBleHRlbnNpb24gdG8gUGF0aCBNVFUgRGlzY292ZXJ5IGRlZmlu
ZWQgaW4gdGhpcyBkb2N1bWVudCBjYW4gYmUNCj4gPiAgICBmb3VuZCBpbiBbUkZDNDgyMV0uICBJ
dCBkZWZpbmVzIGEgbWV0aG9kIGZvciBQYWNrZXRpemF0aW9uIExheWVyIFBhdGgNCj4gPiAgICBN
VFUgRGlzY292ZXJ5IChQTFBNVFVEKS4gIEluIHRoZSBhYnNlbmNlIG9mIElDTVAgbWVzc2FnZXMs
IHRoZSBwcm9wZXINCj4gPiAgICBNVFUgaXMgZGV0ZXJtaW5lZCBieSBzdGFydGluZyB3aXRoIHNt
YWxsIHBhY2tldHMgYW5kIHByb2Jpbmcgd2l0aA0KPiA+ICAgIHN1Y2Nlc3NpdmVseSBsYXJnZXIg
cGFja2V0cy4gIFRoZSBidWxrIG9mIHRoZSBhbGdvcml0aG0gaXMNCj4gPiAgICBpbXBsZW1lbnRl
ZCBhYm92ZSBJUCwgaW4gdGhlIHRyYW5zcG9ydCBsYXllciAoZS5nLiwgVENQKSBvciBvdGhlcg0K
PiA+ICAgICJQYWNrZXRpemF0aW9uIFByb3RvY29sIiB0aGF0IGlzIHJlc3BvbnNpYmxlIGZvciBk
ZXRlcm1pbmluZyBwYWNrZXQNCj4gPiAgICBib3VuZGFyaWVzLg0KPiA+IE5FVzoNCj4gPiAgICBB
biBleHRlbnNpb24gdG8gUGF0aCBNVFUgRGlzY292ZXJ5IGRlZmluZWQgaW4gdGhpcyBkb2N1bWVu
dCBjYW4gYmUNCj4gPiAgICBmb3VuZCBpbiBbUkZDNDgyMV0uICBJdCBkZWZpbmVzIGEgbWV0aG9k
IGZvciBQYWNrZXRpemF0aW9uIExheWVyIFBhdGgNCj4gPiAgICBNVFUgRGlzY292ZXJ5IChQTFBN
VFVEKSBkZXNpZ25lZCBmb3IgdXNlIGluIGVudmlyb25tZW50cyBpbiB3aGljaA0KPiA+ICAgIGRl
bGl2ZXJ5IG9mIElDTVAgbWVzc2FnZXMgdG8gYSBob3N0IGFyZSBub3QgYXNzdXJlZC4gIEluIHRo
aXMgYWxnb3JpdGhtLA0KPiA+ICAgIHRoZSBwcm9wZXINCj4gPiAgICBNVFUgaXMgZGV0ZXJtaW5l
ZCBieSBzdGFydGluZyB3aXRoIHNtYWxsIHBhY2tldHMgYW5kIHByb2Jpbmcgd2l0aA0KPiA+ICAg
IHN1Y2Nlc3NpdmVseSBsYXJnZXIgcGFja2V0cy4gIFRoZSBidWxrIG9mIHRoZSBhbGdvcml0aG0g
aXMNCj4gPiAgICBpbXBsZW1lbnRlZCBhYm92ZSBJUCwgaW4gdGhlIHRyYW5zcG9ydCBsYXllciAo
ZS5nLiwgVENQKSBvciBvdGhlcg0KPiA+ICAgICJQYWNrZXRpemF0aW9uIFByb3RvY29sIiB0aGF0
IGlzIHJlc3BvbnNpYmxlIGZvciBkZXRlcm1pbmluZyBwYWNrZXQNCj4gPiAgICBib3VuZGFyaWVz
Lg0KPiANCj4gVGhhdCBpcyBlc3NlbnRpYWxseSB3aGF0IEkgd2FzIHNheWluZyB3aGVuIEkgc2Fp
ZCB0aGF0Og0KPiANCj4gICAgICJJdCBpcyByZWNvbW1lbmRlZCB0aGF0IElQdjYgbm9kZXMgdGhh
dCBzZW5kIHBhY2tldHMgbGFyZ2VyIHRoYW4gMTI4MCBieXRlcw0KPiAgICAgdG8gSW50ZXJuZXQg
ZGVzdGluYXRpb25zIHVzZSBQTFBNVFVEIHRvIG92ZXJjb21lIHNpbGVudCBmYWlsdXJlcyBvZiBz
dGFuZGFyZA0KPiAgICAgUGF0aCBNVFUgZGlzY292ZXJ5LiINCj4gDQo+IHdoZXJlICJJbnRlcm5l
dCBkZXN0aW5hdGlvbnMiIHJlZmVycyB0byBkZXN0aW5hdGlvbnMgb3V0c2lkZSBvZiB0aGUgc291
cmNlDQo+IG5vZGUncyBhZG1pbmlzdHJhdGl2ZSBkb21haW4gc2luY2Ugc3RhbmRhcmQgUE1UVUQg
cHJlc3VtYWJseSB3b3Jrcw0KPiB3aXRoaW4gYSB3ZWxsLW1hbmFnZWQgYWRtaW5pc3RyYXRpdmUg
ZG9tYWluLg0KPiANCj4gV2UgbmVlZCB0byBhbHNvIG1ha2UgaXQgY2xlYXIgdGhhdCBzdGFuZGFy
ZCBQTVRVRCBwZXIgSUNNUCBtZXNzYWdpbmcNCj4gaXMgdGhlIHByZWZlcnJlZCBvcHRpb24gd2hl
biBpdCBjYW4gYmUgdHJ1c3RlZCAtIG90aGVyd2lzZSwgd2Ugc2hvdWxkIGJlDQo+IGRlcHJlY2F0
aW5nIFJGQzE5ODEgaW5zdGVhZCBvZiBtYWtpbmcgaXQgYSBzdGFuZGFyZC4NCj4gDQo+IFRoYW5r
cyAtIEZyZWQNCj4gZnJlZC5sLnRlbXBsaW5AYm9laW5nLmNvbQ0KPiANCj4gPiBNb3N0IG9mIHRo
ZSBkaWZmcyBzZWVtIHRvIGhhdmUgdG8gZG8gd2l0aCB0aGUgYmlibGlvZ3JhcGh5IG9yIGRldGFp
bHMgb2YgdGhlIGRlZmluaXRpb25zLiBJJ20gbm90IHN1cmUgd2hhdCB0aGUgY2hhbmdlcyBpbiBk
ZWZpbml0aW9ucw0KPiA+IGFjdHVhbGx5IGFkZGVkLCBidXQgc2F3IG5vdGhpbmcgcGVybmljaW91
cyBpbiB0aGF0Lg0KPiA+DQo+ID4gUmVnYXJkaW5nIHRoZSBwb2ludCBGcmVkIFRlbXBsaW4gaGFz
IHJhaXNlZCAoYSBzdHJvbmdlciByZWNvbW1lbmRhdGlvbiBmb3IgUkZDIDQ4MjEpLCBJIHdvcnJ5
IGp1c3QgYSBiaXQgYWJvdXQgdGhlIGxldmVsIG9mDQo+ID4gZXhwZXJpZW5jZSB3ZSBoYXZlIHdp
dGggaXQuIExpa2UgRnJlZCwgSSByZWFsbHkgbGlrZSB0aGUgY29uY2VwdC4gSSBrbm93IGl0IGlz
IGltcGxlbWVudGVkIGluIExpbnV4LCBidXQgaXRzIHVzZSBieSBhbiBhcHBsaWNhdGlvbiBpbg0K
PiA+IG9wdGlvbmFsLCBhbmQgQUZBSUsgbm8gYXBwbGljYXRpb25zIGFjdHVhbGx5IHVzZSBpdC4g
VGhlIGF1dGhvcnMgbWlnaHQgaGF2ZSBtb3JlIHRvIHNheSwgYnV0IEkgZG9uJ3QgdGhpbmsgd2Un
cmUgcmVhZHkgZm9yIGENCj4gPiByZWNvbW1lbmRhdGlvbi4NCj4gLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gSUVU
RiBJUHY2IHdvcmtpbmcgZ3JvdXAgbWFpbGluZyBsaXN0DQo+IGlwdjZAaWV0Zi5vcmcNCj4gQWRt
aW5pc3RyYXRpdmUgUmVxdWVzdHM6IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGlu
Zm8vaXB2Ng0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0K


From nobody Thu Feb  4 10:49:52 2016
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1DD31ACD56 for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 10:49:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.502
X-Spam-Level: 
X-Spam-Status: No, score=-114.502 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TH6lIUGEE6As for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 10:49:50 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85D0F1ACD54 for <ipv6@ietf.org>; Thu,  4 Feb 2016 10:49:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2202; q=dns/txt; s=iport; t=1454611790; x=1455821390; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=xx5W62ENC1ObmQVNZVCSjl4wQo+et87NtIg54RN1sWw=; b=BOKbvgoyRXWkXezUZvphXCE7OUChShEEJgsmhVs8nQP64IFIvShVA0w4 87CAON7zeP+yt09I5YTgFKtnEysEwDLUFuJkotylLwsG6jC6CoEb42VMT 0ARQ77rbtQruuS9QG/Rl3A4/mpTrFbUoWHfmHYOqYGpBwBGYSpXPq8YlS w=;
X-Files: signature.asc : 833
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CyAgCxnLNW/4YNJK1egzqBPwaIVbEBD?= =?us-ascii?q?oFmhg0CgT44FAEBAQEBAQGBCoRBAQEBAwF5BQsCAQgYLjIlAgQOBQ6IBQjBDwE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBAQEBAQEBAQ0Ih38IgkKHXYEPBZZxAYJ9gWOIboFbjRaKb?= =?us-ascii?q?oNRAR4BQ4NkagGHLXwBAQE?=
X-IronPort-AV: E=Sophos;i="5.22,396,1449532800";  d="asc'?scan'208";a="70142132"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 04 Feb 2016 18:49:49 +0000
Received: from XCH-ALN-012.cisco.com (xch-aln-012.cisco.com [173.36.7.22]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id u14InnNT004388 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 4 Feb 2016 18:49:49 GMT
Received: from xch-rcd-013.cisco.com (173.37.102.23) by XCH-ALN-012.cisco.com (173.36.7.22) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 4 Feb 2016 12:49:49 -0600
Received: from xch-rcd-013.cisco.com ([173.37.102.23]) by XCH-RCD-013.cisco.com ([173.37.102.23]) with mapi id 15.00.1104.009; Thu, 4 Feb 2016 12:49:48 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Fred Templin <Fred.L.Templin@boeing.com>
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AQHRX2tTSDlY+6HQH0uuyx8Jsd7k2Q==
Date: Thu, 4 Feb 2016 18:49:48 +0000
Message-ID: <8E7CAC70-9193-43B2-8A47-0C731B5464CA@cisco.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com> <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395DEF3@XCH-BLV-105.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983183395DEF3@XCH-BLV-105.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3112)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.248.194]
Content-Type: multipart/signed; boundary="Apple-Mail=_1C9E0562-2877-41D3-8D48-9BBD5CF8007F"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/LuRVxz1NSdFn2-ZqID28M0ymX7U>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 18:49:52 -0000

--Apple-Mail=_1C9E0562-2877-41D3-8D48-9BBD5CF8007F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Feb 4, 2016, at 10:37 AM, Templin, Fred L =
<Fred.L.Templin@boeing.com> wrote:
>=20
> Your text could be modified by simply adding the word "accurate" as =
follows:
>=20
>  "It defines a method for Packetization Layer Path MTU Discovery =
(PLPMTUD)
>    designed for use in environments in which delivery of accurate ICMP =
messages
>    to a host are not assured."

So you added the word "accurate". Anything else?

My question would be what makes an ICMP "accurate", and how the host =
might or might not determine accuracy. As near as I can tell, RFC 1981 =
says that if a host receives an ICMP Packet Too Big, it should make the =
packet smaller. If the ICMP has been spoofed, unless the spoofer has =
done something really egregious, I don't know how the receiving host =
would know that.

Given that, I don't think the wording change helps.

--Apple-Mail=_1C9E0562-2877-41D3-8D48-9BBD5CF8007F
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIVAwUBVrOdS0ayAOS/EQ8MAQLqyQ//ePG+nN961nd4qgLUuzyMVGxJjRKDsYqS
3+r4eAlBrzdGH6D6R6PKJXbxc4g5XHDg0yeufHm34Lu0W/bn6BOQJ830oyOx/amr
WBo99406Rcz3GGydp72h7IuD8VjmZE5gBxPvf3byxzdLPPgT1NUm68n1Xq/j7LiD
HimTOV5gBWVDC0Hy4W84QU/EoiPdiLmCXT3Y8+KJt7HoOCglUvQyuGpraBUVhHBl
9MQNsisv8QN6y4REEtrbp4zQ2hWd/+KL+uBAQAEh0IX3hyGapruCZXDN/JDKLavV
9a5KzaCPqlZDbvPrjMiRk3ZPO+C5H/LghXaMYR2VG1rxBvDG+jSXmVMoHJilm+q7
RtryTH/7A7b/iofjujNMKDl/ks/eCz/GkFrxC3jg7uOhW2rDoirCH3/68zOLNMdk
n4QpuAmno1faDZkcBfGBkyYw/+DTb5CjdScd624aXn1D3voF7F9OlmHOYFLc1jaR
sLgdDQMVJ3o9dwwolaDiE4QPqnvPsoxgyjpj5tPzJMR1b997st6O5sOuo7bqPqlX
OdmbPcW6/gcpbB/iDYTdDVCQurDyJGJ2Z5DXjA1MNJ37lbOogKj9eW8nGAnJ3dJB
y8YfNngpjhPEy8A/9wp3eZfPrZh6w2zG5H1ztDBken2wXdxToLqu1GeFKklxqjvO
wC7UQ4NhEv4=
=NiHd
-----END PGP SIGNATURE-----

--Apple-Mail=_1C9E0562-2877-41D3-8D48-9BBD5CF8007F--


From nobody Thu Feb  4 10:58:53 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C9EF1ACD7A for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 10:58:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 woq3Mb5Joh7M for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 10:58:49 -0800 (PST)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (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 E67871ACD79 for <ipv6@ietf.org>; Thu,  4 Feb 2016 10:58:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u14IwmCT003989; Thu, 4 Feb 2016 11:58:48 -0700
Received: from XCH-BLV-208.nw.nos.boeing.com (xch-blv-208.nw.nos.boeing.com [10.57.37.5]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u14Iwd3T003531 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 4 Feb 2016 11:58:40 -0700
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-BLV-208.nw.nos.boeing.com ([169.254.8.46]) with mapi id 14.03.0235.001; Thu, 4 Feb 2016 10:58:39 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AQHRX2tT80dfpGCQDUCIhA2edhybgJ8cKO6QgAAMGWCAAIvjAP//enWA
Date: Thu, 4 Feb 2016 18:58:38 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395DFFF@XCH-BLV-105.nw.nos.boeing.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com> <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395DEF3@XCH-BLV-105.nw.nos.boeing.com> <8E7CAC70-9193-43B2-8A47-0C731B5464CA@cisco.com>
In-Reply-To: <8E7CAC70-9193-43B2-8A47-0C731B5464CA@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/yB3kmhZjF6DB8t6WPgAksdTgj4g>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 18:58:51 -0000

Hi Fred,

> -----Original Message-----
> From: Fred Baker (fred) [mailto:fred@cisco.com]
> Sent: Thursday, February 04, 2016 10:50 AM
> To: Templin, Fred L
> Cc: Bob Hinden; 6man WG
> Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
>=20
>=20
> > On Feb 4, 2016, at 10:37 AM, Templin, Fred L <Fred.L.Templin@boeing.com=
> wrote:
> >
> > Your text could be modified by simply adding the word "accurate" as fol=
lows:
> >
> >  "It defines a method for Packetization Layer Path MTU Discovery (PLPMT=
UD)
> >    designed for use in environments in which delivery of accurate ICMP =
messages
> >    to a host are not assured."
>=20
> So you added the word "accurate". Anything else?
>=20
> My question would be what makes an ICMP "accurate", and how the host migh=
t or might not determine accuracy. As near as I can tell,
> RFC 1981 says that if a host receives an ICMP Packet Too Big, it should m=
ake the packet smaller. If the ICMP has been spoofed, unless
> the spoofer has done something really egregious, I don't know how the rec=
eiving host would know that.

ICMP spoofing is exactly the point. But, it is not up to the host to determ=
ine
whether an ICMP is accurate - it is up to the host to determine whether it =
is
in an environment in which delivery of accurate ICMP messages is not assure=
d.

> Given that, I don't think the wording change helps.

Without "accurate", the text does not address failure mode 2).

Thanks - Fred
fred.l.templin@boeing.com


From nobody Thu Feb  4 11:02:51 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A89E51ACDAA for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:02:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 2iiSUxD94iCd for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:02:47 -0800 (PST)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) (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 E07F41ACDA4 for <ipv6@ietf.org>; Thu,  4 Feb 2016 11:02:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u14J2sWV032568; Thu, 4 Feb 2016 11:02:54 -0800
Received: from XCH-PHX-210.sw.nos.boeing.com (xch-phx-210.sw.nos.boeing.com [130.247.25.65]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u14J2lXh032473 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 4 Feb 2016 11:02:48 -0800
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-PHX-210.sw.nos.boeing.com ([169.254.10.63]) with mapi id 14.03.0235.001; Thu, 4 Feb 2016 11:02:40 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AQHRX2tT80dfpGCQDUCIhA2edhybgJ8cKO6QgAAMGWCAAIvjAP//enWAgAACgkA=
Date: Thu, 4 Feb 2016 19:02:39 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395E016@XCH-BLV-105.nw.nos.boeing.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com> <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395DEF3@XCH-BLV-105.nw.nos.boeing.com> <8E7CAC70-9193-43B2-8A47-0C731B5464CA@cisco.com> <2134F8430051B64F815C691A62D983183395DFFF@XCH-BLV-105.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983183395DFFF@XCH-BLV-105.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/fKrXr3DsayxN9Q9s9DFUOoy0tw4>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 19:02:49 -0000

I will make one other change recommendation:

OLD:
It defines a method for Packetization Layer Path MTU Discovery (PLPMTUD)
designed for use in environments in which delivery of accurate ICMP message=
s
to a host are not assured.

NEW:
It defines a method for Packetization Layer Path MTU Discovery (PLPMTUD)
designed for use over paths for which delivery of accurate ICMP messages
to a host are not assured.

Fred
fred.l.templin@boeing.com

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Templin, Fred L
> Sent: Thursday, February 04, 2016 10:59 AM
> To: Fred Baker (fred)
> Cc: 6man WG; Bob Hinden
> Subject: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
>=20
> Hi Fred,
>=20
> > -----Original Message-----
> > From: Fred Baker (fred) [mailto:fred@cisco.com]
> > Sent: Thursday, February 04, 2016 10:50 AM
> > To: Templin, Fred L
> > Cc: Bob Hinden; 6man WG
> > Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
> >
> >
> > > On Feb 4, 2016, at 10:37 AM, Templin, Fred L <Fred.L.Templin@boeing.c=
om> wrote:
> > >
> > > Your text could be modified by simply adding the word "accurate" as f=
ollows:
> > >
> > >  "It defines a method for Packetization Layer Path MTU Discovery (PLP=
MTUD)
> > >    designed for use in environments in which delivery of accurate ICM=
P messages
> > >    to a host are not assured."
> >
> > So you added the word "accurate". Anything else?
> >
> > My question would be what makes an ICMP "accurate", and how the host mi=
ght or might not determine accuracy. As near as I can
> tell,
> > RFC 1981 says that if a host receives an ICMP Packet Too Big, it should=
 make the packet smaller. If the ICMP has been spoofed,
> unless
> > the spoofer has done something really egregious, I don't know how the r=
eceiving host would know that.
>=20
> ICMP spoofing is exactly the point. But, it is not up to the host to dete=
rmine
> whether an ICMP is accurate - it is up to the host to determine whether i=
t is
> in an environment in which delivery of accurate ICMP messages is not assu=
red.
>=20
> > Given that, I don't think the wording change helps.
>=20
> Without "accurate", the text does not address failure mode 2).
>=20
> Thanks - Fred
> fred.l.templin@boeing.com
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------



From nobody Thu Feb  4 11:04:15 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 310701ACDB1 for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:04:14 -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] 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 AgsC0ANylz3D for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:04:13 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB55D1ACDAA for <6man@ietf.org>; Thu,  4 Feb 2016 11:04:12 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 8A7FD206AC2; Thu,  4 Feb 2016 20:04:09 +0100 (CET)
To: "6man@ietf.org" <6man@ietf.org>
From: Fernando Gont <fgont@si6networks.com>
Subject: rfc2460bis and Frag ID generation
X-Enigmail-Draft-Status: N1110
Message-ID: <56B39FB8.4090604@si6networks.com>
Date: Thu, 4 Feb 2016 16:00:08 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/9Cz5ew7RaQelFYDLNaGV8gtrSDU>
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 19:04:14 -0000

Bob/folks,

The current text regarding frag ID generation in rfc2460bis says:

---- cut here ----
      *  "recently" means within the maximum likely lifetime of a
         packet, including transit time from source to destination and
         time spent awaiting reassembly with other fragments of the same
         packet.  However, it is not required that a source node know
         the maximum packet lifetime.  Rather, it is assumed that the
         requirement can be met by maintaining the Identification value
         as a simple, 32-bit, "wrap-around" counter, incremented each
         time a packet must be fragmented.  It is an implementation
         choice whether to maintain a single counter for the node or
         multiple counters, e.g., one for each of the node's possible
         source addresses, or one for each active (source address,
         destination address) combination.
---- cut here ----


I suggest changing the text to:

---- cut here ----
      *  "recently" means within the maximum likely lifetime of a
         packet, including transit time from source to destination and
         time spent awaiting reassembly with other fragments of the same
         packet.  However, it is not required that a source node know
         the maximum packet lifetime.  Rather, it is assumed that the
         requirement can be met by implementing an algorithm that
         results in a low identification reuse frequency. [RFC7739]
         discusses possible algorithms that can meet this requirement
         while avoiding possible security and privacy issues.
---- cut here ----

(where the ref to RFC7739 is obviously informative, rather than normative).

 -- Bottom-line is that rfc2460bis shouldn't suggest algorithms that
have known issues, and it's better to have an informative reference to
RFC7739, where possible algorithms are discussed.

Thoughts?

Thanks!

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





From nobody Thu Feb  4 11:04:25 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B78391ACDBC for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:04:21 -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] 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 AN4UtxpeSi8X for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:04:18 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CB1E1ACDB1 for <ipv6@ietf.org>; Thu,  4 Feb 2016 11:04:18 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id E100D206AC2; Thu,  4 Feb 2016 20:04:14 +0100 (CET)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
To: "Fred Baker (fred)" <fred@cisco.com>, Bob Hinden <bob.hinden@gmail.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B3A062.4090108@si6networks.com>
Date: Thu, 4 Feb 2016 16:02:58 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/607D-6HjohoeVprdAdOxrWkfNyw>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 19:04:21 -0000

On 02/04/2016 01:44 PM, Fred Baker (fred) wrote:
> 
> Regarding the point Fred Templin has raised (a stronger
> recommendation for RFC 4821), I worry just a bit about the level of
> experience we have with it. Like Fred, I really like the concept. I
> know it is implemented in Linux, but its use by an application in
> optional, and AFAIK no applications actually use it. The authors
> might have more to say, but I don't think we're ready for a
> recommendation.

My recollection of discussing this with Linux devs at the time was that
they'd use RFC4821 mostly for blackhole detection than as a complete
ICMP-less PMTUD. The reason? -- convergence time.

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





From nobody Thu Feb  4 11:07:23 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5444E1ACDCA for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:07:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 JPR0DY0Kt2HA for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:07:21 -0800 (PST)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (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 AC3631ACDC6 for <ipv6@ietf.org>; Thu,  4 Feb 2016 11:07:21 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u14J7Khf040092; Thu, 4 Feb 2016 12:07:21 -0700
Received: from XCH-PHX-310.sw.nos.boeing.com (xch-phx-310.sw.nos.boeing.com [130.247.25.169]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u14J7Ex2039656 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 4 Feb 2016 12:07:15 -0700
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-PHX-310.sw.nos.boeing.com ([169.254.10.216]) with mapi id 14.03.0235.001;  Thu, 4 Feb 2016 11:07:15 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>, "Fred Baker (fred)" <fred@cisco.com>, Bob Hinden <bob.hinden@gmail.com>
Subject: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AQHRX36p80dfpGCQDUCIhA2edhybgJ8cPvsA
Date: Thu, 4 Feb 2016 19:07:14 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395E058@XCH-BLV-105.nw.nos.boeing.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com> <56B3A062.4090108@si6networks.com>
In-Reply-To: <56B3A062.4090108@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ZoKMYakCWyHB_vy6jSIA64gjigQ>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 19:07:23 -0000

Hi Fernando,

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Fernando Gont
> Sent: Thursday, February 04, 2016 11:03 AM
> To: Fred Baker (fred); Bob Hinden
> Cc: 6man WG
> Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
>=20
> On 02/04/2016 01:44 PM, Fred Baker (fred) wrote:
> >
> > Regarding the point Fred Templin has raised (a stronger
> > recommendation for RFC 4821), I worry just a bit about the level of
> > experience we have with it. Like Fred, I really like the concept. I
> > know it is implemented in Linux, but its use by an application in
> > optional, and AFAIK no applications actually use it. The authors
> > might have more to say, but I don't think we're ready for a
> > recommendation.
>=20
> My recollection of discussing this with Linux devs at the time was that
> they'd use RFC4821 mostly for blackhole detection than as a complete
> ICMP-less PMTUD. The reason? -- convergence time.

Right, that is why RFC1981(bis) PMTUD should be preferred for use over
paths for which delivery of accurate ICMP messages to a host *is* assured.

Thanks - Fred
fred.l.templin@boeing.com

> Thanks,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>=20
>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------



From nobody Thu Feb  4 11:16:18 2016
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B04391ACD6E for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:16:17 -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 3f8L3d_D_PxH for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:16:15 -0800 (PST)
Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AED731ACD45 for <ipv6@ietf.org>; Thu,  4 Feb 2016 11:16:15 -0800 (PST)
Received: by mail-ig0-x236.google.com with SMTP id rs20so23086030igc.0 for <ipv6@ietf.org>; Thu, 04 Feb 2016 11:16:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=BNf+6Rs5mAFDqcDAqava4QDCps5VSN+Ml7nJbu5C8ys=; b=Clwbw2wF0nWWsnMjbTO9x6m8wdf+b4c1p6mJ8KGfn3hCSUvdGGJHwVgHYnP4yBpFII eaBXgnkcgfwM+kPxzZWbDWtTbGYKpeKMyywNut3da/XqTbLx3TCiTSLn2BSJGOVRPALg TOvwpNJKpCC/nt1GhBdJgF2t3sQz7rT6xRgFE7x5VNEcsb7c/L3/pSJ7GH9qGOPCjtNr TW8BvXm+brg43jTj0N9EoSBT09+sAq+zOJ71ss8As1r9zNJ3Piuqd5v2Px0Amp5vwQfR 13zoq541gQFEH9cm4KMFBQbaBRQ8N+NrCwrFrH7HCSabDgq1qX0bJ3BnQDQ+p/VthcQo KFfw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=BNf+6Rs5mAFDqcDAqava4QDCps5VSN+Ml7nJbu5C8ys=; b=bjO+10f3w38tTr040XeyE/LBzqC1bNHWcpKo1agvvrC8cdtuThj1QyJV1gCDpQ41+4 eIm+o8FJqUGYncQl2wsESlEktJ4RqVI3u9jTr2PTPFqMGHYVj97c2Hclk/uvzzb+dm3y anU2FQfarMoppoQGJaotfAIIdMsFKc1a5Cn/sC5gMkeFK4KGOk6OvraeKgWJx7Q2OkIa soZCGhZV4vytp4dRG9Wcc9j8EF0xnqvL1WxC4IRPSXqe1dZs5gI+woA/XwsexKtqyC/4 SyhBEYi8k6I5Xu80Jh/O3WK3LXamGWeRbmHGQSTyVqCV/06etsMMq1/nTzorr5yKneyy k/pQ==
X-Gm-Message-State: AG10YORZKQpgzxn2qQAoVw47pFxybt9+tG+wTb7FUtfg7AhJw1PvH+2rnZyjm+G5NqchQw==
X-Received: by 10.50.30.6 with SMTP id o6mr10800102igh.57.1454613375099; Thu, 04 Feb 2016 11:16:15 -0800 (PST)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id nq10sm5296914igb.2.2016.02.04.11.16.14 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 04 Feb 2016 11:16:14 -0800 (PST)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_CEE61186-4B8C-4284-8F9E-D5502D68732C"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <2134F8430051B64F815C691A62D983183395DFFF@XCH-BLV-105.nw.nos.boeing.com>
Date: Thu, 4 Feb 2016 11:16:12 -0800
Message-Id: <4E0B0B8D-4AE2-47F2-88F0-20589DB48BE1@gmail.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com> <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395DEF3@XCH-BLV-105.nw.nos.boeing.com> <8E7CAC70-9193-43B2-8A47-0C731B5464CA@cisco.com> <2134F8430051B64F815C691A62D983183395DFFF@XCH-BLV-105.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/h0l5m_TQ82w_xd58CzEYSCsIhZw>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 19:16:17 -0000

--Apple-Mail=_CEE61186-4B8C-4284-8F9E-D5502D68732C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Fred,

> On Feb 4, 2016, at 10:58 AM, Templin, Fred L =
<Fred.L.Templin@boeing.com> wrote:
>=20
> Hi Fred,
>=20
>> -----Original Message-----
>> From: Fred Baker (fred) [mailto:fred@cisco.com]
>> Sent: Thursday, February 04, 2016 10:50 AM
>> To: Templin, Fred L
>> Cc: Bob Hinden; 6man WG
>> Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
>>=20
>>=20
>>> On Feb 4, 2016, at 10:37 AM, Templin, Fred L =
<Fred.L.Templin@boeing.com> wrote:
>>>=20
>>> Your text could be modified by simply adding the word "accurate" as =
follows:
>>>=20
>>> "It defines a method for Packetization Layer Path MTU Discovery =
(PLPMTUD)
>>>   designed for use in environments in which delivery of accurate =
ICMP messages
>>>   to a host are not assured."
>>=20
>> So you added the word "accurate". Anything else?
>>=20
>> My question would be what makes an ICMP "accurate", and how the host =
might or might not determine accuracy. As near as I can tell,
>> RFC 1981 says that if a host receives an ICMP Packet Too Big, it =
should make the packet smaller. If the ICMP has been spoofed, unless
>> the spoofer has done something really egregious, I don't know how the =
receiving host would know that.
>=20
> ICMP spoofing is exactly the point. But, it is not up to the host to =
determine
> whether an ICMP is accurate - it is up to the host to determine =
whether it is
> in an environment in which delivery of accurate ICMP messages is not =
assured.
>=20
>> Given that, I don't think the wording change helps.
>=20
> Without "accurate", the text does not address failure mode 2).

How is a host supposed to know if it is an =E2=80=9Caccurate ICMP =
message=E2=80=9D?

This is starting to read to me like creating a new specification, not =
advancing the one we have now.

Bob

>=20
> Thanks - Fred
> fred.l.templin@boeing.com
>=20


--Apple-Mail=_CEE61186-4B8C-4284-8F9E-D5502D68732C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJWs6N8AAoJEK7rdBF357uoLocIAJyy1igaJDLLUQsOpIv6eJ7S
YN//UDb5FiNnx6Y+91G/teIKGYS9XoaZDP37tuQyrY3PdwrU0lJgcbWU1sEvazck
rfX7SMIabQ/ioZGRiMHN9kIafLL2xgZ0BvzEVEjyarY9UPWHbrhKioMbGiYuUVew
BG5ZZmdrkKtzhbQQ2EWtAQoIKdzL0DeqB5mrT2ABS3Ozv6u1AP19Di8tCNgG9qfD
Rc6jhAqvSdaMOHLqiLy3LKNt4Nh7cLJLVwxwgN/gNnlaVnFy0h4A3qTDwu9sICPK
RyPPb9ZjD2OaUq4ky6Q59QKE4cMnZvdulH/VoH6DiwkdDAK8cbnVd9j3rTZ4ENE=
=mSKI
-----END PGP SIGNATURE-----

--Apple-Mail=_CEE61186-4B8C-4284-8F9E-D5502D68732C--


From nobody Thu Feb  4 11:24:24 2016
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43A981ACE10 for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:24: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 MhHXOUCTRUv3 for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:24:21 -0800 (PST)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8659E1ACE0F for <6man@ietf.org>; Thu,  4 Feb 2016 11:24:21 -0800 (PST)
Received: by mail-io0-x233.google.com with SMTP id g73so104417652ioe.3 for <6man@ietf.org>; Thu, 04 Feb 2016 11:24:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=2U6WQ/fnuuOAWQiKOKYeVVe4rmR3nd88kDvIJWhiayk=; b=kggO3VHmgc5J9ANIP0ChyUprTr5of+hirPFTcQr3hlMwi9tHL3C2Rh7uMJIF89pT29 SZCAwfWZuN8qc1ssDPodv1LcQlDedsXYfVldthrSsw9uSSLRCJ5G1x3bOZb4dKxzQJwo qNhC4IkuKex53rnZQ44vBOY7Mku6TO0g1cdaExuZc1wyfzJqRp49rOXTMfSwM5bkyIDJ DXYVZbhBRzYJ/MROyQRxsFxm5jJtR4weEQYytHW331yMyP80/T2lcKJl40yRmkyOSZsm gST3Dd+615MnHETlNG4EQDlcFBi9mxiEaBJfd4wc/IUjdJ2MBbqXD00FK3Va/Sv66/Sf oAiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=2U6WQ/fnuuOAWQiKOKYeVVe4rmR3nd88kDvIJWhiayk=; b=WZpTJsT8qJZvUSm2wvfA8XNnL3i6F7hrCVsN8wmTh6l21qBLsig7II0e67SDDJMqzX LXS3JVqtJ+VkZFxBGcWPkeKXY3QamuXhZyAcVBfGnZ+LQL4GEFkPyzCSyrvHwcd9DjAi BUWh/RjjoeKaUb0w3GyS0ArvzgVecuQI2cGvTyAvBTpPBZXIHGLlgca6bCFLLs6jCS8O 0//hQ+8IH89I5CtrV0DQ87my4ha2PIjzhQhx/ucI7sLMpuUP4wyPwcsoQYHslhoUBiZt +/PtBiKOqPfV3jJQMk8vjQeQuJxvaPaVGkTcbU+r725eaESOeFYajlNoE9HfqfFVSP3C XKmg==
X-Gm-Message-State: AG10YOSGl1+wfrSA2G8R8V6Z2/+/X82hTrG1o0UhvcJf292EwkCH6AEw7khosP+A1V+y3w==
X-Received: by 10.107.29.19 with SMTP id d19mr12585006iod.24.1454613860982; Thu, 04 Feb 2016 11:24:20 -0800 (PST)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id l11sm5365302iol.17.2016.02.04.11.24.20 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 04 Feb 2016 11:24:20 -0800 (PST)
Subject: Re: rfc2460bis and Frag ID generation
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_4ACEDEB9-8B61-4A28-B772-286AC49370C0"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <56B39FB8.4090604@si6networks.com>
Date: Thu, 4 Feb 2016 11:24:18 -0800
Message-Id: <6EF1C55C-FE16-4019-A6C9-6AD67DA42E84@gmail.com>
References: <56B39FB8.4090604@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/tDOXngsdoo147VWNKNZM6aBUvJU>
Cc: "6man@ietf.org" <6man@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 19:24:23 -0000

--Apple-Mail=_4ACEDEB9-8B61-4A28-B772-286AC49370C0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Fernando,

> On Feb 4, 2016, at 11:00 AM, Fernando Gont <fgont@si6networks.com> =
wrote:
>=20
> Bob/folks,
>=20
> The current text regarding frag ID generation in rfc2460bis says:
>=20
> ---- cut here ----
>      *  "recently" means within the maximum likely lifetime of a
>         packet, including transit time from source to destination and
>         time spent awaiting reassembly with other fragments of the =
same
>         packet.  However, it is not required that a source node know
>         the maximum packet lifetime.  Rather, it is assumed that the
>         requirement can be met by maintaining the Identification value
>         as a simple, 32-bit, "wrap-around" counter, incremented each
>         time a packet must be fragmented.  It is an implementation
>         choice whether to maintain a single counter for the node or
>         multiple counters, e.g., one for each of the node's possible
>         source addresses, or one for each active (source address,
>         destination address) combination.
> ---- cut here ----
>=20
>=20
> I suggest changing the text to:
>=20
> ---- cut here ----
>      *  "recently" means within the maximum likely lifetime of a
>         packet, including transit time from source to destination and
>         time spent awaiting reassembly with other fragments of the =
same
>         packet.  However, it is not required that a source node know
>         the maximum packet lifetime.  Rather, it is assumed that the
>         requirement can be met by implementing an algorithm that
>         results in a low identification reuse frequency. [RFC7739]
>         discusses possible algorithms that can meet this requirement
>         while avoiding possible security and privacy issues.
> ---- cut here ----
>=20
> (where the ref to RFC7739 is obviously informative, rather than =
normative).
>=20
> -- Bottom-line is that rfc2460bis shouldn't suggest algorithms that
> have known issues, and it's better to have an informative reference to
> RFC7739, where possible algorithms are discussed.
>=20
> Thoughts?

I looked at this earlier and also thought the 32-bit wrap around counter =
text was dated.  I am OK with something similar to what you proposed.  =
My read of the current text is that it is describes the 32-bit wrap =
around counter as an example, as opposed the only way to do it, so an =
update like this would be OK.

Other comments?

Thanks,
Bob



--Apple-Mail=_4ACEDEB9-8B61-4A28-B772-286AC49370C0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJWs6ViAAoJEK7rdBF357uoBU0H/jzNcg/50R7KXC059/wMyaP+
ErUhAnrOH5aEylJFnSsW7C2fKTKWet3jAnaHg7Snm0ouOC1OqlmCT3HYLFXIJZqe
EgAeExtjZWbvu476BWC+CkzcYCdRyjQH9lfriw1wUANRkvZedTCdHWbt0rOl0BuP
HMgyP7B1y/WRLvGhSZrbGaiyOZHytF9N6FUZVmG1LeqUxbX0kQsO8a4SBEEgQy+W
C5E3rRs9ZZIofD+Qh+CmZHeYelhn0CzgFrqAmSchWvx3lgTPvD68F6pM/VMlrXa7
ehYkV+uWu5HcOG0uXDW0u9OwlZklJlv8JzOymG0jndimZf247jmQZTvUIOn6JwI=
=bptI
-----END PGP SIGNATURE-----

--Apple-Mail=_4ACEDEB9-8B61-4A28-B772-286AC49370C0--


From nobody Thu Feb  4 11:35:05 2016
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D12661ACE32 for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:35:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R0N55EGLWVUb for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:35:02 -0800 (PST)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D61C1ACE31 for <ipv6@ietf.org>; Thu,  4 Feb 2016 11:35:02 -0800 (PST)
Received: by mail-io0-x229.google.com with SMTP id 9so105008565iom.1 for <ipv6@ietf.org>; Thu, 04 Feb 2016 11:35:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=8aero4dT4kfSLPeyiYO1sMXRhwPv+vOmIHO3md1XBz8=; b=XDftVi46ZccqqkSZSqSZrLZ2Ztd744nOq0rDbUb0rpq/NdXjAcDdRnrs7x1tlCkLYV cYSoOGqC/W4N7r8cIuVFPCTROeCelXXcAv947Ly4zSg27Lk7h5gfbXr3/NH+L2EIvaWN kOgZURM1M3a5bcFNt8nCZyfU5diownlJUWf2IAPp2T9gPr1BXqjlnaTtLiFYg6Ch8t1C MYhow7ywP9Ugzjp5hBCgXGuHxrOz1q+518CUrhdOQTGpyTrb72PhZQD2kPSU4Edguv2r 659CzXdFwaXPB2V26mzR/CmCnJIjKjMFRAuxL/AlArPawqb2/Cb5rm4LwvGTkHs25k7g Ij6Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=8aero4dT4kfSLPeyiYO1sMXRhwPv+vOmIHO3md1XBz8=; b=DNCaDxqflcUQTkzxJHTEBzQy7W2yFx8K5tfC7EMGFl/rZxhjk62ctIQQHtggzghBNJ ZxbfTfmWJg4wE7pCxqCQrwNxJ47k+wyD1YmNl2xB8m9kJtyF2rN28SeRvI4xKuLlFoKN g0rDF7HWaYjJgSpOW8s+DDmx4tV9VxbQdOgVel1s09gBOMlKZMePLwnrQd/s8/ZDbH5T 8bZ0Wwp/fbZAemxMQaq64RoggjKtgYpuVXRGzOVVjocVy4D0QctqikpzWX9bTsNjfzSn J3ELlGpNjqs/Zf8PtyAj5GxvIVJ5o0ZwaidK5D/eyOoUVq6kKUFsNoblj8VENAf1eV6u fqeA==
X-Gm-Message-State: AG10YORenKpRP6D4/DHMpPJxjsJFhvYZcItU/ddHfYBlQC8T0SE0JMj+3N8Yqhe/u33WXFEvwmn9n0/g/p/9ZQ==
MIME-Version: 1.0
X-Received: by 10.107.137.142 with SMTP id t14mr12057253ioi.172.1454614501491;  Thu, 04 Feb 2016 11:35:01 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.169.35 with HTTP; Thu, 4 Feb 2016 11:35:01 -0800 (PST)
In-Reply-To: <2052A806-4D40-4A17-9892-90E39B67C65C@gmail.com>
References: <2052A806-4D40-4A17-9892-90E39B67C65C@gmail.com>
Date: Thu, 4 Feb 2016 11:35:01 -0800
X-Google-Sender-Auth: l5MYVfpFbDD--NBcXBzr5QhHb5A
Message-ID: <CAJE_bqekFsfHPkfLTAOHgdL-MpvwNSV=gB8Cv0x+YrD66JUyMg@mail.gmail.com>
Subject: Re: 6MAN WG Last Call - draft-ietf-6man-multi-homed-host-03.txt
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Bob Hinden <bob.hinden@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/l9c7RlChDGr0VUYGJgicfPdNH_s>
Cc: IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 19:35:04 -0000

At Wed, 3 Feb 2016 14:28:07 -0800,
Bob Hinden <bob.hinden@gmail.com> wrote:

> This message starts a two week 6MAN Working Group Last Call on advancing:
>
>        Title           : Routing packets from hosts in a multi-prefix network
>        Authors         : Fred Baker
>                          Brian Carpenter
>        Filename        : draft-ietf-6man-multi-homed-host-03.txt
>        Pages           : 13
>        Date            : 2015-12-16
>
>    https://tools.ietf.org/html/draft-ietf-6man-multi-homed-host-03
>
> as a Proposed Standard.  Substantive comments and statements of
> support for publishing this document should be directed to the
> mailing list.  Editorial suggestions can be sent to the authors.
> This last call will end on 17 February 2016.

I think this version is basically good enough for publication.

I have some comments on the latest version.  I don't think they are
blocking issues but may be better addressed before sending it to the
IESG.

- Some of my previous comments seem to be still open.  Although I
  already stated I wouldn't insist, it's not clear whether they were
  rejected as a result or just overlooked, so I'm re-raising them
  here: https://mailarchive.ietf.org/arch/msg/ipv6/42QPrrvdShflkz06tn3vdw33iEo
  The seeming open points are:
  + whether to move the host-model discussion to an appendix
  + about the term "addressless"

- Section 3.1

   As described in [RFC4191] and [RFC4861], a Router Advertisement may
   contain zero or more Prefix information Options (PIOs), zero or more
   Route Information Options (RIOs), or a Default Router List.

  I'm not sure if I can understand the "or a Default Router List"
  part.  If it means 'Router Advertisement may contain...a Default
  Router List', it doesn't make sense since an RA (or any of its
  options) doesn't contain such a list (Default Router List is
  something that a host maintains based on the content of RA).

- Section 3.1: likewise, the use of 'a default router list' in the
  following sentence is confusing, too:

   [...]  In a multi-
   homed network implementing source/destination routing, the
   interpretation of a default router list or an RIO has to be modified
   with the words "if the source address is in one of the prefixes I
   advertise in a PIO".

- Section 3.1

   Bob's first hop routers are Bob-A (to upstream ISP A advertising
   prefix A') and Bob-B (to upstream network B and advertising prefix
   B').

  I'd suggest something like PA and PB instead of A' and B'.  It may
  be a matter of taste, but to me X and X' refer to different
  instances of the same kind of concept (like both are addresses or
  both are prefixes), so the current notation is confusing.

- Section 3.4

   There is potential for adverse interaction with any off-link Redirect
   (Redirect for a GUA destination that is not on-link) message sent by

  Is there any particular intent about why we specially say "GUA" here
  instead of, e.g., just "a global destination"?  For example, does it
  intend to exclude ULAs?  If so, why?  In case of ULAs, while the
  proposed host behavior may be less critical with ULAs in practice, I
  don't see any technical reason why we can't use it for ULAs.

--
JINMEI, Tatuya


From nobody Thu Feb  4 11:37:05 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56E191ACE31 for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:37:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 hmiGs7EkzqtY for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:37:03 -0800 (PST)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) (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 082CE1ACE27 for <ipv6@ietf.org>; Thu,  4 Feb 2016 11:37:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u14Jb87a009033; Thu, 4 Feb 2016 11:37:08 -0800
Received: from XCH-BLV-202.nw.nos.boeing.com (xch-blv-202.nw.nos.boeing.com [10.57.37.69]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u14Jb0tW008975 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 4 Feb 2016 11:37:00 -0800
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-BLV-202.nw.nos.boeing.com ([169.254.2.106]) with mapi id 14.03.0235.001; Thu, 4 Feb 2016 11:36:54 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AQHRX2tT80dfpGCQDUCIhA2edhybgJ8cKO6QgAAMGWCAAIvjAP//enWAgACM6wD//34U0A==
Date: Thu, 4 Feb 2016 19:36:53 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395E0F9@XCH-BLV-105.nw.nos.boeing.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com> <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395DEF3@XCH-BLV-105.nw.nos.boeing.com> <8E7CAC70-9193-43B2-8A47-0C731B5464CA@cisco.com> <2134F8430051B64F815C691A62D983183395DFFF@XCH-BLV-105.nw.nos.boeing.com> <4E0B0B8D-4AE2-47F2-88F0-20589DB48BE1@gmail.com>
In-Reply-To: <4E0B0B8D-4AE2-47F2-88F0-20589DB48BE1@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/hVWLVSiFweKgYD5iqF_A7B09sic>
Cc: IPv6 List <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 19:37:04 -0000

SGkgQm9iLA0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IEJvYiBIaW5k
ZW4gW21haWx0bzpib2IuaGluZGVuQGdtYWlsLmNvbV0NCj4gU2VudDogVGh1cnNkYXksIEZlYnJ1
YXJ5IDA0LCAyMDE2IDExOjE2IEFNDQo+IFRvOiBUZW1wbGluLCBGcmVkIEwNCj4gQ2M6IEJvYiBI
aW5kZW47IEZyZWQgQmFrZXIgKGZyZWQpOyBJUHY2IExpc3QNCj4gU3ViamVjdDogUmU6IDZNQU46
IEFkb3B0aW9uIGNhbGwgb24gZHJhZnQtaGluZGVuLTZtYW4tcmZjMTk4MWJpcy0wMQ0KPiANCj4g
RnJlZCwNCj4gDQo+ID4gT24gRmViIDQsIDIwMTYsIGF0IDEwOjU4IEFNLCBUZW1wbGluLCBGcmVk
IEwgPEZyZWQuTC5UZW1wbGluQGJvZWluZy5jb20+IHdyb3RlOg0KPiA+DQo+ID4gSGkgRnJlZCwN
Cj4gPg0KPiA+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+PiBGcm9tOiBGcmVkIEJh
a2VyIChmcmVkKSBbbWFpbHRvOmZyZWRAY2lzY28uY29tXQ0KPiA+PiBTZW50OiBUaHVyc2RheSwg
RmVicnVhcnkgMDQsIDIwMTYgMTA6NTAgQU0NCj4gPj4gVG86IFRlbXBsaW4sIEZyZWQgTA0KPiA+
PiBDYzogQm9iIEhpbmRlbjsgNm1hbiBXRw0KPiA+PiBTdWJqZWN0OiBSZTogNk1BTjogQWRvcHRp
b24gY2FsbCBvbiBkcmFmdC1oaW5kZW4tNm1hbi1yZmMxOTgxYmlzLTAxDQo+ID4+DQo+ID4+DQo+
ID4+PiBPbiBGZWIgNCwgMjAxNiwgYXQgMTA6MzcgQU0sIFRlbXBsaW4sIEZyZWQgTCA8RnJlZC5M
LlRlbXBsaW5AYm9laW5nLmNvbT4gd3JvdGU6DQo+ID4+Pg0KPiA+Pj4gWW91ciB0ZXh0IGNvdWxk
IGJlIG1vZGlmaWVkIGJ5IHNpbXBseSBhZGRpbmcgdGhlIHdvcmQgImFjY3VyYXRlIiBhcyBmb2xs
b3dzOg0KPiA+Pj4NCj4gPj4+ICJJdCBkZWZpbmVzIGEgbWV0aG9kIGZvciBQYWNrZXRpemF0aW9u
IExheWVyIFBhdGggTVRVIERpc2NvdmVyeSAoUExQTVRVRCkNCj4gPj4+ICAgZGVzaWduZWQgZm9y
IHVzZSBpbiBlbnZpcm9ubWVudHMgaW4gd2hpY2ggZGVsaXZlcnkgb2YgYWNjdXJhdGUgSUNNUCBt
ZXNzYWdlcw0KPiA+Pj4gICB0byBhIGhvc3QgYXJlIG5vdCBhc3N1cmVkLiINCj4gPj4NCj4gPj4g
U28geW91IGFkZGVkIHRoZSB3b3JkICJhY2N1cmF0ZSIuIEFueXRoaW5nIGVsc2U/DQo+ID4+DQo+
ID4+IE15IHF1ZXN0aW9uIHdvdWxkIGJlIHdoYXQgbWFrZXMgYW4gSUNNUCAiYWNjdXJhdGUiLCBh
bmQgaG93IHRoZSBob3N0IG1pZ2h0IG9yIG1pZ2h0IG5vdCBkZXRlcm1pbmUgYWNjdXJhY3kuIEFz
IG5lYXIgYXMgSSBjYW4NCj4gdGVsbCwNCj4gPj4gUkZDIDE5ODEgc2F5cyB0aGF0IGlmIGEgaG9z
dCByZWNlaXZlcyBhbiBJQ01QIFBhY2tldCBUb28gQmlnLCBpdCBzaG91bGQgbWFrZSB0aGUgcGFj
a2V0IHNtYWxsZXIuIElmIHRoZSBJQ01QIGhhcyBiZWVuIHNwb29mZWQsDQo+IHVubGVzcw0KPiA+
PiB0aGUgc3Bvb2ZlciBoYXMgZG9uZSBzb21ldGhpbmcgcmVhbGx5IGVncmVnaW91cywgSSBkb24n
dCBrbm93IGhvdyB0aGUgcmVjZWl2aW5nIGhvc3Qgd291bGQga25vdyB0aGF0Lg0KPiA+DQo+ID4g
SUNNUCBzcG9vZmluZyBpcyBleGFjdGx5IHRoZSBwb2ludC4gQnV0LCBpdCBpcyBub3QgdXAgdG8g
dGhlIGhvc3QgdG8gZGV0ZXJtaW5lDQo+ID4gd2hldGhlciBhbiBJQ01QIGlzIGFjY3VyYXRlIC0g
aXQgaXMgdXAgdG8gdGhlIGhvc3QgdG8gZGV0ZXJtaW5lIHdoZXRoZXIgaXQgaXMNCj4gPiBpbiBh
biBlbnZpcm9ubWVudCBpbiB3aGljaCBkZWxpdmVyeSBvZiBhY2N1cmF0ZSBJQ01QIG1lc3NhZ2Vz
IGlzIG5vdCBhc3N1cmVkLg0KPiA+DQo+ID4+IEdpdmVuIHRoYXQsIEkgZG9uJ3QgdGhpbmsgdGhl
IHdvcmRpbmcgY2hhbmdlIGhlbHBzLg0KPiA+DQo+ID4gV2l0aG91dCAiYWNjdXJhdGUiLCB0aGUg
dGV4dCBkb2VzIG5vdCBhZGRyZXNzIGZhaWx1cmUgbW9kZSAyKS4NCj4gDQo+IEhvdyBpcyBhIGhv
c3Qgc3VwcG9zZWQgdG8ga25vdyBpZiBpdCBpcyBhbiDigJxhY2N1cmF0ZSBJQ01QIG1lc3NhZ2Xi
gJ0/DQoNClJlcGVhdGluZyB3aGF0IEkgc2FpZCB3aXRoIGEgbmVjZXNzYXJ5IGNvcnJlY3Rpb246
DQoNCiAgIkJ1dCwgaXQgaXMgbm90IHVwIHRvIHRoZSBob3N0IHRvIGRldGVybWluZQ0KICAgIHdo
ZXRoZXIgYW4gSUNNUCBpcyBhY2N1cmF0ZSAtIGl0IGlzIHVwIHRvIHRoZSBob3N0IHRvIGRldGVy
bWluZSB3aGV0aGVyIGl0IGlzDQogICAgdXNpbmcgYSBwYXRoIGZvciB3aGljaCBkZWxpdmVyeSBv
ZiBhY2N1cmF0ZSBJQ01QIG1lc3NhZ2UgaXMgbm90IGFzc3VyZWQuIg0KDQo+IFRoaXMgaXMgc3Rh
cnRpbmcgdG8gcmVhZCB0byBtZSBsaWtlIGNyZWF0aW5nIGEgbmV3IHNwZWNpZmljYXRpb24sIG5v
dCBhZHZhbmNpbmcgdGhlIG9uZSB3ZSBoYXZlIG5vdy4NCg0KTm90IGF0IGFsbC4gWW91IHdlcmUg
b25seSB0b28gaGFwcHkgdG8gYWNjZXB0IEZyZWQgQmFrZXIncyBzdWdnZXN0aW9uOyBJDQpoYXZl
IHNpbXBseSBtb2RpZmllZCB0aGUgYXNwZWN0cyBvZiBoaXMgc3VnZ2VzdGlvbiB0aGF0IHdlcmUg
bGFja2luZw0KYW5kL29yIGluYWNjdXJhdGUuDQoNClRoYW5rcyAtIEZyZWQNCmZyZWQubC50ZW1w
bGluQGJvZWluZy5jb20NCg0KPiBCb2INCg==


From nobody Thu Feb  4 11:37:22 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55E431ACD39 for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:37:21 -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] 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 Bc0VcsWTWpux for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:37:19 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D68F1ACE38 for <6man@ietf.org>; Thu,  4 Feb 2016 11:37:19 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id B5C34206ABF; Thu,  4 Feb 2016 20:37:16 +0100 (CET)
Subject: Re: rfc2460bis and Frag ID generation
To: Bob Hinden <bob.hinden@gmail.com>
References: <56B39FB8.4090604@si6networks.com> <6EF1C55C-FE16-4019-A6C9-6AD67DA42E84@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B3A84C.3090307@si6networks.com>
Date: Thu, 4 Feb 2016 16:36:44 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <6EF1C55C-FE16-4019-A6C9-6AD67DA42E84@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/dugzm_8vQRrorjDkvL3M8Tf5_NU>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 19:37:21 -0000

Hi, Bob,

On 02/04/2016 04:24 PM, Bob Hinden wrote:
> Fernando,
> 
>> On Feb 4, 2016, at 11:00 AM, Fernando Gont <fgont@si6networks.com>
>> wrote:
>> 
>> Bob/folks,
>> 
>> The current text regarding frag ID generation in rfc2460bis says:
>> 
>> ---- cut here ---- *  "recently" means within the maximum likely
>> lifetime of a packet, including transit time from source to
>> destination and time spent awaiting reassembly with other fragments
>> of the same packet.  However, it is not required that a source node
>> know the maximum packet lifetime.  Rather, it is assumed that the 
>> requirement can be met by maintaining the Identification value as a
>> simple, 32-bit, "wrap-around" counter, incremented each time a
>> packet must be fragmented.  It is an implementation choice whether
>> to maintain a single counter for the node or multiple counters,
>> e.g., one for each of the node's possible source addresses, or one
>> for each active (source address, destination address) combination. 
>> ---- cut here ----
>> 
>> 
>> I suggest changing the text to:
>> 
>> ---- cut here ---- *  "recently" means within the maximum likely
>> lifetime of a packet, including transit time from source to
>> destination and time spent awaiting reassembly with other fragments
>> of the same packet.  However, it is not required that a source node
>> know the maximum packet lifetime.  Rather, it is assumed that the 
>> requirement can be met by implementing an algorithm that results in
>> a low identification reuse frequency. [RFC7739] discusses possible
>> algorithms that can meet this requirement while avoiding possible
>> security and privacy issues. ---- cut here ----
>> 
>> (where the ref to RFC7739 is obviously informative, rather than
>> normative).
>> 
>> -- Bottom-line is that rfc2460bis shouldn't suggest algorithms
>> that have known issues, and it's better to have an informative
>> reference to RFC7739, where possible algorithms are discussed.
>> 
>> Thoughts?
> 
> I looked at this earlier and also thought the 32-bit wrap around
> counter text was dated.  I am OK with something similar to what you
> proposed.  My read of the current text is that it is describes the
> 32-bit wrap around counter as an example, as opposed the only way to
> do it, so an update like this would be OK.

That's my take as well. So this change would essentially just remove the
current example, and point to RFC7739 for examples, where different
algorithms and pros/cons of each of them are analyzed.

Thanks!

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





From nobody Thu Feb  4 11:40:31 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1C0B1ACE3C for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:40:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 ppdhocazBP2Y for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:40:29 -0800 (PST)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) (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 3BB441ACED6 for <ipv6@ietf.org>; Thu,  4 Feb 2016 11:39:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u14JdxU1004772; Thu, 4 Feb 2016 11:39:59 -0800
Received: from XCH-BLV-506.nw.nos.boeing.com (xch-blv-506.nw.nos.boeing.com [130.247.25.196]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u14Jdno4004521 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 4 Feb 2016 11:39:49 -0800
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-BLV-506.nw.nos.boeing.com ([169.254.6.100]) with mapi id 14.03.0235.001; Thu, 4 Feb 2016 11:39:42 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: RFC1191(bis)? RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: RFC1191(bis)? RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AdFfg3+BLtBoX934QD+GvVlTF9JUNw==
Date: Thu, 4 Feb 2016 19:39:41 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395E134@XCH-BLV-105.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/qq5WMh0ThLqrTlD8fcLmfiIYYXY>
Cc: IPv6 List <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 19:40:30 -0000

V2hpbGUgd2UgYXJlIGF0IGl0LCBzaG91bGQgd2UgYWxzbyB3b3JrIG9uIFJGQzExOTEoYmlzKT8g
WWVzLCBJIGtub3cgdGhhdA0KdGhhdCBpcyBJUHY0LCBidXQgaXQgaXMgdXNlZCBpbiBtZWNoYW5p
c21zIHN1Y2ggYXMgSVB2Ni1vdmVyLUlQdjQgdHVubmVscy4NCg0KQUZBSUNULCB0aGUgZXhhY3Qg
c2FtZSBlZGl0cyB0aGF0IGFyZSBiZWluZyBhcHBsaWVkIHRvIFJGQzE5ODEoYmlzKQ0Kd291bGQg
YXBwbHkgZXF1YWxseSB0byBSRkMxMTkxKGJpcykuDQoNClRoYW5rcyAtIEZyZWQNCmZyZWQubC50
ZW1wbGluQGJvZWluZy5jb20NCg==


From nobody Thu Feb  4 11:48:57 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E3191ACE98 for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:48:56 -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] 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 v8Zrh-ny4HVX for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:48:55 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 27C2F1ACE53 for <6man@ietf.org>; Thu,  4 Feb 2016 11:48:55 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 7253A206ABF; Thu,  4 Feb 2016 20:48:47 +0100 (CET)
Subject: Re: rfc2460bis and Frag ID generation
To: Bob Hinden <bob.hinden@gmail.com>
References: <56B39FB8.4090604@si6networks.com> <6EF1C55C-FE16-4019-A6C9-6AD67DA42E84@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <56B3A990.9070000@si6networks.com>
Date: Thu, 4 Feb 2016 16:42:08 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <6EF1C55C-FE16-4019-A6C9-6AD67DA42E84@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/3QxxesW4OYvG_cX--nTOuuAOcvk>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 19:48:56 -0000

On 02/04/2016 04:24 PM, Bob Hinden wrote:
[....]
>> 
>> Thoughts?
> 
> I looked at this earlier and also thought the 32-bit wrap around
> counter text was dated.  I am OK with something similar to what you
> proposed.  My read of the current text is that it is describes the
> 32-bit wrap around counter as an example, as opposed the only way to
> do it, so an update like this would be OK.
> 
> Other comments?

BTW, please let me know if the current version will not be revised in
less than, say, 1 week, and I could do a full review....

Thanks!

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





From nobody Thu Feb  4 11:50:37 2016
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD961ACEAD for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:50:36 -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 LlIH2W4EsRc9 for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 11:50:34 -0800 (PST)
Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 786811ACEB1 for <ipv6@ietf.org>; Thu,  4 Feb 2016 11:50:34 -0800 (PST)
Received: by mail-ig0-x236.google.com with SMTP id 5so68510429igt.0 for <ipv6@ietf.org>; Thu, 04 Feb 2016 11:50:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=cj4GSaj9al4o+BF1wh22ThWF/btvfKnTCCLZ3LKdtPA=; b=b0TARBMXLq93sIta+YFIthDvdjthgquGbt+iCKtaQK8AuO9UqvDld+tdjhvTqD7SiQ PBPU28OpO3CyJhicFMgqQblqaUkNCOWpv5kGEU4EPX+kgfIfPwXbgTfGy1kOkEpvQ8DA TfNsuT9CvxQOh1B/szwBEy3L9+AW9cAnFCZbwEZGhjw0SA0UGdwJW1utZu+0e0KhUJNU njJLyoQXEJ8HZGkID9wQ1wd7q+t18XEG8yoi8uFmDZtXL4otEKAR21Ltkt2QRpJob6u5 WDYzan8MkfUVul0J2sg+850kuSeGafV1uljXm1lvYS+EEbI/iA2qP0QlnHsBZlfMcbnK uz/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=cj4GSaj9al4o+BF1wh22ThWF/btvfKnTCCLZ3LKdtPA=; b=YCP99jjDJhnrSbHk/KfuoMWa8CZDeiJeXAfVAwTUP9cHUmzO//sYwWiVLwHcrGC1SP Ra0uyijgPu8czw2MKt+U3f6W3P+qX/QbZk7BAfoqzifajrhMLwozuixq/6Xwb7Q6K8HZ H9HeIiaTGveTjMZGEHougufCpF/Gi255yWJkSqv3mkdeXPPM240Oj5Kmxhgv3uo9iQ06 2gb+rVLrdF6tU2VN7qtxJz8Zdt3+LYFh7ZRMnONyTjxu/uCy4Mf6o9GFCU3Y9KCCs97N Bx7bbNq/7w3nneDe8kBpJsd66+llstZgTb+9xuaLfS8PlcwxIBLG4xo2QGIhnVls8efw WLxQ==
X-Gm-Message-State: AG10YOQdih7so1ECMvV0e57eWiws9quwSh/6XSDZGnNYbgOtVztnwSN4Ri1fBNopNqVXEg==
X-Received: by 10.50.50.73 with SMTP id a9mr10779245igo.72.1454615433971; Thu, 04 Feb 2016 11:50:33 -0800 (PST)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id oo7sm10497690igb.5.2016.02.04.11.50.32 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 04 Feb 2016 11:50:32 -0800 (PST)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_D7E9684E-A59A-4E56-B416-224E4427DBB3"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <2134F8430051B64F815C691A62D983183395E0F9@XCH-BLV-105.nw.nos.boeing.com>
Date: Thu, 4 Feb 2016 11:50:30 -0800
Message-Id: <DBB48545-B7B4-4E80-80FF-FAD84E1BDE78@gmail.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com> <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395DEF3@XCH-BLV-105.nw.nos.boeing.com> <8E7CAC70-9193-43B2-8A47-0C731B5464CA@cisco.com> <2134F8430051B64F815C691A62D983183395DFFF@XCH-BLV-105.nw.nos.boeing.com> <4E0B0B8D-4AE2-47F2-88F0-20589DB48BE1@gmail.com> <2134F8430051B64F815C691A62D983183395E0F9@XCH-BLV-105.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/TWNPMMyqMtG3-x2mwO67VwM0LVc>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 19:50:36 -0000

--Apple-Mail=_D7E9684E-A59A-4E56-B416-224E4427DBB3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Fred,

> On Feb 4, 2016, at 11:36 AM, Templin, Fred L =
<Fred.L.Templin@boeing.com> wrote:
>=20
> Hi Bob,
>=20
>> -----Original Message-----
>> From: Bob Hinden [mailto:bob.hinden@gmail.com]
>> Sent: Thursday, February 04, 2016 11:16 AM
>> To: Templin, Fred L
>> Cc: Bob Hinden; Fred Baker (fred); IPv6 List
>> Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
>>=20
>> Fred,
>>=20
>>> On Feb 4, 2016, at 10:58 AM, Templin, Fred L =
<Fred.L.Templin@boeing.com> wrote:
>>>=20
>>> Hi Fred,
>>>=20
>>>> -----Original Message-----
>>>> From: Fred Baker (fred) [mailto:fred@cisco.com]
>>>> Sent: Thursday, February 04, 2016 10:50 AM
>>>> To: Templin, Fred L
>>>> Cc: Bob Hinden; 6man WG
>>>> Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
>>>>=20
>>>>=20
>>>>> On Feb 4, 2016, at 10:37 AM, Templin, Fred L =
<Fred.L.Templin@boeing.com> wrote:
>>>>>=20
>>>>> Your text could be modified by simply adding the word "accurate" =
as follows:
>>>>>=20
>>>>> "It defines a method for Packetization Layer Path MTU Discovery =
(PLPMTUD)
>>>>>  designed for use in environments in which delivery of accurate =
ICMP messages
>>>>>  to a host are not assured."
>>>>=20
>>>> So you added the word "accurate". Anything else?
>>>>=20
>>>> My question would be what makes an ICMP "accurate", and how the =
host might or might not determine accuracy. As near as I can
>> tell,
>>>> RFC 1981 says that if a host receives an ICMP Packet Too Big, it =
should make the packet smaller. If the ICMP has been spoofed,
>> unless
>>>> the spoofer has done something really egregious, I don't know how =
the receiving host would know that.
>>>=20
>>> ICMP spoofing is exactly the point. But, it is not up to the host to =
determine
>>> whether an ICMP is accurate - it is up to the host to determine =
whether it is
>>> in an environment in which delivery of accurate ICMP messages is not =
assured.
>>>=20
>>>> Given that, I don't think the wording change helps.
>>>=20
>>> Without "accurate", the text does not address failure mode 2).
>>=20
>> How is a host supposed to know if it is an =E2=80=9Caccurate ICMP =
message=E2=80=9D?
>=20
> Repeating what I said with a necessary correction:
>=20
>  "But, it is not up to the host to determine
>    whether an ICMP is accurate - it is up to the host to determine =
whether it is
>    using a path for which delivery of accurate ICMP message is not =
assured.=E2=80=9D


Same question.  How is the host supposed determine "it is using a path =
for which delivery of accurate ICMP message is not assured=E2=80=9D?  =
Don=E2=80=99t you think that if are going to ask the host to validate =
the ICMP PTB messages, we need to provide some algorithm or approach to =
do that.

>=20
>> This is starting to read to me like creating a new specification, not =
advancing the one we have now.
>=20
> Not at all. You were only too happy to accept Fred Baker's suggestion; =
I
> have simply modified the aspects of his suggestion that were lacking
> and/or inaccurate.
>=20

Fred Baker=E2=80=99s change was to replace"

  (PLPMTUD).  In the absence of ICMP messages, the proper

with:

  (PLPMTUD) designed for use in environments in which
  delivery of ICMP messages to a host are not assured.  In this =
algorithm,
  the proper

Bob


--Apple-Mail=_D7E9684E-A59A-4E56-B416-224E4427DBB3
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJWs6uHAAoJEK7rdBF357uotC8H/1Ra36A/oIzv7JLjg0xV0VAg
j17FvXSWT6FOllQywS2Zk4x+rdGV3mBJaOzU+lNd8n04c3i0lWIK2BQXMO4TVetV
4SiV1jf0pISNUrhIO3VsF1w+Wf9SZVatn//lIO/PFWXs8PhB1+Nf1GD5QeRJsVZK
ghgTytBgFHO/pElb466gOxYTOFl8om87S4HowUiIDj7dEyrNY9AAwubA5PWSQ1eD
gC6Ts5gTxiqR8FK7V9Z2HPH1suhVHXiq8SqZsDvNctqDYTNyJzR+uRpAczfDCmqP
5y2qH2kRkV9xirEtRoTl1GeNhouwkDe0OlhYFUsiQUvHYiHUyZ/igTp1sbDBaKs=
=yiWR
-----END PGP SIGNATURE-----

--Apple-Mail=_D7E9684E-A59A-4E56-B416-224E4427DBB3--


From nobody Thu Feb  4 12:01:15 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EA3F1AD068 for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 12:01:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 E4Q4__Xqdf0e for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 12:01:10 -0800 (PST)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) (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 A42CC1AD0EA for <ipv6@ietf.org>; Thu,  4 Feb 2016 12:00:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u14K0sXX020670; Thu, 4 Feb 2016 12:00:54 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com (xch-blv-504.nw.nos.boeing.com [130.247.25.194]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u14K0iaL020412 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 4 Feb 2016 12:00:44 -0800
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-BLV-504.nw.nos.boeing.com ([169.254.4.52]) with mapi id 14.03.0235.001; Thu, 4 Feb 2016 12:00:37 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AQHRX2tT80dfpGCQDUCIhA2edhybgJ8cKO6QgAAMGWCAAIvjAP//enWAgACM6wD//34U0IAAi4EA//97I8A=
Date: Thu, 4 Feb 2016 20:00:37 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395E18D@XCH-BLV-105.nw.nos.boeing.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com> <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395DEF3@XCH-BLV-105.nw.nos.boeing.com> <8E7CAC70-9193-43B2-8A47-0C731B5464CA@cisco.com> <2134F8430051B64F815C691A62D983183395DFFF@XCH-BLV-105.nw.nos.boeing.com> <4E0B0B8D-4AE2-47F2-88F0-20589DB48BE1@gmail.com> <2134F8430051B64F815C691A62D983183395E0F9@XCH-BLV-105.nw.nos.boeing.com> <DBB48545-B7B4-4E80-80FF-FAD84E1BDE78@gmail.com>
In-Reply-To: <DBB48545-B7B4-4E80-80FF-FAD84E1BDE78@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/sJuMwSz2zbVCD-VBBtZE6UWoK8A>
Cc: IPv6 List <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 20:01:14 -0000

SGkgQm9iLA0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IEJvYiBIaW5k
ZW4gW21haWx0bzpib2IuaGluZGVuQGdtYWlsLmNvbV0NCj4gU2VudDogVGh1cnNkYXksIEZlYnJ1
YXJ5IDA0LCAyMDE2IDExOjUxIEFNDQo+IFRvOiBUZW1wbGluLCBGcmVkIEwNCj4gQ2M6IEJvYiBI
aW5kZW47IEZyZWQgQmFrZXIgKGZyZWQpOyBJUHY2IExpc3QNCj4gU3ViamVjdDogUmU6IDZNQU46
IEFkb3B0aW9uIGNhbGwgb24gZHJhZnQtaGluZGVuLTZtYW4tcmZjMTk4MWJpcy0wMQ0KPiANCj4g
RnJlZCwNCj4gDQo+ID4gT24gRmViIDQsIDIwMTYsIGF0IDExOjM2IEFNLCBUZW1wbGluLCBGcmVk
IEwgPEZyZWQuTC5UZW1wbGluQGJvZWluZy5jb20+IHdyb3RlOg0KPiA+DQo+ID4gSGkgQm9iLA0K
PiA+DQo+ID4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4+IEZyb206IEJvYiBIaW5k
ZW4gW21haWx0bzpib2IuaGluZGVuQGdtYWlsLmNvbV0NCj4gPj4gU2VudDogVGh1cnNkYXksIEZl
YnJ1YXJ5IDA0LCAyMDE2IDExOjE2IEFNDQo+ID4+IFRvOiBUZW1wbGluLCBGcmVkIEwNCj4gPj4g
Q2M6IEJvYiBIaW5kZW47IEZyZWQgQmFrZXIgKGZyZWQpOyBJUHY2IExpc3QNCj4gPj4gU3ViamVj
dDogUmU6IDZNQU46IEFkb3B0aW9uIGNhbGwgb24gZHJhZnQtaGluZGVuLTZtYW4tcmZjMTk4MWJp
cy0wMQ0KPiA+Pg0KPiA+PiBGcmVkLA0KPiA+Pg0KPiA+Pj4gT24gRmViIDQsIDIwMTYsIGF0IDEw
OjU4IEFNLCBUZW1wbGluLCBGcmVkIEwgPEZyZWQuTC5UZW1wbGluQGJvZWluZy5jb20+IHdyb3Rl
Og0KPiA+Pj4NCj4gPj4+IEhpIEZyZWQsDQo+ID4+Pg0KPiA+Pj4+IC0tLS0tT3JpZ2luYWwgTWVz
c2FnZS0tLS0tDQo+ID4+Pj4gRnJvbTogRnJlZCBCYWtlciAoZnJlZCkgW21haWx0bzpmcmVkQGNp
c2NvLmNvbV0NCj4gPj4+PiBTZW50OiBUaHVyc2RheSwgRmVicnVhcnkgMDQsIDIwMTYgMTA6NTAg
QU0NCj4gPj4+PiBUbzogVGVtcGxpbiwgRnJlZCBMDQo+ID4+Pj4gQ2M6IEJvYiBIaW5kZW47IDZt
YW4gV0cNCj4gPj4+PiBTdWJqZWN0OiBSZTogNk1BTjogQWRvcHRpb24gY2FsbCBvbiBkcmFmdC1o
aW5kZW4tNm1hbi1yZmMxOTgxYmlzLTAxDQo+ID4+Pj4NCj4gPj4+Pg0KPiA+Pj4+PiBPbiBGZWIg
NCwgMjAxNiwgYXQgMTA6MzcgQU0sIFRlbXBsaW4sIEZyZWQgTCA8RnJlZC5MLlRlbXBsaW5AYm9l
aW5nLmNvbT4gd3JvdGU6DQo+ID4+Pj4+DQo+ID4+Pj4+IFlvdXIgdGV4dCBjb3VsZCBiZSBtb2Rp
ZmllZCBieSBzaW1wbHkgYWRkaW5nIHRoZSB3b3JkICJhY2N1cmF0ZSIgYXMgZm9sbG93czoNCj4g
Pj4+Pj4NCj4gPj4+Pj4gIkl0IGRlZmluZXMgYSBtZXRob2QgZm9yIFBhY2tldGl6YXRpb24gTGF5
ZXIgUGF0aCBNVFUgRGlzY292ZXJ5IChQTFBNVFVEKQ0KPiA+Pj4+PiAgZGVzaWduZWQgZm9yIHVz
ZSBpbiBlbnZpcm9ubWVudHMgaW4gd2hpY2ggZGVsaXZlcnkgb2YgYWNjdXJhdGUgSUNNUCBtZXNz
YWdlcw0KPiA+Pj4+PiAgdG8gYSBob3N0IGFyZSBub3QgYXNzdXJlZC4iDQo+ID4+Pj4NCj4gPj4+
PiBTbyB5b3UgYWRkZWQgdGhlIHdvcmQgImFjY3VyYXRlIi4gQW55dGhpbmcgZWxzZT8NCj4gPj4+
Pg0KPiA+Pj4+IE15IHF1ZXN0aW9uIHdvdWxkIGJlIHdoYXQgbWFrZXMgYW4gSUNNUCAiYWNjdXJh
dGUiLCBhbmQgaG93IHRoZSBob3N0IG1pZ2h0IG9yIG1pZ2h0IG5vdCBkZXRlcm1pbmUgYWNjdXJh
Y3kuIEFzIG5lYXIgYXMgSQ0KPiBjYW4NCj4gPj4gdGVsbCwNCj4gPj4+PiBSRkMgMTk4MSBzYXlz
IHRoYXQgaWYgYSBob3N0IHJlY2VpdmVzIGFuIElDTVAgUGFja2V0IFRvbyBCaWcsIGl0IHNob3Vs
ZCBtYWtlIHRoZSBwYWNrZXQgc21hbGxlci4gSWYgdGhlIElDTVAgaGFzIGJlZW4gc3Bvb2ZlZCwN
Cj4gPj4gdW5sZXNzDQo+ID4+Pj4gdGhlIHNwb29mZXIgaGFzIGRvbmUgc29tZXRoaW5nIHJlYWxs
eSBlZ3JlZ2lvdXMsIEkgZG9uJ3Qga25vdyBob3cgdGhlIHJlY2VpdmluZyBob3N0IHdvdWxkIGtu
b3cgdGhhdC4NCj4gPj4+DQo+ID4+PiBJQ01QIHNwb29maW5nIGlzIGV4YWN0bHkgdGhlIHBvaW50
LiBCdXQsIGl0IGlzIG5vdCB1cCB0byB0aGUgaG9zdCB0byBkZXRlcm1pbmUNCj4gPj4+IHdoZXRo
ZXIgYW4gSUNNUCBpcyBhY2N1cmF0ZSAtIGl0IGlzIHVwIHRvIHRoZSBob3N0IHRvIGRldGVybWlu
ZSB3aGV0aGVyIGl0IGlzDQo+ID4+PiBpbiBhbiBlbnZpcm9ubWVudCBpbiB3aGljaCBkZWxpdmVy
eSBvZiBhY2N1cmF0ZSBJQ01QIG1lc3NhZ2VzIGlzIG5vdCBhc3N1cmVkLg0KPiA+Pj4NCj4gPj4+
PiBHaXZlbiB0aGF0LCBJIGRvbid0IHRoaW5rIHRoZSB3b3JkaW5nIGNoYW5nZSBoZWxwcy4NCj4g
Pj4+DQo+ID4+PiBXaXRob3V0ICJhY2N1cmF0ZSIsIHRoZSB0ZXh0IGRvZXMgbm90IGFkZHJlc3Mg
ZmFpbHVyZSBtb2RlIDIpLg0KPiA+Pg0KPiA+PiBIb3cgaXMgYSBob3N0IHN1cHBvc2VkIHRvIGtu
b3cgaWYgaXQgaXMgYW4g4oCcYWNjdXJhdGUgSUNNUCBtZXNzYWdl4oCdPw0KPiA+DQo+ID4gUmVw
ZWF0aW5nIHdoYXQgSSBzYWlkIHdpdGggYSBuZWNlc3NhcnkgY29ycmVjdGlvbjoNCj4gPg0KPiA+
ICAiQnV0LCBpdCBpcyBub3QgdXAgdG8gdGhlIGhvc3QgdG8gZGV0ZXJtaW5lDQo+ID4gICAgd2hl
dGhlciBhbiBJQ01QIGlzIGFjY3VyYXRlIC0gaXQgaXMgdXAgdG8gdGhlIGhvc3QgdG8gZGV0ZXJt
aW5lIHdoZXRoZXIgaXQgaXMNCj4gPiAgICB1c2luZyBhIHBhdGggZm9yIHdoaWNoIGRlbGl2ZXJ5
IG9mIGFjY3VyYXRlIElDTVAgbWVzc2FnZSBpcyBub3QgYXNzdXJlZC7igJ0NCj4gDQo+IA0KPiBT
YW1lIHF1ZXN0aW9uLiAgSG93IGlzIHRoZSBob3N0IHN1cHBvc2VkIGRldGVybWluZSAiaXQgaXMg
dXNpbmcgYSBwYXRoIGZvciB3aGljaCBkZWxpdmVyeSBvZiBhY2N1cmF0ZSBJQ01QIG1lc3NhZ2Ug
aXMgbm90IGFzc3VyZWTigJ0/DQo+IERvbuKAmXQgeW91IHRoaW5rIHRoYXQgaWYgYXJlIGdvaW5n
IHRvIGFzayB0aGUgaG9zdCB0byB2YWxpZGF0ZSB0aGUgSUNNUCBQVEIgbWVzc2FnZXMsIHdlIG5l
ZWQgdG8gcHJvdmlkZSBzb21lIGFsZ29yaXRobSBvciBhcHByb2FjaA0KPiB0byBkbyB0aGF0Lg0K
DQpZb3Uga2VlcCBtaXNzaW5nIHRoZSBwb2ludDsgdGhlIGhvc3QgaXMgTk9UIHN1cHBvc2VkIHRv
IHZhbGlkYXRlIHRoZSBJQ01QIFBUQg0KbWVzc2FnZTsgaXQgaXMgc2ltcGx5IGFkdmlzZWQgdG8g
ZGV0ZXJtaW5lIHdoZXRoZXIgaXQgaXMgdXNpbmcgYSBwYXRoIGZvciB3aGljaA0KZGVsaXZlcnkg
b2YgYWNjdXJhdGUgSUNNUFAgbWVzc2FnZXMgaXMgbm90IGFzc3VyZWQuDQoNCj4gPj4gVGhpcyBp
cyBzdGFydGluZyB0byByZWFkIHRvIG1lIGxpa2UgY3JlYXRpbmcgYSBuZXcgc3BlY2lmaWNhdGlv
biwgbm90IGFkdmFuY2luZyB0aGUgb25lIHdlIGhhdmUgbm93Lg0KPiA+DQo+ID4gTm90IGF0IGFs
bC4gWW91IHdlcmUgb25seSB0b28gaGFwcHkgdG8gYWNjZXB0IEZyZWQgQmFrZXIncyBzdWdnZXN0
aW9uOyBJDQo+ID4gaGF2ZSBzaW1wbHkgbW9kaWZpZWQgdGhlIGFzcGVjdHMgb2YgaGlzIHN1Z2dl
c3Rpb24gdGhhdCB3ZXJlIGxhY2tpbmcNCj4gPiBhbmQvb3IgaW5hY2N1cmF0ZS4NCj4gPg0KPiAN
Cj4gRnJlZCBCYWtlcuKAmXMgY2hhbmdlIHdhcyB0byByZXBsYWNlIg0KPiANCj4gICAoUExQTVRV
RCkuICBJbiB0aGUgYWJzZW5jZSBvZiBJQ01QIG1lc3NhZ2VzLCB0aGUgcHJvcGVyDQo+IA0KPiB3
aXRoOg0KPiANCj4gICAoUExQTVRVRCkgZGVzaWduZWQgZm9yIHVzZSBpbiBlbnZpcm9ubWVudHMg
aW4gd2hpY2gNCj4gICBkZWxpdmVyeSBvZiBJQ01QIG1lc3NhZ2VzIHRvIGEgaG9zdCBhcmUgbm90
IGFzc3VyZWQuICBJbiB0aGlzIGFsZ29yaXRobSwNCj4gICB0aGUgcHJvcGVyDQoNCiJFbnZpcm9u
bWVudHMiIGlzIGluYWNjdXJhdGUgLSB0aGUgY29ycmVjdCB3b3JkIGlzICJwYXRoIi4gQSBob3N0
IGNvdWxkIGJlIGluIGFuDQplbnZpcm9ubWVudCB3aGVyZSBJQ01QLWJhc2VkIFBNVFVEIHdvcmtz
IHBlcmZlY3RseSBmb3IgcGF0aCBBIGFuZCBmYWlscw0KbWlzZXJhYmxlIGZvciBwYXRoIEIuIFRo
YXQgaXMgd2h5IGl0IGlzIGNhbGxlZCAiUGF0aCIgTVRVIGRpc2NvdmVyeSwgYW5kIG5vdA0KIkVu
dmlyb25tZW50IiBNVFUgZGlzY292ZXJ5Lg0KDQpUaGFua3MgLSBGcmVkDQpmcmVkLmwudGVtcGxp
bkBib2VpbmcuY29tDQoNCj4gQm9iDQoNCg==


From nobody Thu Feb  4 12:05:03 2016
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A4D41ACEEF for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 12:05:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.502
X-Spam-Level: 
X-Spam-Status: No, score=-114.502 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cWEfqokIHKzp for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 12:05:00 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F7851ACE0A for <ipv6@ietf.org>; Thu,  4 Feb 2016 12:05:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3295; q=dns/txt; s=iport; t=1454616300; x=1455825900; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=5ka/JxS3X21e0aaMW3hjIuU70W6bEhRfUly37KVQIwE=; b=RpjLehNFj7SKS00cCkg/xspzWg0ghH8/B0iC2iyt9koN6lrwlolxG4W0 xrZemQhrd6L6RU/F2K3PzQ7aL2H7vDIHWwODn2axDbLbY7Cvmj421wIVr JMrZyHxxg6AyhUNvA22uLGvti+sB8H1VyChTH20zkKnb9kZ2BqsUbs+pq Y=;
X-Files: signature.asc : 833
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CyAgDXrbNW/4gNJK1egzqBPwaIVbEBD?= =?us-ascii?q?oFmhg0CgT84FAEBAQEBAQGBCoRBAQEBAwF5BQsCAQgYLjIlAgQOBQ6IBQjBCgE?= =?us-ascii?q?BAQEBAQEBAQEBAQEBAQEBAQEBAQ0Ih3+CSoQ4gyWBDwWWcQGCfYFjiG6BW40Wi?= =?us-ascii?q?m6DUQEeAUOCAxmBSGoBhy18AQEB?=
X-IronPort-AV: E=Sophos;i="5.22,397,1449532800";  d="asc'?scan'208";a="234908451"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 04 Feb 2016 20:04:59 +0000
Received: from XCH-RCD-011.cisco.com (xch-rcd-011.cisco.com [173.37.102.21]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id u14K4xG8020561 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 4 Feb 2016 20:04:59 GMT
Received: from xch-rcd-013.cisco.com (173.37.102.23) by XCH-RCD-011.cisco.com (173.37.102.21) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 4 Feb 2016 14:04:58 -0600
Received: from xch-rcd-013.cisco.com ([173.37.102.23]) by XCH-RCD-013.cisco.com ([173.37.102.23]) with mapi id 15.00.1104.009; Thu, 4 Feb 2016 14:04:58 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Fred Templin <Fred.L.Templin@boeing.com>
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AQHRX2tTSDlY+6HQH0uuyx8Jsd7k2Q==
Date: Thu, 4 Feb 2016 20:04:58 +0000
Message-ID: <23785BDF-DA09-411F-A5DF-9B3E517BDC5E@cisco.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com> <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395DEF3@XCH-BLV-105.nw.nos.boeing.com> <8E7CAC70-9193-43B2-8A47-0C731B5464CA@cisco.com> <2134F8430051B64F815C691A62D983183395DFFF@XCH-BLV-105.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983183395DFFF@XCH-BLV-105.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3112)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.248.194]
Content-Type: multipart/signed; boundary="Apple-Mail=_3F2AA7CA-7498-4C3F-AA46-5DD30E40BB4E"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/4U6LtNgjH3-JN8xj3ZH8TxvJS98>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 20:05:02 -0000

--Apple-Mail=_3F2AA7CA-7498-4C3F-AA46-5DD30E40BB4E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On Feb 4, 2016, at 10:58 AM, Templin, Fred L =
<Fred.L.Templin@boeing.com> wrote:
>=20
> Hi Fred,
>> On Feb 4, 2016, at 10:37 AM, Templin, Fred L =
<Fred.L.Templin@boeing.com> wrote:
>>> Your text could be modified by simply adding the word "accurate" as =
follows:
>>>=20
>>> "It defines a method for Packetization Layer Path MTU Discovery =
(PLPMTUD)
>>>   designed for use in environments in which delivery of accurate =
ICMP messages
>>>   to a host are not assured."
>>=20
>> So you added the word "accurate". Anything else?
>>=20
>> My question would be what makes an ICMP "accurate", and how the host =
might or might not determine accuracy. As near as I can tell,
>> RFC 1981 says that if a host receives an ICMP Packet Too Big, it =
should make the packet smaller. If the ICMP has been spoofed, unless
>> the spoofer has done something really egregious, I don't know how the =
receiving host would know that.
>=20
> ICMP spoofing is exactly the point. But, it is not up to the host to =
determine
> whether an ICMP is accurate - it is up to the host to determine =
whether it is
> in an environment in which delivery of accurate ICMP messages is not =
assured.

Well, again, what is the test? How do I *know* that I am in an =
environment designed by a clueless operator? I can imagine that MAYBE a =
host sends an MSS-sized message and gets no Ack, but sends a smaller =
message and gets an ack for that. If we were to actually specify that =
test, I'll bet we would back ourselves into RFC 4821, and the test would =
become that RFC 4821 came up with a smaller number than RFC 1981 did.

I'd really like to not require someone to go test something and pick a =
PMTU algorithm based on the test. RFC 4821 has an attribute, which is =
that it is designed to be independent of ICMP and otherwise achieve some =
approximation to RFC 1981. In the text I suggested that is as much as I =
felt was appropriate to say.

--Apple-Mail=_3F2AA7CA-7498-4C3F-AA46-5DD30E40BB4E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIVAwUBVrOu6kayAOS/EQ8MAQLS+xAAwJ2IRd5A4FAb3ZNjTNGApfOifD7aGrMD
OOTAIQWFI3sXwBymYwUAHEefyYPL9ol9yy7BW3n2BgnePyrO59vuDmY4VI493FPG
9ysa/k4Y2/gxxa8nhVvuv+PKoetvL0xtF+Haj0DHECS+71dp01lS8oFuByUsCwdD
jYsnKmnqnNAOXgPiGafGPgTplpxu9z/DwetCFHjlpUtIgQl8Wjst5wth/Se4bHen
bV7ph/xSyGBScmX2KbbVnKyjdsD1Hm+3EzD6vncXFnlWmFzEHyap29JXQXGYYVRs
TB3zoO+zht0fUJ3hHb0N1dw2tkMgpt0Af3YcnqCoO5DlT/8Tuj6zvVRO7vzeyMeR
McqRlpbC4/JsIDQmDnbKZi4FEU8hP5NZWRn+S+wSlc5DaK0knlxpGw3blwAgMVgl
sYwf8xLBqPs4CTqmIJe1LaQv7kvMBaZkmrHiZszWOS9/LzosNUBg6GT9AFZMiWGa
IrhOf/2SJUG7TExfxkN1TRe0A8vAaL8YCrWnsAg7NfUobvoEm2xNq3EJ/Yb3rsdW
0HDw1cpfmSQZMBBVPJpEk0gDREZf+wceMEY2a61fx+zLxC/g1p9BloTmsvsk6W8O
ddw18IOJXHZ1QnlnwZ1+JQZBt8FFtaSxoMXcHrqa9h1YnYGVnpgXWpoRM3VUNA1d
Ji7PK+kMl84=
=2H4r
-----END PGP SIGNATURE-----

--Apple-Mail=_3F2AA7CA-7498-4C3F-AA46-5DD30E40BB4E--


From nobody Thu Feb  4 12:05:20 2016
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADD1C1ACF08 for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 12:05:18 -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 22poNT_n5Kns for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 12:05:15 -0800 (PST)
Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E881E1AD074 for <6man@ietf.org>; Thu,  4 Feb 2016 12:05:13 -0800 (PST)
Received: by mail-qk0-x230.google.com with SMTP id s68so25694599qkh.3 for <6man@ietf.org>; Thu, 04 Feb 2016 12:05:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=7gv8zUg1HOg9RcAYjYjJcaTtGYGxkztNU6Zpu1Pxjvg=; b=X67UySi/bvTIJzBUnyHNjhsO3TOLubhxO4fRx9QG91bl9rTXAZ3jAjAk9E3oi8DWZc 70Ydv+6CEAvVmJydEhQdvXNamj0m5Do3CUVE38JlFEc3XEak74kkNO8zp/I6iZxYW+vG c4I1rfXo8+fkmtcaXbd2/d0xjLq6Wg1ltMXyCh69b+yRgz6fzADZ9rPHGzm3sdhgEFsO L+Jg3AWXQCYqw8pgEi4jeNgRUkj+gZGVMBm/Zr8ZsgprfheCyyighFPGIH/geVBfaX0u ZOFZBrcRr7VshIP1JOssWmHRbgMg7x9ZlLIS1boO9sBpRrg33wTpy3eqNdi8cvcxaod0 mPjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=7gv8zUg1HOg9RcAYjYjJcaTtGYGxkztNU6Zpu1Pxjvg=; b=Snoq8/X5d17Km1/lFnlzloaNwrOEqi5+myPF2XXUk62GIOTqm3TjD0MyT+fpn3pc6g IZn1sIAIWv36l62IU9MBFiyXholK5WNBNN+6mfqkV3GNP1mnw+70baamsJXXe3NMGJjI rAw+WCqMrI0hXdvrOVEb1x5ysVtbCxIZnN1+C12oVIxraWfb2QludgjxJHs+E6huVE0j SQbj8vYDM4qnjAOrceXJ/uvMJJ7iKl68lZoWaKlmXpNDLSuCKYaxvZCZi75gYOQclQnr NIoUO9kXz7pzvsY2YlCw7qa5YL2ne2pCeu4nZ4K9WHbGUJz9kRDRke9OBEYRhi0NXmO4 AfQA==
X-Gm-Message-State: AG10YOT4bWA9wvK3vaMk5LWWvfP2aLg1S+y0oyhmdL7s4NgkGQUTIxyDnzvDm3j/LRMC2g==
X-Received: by 10.55.74.141 with SMTP id x135mr11561922qka.20.1454616313164; Thu, 04 Feb 2016 12:05:13 -0800 (PST)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id j67sm5973076qgj.35.2016.02.04.12.05.12 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 04 Feb 2016 12:05:12 -0800 (PST)
Subject: Re: rfc2460bis and Frag ID generation
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_0D419F4E-4005-44AE-9C6D-19EC90254C59"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <56B3A990.9070000@si6networks.com>
Date: Thu, 4 Feb 2016 12:05:08 -0800
Message-Id: <2E3B4659-E282-4AF5-810D-EB951E1A3F13@gmail.com>
References: <56B39FB8.4090604@si6networks.com> <6EF1C55C-FE16-4019-A6C9-6AD67DA42E84@gmail.com> <56B3A990.9070000@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/soQNBwjYvju4RpvSDpdN57HAi38>
Cc: "6man@ietf.org" <6man@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 20:05:18 -0000

--Apple-Mail=_0D419F4E-4005-44AE-9C6D-19EC90254C59
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Fernanco,

> On Feb 4, 2016, at 11:42 AM, Fernando Gont <fgont@si6networks.com> =
wrote:
>=20
> On 02/04/2016 04:24 PM, Bob Hinden wrote:
> [....]
>>>=20
>>> Thoughts?
>>=20
>> I looked at this earlier and also thought the 32-bit wrap around
>> counter text was dated.  I am OK with something similar to what you
>> proposed.  My read of the current text is that it is describes the
>> 32-bit wrap around counter as an example, as opposed the only way to
>> do it, so an update like this would be OK.
>>=20
>> Other comments?
>=20
> BTW, please let me know if the current version will not be revised in
> less than, say, 1 week, and I could do a full review=85.

Not sure, other than this possible change, I don=92t have anything else =
queued up.

Bob

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


--Apple-Mail=_0D419F4E-4005-44AE-9C6D-19EC90254C59
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJWs671AAoJEK7rdBF357uoWK8H/03R3doN1WGaZWcC/Yw3VcUp
aFtycRimhx+qCNITTS1yvXYMJQunIIGzp+c4WIqAv9323jDhcCMPynrCwcrkNsn+
BPKNCouyWEGVwTw+eH/rN50NJDxJ0WEcmTPBzLK+nP8kfpW6hYWbDfUNlDXXeHza
fTTJdOfV7r9DqUswH0vXTLzIpMep9kr+WmuoTuqgbreitn4Bkrspi8/nl0TxFVVy
7PsoESLCaRZKSQdV4bK9vcX3jnqdwT2XJ5FSzd1D2niZy5MdJ4rJ8VWENI2vyKEQ
fgITdIlJ4c+yNUkOn4smZCPBMCJMx93BkTs8NNKKwMCoE6lLAgv6T+SYu8zT46Q=
=YFD1
-----END PGP SIGNATURE-----

--Apple-Mail=_0D419F4E-4005-44AE-9C6D-19EC90254C59--


From nobody Thu Feb  4 12:16:55 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3199E1AD074 for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 12:16:54 -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] 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 PaqvM8uisRhn for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 12:16:50 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 469F01AD05F for <6man@ietf.org>; Thu,  4 Feb 2016 12:16:50 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id E74E6206AC2; Thu,  4 Feb 2016 21:16:46 +0100 (CET)
Subject: Re: rfc2460bis and Frag ID generation
To: Bob Hinden <bob.hinden@gmail.com>
References: <56B39FB8.4090604@si6networks.com> <6EF1C55C-FE16-4019-A6C9-6AD67DA42E84@gmail.com> <56B3A990.9070000@si6networks.com> <2E3B4659-E282-4AF5-810D-EB951E1A3F13@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <56B3B1A0.4060503@si6networks.com>
Date: Thu, 4 Feb 2016 17:16:32 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <2E3B4659-E282-4AF5-810D-EB951E1A3F13@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/PvyeakCtULmLiWAnIh1L6BVja4Y>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 20:16:54 -0000

On 02/04/2016 05:05 PM, Bob Hinden wrote:
> Fernanco,
> 
>> On Feb 4, 2016, at 11:42 AM, Fernando Gont <fgont@si6networks.com> wrote:
>>
>> On 02/04/2016 04:24 PM, Bob Hinden wrote:
>> [....]
>>>>
>>>> Thoughts?
>>>
>>> I looked at this earlier and also thought the 32-bit wrap around
>>> counter text was dated.  I am OK with something similar to what you
>>> proposed.  My read of the current text is that it is describes the
>>> 32-bit wrap around counter as an example, as opposed the only way to
>>> do it, so an update like this would be OK.
>>>
>>> Other comments?
>>
>> BTW, please let me know if the current version will not be revised in
>> less than, say, 1 week, and I could do a full review….
> 
> Not sure, other than this possible change, I don’t have anything else queued up.

I meant... if the I-D is going to be stable for a few days, I can do a
complete review. Otherwise I'd wait for the next rev, so that I review
the updated doc...

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





From nobody Thu Feb  4 12:33:37 2016
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 607C71AD16B for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 12:33:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id up40Di_1xbeL for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 12:33:32 -0800 (PST)
Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB5771AD10A for <6man@ietf.org>; Thu,  4 Feb 2016 12:33:32 -0800 (PST)
Received: by mail-io0-x22a.google.com with SMTP id 9so106826079iom.1 for <6man@ietf.org>; Thu, 04 Feb 2016 12:33:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=rD7uRK+YaZssyW4CvPMe2Z6o6IwxFci05tjYYsRuinc=; b=nJSgM9/vzAElGTLkmYlHWDSh42bCbl3jMTvdfhhM2y4vFRt194dE2+kOqPLP1Ud46S DgkvztqHg6Fzrue93BrY8+HdCECs+oZwf537Oj9Y7vDEICLW1PFa+D0upWWFkIaTSe8N dP+c1lmGpwWUbC9k20Nxbvf0dzIcyNAqqwFl2u8oX4+3fMIleU79HAZ2fVVdAX86LOlI o+BGh/EN5lvSfFsO34OzNzIsahJIy0ijoOhRM/BB6xG/ZpjCpP6ekWZ0iAgtRmxvUZpV 7RN2innxZ/i23WdYWIyQBEK93j7pGyOKMMSaDMQYqLWgWeMkBxcBLqBk7ww9TVgELgJI RsUA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=rD7uRK+YaZssyW4CvPMe2Z6o6IwxFci05tjYYsRuinc=; b=GoqIoNHKmHWCkRKcju8ijgE7vrU3F+Hs66nXj161JFMps+lwe5qv5IxeVzSZWv5L+n /EcJ94hA6pjimgFXbiGJmgkj4L3enid+PU6Dil7pvJtUa/Jpo4AipkWlUWBTIWWc5ftn j8ZZOfq3ukSUNbWqRkiLEaQU+y6PRqbBm/GuHMHxnkzWnHMsNDWBnNzLoc3srNR5OkOV lAmsENyBxX9/ARtRd1IMXyJwEvPE/pzt4HtHZKKT091wWomajlfvvuy6393mtJF6DAZp 665Y6wI/+cTwZ86nkRE+50KDxxrYHFq2jvBujzYlkgUdAnaZht4PHMKF9OjD1iQs+KQS ysJg==
X-Gm-Message-State: AG10YOQQsW0CIJNoiNnjSMGZ43A5ol993oivoOgWw44sdZHbGtT5jqmwYlKEB4FJ2YQ/Lw==
X-Received: by 10.107.18.199 with SMTP id 68mr10703308ios.130.1454618012192; Thu, 04 Feb 2016 12:33:32 -0800 (PST)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id c79sm4648918iod.5.2016.02.04.12.33.30 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 04 Feb 2016 12:33:30 -0800 (PST)
Subject: Re: rfc2460bis and Frag ID generation
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_396B12DC-84DF-448D-BF51-CBD9E64CF680"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <56B3B1A0.4060503@si6networks.com>
Date: Thu, 4 Feb 2016 12:33:28 -0800
Message-Id: <76DA9112-E45D-47EA-AAC2-03F11C87B786@gmail.com>
References: <56B39FB8.4090604@si6networks.com> <6EF1C55C-FE16-4019-A6C9-6AD67DA42E84@gmail.com> <56B3A990.9070000@si6networks.com> <2E3B4659-E282-4AF5-810D-EB951E1A3F13@gmail.com> <56B3B1A0.4060503@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/shnZmCmTAMUR4j9NJ03HqPbNVRI>
Cc: "6man@ietf.org" <6man@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 20:33:34 -0000

--Apple-Mail=_396B12DC-84DF-448D-BF51-CBD9E64CF680
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


> On Feb 4, 2016, at 12:16 PM, Fernando Gont <fgont@si6networks.com> =
wrote:
>=20
> On 02/04/2016 05:05 PM, Bob Hinden wrote:
>> Fernanco,
>>=20
>>> On Feb 4, 2016, at 11:42 AM, Fernando Gont <fgont@si6networks.com> =
wrote:
>>>=20
>>> On 02/04/2016 04:24 PM, Bob Hinden wrote:
>>> [....]
>>>>>=20
>>>>> Thoughts?
>>>>=20
>>>> I looked at this earlier and also thought the 32-bit wrap around
>>>> counter text was dated.  I am OK with something similar to what you
>>>> proposed.  My read of the current text is that it is describes the
>>>> 32-bit wrap around counter as an example, as opposed the only way =
to
>>>> do it, so an update like this would be OK.
>>>>=20
>>>> Other comments?
>>>=20
>>> BTW, please let me know if the current version will not be revised =
in
>>> less than, say, 1 week, and I could do a full review=85.
>>=20
>> Not sure, other than this possible change, I don=92t have anything =
else queued up.
>=20
> I meant... if the I-D is going to be stable for a few days, I can do a
> complete review. Otherwise I'd wait for the next rev, so that I review
> the updated doc=85

I promise not to make any changes until next week :-)

More importantly, I doubt there will be any major changes going forward.

Bob

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


--Apple-Mail=_396B12DC-84DF-448D-BF51-CBD9E64CF680
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJWs7WZAAoJEK7rdBF357uo69AH/0dxPHp2B58SrS/TZ8ow9lO8
kLSvUaiCSA54GlDxQrjlr/eM5P/FePN1s2QVTvFl/LJdPYu3rsnSgMVCPfVbpcOT
Ys6+24hndXAWt74Q7sVsxLNECc3VmWJ672PkcrfcWu9s16tPxDRAUnziWnahy0fW
I3pUn4wYc6SeuINTstNLPNqbNaRmZQkC+bCmqmTymen3IUN4NVqa8UBsaEIB7LKC
4uSTtce3SSjARxZe1wcdXnxogecdXfc25BwQkJe7THYseYOMNG+WNFtqJWI94Glu
NjL1x+0+IBGEmQj0DYNDG7l/VkCawifv+lzISnRnfy+zh/6JE+DOTmzqoEySoDU=
=xviR
-----END PGP SIGNATURE-----

--Apple-Mail=_396B12DC-84DF-448D-BF51-CBD9E64CF680--


From nobody Thu Feb  4 12:45:27 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CEC51ACDF9 for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 12:45:26 -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] 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 IguCo250rbrj for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 12:45:25 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D18931AD190 for <6man@ietf.org>; Thu,  4 Feb 2016 12:45:24 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 16185206ABF; Thu,  4 Feb 2016 21:45:21 +0100 (CET)
Subject: Re: rfc2460bis and Frag ID generation
To: Bob Hinden <bob.hinden@gmail.com>
References: <56B39FB8.4090604@si6networks.com> <6EF1C55C-FE16-4019-A6C9-6AD67DA42E84@gmail.com> <56B3A990.9070000@si6networks.com> <2E3B4659-E282-4AF5-810D-EB951E1A3F13@gmail.com> <56B3B1A0.4060503@si6networks.com> <76DA9112-E45D-47EA-AAC2-03F11C87B786@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <56B3B64E.4080605@si6networks.com>
Date: Thu, 4 Feb 2016 17:36:30 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <76DA9112-E45D-47EA-AAC2-03F11C87B786@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ViU5elxKC_APgUrp8UwbKjvd-YA>
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 20:45:26 -0000

On 02/04/2016 05:33 PM, Bob Hinden wrote:
> 
>> On Feb 4, 2016, at 12:16 PM, Fernando Gont <fgont@si6networks.com> wrote:
>>
>> On 02/04/2016 05:05 PM, Bob Hinden wrote:
>>> Fernanco,
>>>
>>>> On Feb 4, 2016, at 11:42 AM, Fernando Gont <fgont@si6networks.com> wrote:
>>>>
>>>> On 02/04/2016 04:24 PM, Bob Hinden wrote:
>>>> [....]
>>>>>>
>>>>>> Thoughts?
>>>>>
>>>>> I looked at this earlier and also thought the 32-bit wrap around
>>>>> counter text was dated.  I am OK with something similar to what you
>>>>> proposed.  My read of the current text is that it is describes the
>>>>> 32-bit wrap around counter as an example, as opposed the only way to
>>>>> do it, so an update like this would be OK.
>>>>>
>>>>> Other comments?
>>>>
>>>> BTW, please let me know if the current version will not be revised in
>>>> less than, say, 1 week, and I could do a full review….
>>>
>>> Not sure, other than this possible change, I don’t have anything else queued up.
>>
>> I meant... if the I-D is going to be stable for a few days, I can do a
>> complete review. Otherwise I'd wait for the next rev, so that I review
>> the updated doc…
> 
> I promise not to make any changes until next week :-)
> 
> More importantly, I doubt there will be any major changes going forward.

Ok. :-) I'll send a full rev this weekend.

Thanks!

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





From nobody Thu Feb  4 14:46:24 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8FD71B333C for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 14:46:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 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, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N_ABL6DVC5UR for <ipv6@ietfa.amsl.com>; Thu,  4 Feb 2016 14:46:20 -0800 (PST)
Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1FA61B3340 for <ipv6@ietf.org>; Thu,  4 Feb 2016 14:46:20 -0800 (PST)
Received: by mail-pa0-x231.google.com with SMTP id cy9so22825284pac.0 for <ipv6@ietf.org>; Thu, 04 Feb 2016 14:46:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=4rRiwG5lhWjaUfoGmgmPdRl/8+2r6ljDuCwRiWndl2A=; b=xBOstZ4Hqo5XVNY2a7fTSxgFAWU7Ow7R9uJ2psl+HmOI52p7quilPWauVKYJhcpgbN npg8Z/shwMKzv8WSpEKAHvDpzIO3WK+PUm7SekIZIEqZgDo69zeR40c/SRoj1vYuVG01 0bCCC6NpBzCrUc5o8FAKWMNLUSRlTGe0MzACkpLNQQA91hZMQS9zUQYHIknCli85TYzK uOaVj+G8LbrkNNSI2ZJpp4evWLwazck4A4ytjxECEpcNTO3b2a+83QJVpG+E3Zz8vkLR NICnYW8SuGkrvN1OGHM9fTj/1+GVB2kdSKspH8QfKY+WfIkBYG12++WDPcXQb/1gZyqN BYFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=4rRiwG5lhWjaUfoGmgmPdRl/8+2r6ljDuCwRiWndl2A=; b=Ee3Qi3WhX+rTKS0GlADURRmtAjfT2rf/3+hbXxhfHk9EoAjPuvpdFBtT2JLxI2Cvb3 kAqlreimeyLcj2hRu1jhWkspSRwqN7bFcl3lRDFu8JNvu5aLrrlN3XSynSUIYBjhEEDM olBQ8if+lksL4Q1q+WekJQ4o79CjUlexTOHOCdjMzUjHms9qp9sciyLxyoCMeQA70/Mm T9/bcoJDMy+x92jl/oVvrljQx6+bfTJtvHweoE3BlTlulH8KkZGOA3eZZ4m4lTYv6wGE +8Qr2yRVZJ+eHMasFY/Pgpq9mfTHoT7KUfPJgvHnZZ/srOELE9v3uaX1q7kaow+8kQTQ Nbmg==
X-Gm-Message-State: AG10YORlg9ECEBoEw6GgxNzD85TBTMDzwihhYUkRPTc/Fs+KH34VyahKK36eacgtfq0oQA==
X-Received: by 10.66.139.234 with SMTP id rb10mr14845857pab.82.1454625980486;  Thu, 04 Feb 2016 14:46:20 -0800 (PST)
Received: from ?IPv6:2406:e007:43ce:1:28cc:dc4c:9703:6781? ([2406:e007:43ce:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id r80sm19543966pfi.9.2016.02.04.14.46.16 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 04 Feb 2016 14:46:18 -0800 (PST)
Subject: Re: 6MAN WG Last Call - draft-ietf-6man-multi-homed-host-03.txt
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Bob Hinden <bob.hinden@gmail.com>
References: <2052A806-4D40-4A17-9892-90E39B67C65C@gmail.com> <CAJE_bqekFsfHPkfLTAOHgdL-MpvwNSV=gB8Cv0x+YrD66JUyMg@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56B3D4BF.9000202@gmail.com>
Date: Fri, 5 Feb 2016 11:46:23 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <CAJE_bqekFsfHPkfLTAOHgdL-MpvwNSV=gB8Cv0x+YrD66JUyMg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ZGUZG43zsDD6epBbX2_uAm12kUU>
Cc: IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Feb 2016 22:46:22 -0000

Jinmei-san,

Thanks for the review. I guess we will not update draft until the WGLC
expires, but my personal comments are below.

On 05/02/2016 08:35, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 wrote:
> At Wed, 3 Feb 2016 14:28:07 -0800,
> Bob Hinden <bob.hinden@gmail.com> wrote:
>=20
>> This message starts a two week 6MAN Working Group Last Call on advanci=
ng:
>>
>>        Title           : Routing packets from hosts in a multi-prefix =
network
>>        Authors         : Fred Baker
>>                          Brian Carpenter
>>        Filename        : draft-ietf-6man-multi-homed-host-03.txt
>>        Pages           : 13
>>        Date            : 2015-12-16
>>
>>    https://tools.ietf.org/html/draft-ietf-6man-multi-homed-host-03
>>
>> as a Proposed Standard.  Substantive comments and statements of
>> support for publishing this document should be directed to the
>> mailing list.  Editorial suggestions can be sent to the authors.
>> This last call will end on 17 February 2016.
>=20
> I think this version is basically good enough for publication.
>=20
> I have some comments on the latest version.  I don't think they are
> blocking issues but may be better addressed before sending it to the
> IESG.
>=20
> - Some of my previous comments seem to be still open.  Although I
>   already stated I wouldn't insist, it's not clear whether they were
>   rejected as a result or just overlooked, so I'm re-raising them
>   here: https://mailarchive.ietf.org/arch/msg/ipv6/42QPrrvdShflkz06tn3v=
dw33iEo
>   The seeming open points are:
>   + whether to move the host-model discussion to an appendix

My personal choice is not to move it, but I would certainly do so
if that was the WG's preference.

>   + about the term "addressless"

Ah, you said:

>> BTW, "an addressless interface" may not be the best term, since in
>> IPv6 any interface should have at least a link-local address.
>> Something like "a link-local-only interface" would be more accurate.

Yes, that is better in an IPv6 document.

> - Section 3.1
>=20
>    As described in [RFC4191] and [RFC4861], a Router Advertisement may
>    contain zero or more Prefix information Options (PIOs), zero or more=

>    Route Information Options (RIOs), or a Default Router List.
>=20
>   I'm not sure if I can understand the "or a Default Router List"
>   part.  If it means 'Router Advertisement may contain...a Default
>   Router List', it doesn't make sense since an RA (or any of its
>   options) doesn't contain such a list (Default Router List is
>   something that a host maintains based on the content of RA).

I think you're correct.

> - Section 3.1: likewise, the use of 'a default router list' in the
>   following sentence is confusing, too:
>=20
>    [...]  In a multi-
>    homed network implementing source/destination routing, the
>    interpretation of a default router list or an RIO has to be modified=

>    with the words "if the source address is in one of the prefixes I
>    advertise in a PIO".

This is correct, isn't it? It applies to what the host has stored in
its default router list and to any new RIOs that it receives. It could
be phrased more carefully, I agree.

>=20
> - Section 3.1
>=20
>    Bob's first hop routers are Bob-A (to upstream ISP A advertising
>    prefix A') and Bob-B (to upstream network B and advertising prefix
>    B').
>=20
>   I'd suggest something like PA and PB instead of A' and B'.  It may
>   be a matter of taste, but to me X and X' refer to different
>   instances of the same kind of concept (like both are addresses or
>   both are prefixes), so the current notation is confusing.

OK

>=20
> - Section 3.4
>=20
>    There is potential for adverse interaction with any off-link Redirec=
t
>    (Redirect for a GUA destination that is not on-link) message sent by=

>=20
>   Is there any particular intent about why we specially say "GUA" here
>   instead of, e.g., just "a global destination"?  For example, does it
>   intend to exclude ULAs?  If so, why?  In case of ULAs, while the
>   proposed host behavior may be less critical with ULAs in practice, I
>   don't see any technical reason why we can't use it for ULAs.

To me it's clear that both "GUA" and "global" include ULAs, because ULAs
are defined to have global scope. Do you think there is a formal
difference between "GUA" and "global"? If so, is it documented?

Thanks
     Brian


From nobody Fri Feb  5 00:04:12 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A60161A01A9 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 00:04:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-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 xdXBDxfdVHqv for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 00:04:09 -0800 (PST)
Received: from cowbell.employees.org (cowbell.employees.org [IPv6:2001:1868:a000:17::142]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A06E91A01A8 for <ipv6@ietf.org>; Fri,  5 Feb 2016 00:04:09 -0800 (PST)
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 0CB3CD7884; Fri,  5 Feb 2016 00:04:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=L4rrr00dIuW9PxbE7rjRHBp8yUo=; b= S4FAFKiGi+5OuTkGJDqIOg+jL69lQvK6cW3P3qEYCqepumbZOpoBxZSWF5cTcP39 A9HeSdoZGywCRE0AZKmPETqXo5M8J4IWSmaFwFj7TwYPu4HW9TbW055Jwdnl2bdr udbssykDPTY7MKUnhQbgHCSgl6r7wooJb4ayPwaJ5bA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=drcu2+rvo6bFBInvYsOvCF3Cqv IlEK0DhLIJqkFpjdG0IQ8lvAr+h4nA+IcqjM+OpjPgasYiU7ZhcjzCOybmRTfUmY aRWlYU9WcVKhwzHGczXkPHb7L7ye/RB9jIjODA08mAPNf/WXelnbA/lJsw3LOR4S owEFD9/ZVRCTGM1ic=
Received: from h.hanazo.no (unknown [173.38.220.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 91FDBD7882; Fri,  5 Feb 2016 00:04:08 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id B4A4110780BE; Fri,  5 Feb 2016 09:04:12 +0100 (CET)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Content-Type: multipart/signed; boundary="Apple-Mail=_4A832F08-AC88-4F0E-A2CE-F7F3F711CBC2"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <2134F8430051B64F815C691A62D983183395E016@XCH-BLV-105.nw.nos.boeing.com>
Date: Fri, 5 Feb 2016 09:04:11 +0100
Message-Id: <A24F9E2D-3F56-4B1A-93C9-7F7BC62C6DF2@employees.org>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com> <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395DEF3@XCH-BLV-105.nw.nos.boeing.com> <8E7CAC70-9193-43B2-8A47-0C731B5464CA@cisco.com> <2134F8430051B64F815C691A62D983183395DFFF@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395E016@XCH-BLV-105.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/JeqJWiTL-eZoU8E_ofYumK3-s3Y>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 08:04:11 -0000

--Apple-Mail=_4A832F08-AC88-4F0E-A2CE-F7F3F711CBC2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Fred,

>=20
> I will make one other change recommendation:
>=20
> OLD:
> It defines a method for Packetization Layer Path MTU Discovery =
(PLPMTUD)
> designed for use in environments in which delivery of accurate ICMP =
messages
> to a host are not assured.
>=20
> NEW:
> It defines a method for Packetization Layer Path MTU Discovery =
(PLPMTUD)
> designed for use over paths for which delivery of accurate ICMP =
messages
> to a host are not assured.

I would posit that there are no such paths. "accurate" ICMP can never be =
guaranteed.

Best regards,
Ole

>> -----Original Message-----
>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Templin, Fred =
L
>> Sent: Thursday, February 04, 2016 10:59 AM
>> To: Fred Baker (fred)
>> Cc: 6man WG; Bob Hinden
>> Subject: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
>>=20
>> Hi Fred,
>>=20
>>> -----Original Message-----
>>> From: Fred Baker (fred) [mailto:fred@cisco.com]
>>> Sent: Thursday, February 04, 2016 10:50 AM
>>> To: Templin, Fred L
>>> Cc: Bob Hinden; 6man WG
>>> Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
>>>=20
>>>=20
>>>> On Feb 4, 2016, at 10:37 AM, Templin, Fred L =
<Fred.L.Templin@boeing.com> wrote:
>>>>=20
>>>> Your text could be modified by simply adding the word "accurate" as =
follows:
>>>>=20
>>>> "It defines a method for Packetization Layer Path MTU Discovery =
(PLPMTUD)
>>>>   designed for use in environments in which delivery of accurate =
ICMP messages
>>>>   to a host are not assured."
>>>=20
>>> So you added the word "accurate". Anything else?
>>>=20
>>> My question would be what makes an ICMP "accurate", and how the host =
might or might not determine accuracy. As near as I can
>> tell,
>>> RFC 1981 says that if a host receives an ICMP Packet Too Big, it =
should make the packet smaller. If the ICMP has been spoofed,
>> unless
>>> the spoofer has done something really egregious, I don't know how =
the receiving host would know that.
>>=20
>> ICMP spoofing is exactly the point. But, it is not up to the host to =
determine
>> whether an ICMP is accurate - it is up to the host to determine =
whether it is
>> in an environment in which delivery of accurate ICMP messages is not =
assured.
>>=20
>>> Given that, I don't think the wording change helps.
>>=20
>> Without "accurate", the text does not address failure mode 2).
>>=20
>> Thanks - Fred
>> fred.l.templin@boeing.com
>>=20
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_4A832F08-AC88-4F0E-A2CE-F7F3F711CBC2
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIcBAEBCgAGBQJWtFd8AAoJEL7aWKiYQt92UfIP/1z6rLna7By8qi80yToDlRs4
Z9w2SsgPhLZdiUe5kgRCA2lPQlpL27MWXYp2rnsC6Oc/O5LjxFQAwVDiHaZjN5di
ZoFZJCaWd2Gm5h4mSER2REOOHMTSCD2zskRwhlJ62XVSSk4dP9ObcjcXBmBqTgYc
J41N493mjn+ySx8MjKfwoJ1PM2af/9uQOdFDYS60rTr6jEprpqD51HKVwaGR0hnS
9SelzwoDb4y5SmyR/q9tSrXjHnz8hY5wLS+tpuAgvYRWDcmWO9Iw61TlxfPwHUF2
zzJmQ+IvYWgG4MCOcyUXPRAGth9ojXro9gbxFL5fvYxCVNuaoUCYiKPrY/sdyYm9
9qu2Vs2xafr0Cv54H18nCnIhEmlsYRTPj4hwbbOwF4cOsDnu6NKF3A4Pw8N3zaXq
JCGCVi5l7tHrJ4W2lB+uhhpR6Le54vxG7SymeAjMRN7/OcsankyNFrgITZHurC4O
nq8hJYZIQseth6GIcf9voiJl/SscXT2Y9fe+ETuV9y6ldqnPsnieszcrKNpBuF2g
Y2mU3gn+CCkt0bXDRnGw/bNekfQyUAOZyxoAoNZ7XbYkfqMBksiGr14/ika+RSJA
DZtPE/CYGDb8v5m6ZZr+GOrPlyaZtK5YSfvg/Icjo1wReqC6ppWowZrnbEiLaWhG
y/Hvor2Jvz8KxMGIV+xL
=Up11
-----END PGP SIGNATURE-----

--Apple-Mail=_4A832F08-AC88-4F0E-A2CE-F7F3F711CBC2--


From nobody Fri Feb  5 00:09:00 2016
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6D5B1A036A for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 00:08:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level: 
X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, 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 BN1HL85hHXKb for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 00:08:57 -0800 (PST)
Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68C811A0369 for <ipv6@ietf.org>; Fri,  5 Feb 2016 00:08:57 -0800 (PST)
Received: by mail-vk0-x22e.google.com with SMTP id e185so52020937vkb.1 for <ipv6@ietf.org>; Fri, 05 Feb 2016 00:08:57 -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; bh=kq3aKg5Jt/1o6Q2K7nkIhyTsf0lBzs6wMxUHeA5POnE=; b=pgruqJ6Dp9bTzrRI/Z5FFwwJpksNb//wijjFOsRWqX37pkOTj4i44ZogVZ6F0CTQ5F MWoRup25+L1TFJFUbhGBAN/jxC1IJpO4xFSeEs3mxYiv0wC3THqbLgAvhLd1x0/OGP2/ 0HmnC9Tqmwsx5vGB6daiPXuasQrCr+die+knJGYDkcDgJW/BWRwEUyM20KJQp7NgNWvo 6nC3tp2L6T4grVJsR+lXv1IUnWg2Lz0TQTyNfd3xFDHnqz/aTyVbFP97Ld3JL4d5Uxk8 bTGkCQQia/W4UpU5kuyLst7Jg46TPPqw2KqH5/s/9s/8DCctAHFQJi9Z1+PySkQxxBIL 89/w==
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=kq3aKg5Jt/1o6Q2K7nkIhyTsf0lBzs6wMxUHeA5POnE=; b=C4CqZYKgG5/q2/IqOHlFO5jUbpq4GAoS9KPS4681yiFNFIXwsnJqahLqfXQR42PtT3 lR36v6D9vAoYzF+bacdGW6GEzNtTw7478Tr98/KwVm96cWPq6ui/jN3hOCTj0nG+vhvb uHwq8cA1qwfzu3kjV+f2IzrTmBAJi9GYq4wLqYyX866vSAJX64r5vIB9fTBfWtIL3k1J IkPiRd4nPh1ZS55BJK3C6i96W14wA+RjLX6+ByCd73fMi48Ve789/vgARlyfEnkGwVaE XaKqQ0PNIjyWE4960mQx3OGpsyM0yzJSyNfB203Rt2eBefNGVsySuaPSx0YkSDF1M2Zi pLfA==
X-Gm-Message-State: AG10YOQCI3p2zIbnnubj3quntsIo1/c4Uy04Sqgc8kpMAQYt3CEoc1X8dgtQETsn5Wt5ut0IbJdILi9NLzdeUg==
MIME-Version: 1.0
X-Received: by 10.31.107.194 with SMTP id k63mr7787718vki.27.1454659736530; Fri, 05 Feb 2016 00:08:56 -0800 (PST)
Received: by 10.103.92.67 with HTTP; Fri, 5 Feb 2016 00:08:56 -0800 (PST)
Received: by 10.103.92.67 with HTTP; Fri, 5 Feb 2016 00:08:56 -0800 (PST)
In-Reply-To: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org>
Date: Fri, 5 Feb 2016 19:08:56 +1100
Message-ID: <CAO42Z2yx2qVWMwf21tYOK0ZpNVXbYm4HVG9K1F-OVMVMO=Njpw@mail.gmail.com>
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
From: Mark Smith <markzzzsmith@gmail.com>
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=001a114786c2dd7a2d052b015c3c
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/oqLOVv5D8-gGpemUf3GXzW9oXuc>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 08:08:59 -0000

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

I support adoption.
On 4 Feb 2016 7:26 AM, <otroan@employees.org> wrote:

> This message starts a two week 6MAN call on adopting:
>
> Name:   draft-hinden-6man-rfc1981bis-01
> Title:  Path MTU Discovery for IP version 6
> Document date:  2015-12-01
> Pages:  16
> URL:
> https://datatracker.ietf.org/doc/draft-hinden-6man-rfc1981bis/
> Htmlized:  https://tools.ietf.org/html/draft-hinden-6man-rfc1981bis-01
> Diff:
> https://tools.ietf.org/rfcdiff?url2=3Ddraft-hinden-6man-rfc1981bis-01.txt
>
> as a working group item. Substantive comments and statements of support
> for adopting this document should be directed to the mailing
> list. Editorial suggestions can be sent to the authors.
>
> This document is part of the working group=E2=80=99s ongoing work on adva=
ncing the
>  core IPv6 standards to Internet Standard.
>
> This adoption call will end on February 17th, 2016.
>
> Regards,
>
> Bob Hinden & Ole Tr=C3=B8an
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>

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

<p dir=3D"ltr">I support adoption.</p>
<div class=3D"gmail_quote">On 4 Feb 2016 7:26 AM,  &lt;<a href=3D"mailto:ot=
roan@employees.org">otroan@employees.org</a>&gt; wrote:<br type=3D"attribut=
ion"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">This message starts a two week 6MAN cal=
l on adopting:<br>
<br>
Name:=C2=A0 =C2=A0draft-hinden-6man-rfc1981bis-01<br>
Title:=C2=A0 Path MTU Discovery for IP version 6<br>
Document date:=C2=A0 2015-12-01<br>
Pages:=C2=A0 16<br>
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.ietf.o=
rg/doc/draft-hinden-6man-rfc1981bis/" rel=3D"noreferrer" target=3D"_blank">=
https://datatracker.ietf.org/doc/draft-hinden-6man-rfc1981bis/</a><br>
Htmlized:=C2=A0 <a href=3D"https://tools.ietf.org/html/draft-hinden-6man-rf=
c1981bis-01" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/ht=
ml/draft-hinden-6man-rfc1981bis-01</a><br>
Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://tools.ietf.org/r=
fcdiff?url2=3Ddraft-hinden-6man-rfc1981bis-01.txt" rel=3D"noreferrer" targe=
t=3D"_blank">https://tools.ietf.org/rfcdiff?url2=3Ddraft-hinden-6man-rfc198=
1bis-01.txt</a><br>
<br>
as a working group item. Substantive comments and statements of support<br>
for adopting this document should be directed to the mailing<br>
list. Editorial suggestions can be sent to the authors.<br>
<br>
This document is part of the working group=E2=80=99s ongoing work on advanc=
ing the<br>
=C2=A0core IPv6 standards to Internet Standard.<br>
<br>
This adoption call will end on February 17th, 2016.<br>
<br>
Regards,<br>
<br>
Bob Hinden &amp; Ole Tr=C3=B8an<br>
<br>
<br>--------------------------------------------------------------------<br=
>
IETF IPv6 working group mailing list<br>
<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listinfo/i=
pv6" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/list=
info/ipv6</a><br>
--------------------------------------------------------------------<br>
<br></blockquote></div>

--001a114786c2dd7a2d052b015c3c--


From nobody Fri Feb  5 00:17:12 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 172521A03AA for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 00:17:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-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 3tQg4T1yKYuZ for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 00:17:09 -0800 (PST)
Received: from cowbell.employees.org (cowbell.employees.org [IPv6:2001:1868:a000:17::142]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 152AB1A03A1 for <ipv6@ietf.org>; Fri,  5 Feb 2016 00:16:39 -0800 (PST)
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 7B9A1D7882; Fri,  5 Feb 2016 00:16:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=U3K6KDRVFgNUS20tsdMHatS5K78=; b= accy4pdwgMKeB24X2NzHJ9VYF/ZXunPRZm38apphHg6AdW15moh50t+jn/8g7Dl4 lL2EVIJV30xynWhJLKLqg6AQOITOwOgC43KCp3WphOEMuMBKnkxE4HpC2vBe6TtY +fuZ/SugK4YN3BuEjJo1yP/m6o+djeKL2zS/PnNWQWg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=sYoh0aDn1uHcXT1yCN/SWXzwUS FpPTftU2aIewZ201ByAl3qqtXmuGUKHvE8eZxlGjtAR0eVMItcO3gsPA+NhAMm+S bUh1Vw5kSCZle4AqCHZzckIAi9Vf2ihD5mjF6XJtMOcHvyv1d4uIORrmHIx7NZiB FyMAMe1N53tNuDcmM=
Received: from h.hanazo.no (unknown [173.38.220.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 3E08CD7881; Fri,  5 Feb 2016 00:16:38 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id AB9F1107863C; Fri,  5 Feb 2016 09:16:42 +0100 (CET)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Content-Type: multipart/signed; boundary="Apple-Mail=_309586F3-915C-42E5-A3FB-27DEE8C90E1A"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <2134F8430051B64F815C691A62D983183395D25D@XCH-BLV-105.nw.nos.boeing.com>
Date: Fri, 5 Feb 2016 09:16:41 +0100
Message-Id: <F01DCA0F-BCBF-4CD3-BF2B-412EE2FDC19C@employees.org>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <2134F8430051B64F815C691A62D983183395D25D@XCH-BLV-105.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/P54gIquy74QlcaiECOc2pTZ6sqw>
Cc: "bob.hinden@gmail.com" <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 08:17:11 -0000

--Apple-Mail=_309586F3-915C-42E5-A3FB-27DEE8C90E1A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Fred,

> One question on the authorship - I can say with some certainty that =
Jack McCann
> and Jeff Mogul are no longer with Digital Equipment Corporation. Would =
they  be
> actively involved in this work if it is accepted as a working group =
item?

I don't expect them to be.
For the documents we're advancing to Internet Standard, and therefore =
only do very minor tweaks to, I think it makes most sense to keep the =
original authors. Unless they object.

Best regards,
Ole

>> -----Original Message-----
>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of =
otroan@employees.org
>> Sent: Wednesday, February 03, 2016 12:26 PM
>> To: 6man WG
>> Cc: bob.hinden@gmail.com
>> Subject: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
>>=20
>> This message starts a two week 6MAN call on adopting:
>>=20
>> Name:	draft-hinden-6man-rfc1981bis-01
>> Title:	Path MTU Discovery for IP version 6
>> Document date:	2015-12-01
>> Pages:	16
>> URL:         =
https://datatracker.ietf.org/doc/draft-hinden-6man-rfc1981bis/
>> Htmlized:  =
https://tools.ietf.org/html/draft-hinden-6man-rfc1981bis-01
>> Diff:          =
https://tools.ietf.org/rfcdiff?url2=3Ddraft-hinden-6man-rfc1981bis-01.txt
>>=20
>> as a working group item. Substantive comments and statements of =
support
>> for adopting this document should be directed to the mailing
>> list. Editorial suggestions can be sent to the authors.
>>=20
>> This document is part of the working group=E2=80=99s ongoing work on =
advancing the
>> core IPv6 standards to Internet Standard.
>>=20
>> This adoption call will end on February 17th, 2016.
>>=20
>> Regards,
>>=20
>> Bob Hinden & Ole Tr=C3=B8an
>=20


--Apple-Mail=_309586F3-915C-42E5-A3FB-27DEE8C90E1A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIcBAEBCgAGBQJWtFpqAAoJEL7aWKiYQt92s78P/iZZiiD+Hbs1t5AWBjUqBGP8
QYpxa/4bMbmD8/DzbJyBBOKfa4txo7YrqHcSjeSFh/jGsFAdrPgJKtWmC9dY3Q+9
iWZjeE/dMKMduU4pLPDSbUIOQ9Se6P8NUxNsCkaC/k3+YJbuF6dL7Kw7+gv3A1p0
cGHpBy91ntWc0SUDQwNFrQ8tsD5mg9TfAluiSOmlAbTWA3JBo2rKC25PXhYYhXbT
Owa5gOgYSK/psxZID6AQUIVwnFTf103okjZSHxwIQkiNXFmPqfyIhK6mFEAVin5l
tYNUnA4qcLU2Z/xB/EhtkxlZVnWbnAYvfALHbIea2NF75woKYAQqx2dkgL1+USmS
/ZNF663KaP01eS4UCMNthhBM/da54P6XekwlS5xFj68YLb2rGuDdhHvNneJiJSle
haLU+oJzefimyKro/lgi5tAorS704C2+aBjYtvx/e94nGZpMmRBBzWMWkWyLPLk8
MiHIVXDDmKEO+8cfurU9IX/aM+rKfwBbarHhdhxETNdfVKRDvjGkWxpA7kf/yWSH
ldHFjrtAOOPBsauAhDBfAeVzTNiQhUuNPdl3RI2tXjtQQyYCjRTyKzNzv7LSLVvP
Uby7z/ML1qc5UNy3HqnmFhsanmwR0e9TN8GCGhk7Ee4sHw4Bf3zSkdeCtYDoxtX5
mPjkO1F/tRB5l2C2/GkE
=mDJ0
-----END PGP SIGNATURE-----

--Apple-Mail=_309586F3-915C-42E5-A3FB-27DEE8C90E1A--


From nobody Fri Feb  5 03:12:12 2016
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C05E1A1EFC for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 03:12:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.982
X-Spam-Level: 
X-Spam-Status: No, score=-4.982 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5ANhXVWcmVrn for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 03:12:09 -0800 (PST)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E5DE1A1EFA for <ipv6@ietf.org>; Fri,  5 Feb 2016 03:12:09 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u15BC7wf007507 for <ipv6@ietf.org>; Fri, 5 Feb 2016 12:12:07 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id ADEBD204710 for <ipv6@ietf.org>; Fri,  5 Feb 2016 12:20:16 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id A2E93204703 for <ipv6@ietf.org>; Fri,  5 Feb 2016 12:20:16 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u15BC6bd032547 for <ipv6@ietf.org>; Fri, 5 Feb 2016 12:12:06 +0100
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: ipv6@ietf.org
Message-ID: <56B48386.2040300@gmail.com>
Date: Fri, 5 Feb 2016 12:12:06 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------010606070809000008010809"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/D8L4jXm9-NxFV2soDyhuLNtVSJY>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 11:12:11 -0000

This is a multi-part message in MIME format.
--------------010606070809000008010809
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hello 6manners,

draft-ietf-6man-default-iids-09 rightfully indicates that the same IID 
should not be used in the LL and GUA addresses of a same interface.  
Because there may be a risk of correlation between addresses by a snooper.

The draft says:
   The negotiated interface identifier is used by the local end of the
   PPP link to autoconfigure an IPv6 link-local unicast address for the
   PPP interface.  However, it SHOULD NOT be assumed that the same
   interface identifier is used in configuring global unicast addresses
   for the PPP interface using IPv6 stateless address autoconfiguration
   [3].

But what does it mean "it SHOULD NOT be assumed"?  Who should not 
assume?  I think the text should rather say: "a same IID should not be 
used for several different scoped addresses of a same interface because 
snoopers may correlated them".

I am asking because I just realized that a cellular ptp link on linux 
3.4 yocto has this risk: it puts the same ppp-negotiated IID on both its 
LL and its GUA (and it adds a 2nd IID to a 2nd GUA - the 'privacy').  I 
guess it is so because the implementer does not understand "it SHOULD 
NOT be assumed"...

Paradoxically that linux _is_ 'privacy' (it has random addresses instead 
of MAC-based addresses) but still has privacy risks (same IID on a GUA 
and its LL).

And what is [3]?  I guess the brackets should be escaped somehow 
otherwise looking at the list of References in this draft there is no [3].

Alex


--------------010606070809000008010809
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <font face="Courier New">Hello 6manners,<br>
      <br>
      draft-ietf-6man-default-iids-09 rightfully indicates that the same
      IID should not be used in the LL and GUA addresses of a same
      interface.Â  Because there may be a risk of correlation between
      addresses by a snooper.<br>
      <br>
      The draft says:<br>
      Â  The negotiated interface identifier is used by the local end of
      the<br>
      Â  PPP link to autoconfigure an IPv6 link-local unicast address for
      the<br>
      Â  PPP interface.Â  However, it SHOULD NOT be assumed that the same<br>
      Â  interface identifier is used in configuring global unicast
      addresses<br>
      Â  for the PPP interface using IPv6 stateless address
      autoconfiguration<br>
      Â  [3].<br>
      <br>
      But what does it mean "it SHOULD NOT be assumed"?Â  Who should not
      assume?Â  I think the text should rather say: "a same IID should
      not be used for several different scoped addresses of a same
      interface because snoopers may correlated them".<br>
      <br>
      I am asking because I just realized that a cellular ptp link on
      linux 3.4 yocto has this risk: it puts the same ppp-negotiated IID
      on both its LL and its GUA (and it adds a 2nd IID to a 2nd GUA -
      the 'privacy').Â  I guess it is so because the implementer does not
      understand "it SHOULD NOT be assumed"...<br>
      <br>
      Paradoxically that linux _is_ 'privacy' (it has random addresses
      instead of MAC-based addresses) but still has privacy risks (same
      IID on a GUA and its LL).<br>
      <br>
      And what is [3]?Â  I guess the brackets should be escaped somehow
      otherwise looking at the list of References in this draft there is
      no [3].<br>
      <br>
      Alex<br>
      <br>
    </font>
  </body>
</html>

--------------010606070809000008010809--


From nobody Fri Feb  5 03:27:34 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB5831A3B9D for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 03:27:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-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 LdSHFFVz9C0v for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 03:27:30 -0800 (PST)
Received: from cowbell.employees.org (cowbell.employees.org [65.50.211.142]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD4821A3B9C for <ipv6@ietf.org>; Fri,  5 Feb 2016 03:27:30 -0800 (PST)
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 49687D7881; Fri,  5 Feb 2016 03:27:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=EdPGkax/KXyvLLlsUD79pvRtVhY=; b= J5P1MYYQTpvW/sVYN6xSNi/6hNAiDj6gjOecDsOGOjARRq+Z1N+CL+Sya4pZ+qBj icrJG99BEVYxC059pPgH7GwVFM69HAxEWZU6Kh2aYo4kkOGXbb+9aHcPKc3ooCZP CQ90XxL6gDJtLs/sh5/MgTO3yfTMHgqtfUE2nqSF1KM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=k6Mu8BBTyaqHmpJ41FS4ztP3d5 SY3xvzM1mLLql5a4DUveP3uopUxJZlSAtC11k0oCwXFoe7i/6DBZ4MLeRBOLpxab UnpbG4i4Sux97GmbcQjen0hvhvqxVKkeVkJE3UlW6rH10EQKPM6fs4XZ03vxw4t/ 2TL0vkaAO+vTn02xI=
Received: from h.hanazo.no (unknown [173.38.220.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 0ACF4D7882; Fri,  5 Feb 2016 03:27:29 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 9F528107F7D8; Fri,  5 Feb 2016 12:27:21 +0100 (CET)
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Content-Type: multipart/signed; boundary="Apple-Mail=_2BCC824D-5B70-498D-83C4-E6E6D2BF8DB6"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <56B48386.2040300@gmail.com>
Date: Fri, 5 Feb 2016 12:27:20 +0100
Message-Id: <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org>
References: <56B48386.2040300@gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/U2vU95Aixu--qqaMjVDRLeM7zFU>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 11:27:32 -0000

--Apple-Mail=_2BCC824D-5B70-498D-83C4-E6E6D2BF8DB6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Alex,

> draft-ietf-6man-default-iids-09 rightfully indicates that the same IID =
should not be used in the LL and GUA addresses of a same interface.  =
Because there may be a risk of correlation between addresses by a =
snooper.
>=20
> The draft says:
>   The negotiated interface identifier is used by the local end of the
>   PPP link to autoconfigure an IPv6 link-local unicast address for the
>   PPP interface.  However, it SHOULD NOT be assumed that the same
>   interface identifier is used in configuring global unicast addresses
>   for the PPP interface using IPv6 stateless address autoconfiguration
>   [3].
>=20
> But what does it mean "it SHOULD NOT be assumed"?  Who should not =
assume?  I think the text should rather say: "a same IID should not be =
used for several different scoped addresses of a same interface because =
snoopers may correlated them".
>=20
> I am asking because I just realized that a cellular ptp link on linux =
3.4 yocto has this risk: it puts the same ppp-negotiated IID on both its =
LL and its GUA (and it adds a 2nd IID to a 2nd GUA - the 'privacy').  I =
guess it is so because the implementer does not understand "it SHOULD =
NOT be assumed"...
>=20
> Paradoxically that linux _is_ 'privacy' (it has random addresses =
instead of MAC-based addresses) but still has privacy risks (same IID on =
a GUA and its LL).
>=20
> And what is [3]?  I guess the brackets should be escaped somehow =
otherwise looking at the list of References in this draft there is no =
[3].

What is the risk of using the same IID for link-local and global =
addresses?
Typically if you can snoop the link-local address then you're onlink and =
leak information about all addresses and their correlations anyway.

cheers,
Ole

--Apple-Mail=_2BCC824D-5B70-498D-83C4-E6E6D2BF8DB6
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIcBAEBCgAGBQJWtIcZAAoJEL7aWKiYQt920XwQALa3ZS+jWxP2lxp+yK5MbYRc
BTgLA1Fm4Z1SJcbg6u1bsnoFCh9fOUnaBs4p4jCtwynGB2/fBwrq4JDwZQsnc+IG
DYxBMWrOsai3jQuTAwFswCgi1dolB6kC6cXCQU5KAMW6aNFSyWN2o4S5X5B4sUUu
sURq/d8DM82TVnOebrRDBxXBswj/YiXJWMMeK0993xrBHTmQ9r7VVpnUeqF5lmD4
so9zUSOuxkEIOydwa09j90wG68KlpXW9816aCfGagADa7Ulah4v9nIPpPFKB1CAg
YzXW/Wq84X1H08G6XBNUtLYPGxHHAsuHmGZJK/Q7ITVHUN5yWTRjQs/aMLLtK+5r
NJy1ZtIT/4awzAVpMigtPfSSV4cFINCkMD9nd23Y8VA2mnSpeMPjH0/hjGoBiU04
Es5UARMLa7HOMYkeKd/3KdWHNGmbmBG5gpmVyoATddvf0Zc6tIWjbh/oPj0LTcpP
Yiz0C6yiO5Xuzlx3eGU6yN/EZwxH3/xfIvlwh00GXZNcPNTABVc9vXZGabLDqPU6
s0z5H0zwCL7m40FKxlA5ag+PcspqWpwprsQx7OlyYmDGTBhn3+AqQpuO2RDrm+I2
WL6bPDEmK42wK2KIRs5TXxuK2MmlC5+9t7rjwCGoZgDehkzfw7YMC8xt7oZyA4oj
UIdUGiL2bJje+CoRwHxY
=nK9Z
-----END PGP SIGNATURE-----

--Apple-Mail=_2BCC824D-5B70-498D-83C4-E6E6D2BF8DB6--


From nobody Fri Feb  5 03:40:04 2016
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 033FF1A6F3F for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 03:40:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.222
X-Spam-Level: 
X-Spam-Status: No, score=-1.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, 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 BNJOcKTwXWkb for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 03:40:00 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 832DE1A6F3E for <ipv6@ietf.org>; Fri,  5 Feb 2016 03:40:00 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u15Bde64012464; Fri, 5 Feb 2016 11:39:40 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u15Bde64012464
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1454672380; bh=W3KFw2a5Vud5ZJQCAW94btSZOLc=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=UW9k1yCN7a4lKtBOlahpeXPPmWleqoCXycg9HPD8gheqNYprMqDMR3sxfv4suT8Xs EURnx/hjvt7B2ejTPeiuR19DQSJr6UJVKpQF8P5qtawLy9MFEEXh5a4tKxL4mZtGqg Nw7WbeEI8AjMwL7M1C2C/hxXLDNRcVGC0NcCWNnE=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s14Bdd21329038561z ret-id none; Fri, 05 Feb 2016 11:39:40 +0000
Received: from [192.168.0.10] (tchowndsl.claranet.co.uk [212.188.254.49]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u15BdZiQ001287 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Feb 2016 11:39:36 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <A24F9E2D-3F56-4B1A-93C9-7F7BC62C6DF2@employees.org>
Date: Fri, 5 Feb 2016 11:39:35 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|0b482edb69610bd02f9fc594a5a3cc18s14Bdd03tjc|ecs.soton.ac.uk|B6942F56-09C7-42D7-9571-244BB61E45F6@ecs.soton.ac.uk>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com> <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395DEF3@XCH-BLV-105.nw.nos.boeing.com> <8E7CAC70-9193-43B2-8A47-0C731B5464CA@cisco.com> <2134F8430051B64F815C691A62D983183395DFFF@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395E016@XCH-BLV-105.nw.nos.boeing.com> <A24F9E2D-3F56-4B1A-93C9-7F7BC62C6DF2@employees.org> <B6942F56-09C7-42D7-9571-244BB61E45F6@ecs.soton.ac.uk>
To: otroan@employees.org
X-Mailer: Apple Mail (2.3112)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s14Bdd213290385600; tid=s14Bdd21329038561z; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=5:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u15Bde64012464
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/vzVqJB0nU82VreY5LX2xp81UYik>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 11:40:03 -0000

> On 5 Feb 2016, at 08:04, otroan@employees.org wrote:
>=20
> Fred,
>=20
>>=20
>> I will make one other change recommendation:
>>=20
>> OLD:
>> It defines a method for Packetization Layer Path MTU Discovery =
(PLPMTUD)
>> designed for use in environments in which delivery of accurate ICMP =
messages
>> to a host are not assured.
>>=20
>> NEW:
>> It defines a method for Packetization Layer Path MTU Discovery =
(PLPMTUD)
>> designed for use over paths for which delivery of accurate ICMP =
messages
>> to a host are not assured.
>=20
> I would posit that there are no such paths. "accurate" ICMP can never =
be guaranteed.

Indeed.  And perhaps for =E2=80=98accurate=E2=80=99 read =E2=80=98reliable=
 and/or trustworthy=E2=80=99.

Tim

>=20
> Best regards,
> Ole
>=20
>>> -----Original Message-----
>>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Templin, Fred =
L
>>> Sent: Thursday, February 04, 2016 10:59 AM
>>> To: Fred Baker (fred)
>>> Cc: 6man WG; Bob Hinden
>>> Subject: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
>>>=20
>>> Hi Fred,
>>>=20
>>>> -----Original Message-----
>>>> From: Fred Baker (fred) [mailto:fred@cisco.com]
>>>> Sent: Thursday, February 04, 2016 10:50 AM
>>>> To: Templin, Fred L
>>>> Cc: Bob Hinden; 6man WG
>>>> Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
>>>>=20
>>>>=20
>>>>> On Feb 4, 2016, at 10:37 AM, Templin, Fred L =
<Fred.L.Templin@boeing.com> wrote:
>>>>>=20
>>>>> Your text could be modified by simply adding the word "accurate" =
as follows:
>>>>>=20
>>>>> "It defines a method for Packetization Layer Path MTU Discovery =
(PLPMTUD)
>>>>>  designed for use in environments in which delivery of accurate =
ICMP messages
>>>>>  to a host are not assured."
>>>>=20
>>>> So you added the word "accurate". Anything else?
>>>>=20
>>>> My question would be what makes an ICMP "accurate", and how the =
host might or might not determine accuracy. As near as I can
>>> tell,
>>>> RFC 1981 says that if a host receives an ICMP Packet Too Big, it =
should make the packet smaller. If the ICMP has been spoofed,
>>> unless
>>>> the spoofer has done something really egregious, I don't know how =
the receiving host would know that.
>>>=20
>>> ICMP spoofing is exactly the point. But, it is not up to the host to =
determine
>>> whether an ICMP is accurate - it is up to the host to determine =
whether it is
>>> in an environment in which delivery of accurate ICMP messages is not =
assured.
>>>=20
>>>> Given that, I don't think the wording change helps.
>>>=20
>>> Without "accurate", the text does not address failure mode 2).
>>>=20
>>> Thanks - Fred
>>> fred.l.templin@boeing.com
>>>=20
>>> --------------------------------------------------------------------
>>> IETF IPv6 working group mailing list
>>> ipv6@ietf.org
>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>> --------------------------------------------------------------------
>>=20
>>=20
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Fri Feb  5 04:34:33 2016
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 663121B37CA for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 04:34:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fGEbcCQvAn1Z for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 04:34:29 -0800 (PST)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DABB1B37C5 for <ipv6@ietf.org>; Fri,  5 Feb 2016 04:34:29 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u15CYPjS022993; Fri, 5 Feb 2016 13:34:25 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id CAA27204731; Fri,  5 Feb 2016 13:42:34 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id BEF33202AB0; Fri,  5 Feb 2016 13:42:34 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u15CYOxh007250; Fri, 5 Feb 2016 13:34:24 +0100
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: otroan@employees.org
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <56B496D0.2090203@gmail.com>
Date: Fri, 5 Feb 2016 13:34:24 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/1NPy8Bv9TYrZAOM_cWDsjLtqwOM>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 12:34:31 -0000

Le 05/02/2016 12:27, otroan@employees.org a écrit :
> Alex,
>
>> draft-ietf-6man-default-iids-09 rightfully indicates that the same IID should not be used in the LL and GUA addresses of a same interface.  Because there may be a risk of correlation between addresses by a snooper.
>>
>> The draft says:
>>    The negotiated interface identifier is used by the local end of the
>>    PPP link to autoconfigure an IPv6 link-local unicast address for the
>>    PPP interface.  However, it SHOULD NOT be assumed that the same
>>    interface identifier is used in configuring global unicast addresses
>>    for the PPP interface using IPv6 stateless address autoconfiguration
>>    [3].
>>
>> But what does it mean "it SHOULD NOT be assumed"?  Who should not assume?  I think the text should rather say: "a same IID should not be used for several different scoped addresses of a same interface because snoopers may correlated them".
>>
>> I am asking because I just realized that a cellular ptp link on linux 3.4 yocto has this risk: it puts the same ppp-negotiated IID on both its LL and its GUA (and it adds a 2nd IID to a 2nd GUA - the 'privacy').  I guess it is so because the implementer does not understand "it SHOULD NOT be assumed"...
>>
>> Paradoxically that linux _is_ 'privacy' (it has random addresses instead of MAC-based addresses) but still has privacy risks (same IID on a GUA and its LL).
>>
>> And what is [3]?  I guess the brackets should be escaped somehow otherwise looking at the list of References in this draft there is no [3].
>
> What is the risk of using the same IID for link-local and global addresses?

I think any correlation risk is worth considering.

In the cellular ptp links there are no MAC addresses in MAC headers; so 
the LL addresses provide great opportunity to track devices.  And if the 
device (LL) has the same address as the application (GUA) then one can 
tell which device consulted which website, for example.

On another hand, if the device had a different address than the app, 
then it would be difficult to say what device consulted what website.

> Typically if you can snoop the link-local address then you're onlink and leak information about all addresses and their correlations anyway.

On a wifi link yes you are onlink, but ptp links are more complex.  A 
p2p link like in cellular extends to actually 2 or 3 different links in 
sequence, from UE to GGSN for example.  This makes for as many 
opportunities to snoop the LL and GUA address even though not the 
snooper is not on the same link (i.e. the snooper can be on the Ethernet 
between a GGSN and a eNodeB, or on one of those, and not be on the air 
between UE and eNodeB).

In all cases, 'privacy' addresses (containing random IIDs rather than 
derived from the constant MAC address) are useful _only_ if there are no 
other GUA addresses on the device which can lead to some form of 
correlation.

Because rarely the applications have the ability to select a specific 
address (i.e. rarely an app can decide to use a privacy address rather 
than an address containing a MAC-derived IID).  So the only means to 
offer privacy to apps is the computer to have only one GUA and that GUA 
to contain a randomly defined IID, and different than the IID in the LL 
address.

Alex

>
> cheers,
> Ole
>


From nobody Fri Feb  5 04:52:24 2016
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 609F31B3815 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 04:52:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ccLaw7_xJTcW for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 04:52:20 -0800 (PST)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13AF71B3817 for <ipv6@ietf.org>; Fri,  5 Feb 2016 04:52:19 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u15CqHEp004776 for <ipv6@ietf.org>; Fri, 5 Feb 2016 13:52:17 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 55547204780 for <ipv6@ietf.org>; Fri,  5 Feb 2016 14:00:27 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 4BD1B2034B0 for <ipv6@ietf.org>; Fri,  5 Feb 2016 14:00:27 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u15CqH5Y017239 for <ipv6@ietf.org>; Fri, 5 Feb 2016 13:52:17 +0100
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: ipv6@ietf.org
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B496D0.2090203@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <56B49B01.8080905@gmail.com>
Date: Fri, 5 Feb 2016 13:52:17 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B496D0.2090203@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Sw6LkIQZU9w4eBItWL87g0BU1Ek>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 12:52:22 -0000

Let me re-phrase shortly: the problem is to consider the issue to be the 
MAC-derived IIDs, whereas that is not the only issue - the linux issue 
is the GUAs derived from LLs not from MAC (even from LLs which are not 
MAC-derived, but ppp-derived), or the IIDs derived from ppp.

I guess a problem statement may make things clearer.  If we had a 
problem statement which said that the problem is IPv6 addresses derived 
from other addresses (e.g. MAC, LL, PPP-IID) then the abstract of this 
draft should say:

> recommends against embedding identifiers isomorhply derived from other addresses, or dictated by other servers,
> in IPv6 Interface Identifiers.

rather than:
> recommends against embedding link-layer addresses in IPv6 Interface
>    Identifiers.

(the interface ID negotiated during the ppp phase is _not_ a link layer 
address;  it is not used like a MAC address in MAC headers, it does not 
address anything; it is an interface ID dictated by the server to the 
client for use in the addresses, optionally 'negotiated' but never seen 
such a negotiation taking place).

Alex

Le 05/02/2016 13:34, Alexandre Petrescu a écrit :
>
>
> Le 05/02/2016 12:27, otroan@employees.org a écrit :
>> Alex,
>>
>>> draft-ietf-6man-default-iids-09 rightfully indicates that the same
>>> IID should not be used in the LL and GUA addresses of a same
>>> interface.  Because there may be a risk of correlation between
>>> addresses by a snooper.
>>>
>>> The draft says:
>>>    The negotiated interface identifier is used by the local end of the
>>>    PPP link to autoconfigure an IPv6 link-local unicast address for the
>>>    PPP interface.  However, it SHOULD NOT be assumed that the same
>>>    interface identifier is used in configuring global unicast addresses
>>>    for the PPP interface using IPv6 stateless address autoconfiguration
>>>    [3].
>>>
>>> But what does it mean "it SHOULD NOT be assumed"?  Who should not
>>> assume?  I think the text should rather say: "a same IID should not
>>> be used for several different scoped addresses of a same interface
>>> because snoopers may correlated them".
>>>
>>> I am asking because I just realized that a cellular ptp link on linux
>>> 3.4 yocto has this risk: it puts the same ppp-negotiated IID on both
>>> its LL and its GUA (and it adds a 2nd IID to a 2nd GUA - the
>>> 'privacy').  I guess it is so because the implementer does not
>>> understand "it SHOULD NOT be assumed"...
>>>
>>> Paradoxically that linux _is_ 'privacy' (it has random addresses
>>> instead of MAC-based addresses) but still has privacy risks (same IID
>>> on a GUA and its LL).
>>>
>>> And what is [3]?  I guess the brackets should be escaped somehow
>>> otherwise looking at the list of References in this draft there is no
>>> [3].
>>
>> What is the risk of using the same IID for link-local and global
>> addresses?
>
> I think any correlation risk is worth considering.
>
> In the cellular ptp links there are no MAC addresses in MAC headers; so
> the LL addresses provide great opportunity to track devices.  And if the
> device (LL) has the same address as the application (GUA) then one can
> tell which device consulted which website, for example.
>
> On another hand, if the device had a different address than the app,
> then it would be difficult to say what device consulted what website.
>
>> Typically if you can snoop the link-local address then you're onlink
>> and leak information about all addresses and their correlations anyway.
>
> On a wifi link yes you are onlink, but ptp links are more complex.  A
> p2p link like in cellular extends to actually 2 or 3 different links in
> sequence, from UE to GGSN for example.  This makes for as many
> opportunities to snoop the LL and GUA address even though not the
> snooper is not on the same link (i.e. the snooper can be on the Ethernet
> between a GGSN and a eNodeB, or on one of those, and not be on the air
> between UE and eNodeB).
>
> In all cases, 'privacy' addresses (containing random IIDs rather than
> derived from the constant MAC address) are useful _only_ if there are no
> other GUA addresses on the device which can lead to some form of
> correlation.
>
> Because rarely the applications have the ability to select a specific
> address (i.e. rarely an app can decide to use a privacy address rather
> than an address containing a MAC-derived IID).  So the only means to
> offer privacy to apps is the computer to have only one GUA and that GUA
> to contain a randomly defined IID, and different than the IID in the LL
> address.
>
> Alex
>
>>
>> cheers,
>> Ole
>>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From nobody Fri Feb  5 05:03:16 2016
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C41401B3839 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 05:03:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 7rcQCuhKTZkL for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 05:03:12 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30FD91B383D for <ipv6@ietf.org>; Fri,  5 Feb 2016 05:03:12 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 0C4528816C for <ipv6@ietf.org>; Fri,  5 Feb 2016 05:03:12 -0800 (PST)
Received: from clemson.jhuapl.edu (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id C1BA2328081A for <ipv6@ietf.org>; Fri,  5 Feb 2016 05:03:11 -0800 (PST)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
To: ipv6@ietf.org
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <2134F8430051B64F815C691A62D983183395D25D@XCH-BLV-105.nw.nos.boeing.com> <F01DCA0F-BCBF-4CD3-BF2B-412EE2FDC19C@employees.org>
From: Brian Haberman <brian@innovationslab.net>
Message-ID: <56B49D89.5050202@innovationslab.net>
Date: Fri, 5 Feb 2016 08:03:05 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <F01DCA0F-BCBF-4CD3-BF2B-412EE2FDC19C@employees.org>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="9IAgsF8QOU8cWgw9EjHxC6RtN5evasf9G"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/rOZdRuNkFKFX04MVnlIVJK1T_j0>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 13:03:14 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--9IAgsF8QOU8cWgw9EjHxC6RtN5evasf9G
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

All,

On 2/5/16 3:16 AM, otroan@employees.org wrote:
> Fred,
>=20
>> One question on the authorship - I can say with some certainty that
>> Jack McCann and Jeff Mogul are no longer with Digital Equipment
>> Corporation. Would they  be actively involved in this work if it is
>> accepted as a working group item?
>=20
> I don't expect them to be. For the documents we're advancing to
> Internet Standard, and therefore only do very minor tweaks to, I
> think it makes most sense to keep the original authors. Unless they
> object.

Um, no. The original authors stay on the draft because they are the ones
responsible for most of the text within the document. Accurate
representation of authorship is critical for many reasons (e.g., IPR).

Regards,
Brian

>=20
> Best regards, Ole
>=20
>>> -----Original Message----- From: ipv6
>>> [mailto:ipv6-bounces@ietf.org] On Behalf Of otroan@employees.org=20
>>> Sent: Wednesday, February 03, 2016 12:26 PM To: 6man WG Cc:
>>> bob.hinden@gmail.com Subject: 6MAN: Adoption call on
>>> draft-hinden-6man-rfc1981bis-01
>>>=20
>>> This message starts a two week 6MAN call on adopting:
>>>=20
>>> Name:	draft-hinden-6man-rfc1981bis-01 Title:	Path MTU Discovery
>>> for IP version 6 Document date:	2015-12-01 Pages:	16 URL:
>>> https://datatracker.ietf.org/doc/draft-hinden-6man-rfc1981bis/=20
>>> Htmlized:
>>> https://tools.ietf.org/html/draft-hinden-6man-rfc1981bis-01 Diff:
>>> https://tools.ietf.org/rfcdiff?url2=3Ddraft-hinden-6man-rfc1981bis-01=
=2Etxt
>>>
>>>
>>>=20
as a working group item. Substantive comments and statements of support
>>> for adopting this document should be directed to the mailing=20
>>> list. Editorial suggestions can be sent to the authors.
>>>=20
>>> This document is part of the working group=92s ongoing work on
>>> advancing the core IPv6 standards to Internet Standard.
>>>=20
>>> This adoption call will end on February 17th, 2016.
>>>=20
>>> Regards,
>>>=20
>>> Bob Hinden & Ole Tr=F8an
>>=20
>=20
>=20
>=20
> --------------------------------------------------------------------=20
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6=20
> --------------------------------------------------------------------
>=20


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2

iQEcBAEBCAAGBQJWtJ2OAAoJEBOZRqCi7goqJ8sH/iJ9AY+V1VpuAmyJZstVSSWy
rHiCrWWTuyY9GvUVqACnNCMwaLsTpIdO/8htD+a49fIYeW8RThNNnT+6ykV7nxA9
Mnmz2QZdKfYboSbwo2pMgIh4mCNLYG9Yzwco/WXSCAEoqVQo5F/aMnXhsqwXP/00
Tw+UeRucnpPVWaAVG0Ueldsa1ysnkB0WZ2L8SqzuzdGRwrVH0L60TG6ptmt/YMuY
mS/uGonYI7oVnhaj5EI6Rs7K1c5WpxQVoirT8xnbsh9pdqGXFcHPhlyrRq78XS/O
XXPDcz6i2nx2V/ZkXgx1XgeAQ5wxA2x1t3Au9aiolzf3yDjW00XyLn0AjxEBuoU=
=b8qK
-----END PGP SIGNATURE-----

--9IAgsF8QOU8cWgw9EjHxC6RtN5evasf9G--


From nobody Fri Feb  5 05:20:03 2016
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4FFA1B3893 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 05:20:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.222
X-Spam-Level: 
X-Spam-Status: No, score=-1.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, 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 vVdEuKDg6lne for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 05:20:01 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B1771B3892 for <ipv6@ietf.org>; Fri,  5 Feb 2016 05:20:00 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u15DJoeJ003186; Fri, 5 Feb 2016 13:19:50 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u15DJoeJ003186
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1454678391; bh=UWYPU5HA0sBZdDJAPgBruDcz9Io=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=fo9XWtFRz1E8L7f7aybltGqWtATIJtbKccjrYwsQRoMH6mQ3Kg3TQjvORTvZ/gbm4 0luavw3J+pVyxqrIUJSCP6qfbeV0kshEP0+PYTaxFKFfzOEULPSgRHUymXHwAvphTB mJlXal3reHn70weZB3XHQlZpORPXah4pesutyu2o=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s14DJo2132905313Me ret-id none; Fri, 05 Feb 2016 13:19:50 +0000
Received: from [192.168.0.10] (tchowndsl.claranet.co.uk [212.188.254.49]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u15DIVxN025433 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Feb 2016 13:18:31 GMT
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <56B49D89.5050202@innovationslab.net>
Date: Fri, 5 Feb 2016 13:18:30 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|311fe9a498c78ae917296ce75ee0f260s14DJo03tjc|ecs.soton.ac.uk|167D1485-EEF0-4EAA-9A6D-3FFF351C6D6E@ecs.soton.ac.uk>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <2134F8430051B64F815C691A62D983183395D25D@XCH-BLV-105.nw.nos.boeing.com> <F01DCA0F-BCBF-4CD3-BF2B-412EE2FDC19C@employees.org> <56B49D89.5050202@innovationslab.net> <167D1485-EEF0-4EAA-9A6D-3FFF351C6D6E@ecs.soton.ac.uk>
To: Brian Haberman <brian@innovationslab.net>
X-Mailer: Apple Mail (2.3112)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s14DJo213290531300; tid=s14DJo2132905313Me; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u15DJoeJ003186
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/hLrwznSe8xTIPutOdHnI2nqrnBw>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 13:20:03 -0000

> On 5 Feb 2016, at 13:03, Brian Haberman <brian@innovationslab.net> =
wrote:
>=20
> All,
>=20
> On 2/5/16 3:16 AM, otroan@employees.org wrote:
>> Fred,
>>=20
>>> One question on the authorship - I can say with some certainty that
>>> Jack McCann and Jeff Mogul are no longer with Digital Equipment
>>> Corporation. Would they  be actively involved in this work if it is
>>> accepted as a working group item?
>>=20
>> I don't expect them to be. For the documents we're advancing to
>> Internet Standard, and therefore only do very minor tweaks to, I
>> think it makes most sense to keep the original authors. Unless they
>> object.
>=20
> Um, no. The original authors stay on the draft because they are the =
ones
> responsible for most of the text within the document. Accurate
> representation of authorship is critical for many reasons (e.g., IPR).

RFC 4861 is a good example, where Hesham was added to the original=20
authors as the collator of edits. There=92s also an Appendix listing the =
changes
in RFC 4861, which we should probably have here too.

Tim

>=20
> Regards,
> Brian
>=20
>>=20
>> Best regards, Ole
>>=20
>>>> -----Original Message----- From: ipv6
>>>> [mailto:ipv6-bounces@ietf.org] On Behalf Of otroan@employees.org=20
>>>> Sent: Wednesday, February 03, 2016 12:26 PM To: 6man WG Cc:
>>>> bob.hinden@gmail.com Subject: 6MAN: Adoption call on
>>>> draft-hinden-6man-rfc1981bis-01
>>>>=20
>>>> This message starts a two week 6MAN call on adopting:
>>>>=20
>>>> Name:	draft-hinden-6man-rfc1981bis-01 Title:	Path MTU =
Discovery
>>>> for IP version 6 Document date:	2015-12-01 Pages:	16 URL:
>>>> https://datatracker.ietf.org/doc/draft-hinden-6man-rfc1981bis/=20
>>>> Htmlized:
>>>> https://tools.ietf.org/html/draft-hinden-6man-rfc1981bis-01 Diff:
>>>> =
https://tools.ietf.org/rfcdiff?url2=3Ddraft-hinden-6man-rfc1981bis-01.txt
>>>>=20
>>>>=20
>>>>=20
> as a working group item. Substantive comments and statements of =
support
>>>> for adopting this document should be directed to the mailing=20
>>>> list. Editorial suggestions can be sent to the authors.
>>>>=20
>>>> This document is part of the working group=92s ongoing work on
>>>> advancing the core IPv6 standards to Internet Standard.
>>>>=20
>>>> This adoption call will end on February 17th, 2016.
>>>>=20
>>>> Regards,
>>>>=20
>>>> Bob Hinden & Ole Tr=F8an
>>>=20
>>=20
>>=20
>>=20
>> --------------------------------------------------------------------=20=

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


From nobody Fri Feb  5 07:55:23 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D73041B3AD8 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 07:55:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 bwSJaLkeh6WS for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 07:55:20 -0800 (PST)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) (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 969C71B313F for <ipv6@ietf.org>; Fri,  5 Feb 2016 07:55:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u15FtHJq002507; Fri, 5 Feb 2016 09:55:17 -0600
Received: from XCH-BLV-103.nw.nos.boeing.com (xch-blv-103.nw.nos.boeing.com [130.247.25.118]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u15FtDM0002496 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 5 Feb 2016 09:55:14 -0600
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-BLV-103.nw.nos.boeing.com ([169.254.3.127]) with mapi id 14.03.0235.001; Fri, 5 Feb 2016 07:55:13 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "otroan@employees.org" <otroan@employees.org>
Subject: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AQHRX2tT80dfpGCQDUCIhA2edhybgJ8cKO6QgAAMGWCAAIvjAP//enWAgAACgkCAAWD8gP//+8Eg
Date: Fri, 5 Feb 2016 15:55:13 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395ECCA@XCH-BLV-105.nw.nos.boeing.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com> <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395DEF3@XCH-BLV-105.nw.nos.boeing.com> <8E7CAC70-9193-43B2-8A47-0C731B5464CA@cisco.com> <2134F8430051B64F815C691A62D983183395DFFF@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395E016@XCH-BLV-105.nw.nos.boeing.com> <A24F9E2D-3F56-4B1A-93C9-7F7BC62C6DF2@employees.org>
In-Reply-To: <A24F9E2D-3F56-4B1A-93C9-7F7BC62C6DF2@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/d6if8ucvEXyzV7ggiOThA-V5DDk>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 15:55:23 -0000

Hi Ole,

> -----Original Message-----
> From: otroan@employees.org [mailto:otroan@employees.org]
> Sent: Friday, February 05, 2016 12:04 AM
> To: Templin, Fred L
> Cc: Fred Baker (fred); Bob Hinden; 6man WG
> Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
>=20
> Fred,
>=20
> >
> > I will make one other change recommendation:
> >
> > OLD:
> > It defines a method for Packetization Layer Path MTU Discovery (PLPMTUD=
)
> > designed for use in environments in which delivery of accurate ICMP mes=
sages
> > to a host are not assured.
> >
> > NEW:
> > It defines a method for Packetization Layer Path MTU Discovery (PLPMTUD=
)
> > designed for use over paths for which delivery of accurate ICMP message=
s
> > to a host are not assured.
>=20
> I would posit that there are no such paths. "accurate" ICMP can never be =
guaranteed.

Forgetting the word "accurate" for the moment, it is reasonable to
expect that paths that begin and end within the same well-managed
administrative domain can be counted on to deliver the necessary
ICMPs and to not deliver bogus ICMPs. Paths that lead to Internet
destinations on the other hand cannot.

If we do not believe that there are paths for which traditional PMTUD
can still be used safely, then we should be working to deprecate
RFC1981 instead of making it a standard.

Thanks - Fred
fred.l.templin@boeing.com

> Best regards,
> Ole
>=20
> >> -----Original Message-----
> >> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Templin, Fred L
> >> Sent: Thursday, February 04, 2016 10:59 AM
> >> To: Fred Baker (fred)
> >> Cc: 6man WG; Bob Hinden
> >> Subject: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
> >>
> >> Hi Fred,
> >>
> >>> -----Original Message-----
> >>> From: Fred Baker (fred) [mailto:fred@cisco.com]
> >>> Sent: Thursday, February 04, 2016 10:50 AM
> >>> To: Templin, Fred L
> >>> Cc: Bob Hinden; 6man WG
> >>> Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
> >>>
> >>>
> >>>> On Feb 4, 2016, at 10:37 AM, Templin, Fred L <Fred.L.Templin@boeing.=
com> wrote:
> >>>>
> >>>> Your text could be modified by simply adding the word "accurate" as =
follows:
> >>>>
> >>>> "It defines a method for Packetization Layer Path MTU Discovery (PLP=
MTUD)
> >>>>   designed for use in environments in which delivery of accurate ICM=
P messages
> >>>>   to a host are not assured."
> >>>
> >>> So you added the word "accurate". Anything else?
> >>>
> >>> My question would be what makes an ICMP "accurate", and how the host =
might or might not determine accuracy. As near as I can
> >> tell,
> >>> RFC 1981 says that if a host receives an ICMP Packet Too Big, it shou=
ld make the packet smaller. If the ICMP has been spoofed,
> >> unless
> >>> the spoofer has done something really egregious, I don't know how the=
 receiving host would know that.
> >>
> >> ICMP spoofing is exactly the point. But, it is not up to the host to d=
etermine
> >> whether an ICMP is accurate - it is up to the host to determine whethe=
r it is
> >> in an environment in which delivery of accurate ICMP messages is not a=
ssured.
> >>
> >>> Given that, I don't think the wording change helps.
> >>
> >> Without "accurate", the text does not address failure mode 2).
> >>
> >> Thanks - Fred
> >> fred.l.templin@boeing.com
> >>
> >> --------------------------------------------------------------------
> >> IETF IPv6 working group mailing list
> >> ipv6@ietf.org
> >> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >> --------------------------------------------------------------------
> >
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> > --------------------------------------------------------------------



From nobody Fri Feb  5 08:25:34 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D7EA1B3B1E for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 08:25:33 -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] 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 pr_3Elt2HZwU for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 08:25:32 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F3341B3B1D for <ipv6@ietf.org>; Fri,  5 Feb 2016 08:25:32 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id CE53C206AEC; Fri,  5 Feb 2016 17:25:28 +0100 (CET)
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, ipv6@ietf.org
References: <56B48386.2040300@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B4CCE0.7090207@si6networks.com>
Date: Fri, 5 Feb 2016 13:25:04 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B48386.2040300@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/fkJwcS-DYO1Gl3k2HaehDHNqmJE>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 16:25:33 -0000

Hi, ALex,

On 02/05/2016 08:12 AM, Alexandre Petrescu wrote:
> Hello 6manners,
> 
> draft-ietf-6man-default-iids-09 rightfully indicates that the same IID
> should not be used in the LL and GUA addresses of a same interface. 
> Because there may be a risk of correlation between addresses by a snooper.
> 
> The draft says:
>   The negotiated interface identifier is used by the local end of the
>   PPP link to autoconfigure an IPv6 link-local unicast address for the
>   PPP interface.  However, it SHOULD NOT be assumed that the same
>   interface identifier is used in configuring global unicast addresses
>   for the PPP interface using IPv6 stateless address autoconfiguration
>   [3].
> 
> But what does it mean "it SHOULD NOT be assumed"?  Who should not
> assume?  I think the text should rather say: "a same IID should not be
> used for several different scoped addresses of a same interface because
> snoopers may correlated them".

You're right. Actually, I'd remove this sentence altogether:
"  However, it SHOULD NOT be assumed that the same
   interface identifier is used in configuring global unicast addresses
   for the PPP interface using IPv6 stateless address autoconfiguration
   [3]."

since RFC7217 takes care of this. Thoughts?




> And what is [3]?  I guess the brackets should be escaped somehow
> otherwise looking at the list of References in this draft there is no [3].

That's a reference in the RFC we're quoting.

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





From nobody Fri Feb  5 08:28:29 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B019E1B3B30 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 08:28:28 -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] 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 t3xT8h1uZCyM for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 08:28:27 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 441D21B3B2C for <ipv6@ietf.org>; Fri,  5 Feb 2016 08:28:27 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 627B6206AEC; Fri,  5 Feb 2016 17:28:23 +0100 (CET)
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: otroan@employees.org, Alexandre Petrescu <alexandre.petrescu@gmail.com>
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B4CD9F.9090606@si6networks.com>
Date: Fri, 5 Feb 2016 13:28:15 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Iv9JgNAPLrXVYKZKqXBZHTLNedw>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 16:28:28 -0000

Ole,

On 02/05/2016 08:27 AM, otroan@employees.org wrote:
> Alex,
> 
>> draft-ietf-6man-default-iids-09 rightfully indicates that the same IID should not be used in the LL and GUA addresses of a same interface.  Because there may be a risk of correlation between addresses by a snooper.
>>
>> The draft says:
>>   The negotiated interface identifier is used by the local end of the
>>   PPP link to autoconfigure an IPv6 link-local unicast address for the
>>   PPP interface.  However, it SHOULD NOT be assumed that the same
>>   interface identifier is used in configuring global unicast addresses
>>   for the PPP interface using IPv6 stateless address autoconfiguration
>>   [3].
>>
>> But what does it mean "it SHOULD NOT be assumed"?  Who should not assume?  I think the text should rather say: "a same IID should not be used for several different scoped addresses of a same interface because snoopers may correlated them".
>>
>> I am asking because I just realized that a cellular ptp link on linux 3.4 yocto has this risk: it puts the same ppp-negotiated IID on both its LL and its GUA (and it adds a 2nd IID to a 2nd GUA - the 'privacy').  I guess it is so because the implementer does not understand "it SHOULD NOT be assumed"...
>>
>> Paradoxically that linux _is_ 'privacy' (it has random addresses instead of MAC-based addresses) but still has privacy risks (same IID on a GUA and its LL).
>>
>> And what is [3]?  I guess the brackets should be escaped somehow otherwise looking at the list of References in this draft there is no [3].
> 
> What is the risk of using the same IID for link-local and global addresses?
> Typically if you can snoop the link-local address then you're onlink and leak information about all addresses and their correlations anyway.

We discussed this one a hundred times now (including for RFC7217). The
risk is that at times such addressess can leak, without the need of the
attacker being pesent on the local link.

e.g., your MTA is on the local-link, and you end up connecting to it
with a LL, which then appears in the email headers. (and there are a
bunch of other possible reasons for that to happen).

Be proactive. MAC addresses in the IID are wrong. Putting them there is
just waiting for trouble.

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





From nobody Fri Feb  5 08:52:10 2016
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D79A1B3B7C for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 08:52:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.502
X-Spam-Level: 
X-Spam-Status: No, score=-114.502 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0auRvBOrlQjB for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 08:52:05 -0800 (PST)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1182A1B3B73 for <ipv6@ietf.org>; Fri,  5 Feb 2016 08:52:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3319; q=dns/txt; s=iport; t=1454691125; x=1455900725; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=mVzXv4rFO+SN0kTueQ4Q5bQl6tcshX75HRXS3p9ux3o=; b=O+qBCJQudkXEeyFdt5tLTuUjaTVFySHqB/RepC4F/TZ4Qw+ZdZa2xw/v wqzQv/SswUxnusJkBGenV8xSjIfBklZ3gXE/BpnB6V448xWwLMauXLGzO D1LST99Pf10zB/a09MEuorG7gxec4CaAhqDqyWoWqw6q6fzgISfLe5E2/ c=;
X-Files: signature.asc : 833
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0C8AgCy0rRW/51dJa1egzqBPwaIVbEND?= =?us-ascii?q?oFmhg0CgTQ4FAEBAQEBAQGBCoRBAQEBBHkMBAIBCBEEAQEBJwcyFAkIAgQOBQ6?= =?us-ascii?q?IDb90AQEBAQEBAQEBAQEBAQEBAQEBAQEBDQiHf4JKhDiDJYEPBZZ1AYJ9gWSDV?= =?us-ascii?q?oUYjnOOPQEeAUODZGoBiH98AQEB?=
X-IronPort-AV: E=Sophos;i="5.22,401,1449532800";  d="asc'?scan'208";a="74226765"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Feb 2016 16:52:04 +0000
Received: from XCH-ALN-012.cisco.com (xch-aln-012.cisco.com [173.36.7.22]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id u15Gq4JO023367 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 5 Feb 2016 16:52:04 GMT
Received: from xch-rcd-013.cisco.com (173.37.102.23) by XCH-ALN-012.cisco.com (173.36.7.22) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 5 Feb 2016 10:52:03 -0600
Received: from xch-rcd-013.cisco.com ([173.37.102.23]) by XCH-RCD-013.cisco.com ([173.37.102.23]) with mapi id 15.00.1104.009; Fri, 5 Feb 2016 10:52:03 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Fred Templin <Fred.L.Templin@boeing.com>
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AQHRX2tTSDlY+6HQH0uuyx8Jsd7k2Q==
Date: Fri, 5 Feb 2016 16:52:03 +0000
Message-ID: <02E8E930-81B0-48C5-A391-6B9EDECB6B90@cisco.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com> <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395DEF3@XCH-BLV-105.nw.nos.boeing.com> <8E7CAC70-9193-43B2-8A47-0C731B5464CA@cisco.com> <2134F8430051B64F815C691A62D983183395DFFF@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395E016@XCH-BLV-105.nw.nos.boeing.com> <A24F9E2D-3F56-4B1A-93C9-7F7BC62C6DF2@employees.org> <2134F8430051B64F815C691A62D983183395ECCA@XCH-BLV-105.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D983183395ECCA@XCH-BLV-105.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3112)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.248.62]
Content-Type: multipart/signed; boundary="Apple-Mail=_4C1496C4-68FB-4C77-82A4-2C043DB0F101"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/SC9SAcdHfYttfJzcqOHyhGuH8cI>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 16:52:08 -0000

--Apple-Mail=_4C1496C4-68FB-4C77-82A4-2C043DB0F101
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Feb 5, 2016, at 7:55 AM, Templin, Fred L <Fred.L.Templin@boeing.com> =
wrote:
> Hi Ole,
>=20
>> -----Original Message-----
>> From: otroan@employees.org [mailto:otroan@employees.org]
>> Sent: Friday, February 05, 2016 12:04 AM
>> To: Templin, Fred L
>> Cc: Fred Baker (fred); Bob Hinden; 6man WG
>> Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
>>=20
>> Fred,
>>=20
>>>=20
>>> I will make one other change recommendation:
>>>=20
>>> OLD:
>>> It defines a method for Packetization Layer Path MTU Discovery =
(PLPMTUD)
>>> designed for use in environments in which delivery of accurate ICMP =
messages
>>> to a host are not assured.
>>>=20
>>> NEW:
>>> It defines a method for Packetization Layer Path MTU Discovery =
(PLPMTUD)
>>> designed for use over paths for which delivery of accurate ICMP =
messages
>>> to a host are not assured.
>>=20
>> I would posit that there are no such paths. "accurate" ICMP can never =
be guaranteed.
>=20
> Forgetting the word "accurate" for the moment, it is reasonable to
> expect that paths that begin and end within the same well-managed
> administrative domain can be counted on to deliver the necessary
> ICMPs and to not deliver bogus ICMPs. Paths that lead to Internet
> destinations on the other hand cannot.
>=20
> If we do not believe that there are paths for which traditional PMTUD
> can still be used safely, then we should be working to deprecate
> RFC1981 instead of making it a standard.

As soon as I say "there is no such attack", one will materialize, so I =
won't assert that.  However, I am not aware of attacks in which someone =
creates ICMP PTBs and sends them to someone else in order to reduce =
their windows unnecessarily. I certainly *am* aware of firewalls and =
other equipment being programmed to either not originate or not allow =
ICMP messages, believing ICMP to be an attack vector.

As far as I know, RFC 4821 is a response to the latter issue.

--Apple-Mail=_4C1496C4-68FB-4C77-82A4-2C043DB0F101
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIVAwUBVrTTN0ayAOS/EQ8MAQLQrRAAhpzfCG3RSpOG0aifEWzrEZWiWwCFAoaV
V0EVMk6t+Rf5enREiMkLkBtrakCL9vuAuEt2iV2kBslbJXfG+liHT7u+lm2NZSv/
OhcPRLN2v4l/gfWRGWeb2yXXdETtY1OKd2l5BhUKysAf+AYFuooGflfubh1WS/4U
rUMTEdQotK0sSaa5bYJlnyjhYqK5j/qlr017EjKi+vXhRERlflOXqulWe7WnAq30
P/asNAaEMW4HDDclCV/+kU8heVOF5lq0c5aKtPv3117RaQAd2k57MJbUBA9ZkYZz
oCKqq+q4F7nT9Kf4aBASwcxicyLxBSH3hoeb8QurTJxqyi7f5PkAUfUbZ/1bQ74z
Y9G5KtG8gl68hceO2nl4hNovJ9Yd/810nLfleaypUHCXPMByUPo+4DEWtGzw37sq
yeSJUl+V2cPkkilj4DxxxNVKC6uxObSehqMfXZ5D7d1WiMibxcYHMuUSZrwbVcCI
lrwCGoTlOwglBKd16FPlCj8C2Iq3ZFGHsCUNH/jUGEKwEMUoe6/OP6mHMean+DXx
b9JW+FYiQo21f8Xy3FrAAJlzsw3zIAF0Ws8RPyEAbAw6oTmv5M1vi/21CKrEq9Hk
hLg53AlhYuRlup7QgjgYdp/81RutD4lCL/F6c8TJwCUEaQky/Nkd0nctb3MIXnji
SRiPjFPUhzg=
=lbpj
-----END PGP SIGNATURE-----

--Apple-Mail=_4C1496C4-68FB-4C77-82A4-2C043DB0F101--


From nobody Fri Feb  5 09:06:57 2016
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D523C1B3BA5 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 09:06:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J1DkJBxbLKFj for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 09:06:55 -0800 (PST)
Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A73F1B3BA0 for <ipv6@ietf.org>; Fri,  5 Feb 2016 09:06:55 -0800 (PST)
Received: by mail-ig0-x232.google.com with SMTP id ik10so44871314igb.1 for <ipv6@ietf.org>; Fri, 05 Feb 2016 09:06:55 -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=tT1Y4A4bXCssvJYrMdI8kUKxiZUhCkf1LQrR+2v9ZTI=; b=tw7/tFszlL2HuWl+kOoVtCPrgB4bKGsXxcDxTxStVPtGvhTw4bPP9bDIinK++NQViX HdttCyMqA7X7XrODtRk0NEP8tbZ+AApMkSk2NT0em0iNKoFkjt7gEvaySmi1VghaA5D3 2gL01o+DWUzyHFgVPhB6RniViIOhtCh+eMJd64e+nHR1Oy2vK7fb8dMCUTro1mfgPv9/ zXh++xAWe/uB8flKt0ZLkgydHJPiBfYka5qZfz2Uk5Kiiaj0OrCoKCHGpWO3dkljxtUT jD0B1IXNw0taMjXMygyklpGl2Xz6C3aIbwTWwfuyT8wkk/KHAW3sXBHoWcMpgr0L6XG3 acQA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=tT1Y4A4bXCssvJYrMdI8kUKxiZUhCkf1LQrR+2v9ZTI=; b=bj+FDEbbQEXUb5cYj7hjpvZ91KHf6fsWJ66OqFYQ4oI5wl1tbY1kmAyn2iRegvkqha 7UgIxokA8/33Xnuc07dfDgAbOy+iIgy9iqv6BU7GXBf94m9JdoWC60Me6qkWtu6ElFOl VPBCMYK+Yh64Jkm4GVjNy+sfT+hpolKGoJurYmnwG1yOKy6QEQu86YORxNNALHtxNsPP sFNvgCwU5YzG0t2c4MpkTZ1LG6KD8QEa6p1vLwgmdVbMKDCpdY9qC5wp/F6nhD57xGkz 84buI0MEENw52Lt9G8Vl0BDg9oD4qycQqpykwPuUcv/ec5Yy2QGao/EFE1JAp4mS3iJd 1dSQ==
X-Gm-Message-State: AG10YOTDkz0iQe8kZDYXof/ovtLPqWsw3+ZLMnKfrCggwAlKV8FFSbcAHLF0WJ5t2hiTuZG5trJCSA3GKmDcbg==
MIME-Version: 1.0
X-Received: by 10.50.150.106 with SMTP id uh10mr10287216igb.41.1454692013790;  Fri, 05 Feb 2016 09:06:53 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.169.35 with HTTP; Fri, 5 Feb 2016 09:06:53 -0800 (PST)
In-Reply-To: <56B3D4BF.9000202@gmail.com>
References: <2052A806-4D40-4A17-9892-90E39B67C65C@gmail.com> <CAJE_bqekFsfHPkfLTAOHgdL-MpvwNSV=gB8Cv0x+YrD66JUyMg@mail.gmail.com> <56B3D4BF.9000202@gmail.com>
Date: Fri, 5 Feb 2016 09:06:53 -0800
X-Google-Sender-Auth: OaoOGoEv1ojTdimt3cye2IiPTr8
Message-ID: <CAJE_bqczUQ1UX=mLBzd=XpoKDjO616NrO4iQYZvK7T7CFVzXOQ@mail.gmail.com>
Subject: Re: 6MAN WG Last Call - draft-ietf-6man-multi-homed-host-03.txt
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/_a_zy1wlUJlUmjRfawB52_Hn0Jw>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 17:06:57 -0000

At Fri, 5 Feb 2016 11:46:23 +1300,
Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

> >   The seeming open points are:
> >   + whether to move the host-model discussion to an appendix
>
> My personal choice is not to move it, but I would certainly do so
> if that was the WG's preference.

Okay.

> > - Section 3.1
> >
> >    As described in [RFC4191] and [RFC4861], a Router Advertisement may
> >    contain zero or more Prefix information Options (PIOs), zero or more
> >    Route Information Options (RIOs), or a Default Router List.
> >
> >   I'm not sure if I can understand the "or a Default Router List"
> >   part.  If it means 'Router Advertisement may contain...a Default
> >   Router List', it doesn't make sense since an RA (or any of its
> >   options) doesn't contain such a list (Default Router List is
> >   something that a host maintains based on the content of RA).
>
> I think you're correct.

Then I guess the sentence will have to be revised, but I can't suggest
anything specific as I don't understand the original intent.  Does
this "Default Router List" perhaps actually means the source IPv6
address of the RA (which will be maintained in the Default Router List
of the receiving host)?

> > - Section 3.1: likewise, the use of 'a default router list' in the
> >   following sentence is confusing, too:
> >
> >    [...]  In a multi-
> >    homed network implementing source/destination routing, the
> >    interpretation of a default router list or an RIO has to be modified
> >    with the words "if the source address is in one of the prefixes I
> >    advertise in a PIO".
>
> This is correct, isn't it? It applies to what the host has stored in
> its default router list and to any new RIOs that it receives. It could
> be phrased more carefully, I agree.

Maybe one source of confusion comes from the fact that this paragraph
starts talking about the content of an RA.  So one possible way to
improve the text would be to revise it focusing on hosts' conceptual
data structures rather than RAs that populate these structures.

On re-reading the text again, I've also noticed a few more glitches:

   [...] In their
   original intent, these indicate general information to a host: [...]
   "you might create or be configured with an address in this prefix", ...

Technically, "you might create an address in this prefix" is a matter
of RFC4862, so I think it should be referenced with RFC4191 and
RFC4861.

Also, I'm not sure if "you might be configured with an address in this
prefix" is part of the "original intent".  While it would be usually
the case that a global address manually configured or by DHCPv6 is in
a prefix advertised in a PIO (and normally with L=1), I would rather
consider it operational reality rather than an "original intent" of
these RFCs.

I think I can suggest alternate text to address some or all of these
points, but to do so I'd like to know the answer to the previous
point.

> > - Section 3.4
> >
> >    There is potential for adverse interaction with any off-link Redirect
> >    (Redirect for a GUA destination that is not on-link) message sent by
> >
> >   Is there any particular intent about why we specially say "GUA" here
> >   instead of, e.g., just "a global destination"?  For example, does it
> >   intend to exclude ULAs?  If so, why?  In case of ULAs, while the
> >   proposed host behavior may be less critical with ULAs in practice, I
> >   don't see any technical reason why we can't use it for ULAs.
>
> To me it's clear that both "GUA" and "global" include ULAs, because ULAs
> are defined to have global scope. Do you think there is a formal
> difference between "GUA" and "global"?  If so, is it documented?

It's probably not so clearly documented, but, for example, RFC4193 has
this text:

   It is expected that they would share the same Subnet IDs with
   provider-based global unicast addresses, if they were being used
   concurrently [GLOBAL].

(Here "they" means local IPv6 addresses) To me this sounds like if you
explicitly say a "global unicast address" it can implicitly indicates
the address is not a local addresses.

On the other hand, I (personally) don't feel such ambiguity about the
term "a global IPv6 address" since, as you noted above, ULAs have the
global scope.

Going back to my original comment, I now see there was no specific
intent in the use of GUA.  Then I suggest revising this

   (Redirect for a GUA destination that is not on-link) message sent by

to

   (Redirect for a global destination that is not on-link) message sent by

to avoid possible confusion.  The latter doesn't explicitly say it's a
unicast destination, but I believe it's obvious from the context (the
destination of a redirect cannot be a multicast address).

--
JINMEI, Tatuya


From nobody Fri Feb  5 09:46:45 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FD0B1A0078 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 09:46:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 DyO8En65foOf for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 09:46:42 -0800 (PST)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) (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 6B38F1A0056 for <ipv6@ietf.org>; Fri,  5 Feb 2016 09:46:42 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u15Hkms2017303; Fri, 5 Feb 2016 09:46:48 -0800
Received: from XCH-BLV-301.nw.nos.boeing.com (xch-blv-301.nw.nos.boeing.com [130.247.25.213]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u15HkgWL017250 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 5 Feb 2016 09:46:42 -0800
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-BLV-301.nw.nos.boeing.com ([169.254.1.229]) with mapi id 14.03.0235.001; Fri, 5 Feb 2016 09:46:36 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
Thread-Topic: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
Thread-Index: AdFgO8UgUUOFg9xdTwqIJb3fPhAIDQ==
Date: Fri, 5 Feb 2016 17:46:35 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395EF42@XCH-BLV-105.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/TVZndamzY-wZAF0Bnh_rm3yVjiA>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 17:46:43 -0000

Hi Fred,

> As soon as I say "there is no such attack", one will materialize, so I wo=
n't assert that.  However, I am not aware of attacks in which
> someone creates ICMP PTBs and sends them to someone else in order to redu=
ce their windows unnecessarily.

RFC4821 Section 11 (Security Considerations) recognizes the potential for s=
poofed
(i.e., inaccurate) ICMP PTB messages and suggests a mitigation (ignore all =
ICMP PTBs).
For paths over which any node in the network can inject an inaccurate ICMP =
PTB
message, an attack vector exists.

> I certainly *am* aware
> of firewalls and other equipment being programmed to either not originate=
 or not allow ICMP messages, believing ICMP to be an
> attack vector.

Right.

> As far as I know, RFC 4821 is a response to the latter issue.

RFC4821 is a response to both issues: 1) Loss of accurate ICMP PTBs, and
2) Receipt of inaccurate ICMP PTBs.

Thanks - Fred
fred.l.templin@boeing.com


From nobody Fri Feb  5 10:02:44 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92E411A1A47 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:02:42 -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] 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 4hjJRC77pqjT for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:02:41 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17A391A1BC3 for <ipv6@ietf.org>; Fri,  5 Feb 2016 10:02:40 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 355EA206AF1; Fri,  5 Feb 2016 19:02:35 +0100 (CET)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
To: "Fred Baker (fred)" <fred@cisco.com>, Fred Templin <Fred.L.Templin@boeing.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com> <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395DEF3@XCH-BLV-105.nw.nos.boeing.com> <8E7CAC70-9193-43B2-8A47-0C731B5464CA@cisco.com> <2134F8430051B64F815C691A62D983183395DFFF@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395E016@XCH-BLV-105.nw.nos.boeing.com> <A24F9E2D-3F56-4B1A-93C9-7F7BC62C6DF2@employees.org> <2134F8430051B64F815C691A62D983183395ECCA@XCH-BLV-105.nw.nos.boeing.com> <02E8E930-81B0-48C5-A391-6B9EDECB6B90@cisco.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B4E2E3.3080902@si6networks.com>
Date: Fri, 5 Feb 2016 14:58:59 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <02E8E930-81B0-48C5-A391-6B9EDECB6B90@cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/BIaAqIYV8h6ZzBEhk6unrwkTvo4>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 18:02:42 -0000

On 02/05/2016 01:52 PM, Fred Baker (fred) wrote:
>> If we do not believe that there are paths for which traditional
>> PMTUD can still be used safely, then we should be working to
>> deprecate RFC1981 instead of making it a standard.
> 
> As soon as I say "there is no such attack", one will materialize, so
> I won't assert that.  However, I am not aware of attacks in which
> someone creates ICMP PTBs and sends them to someone else in order to
> reduce their windows unnecessarily. 

Please see: <https://tools.ietf.org/html/rfc5927> (Section 7, specifically).

FWIW, in the IPv4 world, some boxes were known to crash when they
received an ICMP PTB claiming an MTU smaller than the IPv4 MTU (68 bytes).


> I certainly *am* aware of
> firewalls and other equipment being programmed to either not
> originate or not allow ICMP messages, believing ICMP to be an attack
> vector.
> 
> As far as I know, RFC 4821 is a response to the latter issue.

Agreed.

FWIW, 4821 can operate completely icmp-less, or it can be employed
simply for PMTUD-balckhole detection (.e., when you detect that
connections are getting stuck because ICMP messages are being dropped).

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





From nobody Fri Feb  5 10:02:54 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E56B11A1EEC for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:02:52 -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] 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 WiTtFgiYSMxs for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:02:48 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C8F91A1BEE for <ipv6@ietf.org>; Fri,  5 Feb 2016 10:02:48 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 7B1FA206AF4; Fri,  5 Feb 2016 19:02:43 +0100 (CET)
Subject: Re: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "Fred Baker (fred)" <fred@cisco.com>
References: <2134F8430051B64F815C691A62D983183395EF42@XCH-BLV-105.nw.nos.boeing.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B4E39A.5040608@si6networks.com>
Date: Fri, 5 Feb 2016 15:02:02 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <2134F8430051B64F815C691A62D983183395EF42@XCH-BLV-105.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/zOVI-eWQ5tdz6vswlrf7CuHW6ug>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 18:02:53 -0000

On 02/05/2016 02:46 PM, Templin, Fred L wrote:
> Hi Fred,
> 
>> As soon as I say "there is no such attack", one will materialize, so I won't assert that.  However, I am not aware of attacks in which
>> someone creates ICMP PTBs and sends them to someone else in order to reduce their windows unnecessarily.
> 
> RFC4821 Section 11 (Security Considerations) recognizes the potential for spoofed
> (i.e., inaccurate) ICMP PTB messages and suggests a mitigation (ignore all ICMP PTBs).
> For paths over which any node in the network can inject an inaccurate ICMP PTB
> message, an attack vector exists.

In theory, you can do some basic validation for ICMP messages. However,
in v6, as a result of possible EHs, you may not find any meaningful data
in the ICMP payload to apply validity checks on.

Anyway, you can implement the countermeasure we implemented in
<https://tools.ietf.org/html/rfc5927#section-7.2> -- I implemented it
for OpenBSD, and it still runs it... and IIRC it was ported to at least
NetBSD later.

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





From nobody Fri Feb  5 10:07:09 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70B801A6FB1 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:07:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Level: 
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_12=0.6, RP_MATCHES_RCVD=-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 yq9mKtP2bBwb for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:07:06 -0800 (PST)
Received: from cowbell.employees.org (cowbell.employees.org [IPv6:2001:1868:a000:17::142]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F75E1A6FA8 for <ipv6@ietf.org>; Fri,  5 Feb 2016 10:07:06 -0800 (PST)
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 1DE40D7888; Fri,  5 Feb 2016 10:07:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=XGZMgQzXGymSYTM1ERHY61z/BEQ=; b= RVhX/eAe5/lh9rg+D1vk78RiX2EYR2zEJ0SRh3k2Fn6Ek97NdwvanZFH6WWeGa8W vYgTeCF+TxCGoAWiwSICqOt3Q4oUbAvsib5+2/HFiMZp0ByZZAQ+effvUR27PBgL F5H4AuvaD1Diyuob2tJq0yHhMVmT57dsIJM4IPiFETM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=bI+eC7wbDnufptU9nHS1T72x76 An24Gg1Tswp4vQY1nTt35CWuhOuWjLzJEGS5+jR74uWSSQ7WUXYhOCk1oCtKb9cE ke+YXkt11YxB+2ja+0MbmuDBqHuc2lWD1DxMieynQ3FXmewd8YrgHN2Xbh6UVk0h 2+A1IjT4VzLJ1vjck=
Received: from h.hanazo.no (unknown [195.159.234.46]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id D1206D7887; Fri,  5 Feb 2016 10:07:05 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id B208F1080E18; Fri,  5 Feb 2016 19:07:05 +0100 (CET)
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Content-Type: multipart/signed; boundary="Apple-Mail=_3D46EEB7-ED97-45FB-8E82-66B162BE5103"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <56B4CD9F.9090606@si6networks.com>
Date: Fri, 5 Feb 2016 19:07:04 +0100
Message-Id: <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org>
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/dz7D8ogmrwshGreVy6LUec2UsVY>
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 18:07:07 -0000

--Apple-Mail=_3D46EEB7-ED97-45FB-8E82-66B162BE5103
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Fernando,

[...]

>>=20
>> What is the risk of using the same IID for link-local and global =
addresses?
>> Typically if you can snoop the link-local address then you're onlink =
and leak information about all addresses and their correlations anyway.
>=20
> We discussed this one a hundred times now (including for RFC7217). The
> risk is that at times such addressess can leak, without the need of =
the
> attacker being pesent on the local link.
>=20
> e.g., your MTA is on the local-link, and you end up connecting to it
> with a LL, which then appears in the email headers. (and there are a
> bunch of other possible reasons for that to happen).
>=20
> Be proactive. MAC addresses in the IID are wrong. Putting them there =
is
> just waiting for trouble.

I didn't say the LL was based on a MAC.
my question was if there was any issue with re-using the IID from the =
link-local in the GUA. assume the link-local is generated f.ex with =
7217.

cheers,
Ole

--Apple-Mail=_3D46EEB7-ED97-45FB-8E82-66B162BE5103
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIcBAEBCgAGBQJWtOTJAAoJEL7aWKiYQt929igP/1V6Am0FaWqI1nVCYRoTZYNT
IQYnrQZ1Tz+y08yjkWzouvSh2qjYfd4KAl5N+A0LpGFIIWPiq/v6FvqmwPYiIK1W
NKPcKYyXiXsbXMRRcv4OvBLnurfzCU8KwkGS+zE+G9pUx5UWzq6aWj4bULwIH9Yn
2sPRqmZ84kkAzOn+y7U+iktps69Jobn16j9r5glBe/rWJ56o4zZ1+BKu8TybN9kl
swmF4dJHdgSWz0Vi7gCz3tOfdn6WXlR50JreKq0TjNP4chgeS6EX0uApOmQ89uWg
uPURwyRwAwx98R+fMqlq0nYQp5HevjNuGJzWqhqyU38jDSyPruJFmpEeeuS0kMfV
E0Xb/lvo4pfMqbVN+XAmlBKsPlH1QLaUOrfWS8q/KhHBGHKca1hg3vfMYoWelGc5
SwpatfHU/v/iL6ZDQgOK+mG09cy6c93+AnKHwAUbADXDQRo6jU4nJxvEQUqOkEJB
nzuOcmtlsx7ewNC9j5Ej9lTn9QGHKXFuw1eci76k4wsACBNatWLjLt5sWEuiOxcU
gBccSewj2xwgUbyryYGgL1gKbcwmvcGzEWp4y4kIzaoVctN5glkwJpIQsnVZLio/
kQw0SQDLQGtqq2SXjdiqDFjYMO0ng/a+S4FLZsCe0X/gbgue5by6101T0o6OfOtT
ew2W1F5XhjAZNiyllYdt
=ZAsp
-----END PGP SIGNATURE-----

--Apple-Mail=_3D46EEB7-ED97-45FB-8E82-66B162BE5103--


From nobody Fri Feb  5 10:11:25 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DC221A6FDB for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:11:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-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 2ZIYNwW2lzjm for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:11:22 -0800 (PST)
Received: from cowbell.employees.org (cowbell.employees.org [65.50.211.142]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3030D1A6FE1 for <ipv6@ietf.org>; Fri,  5 Feb 2016 10:11:20 -0800 (PST)
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id E8DE4D7887; Fri,  5 Feb 2016 10:11:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=50hmyq4sjNt9/KrEPJGm5Mr2jvM=; b= al5/CskzxdoSF//cFAV9Z/YF67JWssStI1BjQKxNQFKQv7c/aMDoVXgk4DkA8LeB anPR4geS3t/o9KXkIrypUUA3dgVynytMFczZ4Fr6JWpKjyB08FTgVLro8mIuXkIG IlEKY3465aq+HwgG3vGIGXA0EBhu7oH7x3eDd8v/fYg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=gfm2uyprkhrNhI+54BpfuQg+60 gQGA3fpqibQt9tHDdfIuN2luME4AFZkt6QyETmSCVj6/F/Dhvdlhgjae1ZnRdqSn YojL1Y/KwOJNc3VtR/uJlTSuJgax0t+IEIZhKc3eTEgSzrOGVJ697IkuedcakZwg DqcKbntLhQ3A979MM=
Received: from h.hanazo.no (unknown [195.159.234.46]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id A995ED7882; Fri,  5 Feb 2016 10:11:19 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id B4C831080EF3; Fri,  5 Feb 2016 19:11:21 +0100 (CET)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Content-Type: multipart/signed; boundary="Apple-Mail=_A9A84D64-0992-49AA-B358-28CEF80C421B"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <56B49D89.5050202@innovationslab.net>
Date: Fri, 5 Feb 2016 19:11:21 +0100
Message-Id: <39408594-E513-46DA-820A-AB0D5CB85C9E@employees.org>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <2134F8430051B64F815C691A62D983183395D25D@XCH-BLV-105.nw.nos.boeing.com> <F01DCA0F-BCBF-4CD3-BF2B-412EE2FDC19C@employees.org> <56B49D89.5050202@innovationslab.net>
To: Brian Haberman <brian@innovationslab.net>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/GENy2qbe_XP_BkacxCU_S4fDFt8>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 18:11:23 -0000

--Apple-Mail=_A9A84D64-0992-49AA-B358-28CEF80C421B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Brian,

>>> One question on the authorship - I can say with some certainty that
>>> Jack McCann and Jeff Mogul are no longer with Digital Equipment
>>> Corporation. Would they  be actively involved in this work if it is
>>> accepted as a working group item?
>>=20
>> I don't expect them to be. For the documents we're advancing to
>> Internet Standard, and therefore only do very minor tweaks to, I
>> think it makes most sense to keep the original authors. Unless they
>> object.
>=20
> Um, no. The original authors stay on the draft because they are the =
ones
> responsible for most of the text within the document. Accurate
> representation of authorship is critical for many reasons (e.g., IPR).

my view is that it is the working group that is responsible for the =
document (and at a larger level the IETF).
and that we have the authors listed on the first page as a way to =
recognise them as the main contributors.

perhaps it is time to remove author names from our documents then.
(as something the IETF should look at, not for these sets of documents =
obviously).

Best regards,
Ole

--Apple-Mail=_A9A84D64-0992-49AA-B358-28CEF80C421B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIcBAEBCgAGBQJWtOXJAAoJEL7aWKiYQt92bKEP/AnB80BeKwfLqj15XnmB6Bi3
LByqUOVFx+2FOLz/A+camysKzWKvHhkpc1tofbGoLiPS4qUWYdW2bAx1H5OoStMO
T1QhdGh+OA9q3M54veJ2dtznokeRfdtEM8nBALfz6UsA6VBR67QrUAoYGzwGaW4l
PYuGUclWc79GKI1Xy2lLOLZBsK22tqvS1yYbhi8Ni46IitiMyGgmnH0S08Cl+Nod
Bm0mAI184nbAqdfAsqn0ndEYApfgcGEbavdYcoQEtsCi0o/FTi87yqdY4RppAKyW
teCVQCAE9QrQ2GEo+QCpWXE1hg7T6D3EyCWno4fWZLT3AiCU4pxpDIEm1XGZmJ79
4bWMWnrJH4AWARAsdsZv0vYdZaFGKRPrhZUTY9kt1kImd/L0u46zPzyW8RvcTbGt
aIpWUzMWYShJcosC7L43nHgUV48jVJC22aApJKEevGqM7czOK8j07GLTJYDQSfyw
zHLhQqmi/TlrsiCZPcua8cDKDmIokJrC2+4+xLbBrRGlaNsByORmy41YKxRlbXUN
B5E6IXxrMmUaOs+8bDVMYLsfrUf2Y1x3t+fGpiV4mlubFtt5arn0yfVQNxpLPWPM
QgxXhyWza4Wzelzj/eN8zv+POs31kaF09BdIH598T+ny5v2z6Zd0nZZThrYT8S6J
N13biG/+LWGKkHNIskbA
=UdMq
-----END PGP SIGNATURE-----

--Apple-Mail=_A9A84D64-0992-49AA-B358-28CEF80C421B--


From nobody Fri Feb  5 10:13:56 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16BBE1A7004 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:13:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 DCmoMT5SPDxH for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:13:53 -0800 (PST)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) (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 4A2561A6FE0 for <ipv6@ietf.org>; Fri,  5 Feb 2016 10:13:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u15IDxOF020497; Fri, 5 Feb 2016 10:14:00 -0800
Received: from XCH-PHX-309.sw.nos.boeing.com (xch-phx-309.sw.nos.boeing.com [130.247.25.163]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u15IDwaN020465 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 5 Feb 2016 10:13:58 -0800
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-PHX-309.sw.nos.boeing.com ([169.254.9.24]) with mapi id 14.03.0235.001; Fri, 5 Feb 2016 10:13:50 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "otroan@employees.org" <otroan@employees.org>
Subject: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
Thread-Topic: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
Thread-Index: AdFgPnAxn72vBLTpQqid+VAMpL4ryQ==
Date: Fri, 5 Feb 2016 18:13:50 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/-hNRCcD92qm2711h2rSmmWQFXFs>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 18:13:55 -0000

Starting this under a new thread, IMHO if we want to promote RFC1981 to sta=
ndard
we should understand its use cases as well as the use cases for RFC4821.

First, it is reasonable to expect that paths that begin and end within the =
same
well-managed administrative domain can be counted on to deliver the necessa=
ry
ICMPs. An example is my employer's corporate network. In that case, traditi=
onal
PMTUD per RFC1981(bis) can be applied alone w/o having to apply RFC4821.

On the other hand, paths that lead to Internet destinations cannot be count=
ed
on to deliver the necessary ICMPs. In that case, RFC4821 provides a mitigat=
ion.

But, if we do not believe that there are paths for which traditional PMTUD
can still be used safely, then we should be working to deprecate RFC1981
instead of making it a standard.

Thanks - Fred
fred.l.templin@boeing.com


From nobody Fri Feb  5 10:23:10 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2EDE1A70FE for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:23:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-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 TuCHzOA6CREq for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:23:07 -0800 (PST)
Received: from cowbell.employees.org (cowbell.employees.org [65.50.211.142]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72C721A70E2 for <ipv6@ietf.org>; Fri,  5 Feb 2016 10:23:07 -0800 (PST)
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 0DA49D7887; Fri,  5 Feb 2016 10:23:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=baOujqsrX4NNSNOg3EWdCqw7Thg=; b= RoAH1PQTMCQcfauyCSyazKzQ6ltJ9yXfpC4GGVNgK2P8g9cgssKGZ7l5jSsYnHg/ 4IUQseQV+/84ieNwprfFZCYjQ/WWPZ+UWScmHHL9RhZZ5BjDQ+3GG6C1DTfarnEL av6esUY3ZtKSMrr1LPLEwYuz8EoqkWwxiPZCOxehLsU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=WIvBIwJC4PHBmmAh/cpAyxjQsU lKy1w1FBLfEF7ZkNEiq3NqxCT2mp3MJm3ZIZPBIgpbVRa9rj/pSRm8InbjAMbguY xX1RrQyY0Yh3fy/K6KmtoFP+YPIXLqolWYhn3TCatTswM3P66tbCxolyZ/BjCJ86 4vkMk/S3Y+up4rXJQ=
Received: from h.hanazo.no (unknown [195.159.234.46]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id C471AD7884; Fri,  5 Feb 2016 10:23:06 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 6114810810C1; Fri,  5 Feb 2016 19:23:03 +0100 (CET)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Content-Type: multipart/signed; boundary="Apple-Mail=_EAA4D00F-91B3-42C8-8896-41E9BAB0833E"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <2134F8430051B64F815C691A62D983183395ECCA@XCH-BLV-105.nw.nos.boeing.com>
Date: Fri, 5 Feb 2016 19:23:02 +0100
Message-Id: <48AD9A1B-C9EF-4451-B8FA-7BBC1BCD9629@employees.org>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com> <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395DEF3@XCH-BLV-105.nw.nos.boeing.com> <8E7CAC70-9193-43B2-8A47-0C731B5464CA@cisco.com> <2134F8430051B64F815C691A62D983183395DFFF@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395E016@XCH-BLV-105.nw.nos.boeing.com> <A24F9E2D-3F56-4B1A-93C9-7F7BC62C6DF2@employees.org> <2134F8430051B64F815C691A62D983183395ECCA@XCH-BLV-105.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/SnYZEDdBnAE0ALsClvvTwXjp55Q>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 18:23:09 -0000

--Apple-Mail=_EAA4D00F-91B3-42C8-8896-41E9BAB0833E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Fred,

[...]

>=20
> Forgetting the word "accurate" for the moment, it is reasonable to
> expect that paths that begin and end within the same well-managed
> administrative domain can be counted on to deliver the necessary
> ICMPs and to not deliver bogus ICMPs. Paths that lead to Internet
> destinations on the other hand cannot.

how is the host supposed to determine that?
the worst thing that can happen with a bogus PMTUD message is that the =
host sets its MTU to 1280.
that might be bad on a 9K end to end link perhaps.

> If we do not believe that there are paths for which traditional PMTUD
> can still be used safely, then we should be working to deprecate
> RFC1981 instead of making it a standard.

I'd rather we looked at getting 4821 deployment and looked at other =
mechanisms that would work better than 1981.

you can make an argument that ICMP messages cannot be "used safely" in =
general.

cheers,
Ole


--Apple-Mail=_EAA4D00F-91B3-42C8-8896-41E9BAB0833E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIcBAEBCgAGBQJWtOiHAAoJEL7aWKiYQt92F4wP/R7Qg106MO+xeGhIuAklGHoM
WnEb/SuR6x/jI9pZDCFbRo4dVe4usz7mim5hMbuWn0b0p/6vU6l1m3Es7ldUcg8v
mkJikbXJnQ/3xByzuPFnvcjjEZEscS239fxFeqSvmJNGhBcKjX8Pz4qS8kARTnMF
oGtvjE7MhyA5a3QCs/rbaK9wunpzkfFiW+1c4Wk7v2Ae7X1rOzPiayZ60VcHl0Zy
apyQ0PUK4ZlzlTnGF4dzEIeqHCJeWvVxnJpVNsH2zvd1d4Ua7Dp4OYlnVa7loEYS
3lf/7W22MXVuoOAKRds0Yf1fjObeCoWfd2zyv0dIjS96dcfseAVDIHQKw5YFUONV
hZoMSjcASn572WFPdLaErExNbNDwT0DOyDqRB4Rt08IiM+rwSvpm6rhjkf6yAKLU
9mET8Tak1jg+FTAs9SKJzA5mRcctutuSuHqLxBmm+4J/9BIWqklwZ0FLmE2eAj9k
FTD+tzX2YPMMo1+nJNfAErlSYFyQu/ms+P7XB+J7nuwm7bJ3UZp8p/nVSMsuWWLR
Yo3+mHrpvp6wytunjF1ouqsoEzgkHPspy4lYjFr0uwUnzvAI9W+OQkkbU4ZfMrc7
RqJDfRgEgG7FOad2oul9r6yDNe4eejw3vSqiPaGAeps+6aEMcV/p6NZOpwkNgjKk
W3s1wCvMoBaja16sBIld
=T6pN
-----END PGP SIGNATURE-----

--Apple-Mail=_EAA4D00F-91B3-42C8-8896-41E9BAB0833E--


From nobody Fri Feb  5 10:25:46 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 710B21A7D84 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:25:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level: 
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_12=0.6, 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 7Eb1WNCSxK-D for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:25:43 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D5641A70FE for <ipv6@ietf.org>; Fri,  5 Feb 2016 10:25:43 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id B0F94206AF1; Fri,  5 Feb 2016 19:25:40 +0100 (CET)
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: otroan@employees.org
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B4E7FB.5010700@si6networks.com>
Date: Fri, 5 Feb 2016 15:20:43 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/K3vBiQfB9jBax6v_GLWQYndkFvo>
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 18:25:44 -0000

On 02/05/2016 03:07 PM, otroan@employees.org wrote:
> Fernando,
> 
> [...]
> 
>>>
>>> What is the risk of using the same IID for link-local and global addresses?
>>> Typically if you can snoop the link-local address then you're onlink and leak information about all addresses and their correlations anyway.
>>
>> We discussed this one a hundred times now (including for RFC7217). The
>> risk is that at times such addressess can leak, without the need of the
>> attacker being pesent on the local link.
>>
>> e.g., your MTA is on the local-link, and you end up connecting to it
>> with a LL, which then appears in the email headers. (and there are a
>> bunch of other possible reasons for that to happen).
>>
>> Be proactive. MAC addresses in the IID are wrong. Putting them there is
>> just waiting for trouble.
> 
> I didn't say the LL was based on a MAC.
> my question was if there was any issue with re-using the IID from the link-local in the GUA. assume the link-local is generated f.ex with 7217.

Oops, my apologies. My answer would be "It unnecessarily enables
correlation of the activities that you carry between the two addresses".

i.e., by simply inspecting the IID I could easily tell that the
activities carried out with one address were performed by the same node
that employed the other address.

My take here is, again: be proactive. If there's no requirement (and
there isn't) for the two IIDs to be the same, then make them different,
and fail on the safe side.

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





From nobody Fri Feb  5 10:25:56 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4D841A82E2 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:25:54 -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] 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 txjaAXUDasFL for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:25:51 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C17551A7D83 for <ipv6@ietf.org>; Fri,  5 Feb 2016 10:25:50 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id DE20C206AF4; Fri,  5 Feb 2016 19:25:46 +0100 (CET)
Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "otroan@employees.org" <otroan@employees.org>
References: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B4E91C.6090905@si6networks.com>
Date: Fri, 5 Feb 2016 15:25:32 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/9SY3ydiWOYGyyiY4hAoKOSwiNX8>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 18:25:54 -0000

On 02/05/2016 03:13 PM, Templin, Fred L wrote:
> Starting this under a new thread, IMHO if we want to promote RFC1981 to standard
> we should understand its use cases as well as the use cases for RFC4821.
> 
> First, it is reasonable to expect that paths that begin and end within the same
> well-managed administrative domain can be counted on to deliver the necessary
> ICMPs. An example is my employer's corporate network. In that case, traditional
> PMTUD per RFC1981(bis) can be applied alone w/o having to apply RFC4821.
> 
> On the other hand, paths that lead to Internet destinations cannot be counted
> on to deliver the necessary ICMPs. In that case, RFC4821 provides a mitigation.
> 
> But, if we do not believe that there are paths for which traditional PMTUD
> can still be used safely, then we should be working to deprecate RFC1981
> instead of making it a standard.

Well, the thing here that you can do RFC1981-only, RFC4821-only, or
RFC1981/RFC4821 (should I say "dual stack"? :-) ).

With that in mind, one could as well have both RFC1981 and RFC4821 as
standards, I guess...

But yes, generally speaking, RFC1981-only is certaianly unreliable.

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





From nobody Fri Feb  5 10:26:08 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57B9A1A86E4 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:26:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 QAEwTqxnFcWK for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:26:02 -0800 (PST)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) (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 E23F81A86E8 for <ipv6@ietf.org>; Fri,  5 Feb 2016 10:25:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u15IPuq8030127; Fri, 5 Feb 2016 12:25:56 -0600
Received: from XCH-PHX-109.sw.nos.boeing.com (xch-phx-109.sw.nos.boeing.com [130.247.25.36]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u15IPs5U029639 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 5 Feb 2016 12:25:55 -0600
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-PHX-109.sw.nos.boeing.com ([169.254.9.35]) with mapi id 14.03.0235.001; Fri, 5 Feb 2016 10:25:53 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>, "Fred Baker (fred)" <fred@cisco.com>
Subject: RE: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
Thread-Topic: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
Thread-Index: AdFgO8UgUUOFg9xdTwqIJb3fPhAIDQARpl8AABAVV8A=
Date: Fri, 5 Feb 2016 18:25:53 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395F017@XCH-BLV-105.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D983183395EF42@XCH-BLV-105.nw.nos.boeing.com> <56B4E39A.5040608@si6networks.com>
In-Reply-To: <56B4E39A.5040608@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/HDYmIT5wlKv9YdOyHvcW4jcnFkQ>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 18:26:06 -0000

Hi Fernando,

> -----Original Message-----
> From: Fernando Gont [mailto:fgont@si6networks.com]
> Sent: Friday, February 05, 2016 10:02 AM
> To: Templin, Fred L; Fred Baker (fred)
> Cc: 6man WG; Bob Hinden
> Subject: Re: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on d=
raft-hinden-6man-rfc1981bis-01)
>=20
> On 02/05/2016 02:46 PM, Templin, Fred L wrote:
> > Hi Fred,
> >
> >> As soon as I say "there is no such attack", one will materialize, so I=
 won't assert that.  However, I am not aware of attacks in which
> >> someone creates ICMP PTBs and sends them to someone else in order to r=
educe their windows unnecessarily.
> >
> > RFC4821 Section 11 (Security Considerations) recognizes the potential f=
or spoofed
> > (i.e., inaccurate) ICMP PTB messages and suggests a mitigation (ignore =
all ICMP PTBs).
> > For paths over which any node in the network can inject an inaccurate I=
CMP PTB
> > message, an attack vector exists.
>=20
> In theory, you can do some basic validation for ICMP messages. However,
> in v6, as a result of possible EHs, you may not find any meaningful data
> in the ICMP payload to apply validity checks on.
>=20
> Anyway, you can implement the countermeasure we implemented in
> <https://tools.ietf.org/html/rfc5927#section-7.2> -- I implemented it
> for OpenBSD, and it still runs it... and IIRC it was ported to at least
> NetBSD later.

Thanks for the reference. It seems to account for the case of paths that ma=
y
deliver inaccurate ICMP PTBs, but does not account for the case of paths th=
at
fail to deliver accurate ICMP PTBs. Do we know of paths always deliver
accurate ICMP PTBs but can also deliver inaccurate ICMP PTBs?=20

Thanks - Fred
fred.l.templin@boeing.com

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



From nobody Fri Feb  5 10:27:36 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EBCD1A8707 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:27:35 -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] 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 XGXu8a9YlMlW for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:27:33 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC7B81A8704 for <ipv6@ietf.org>; Fri,  5 Feb 2016 10:27:33 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id EBA36206AF1; Fri,  5 Feb 2016 19:27:29 +0100 (CET)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
To: otroan@employees.org, "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com> <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395DEF3@XCH-BLV-105.nw.nos.boeing.com> <8E7CAC70-9193-43B2-8A47-0C731B5464CA@cisco.com> <2134F8430051B64F815C691A62D983183395DFFF@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395E016@XCH-BLV-105.nw.nos.boeing.com> <A24F9E2D-3F56-4B1A-93C9-7F7BC62C6DF2@employees.org> <2134F8430051B64F815C691A62D983183395ECCA@XCH-BLV-105.nw.nos.boeing.com> <48AD9A1B-C9EF-4451-B8FA-7BBC1BCD9629@employees.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B4E98A.602@si6networks.com>
Date: Fri, 5 Feb 2016 15:27:22 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <48AD9A1B-C9EF-4451-B8FA-7BBC1BCD9629@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/PALL_XBzBBXP1Oe20XlnX0dp7Fk>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 18:27:35 -0000

On 02/05/2016 03:23 PM, otroan@employees.org wrote:
> Fred,
> 
> [...]
> 
>>
>> Forgetting the word "accurate" for the moment, it is reasonable to
>> expect that paths that begin and end within the same well-managed
>> administrative domain can be counted on to deliver the necessary
>> ICMPs and to not deliver bogus ICMPs. Paths that lead to Internet
>> destinations on the other hand cannot.
> 
> how is the host supposed to determine that?
> the worst thing that can happen with a bogus PMTUD message is that the host sets its MTU to 1280.
> that might be bad on a 9K end to end link perhaps.

Agreed. The situation is way better in the IPv6-world than in its IPv4
counterpart. In the worst case scenario, you can downgrade an IPv6 to a
1280-byte MTU. But in IPv4 you can downgrade a flow to a 68-byte MTU.

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





From nobody Fri Feb  5 10:30:48 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 817841A8709 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:30:47 -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] 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 sTic95Cjo8Lm for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:30:46 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E26351A86E8 for <ipv6@ietf.org>; Fri,  5 Feb 2016 10:30:45 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 8D638206A2B; Fri,  5 Feb 2016 19:30:37 +0100 (CET)
Subject: Re: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "Fred Baker (fred)" <fred@cisco.com>
References: <2134F8430051B64F815C691A62D983183395EF42@XCH-BLV-105.nw.nos.boeing.com> <56B4E39A.5040608@si6networks.com> <2134F8430051B64F815C691A62D983183395F017@XCH-BLV-105.nw.nos.boeing.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <56B4EA46.3080102@si6networks.com>
Date: Fri, 5 Feb 2016 15:30:30 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <2134F8430051B64F815C691A62D983183395F017@XCH-BLV-105.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/DKCfFL948g_AcpF6bNVVMPsYihk>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 18:30:47 -0000

On 02/05/2016 03:25 PM, Templin, Fred L wrote:
> Hi Fernando,
> 
>> -----Original Message-----
>> From: Fernando Gont [mailto:fgont@si6networks.com]
>> Sent: Friday, February 05, 2016 10:02 AM
>> To: Templin, Fred L; Fred Baker (fred)
>> Cc: 6man WG; Bob Hinden
>> Subject: Re: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
>>
>> On 02/05/2016 02:46 PM, Templin, Fred L wrote:
>>> Hi Fred,
>>>
>>>> As soon as I say "there is no such attack", one will materialize, so I won't assert that.  However, I am not aware of attacks in which
>>>> someone creates ICMP PTBs and sends them to someone else in order to reduce their windows unnecessarily.
>>>
>>> RFC4821 Section 11 (Security Considerations) recognizes the potential for spoofed
>>> (i.e., inaccurate) ICMP PTB messages and suggests a mitigation (ignore all ICMP PTBs).
>>> For paths over which any node in the network can inject an inaccurate ICMP PTB
>>> message, an attack vector exists.
>>
>> In theory, you can do some basic validation for ICMP messages. However,
>> in v6, as a result of possible EHs, you may not find any meaningful data
>> in the ICMP payload to apply validity checks on.
>>
>> Anyway, you can implement the countermeasure we implemented in
>> <https://tools.ietf.org/html/rfc5927#section-7.2> -- I implemented it
>> for OpenBSD, and it still runs it... and IIRC it was ported to at least
>> NetBSD later.
> 
> Thanks for the reference. It seems to account for the case of paths that may
> deliver inaccurate ICMP PTBs, but does not account for the case of paths that
> fail to deliver accurate ICMP PTBs. Do we know of paths always deliver
> accurate ICMP PTBs but can also deliver inaccurate ICMP PTBs? 

What do you mean by "accurate"?

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





From nobody Fri Feb  5 10:40:18 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6D531A8757 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:40:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 o2ntfSgIf-Kj for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:40:15 -0800 (PST)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) (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 AA43B1A8756 for <ipv6@ietf.org>; Fri,  5 Feb 2016 10:40:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u15IeLX0020586; Fri, 5 Feb 2016 10:40:21 -0800
Received: from XCH-PHX-309.sw.nos.boeing.com (xch-phx-309.sw.nos.boeing.com [130.247.25.163]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u15IeH8R020540 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 5 Feb 2016 10:40:17 -0800
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-PHX-309.sw.nos.boeing.com ([169.254.9.24]) with mapi id 14.03.0235.001; Fri, 5 Feb 2016 10:40:10 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "otroan@employees.org" <otroan@employees.org>
Subject: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Topic: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Thread-Index: AQHRX2tT80dfpGCQDUCIhA2edhybgJ8cKO6QgAAMGWCAAIvjAP//enWAgAACgkCAAWD8gP//+8EggACxJgD//3o18A==
Date: Fri, 5 Feb 2016 18:40:10 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395F0AD@XCH-BLV-105.nw.nos.boeing.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <DB69251C-55E5-4577-9C0A-0541A8946940@cisco.com> <2134F8430051B64F815C691A62D983183395DE77@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395DEF3@XCH-BLV-105.nw.nos.boeing.com> <8E7CAC70-9193-43B2-8A47-0C731B5464CA@cisco.com> <2134F8430051B64F815C691A62D983183395DFFF@XCH-BLV-105.nw.nos.boeing.com> <2134F8430051B64F815C691A62D983183395E016@XCH-BLV-105.nw.nos.boeing.com> <A24F9E2D-3F56-4B1A-93C9-7F7BC62C6DF2@employees.org> <2134F8430051B64F815C691A62D983183395ECCA@XCH-BLV-105.nw.nos.boeing.com> <48AD9A1B-C9EF-4451-B8FA-7BBC1BCD9629@employees.org>
In-Reply-To: <48AD9A1B-C9EF-4451-B8FA-7BBC1BCD9629@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/pQUJ604ay7ckwgFoGihUYAJuXb0>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 18:40:17 -0000

Hi Ole,

> -----Original Message-----
> From: otroan@employees.org [mailto:otroan@employees.org]
> Sent: Friday, February 05, 2016 10:23 AM
> To: Templin, Fred L
> Cc: Fred Baker (fred); Bob Hinden; 6man WG
> Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
>=20
> Fred,
>=20
> [...]
>=20
> >
> > Forgetting the word "accurate" for the moment, it is reasonable to
> > expect that paths that begin and end within the same well-managed
> > administrative domain can be counted on to deliver the necessary
> > ICMPs and to not deliver bogus ICMPs. Paths that lead to Internet
> > destinations on the other hand cannot.
>=20
> how is the host supposed to determine that?

In some well managed networks, the only way to reach correspondent
nodes in the Internet is to go through a proxy that breaks the TCP
connection into an "inside" segment and an "outside" segment. And,
within any "inside" path including those that lead to a proxy, RFC1981
can be applied w/o also applying RFC4821.

> the worst thing that can happen with a bogus PMTUD message is that the ho=
st sets its MTU to 1280.
> that might be bad on a 9K end to end link perhaps.

Yes, it still works but at the minimum IPv6 MTU. We want an Internet
that can robustly adapt to paths with larger MTUs without suffering
performance-degrading attacks.

> > If we do not believe that there are paths for which traditional PMTUD
> > can still be used safely, then we should be working to deprecate
> > RFC1981 instead of making it a standard.
>=20
> I'd rather we looked at getting 4821 deployment and looked at other mecha=
nisms that would work better than 1981.

What do you mean by better than RFC1981? For paths over which it can be
counted on to work, RFC1981 is better than RFC4821.
=20
> you can make an argument that ICMP messages cannot be "used safely" in ge=
neral.

But, it depends - paths over which RFC1981 can be counted on to work (e.g.,
well-managed administrative domains) would be considered a use case where
ICMP messages can be used safely.

Thanks - Fred
fred.l.templin@boeing.com

> cheers,
> Ole



From nobody Fri Feb  5 10:42:50 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABCB31A8770 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:42:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 P1WvC8DmJWNC for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:42:47 -0800 (PST)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) (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 342B81A876B for <ipv6@ietf.org>; Fri,  5 Feb 2016 10:42:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u15IgqEu025258; Fri, 5 Feb 2016 10:42:53 -0800
Received: from XCH-BLV-505.nw.nos.boeing.com (xch-blv-505.nw.nos.boeing.com [130.247.25.195]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u15IgpKc025251 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 5 Feb 2016 10:42:51 -0800
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-BLV-505.nw.nos.boeing.com ([169.254.5.220]) with mapi id 14.03.0235.001; Fri, 5 Feb 2016 10:42:44 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>, "Fred Baker (fred)" <fred@cisco.com>
Subject: RE: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
Thread-Topic: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
Thread-Index: AdFgO8UgUUOFg9xdTwqIJb3fPhAIDQARpl8AABAVV8D//4dJAIAAg16g
Date: Fri, 5 Feb 2016 18:42:44 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395F0CE@XCH-BLV-105.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D983183395EF42@XCH-BLV-105.nw.nos.boeing.com> <56B4E39A.5040608@si6networks.com> <2134F8430051B64F815C691A62D983183395F017@XCH-BLV-105.nw.nos.boeing.com> <56B4EA46.3080102@si6networks.com>
In-Reply-To: <56B4EA46.3080102@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/bkBXWaS9ITYwImyRpE-oGGp4Or8>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 18:42:48 -0000

Hi Fernando,

> -----Original Message-----
> From: Fernando Gont [mailto:fgont@si6networks.com]
> Sent: Friday, February 05, 2016 10:31 AM
> To: Templin, Fred L; Fred Baker (fred)
> Cc: Bob Hinden; 6man WG
> Subject: Re: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on d=
raft-hinden-6man-rfc1981bis-01)
>=20
> On 02/05/2016 03:25 PM, Templin, Fred L wrote:
> > Hi Fernando,
> >
> >> -----Original Message-----
> >> From: Fernando Gont [mailto:fgont@si6networks.com]
> >> Sent: Friday, February 05, 2016 10:02 AM
> >> To: Templin, Fred L; Fred Baker (fred)
> >> Cc: 6man WG; Bob Hinden
> >> Subject: Re: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call o=
n draft-hinden-6man-rfc1981bis-01)
> >>
> >> On 02/05/2016 02:46 PM, Templin, Fred L wrote:
> >>> Hi Fred,
> >>>
> >>>> As soon as I say "there is no such attack", one will materialize, so=
 I won't assert that.  However, I am not aware of attacks in
> which
> >>>> someone creates ICMP PTBs and sends them to someone else in order to=
 reduce their windows unnecessarily.
> >>>
> >>> RFC4821 Section 11 (Security Considerations) recognizes the potential=
 for spoofed
> >>> (i.e., inaccurate) ICMP PTB messages and suggests a mitigation (ignor=
e all ICMP PTBs).
> >>> For paths over which any node in the network can inject an inaccurate=
 ICMP PTB
> >>> message, an attack vector exists.
> >>
> >> In theory, you can do some basic validation for ICMP messages. However=
,
> >> in v6, as a result of possible EHs, you may not find any meaningful da=
ta
> >> in the ICMP payload to apply validity checks on.
> >>
> >> Anyway, you can implement the countermeasure we implemented in
> >> <https://tools.ietf.org/html/rfc5927#section-7.2> -- I implemented it
> >> for OpenBSD, and it still runs it... and IIRC it was ported to at leas=
t
> >> NetBSD later.
> >
> > Thanks for the reference. It seems to account for the case of paths tha=
t may
> > deliver inaccurate ICMP PTBs, but does not account for the case of path=
s that
> > fail to deliver accurate ICMP PTBs. Do we know of paths always deliver
> > accurate ICMP PTBs but can also deliver inaccurate ICMP PTBs?
>=20
> What do you mean by "accurate"?

By "accurate" I mean:

- the router that sends the ICMP PTB is telling the truth that there is a r=
estricting link
- the MTU value that the router writes in the PTB is in fact the true MTU o=
f the
   restricting link

Thanks - Fred
fred.l.templin@boeing.com

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



From nobody Fri Feb  5 10:51:06 2016
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D988F1A879A for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:51:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 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, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24wig9zw5xxL for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 10:51:03 -0800 (PST)
Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CABEC1A87BB for <ipv6@ietf.org>; Fri,  5 Feb 2016 10:51:02 -0800 (PST)
Received: by mail-qg0-x231.google.com with SMTP id b35so74599406qge.0 for <ipv6@ietf.org>; Fri, 05 Feb 2016 10:51:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=thx24L/6vmB8eOzibFp6XUEMt3+49k6NhsXu5Eb++xQ=; b=yvaUUK4+Bpw0fzhjnc4Ep71ir/c1MzvvgbFzVqpcSR0BzqL/sRDb032NCL3ILgd1+Y Is6Lj43xalmmqTNnyJo2dHS7t4Z6LePzQM2zSMSs6qOgCEEn2qd9ZlsT9Q5Hoj0ExBIO 6AJcslEO6o/Rsad3fqgfweBGTi27y5NmU1f8TS5m+Jt0aD5PgA/uyJX/e2VuT7gRfhlu HljKGGvDn3BiYxfEYMnTbjAYmY/ygdtNKsX5TJR3n+odMODhRZZTH4wjzLWRbedQGhu6 feplGQk0udJ01OIxCV225DUK3iKyxCERuLeE4W6kNfJBLbthe+fK6FLIdXaVRS1U0oO7 s7XQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=thx24L/6vmB8eOzibFp6XUEMt3+49k6NhsXu5Eb++xQ=; b=HXgHOiVb8biDyhRUZbRswCdjqcOh6jPq7lj/g/fZA8QFwV6KyuXR3MIOgwcZuwqAOB ga2L0M18PiN3qV7yaj1fOg6C6FlvxDWtkrfSMmp7CsWv24I/+EbKdwvEf/+vIol9BUhA vVW5MrIq80yk0pi+nTzxNvztHR29I9BRfkEN97vMj9WTXDb29Ur8AJK2DhGhpwICGB4c gxdr4newcMATfja3ASb5V3AtFh1vmQMIqY605wRuWtQLNWGcOW2FKfVJaFa+yEUJbXL1 wOK05eqQpItK61KtszxJU6bl0idH/+sfpCteqxWL1P7z7KcA4PzJrv3gcgjVrMRdqVNi ko+Q==
X-Gm-Message-State: AG10YORyUlnbYceCh1y8gBV+aEhxM0glx/H6UqKVb0GNU2NqjbBu3+WGXVZ95kYyvxNyvA==
X-Received: by 10.141.23.137 with SMTP id z131mr19449084qhd.52.1454698261994;  Fri, 05 Feb 2016 10:51:01 -0800 (PST)
Received: from ?IPv6:2601:647:4d00:abf0:f819:b18a:1d71:b4ae? ([2601:647:4d00:abf0:f819:b18a:1d71:b4ae]) by smtp.gmail.com with ESMTPSA id p80sm8472315qge.0.2016.02.05.10.51.00 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 05 Feb 2016 10:51:00 -0800 (PST)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_1D267B4D-9A2E-48E4-BB5B-4B954C3B70B8"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <39408594-E513-46DA-820A-AB0D5CB85C9E@employees.org>
Date: Fri, 5 Feb 2016 10:50:58 -0800
Message-Id: <42284482-EDBB-47DA-8CF6-D685355A9E49@gmail.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <2134F8430051B64F815C691A62D983183395D25D@XCH-BLV-105.nw.nos.boeing.com> <F01DCA0F-BCBF-4CD3-BF2B-412EE2FDC19C@employees.org> <56B49D89.5050202@innovationslab.net> <39408594-E513-46DA-820A-AB0D5CB85C9E@employees.org>
To: =?utf-8?Q?Ole_Tr=C3=B8an?= <otroan@employees.org>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/SxKyKLl3NrFLprRStHbTPIRJ0UU>
Cc: IPv6 List <ipv6@ietf.org>, Brian Haberman <brian@innovationslab.net>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 18:51:05 -0000

--Apple-Mail=_1D267B4D-9A2E-48E4-BB5B-4B954C3B70B8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Ole,

> On Feb 5, 2016, at 10:11 AM, otroan@employees.org wrote:
>=20
> Brian,
>=20
>>>> One question on the authorship - I can say with some certainty that
>>>> Jack McCann and Jeff Mogul are no longer with Digital Equipment
>>>> Corporation. Would they  be actively involved in this work if it is
>>>> accepted as a working group item?
>>>=20
>>> I don't expect them to be. For the documents we're advancing to
>>> Internet Standard, and therefore only do very minor tweaks to, I
>>> think it makes most sense to keep the original authors. Unless they
>>> object.
>>=20
>> Um, no. The original authors stay on the draft because they are the =
ones
>> responsible for most of the text within the document. Accurate
>> representation of authorship is critical for many reasons (e.g., =
IPR).
>=20
> my view is that it is the working group that is responsible for the =
document (and at a larger level the IETF).
> and that we have the authors listed on the first page as a way to =
recognise them as the main contributors.

I think this recognition is important.  The are the authors of the =
document that represents the working group=92s consensus.

>=20
> perhaps it is time to remove author names from our documents then.
> (as something the IETF should look at, not for these sets of documents =
obviously).

I don=92t support this notion.

Bob


--Apple-Mail=_1D267B4D-9A2E-48E4-BB5B-4B954C3B70B8
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJWtO8SAAoJEK7rdBF357uohh0H/iYT3PXoCPOmEUcrW3i2KJIi
WWLKvqQF6/FiTM+RCLeXt8CpYXNn0NPMR7JKuwqBjwC6+n/V1iiqj18k3516e4rJ
GRei5xauRjrb5yecwvWTRWZHe1xXmVDmaTMQfUEUnWG8HpOB3GKlV0Djue7drQRg
8meZB4ER1HiMHIVOtooctKcImcNrjrJQyfRA+6y+RAKX7SOJ+QeroYmok97SfyGs
C+ezei2tUR1A+v1IkgHV3Sl3vT8nHy8G5A8UvIrsMOkxFfjgP+8s2VXd9VUqIerK
NmOCueQJiuRsmL98nT9ONncctmQaLkTLaADgOSwopiGu71X++czQinmWA7dYtjE=
=9lf4
-----END PGP SIGNATURE-----

--Apple-Mail=_1D267B4D-9A2E-48E4-BB5B-4B954C3B70B8--


From nobody Fri Feb  5 11:01:04 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A04801A8833 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 11:01:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 UHojLEhS9kyT for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 11:01:00 -0800 (PST)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) (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 0777C1A882B for <ipv6@ietf.org>; Fri,  5 Feb 2016 11:00:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u15J15tp026295; Fri, 5 Feb 2016 11:01:05 -0800
Received: from XCH-BLV-103.nw.nos.boeing.com (xch-blv-103.nw.nos.boeing.com [130.247.25.118]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u15J0v3a026071 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 5 Feb 2016 11:00:57 -0800
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-BLV-103.nw.nos.boeing.com ([169.254.3.127]) with mapi id 14.03.0235.001; Fri, 5 Feb 2016 11:00:51 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>, "otroan@employees.org" <otroan@employees.org>
Subject: RE: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
Thread-Topic: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
Thread-Index: AdFgPnAxn72vBLTpQqid+VAMpL4ryQARzbYAAA+V7eA=
Date: Fri, 5 Feb 2016 19:00:50 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395F14A@XCH-BLV-105.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com> <56B4E91C.6090905@si6networks.com>
In-Reply-To: <56B4E91C.6090905@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Ci-xAlYE_LrHEY65Y33kvVst9Ng>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 19:01:01 -0000

Hi Fernando,

> -----Original Message-----
> From: Fernando Gont [mailto:fgont@si6networks.com]
> Sent: Friday, February 05, 2016 10:26 AM
> To: Templin, Fred L; otroan@employees.org
> Cc: Bob Hinden; 6man WG; Fred Baker (fred)
> Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption cal=
l on draft-hinden-6man-rfc1981bis-01)
>=20
> On 02/05/2016 03:13 PM, Templin, Fred L wrote:
> > Starting this under a new thread, IMHO if we want to promote RFC1981 to=
 standard
> > we should understand its use cases as well as the use cases for RFC4821=
.
> >
> > First, it is reasonable to expect that paths that begin and end within =
the same
> > well-managed administrative domain can be counted on to deliver the nec=
essary
> > ICMPs. An example is my employer's corporate network. In that case, tra=
ditional
> > PMTUD per RFC1981(bis) can be applied alone w/o having to apply RFC4821=
.
> >
> > On the other hand, paths that lead to Internet destinations cannot be c=
ounted
> > on to deliver the necessary ICMPs. In that case, RFC4821 provides a mit=
igation.
> >
> > But, if we do not believe that there are paths for which traditional PM=
TUD
> > can still be used safely, then we should be working to deprecate RFC198=
1
> > instead of making it a standard.
>=20
> Well, the thing here that you can do RFC1981-only, RFC4821-only, or
> RFC1981/RFC4821 (should I say "dual stack"? :-) ).
>=20
> With that in mind, one could as well have both RFC1981 and RFC4821 as
> standards, I guess...
>=20
> But yes, generally speaking, RFC1981-only is certaianly unreliable.

Except for within well-managed administrative domains where RFC1981-only
is sufficient. They do exist; I am typing this message from within one righ=
t now.

Thanks - Fred
fred.l.templin@boeing.com

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



From nobody Fri Feb  5 11:04:40 2016
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 395EC1A883E for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 11:04:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id esRlmjTzLhav for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 11:04:36 -0800 (PST)
Received: from mail-qg0-x233.google.com (mail-qg0-x233.google.com [IPv6:2607:f8b0:400d:c04::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D5CC1A87D5 for <ipv6@ietf.org>; Fri,  5 Feb 2016 11:04:36 -0800 (PST)
Received: by mail-qg0-x233.google.com with SMTP id b35so74942666qge.0 for <ipv6@ietf.org>; Fri, 05 Feb 2016 11:04:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=5xkCCWR+6UU/s+Sh2xP0XKdks/E5wr7QB8DjN3A2urU=; b=G0fgHfbLju+eTQlF7FbW7kxb1KeKSXVx9MY/DwUGCE622Ewb+WsyYzsC5Q43ZH86ME Dd7SR3xd6PeWGxFtLu3KfnVJO/tt4h/o7ruazl23aMwTJ595X1XE01jMR7wqEaYMtpAw p2bbjkVlwQmApkb73ENlu40IYxPHlh3ZLblMYciA3vb4EJrSHMyJkGPdFYzGmPwWyZlR WaqfUnQx7ROJVmC7eoJ0xCmBfgzVRwmxV1C6sNRtWNS5xpBntVMUdOmv82hp49+UYeob Em6oO0KWcYOX75Hc/lSXZr9Y04YzY9ZWtU897YKVkTTsh4wLyOdaa36kKidNXa4pVY9Y yeLA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=5xkCCWR+6UU/s+Sh2xP0XKdks/E5wr7QB8DjN3A2urU=; b=dhQJWH1KBpTdUJWjJSnv36dxzK3iBe8+OWwYHbTvNRWhc6l9zrooq0ochkDMiILsr8 8Vb0nnIgD5eZA6s8RZRGNMynjDNHEwV1Mc5qm/3El5YWgUNKrRvTpwm60uxVdFkW5U6v ystNyrY+2FY4F5w/ouEneNN6vSqW+aIvuog+M6nBZnY5CSlu3d0BqWHaIhlCKUZQI1CW ZTZL/GKcN02B5NCcOVL2Jwxm/s5Qz9mx9VPfR6iYwKwOUJfHxBF8AI7Ynqeg2UpB/rvs RLlQRG+YKbRATPvIBzhG7+Mda/KNcOxlGdAzv9Tro52QUps0W6mn6Mh3iqV3JflEYFqQ KmgA==
X-Gm-Message-State: AG10YOT3H7JV5IE+9gUA4/icWMmNzFi5DC/UoVoZMb8vajt03EKnoiDRTr0f6t5fJTqDiw==
X-Received: by 10.140.16.225 with SMTP id 88mr19025635qgb.96.1454699075839; Fri, 05 Feb 2016 11:04:35 -0800 (PST)
Received: from [10.0.0.24] (c-71-202-19-53.hsd1.ca.comcast.net. [71.202.19.53]) by smtp.gmail.com with ESMTPSA id w16sm8516318qka.35.2016.02.05.11.04.34 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 05 Feb 2016 11:04:34 -0800 (PST)
Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_569777CC-2804-4C2F-B553-CB6BF723EE33"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com>
Date: Fri, 5 Feb 2016 11:04:31 -0800
Message-Id: <93A717B5-CDAD-4273-B3A3-8A48C984109D@gmail.com>
References: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/FLm8sXMGvh8s0Diu6NQEGjqh1aE>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 19:04:38 -0000

--Apple-Mail=_569777CC-2804-4C2F-B553-CB6BF723EE33
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Fred,

> On Feb 5, 2016, at 10:13 AM, Templin, Fred L =
<Fred.L.Templin@boeing.com> wrote:
>=20
> Starting this under a new thread, IMHO if we want to promote RFC1981 =
to standard
> we should understand its use cases as well as the use cases for =
RFC4821.

Sorry for being argumentative, but this is not a requirement to move =
RFC1981 to Internet Standard.  It=E2=80=99s already at Draft Standard.  =
See RFC6410.

Instead continuing the debate over how RFC4821 should be cited in =
rfc1981bis, I am starting to think that a separate new document could =
discuss the relationship between the two approaches to learning the MTU, =
and make some recommendations on how they should be used together or =
separately.  Perhaps a BCP or update to Node Requirements.

I don=E2=80=99t think this topic needs to be part of advancing RFC1981.

Bob

>=20
> First, it is reasonable to expect that paths that begin and end within =
the same
> well-managed administrative domain can be counted on to deliver the =
necessary
> ICMPs. An example is my employer's corporate network. In that case, =
traditional
> PMTUD per RFC1981(bis) can be applied alone w/o having to apply =
RFC4821.
>=20
> On the other hand, paths that lead to Internet destinations cannot be =
counted
> on to deliver the necessary ICMPs. In that case, RFC4821 provides a =
mitigation.
>=20
> But, if we do not believe that there are paths for which traditional =
PMTUD
> can still be used safely, then we should be working to deprecate =
RFC1981
> instead of making it a standard.
>=20
> Thanks - Fred
> fred.l.templin@boeing.com
>=20


--Apple-Mail=_569777CC-2804-4C2F-B553-CB6BF723EE33
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJWtPJAAAoJEK7rdBF357uoRUgH/Rqvb7QR3LKhaSujGgpwHF5l
QTsfNQpHvCLiQCW9kue1LZjywQMiedk5XtlPUsDI+hx8V3FV4h0lMg9n/dsR/tYv
MYabnAoLovfCQ7NaNM/gVGab4dvYbQox2Bi3rACvek+R88zCHEd/W1kwLuY4iKsF
/BZGMJP35uIV3rrc/qiC58/Admdq0FKAagOjvYiupTDFBT1qoNTZUwGsZqO+nnd/
MrPELdCztQsoau40ToMC95Yf+Cy6xFPJ7vYxZFNgKwE/AFnIqXcnKond+uo6VeOC
aX5fDJzVF8hDmzBI7nVIzeUKea6lEKRx+wu3jHt5tugaIEAKMbTbXOISt3WXuS4=
=gRvq
-----END PGP SIGNATURE-----

--Apple-Mail=_569777CC-2804-4C2F-B553-CB6BF723EE33--


From nobody Fri Feb  5 11:16:18 2016
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E38591A885C for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 11:16:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-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 ELbslYvGcs9w for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 11:16:15 -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 40E671A8859 for <ipv6@ietf.org>; Fri,  5 Feb 2016 11:16:15 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 0E5D42009E; Fri,  5 Feb 2016 14:16:14 -0500 (EST)
Received: from obiwan.sandelman.ca (ip6-localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id C4AA863751; Fri,  5 Feb 2016 14:16:13 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Templin\, Fred L" <Fred.L.Templin@boeing.com>
Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
In-Reply-To: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 05 Feb 2016 14:16:13 -0500
Message-ID: <7592.1454699773@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/rEzC81K_he5IVymbI0Q3s_tzP8k>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 19:16:17 -0000

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


Templin, Fred L <Fred.L.Templin@boeing.com> wrote:
    > On the other hand, paths that lead to Internet destinations cannot be
    > counted on to deliver the necessary ICMPs. In that case, RFC4821
    > provides a mitigation.

    > But, if we do not believe that there are paths for which traditional
    > PMTUD can still be used safely, then we should be working to deprecate
    > RFC1981 instead of making it a standard.

I think that the mitigation is far more reliable than 1981.
So, I'd rather deprecate RFC1981.

{I noticed that 4821 is not on by default in most Linux distros/kernels,
and I actually want to know if there is some reason for it}

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




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

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

iQEVAwUBVrT0+oCLcPvd0N1lAQLeQgf/dl6qjr0/7xcx2gh1xfAVsY0PSxFIE5zK
4gf0E92CEpAclkwcl90tvPzyL8WWD+tZdVMnJ7oJuNTC0RKmmULYqBm/MXK83tMc
OXKKONwCqLZaPOiBrbPHuhiybMxY65DlCa6snkYxDWhFbv8uAdnx9EgqljNlN+9a
bCKZ3+2vAcznATkwLrztXRCGhAvHc9uvgaEDQ46Muy+nSJg7BrhmUSPYSCJKFBkD
S847FEnUS5Skn5upkIYFJmoctjY2t3+KSpqLurgTb7z46QBZXOhCXNN9B4pTBQ/7
ANqNQuWe3PK4zBLwUV+JCfhMKDGOuE9H/+KRmbaNn8zvD7izIdXBsw==
=F0ob
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Feb  5 11:22:28 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E8D81A8879 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 11:22:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 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, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oRDVlnnuvSYn for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 11:22:24 -0800 (PST)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 124FB1A8873 for <ipv6@ietf.org>; Fri,  5 Feb 2016 11:22:24 -0800 (PST)
Received: by mail-pa0-x235.google.com with SMTP id ho8so38616649pac.2 for <ipv6@ietf.org>; Fri, 05 Feb 2016 11:22:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=xMMZyWQWe4W2jHJelPkpELk2BoaHhGK1Yu8Fo5nfiVk=; b=w5jhFlnfviehbSuc56SRfHaU5LtK40p01fjBIKh+xmsGjYKk6efwOIAYX+LkTl7c9L Jz3/QISnpahRVdKmJakiachZ0X3LZGEX6/ouB3EdWcbPxAXUfn9XEUz/Jgttp1GRdbAx +lM5sHZrCbw12wHtPTrjqJNpOM+3KgmSpQtS1zlEx3qYDyugemuNprPn5Qgn6gLLt63o r/HdonwdF1m2W9Gq0lOHzSHL6ol3pX0Y34v7eyb0UL4djK8/SQTQ1uZKVE6rFajsQZFq iR9apwyYP8ZcEmucWyKr9xPqt3NwPOVT34vX0kQGjpe386WXo4JiA9+Ps9ja7SW3yWpd kRuQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=xMMZyWQWe4W2jHJelPkpELk2BoaHhGK1Yu8Fo5nfiVk=; b=M6tyuwvm5QxSa1BJ7Lfq/xwKeWCjnv281fPyXrpxjTnJXVPb6pCBjDDA/uw65Ig5wb ra0NYGYCgc0HlJF3KrjSIpgT8hn0wq0/XFtrGk+1uhV68qa6yLYMjatgnxMh6dBNakh2 rW++SxlNjdWS5NouANVa3Jf+tv1mpichT1u0+f/aTPkv0CfKUYechgJPmbYBdxNyNPiF 1AxhPxPn1lvgv69KxwNTG9yAJraABK5WJKFUj7+X99od772tMO/kOV7AF1C/g19oVxeJ KAHc1WcV1wAMVHcash8+Zl+MnPfoBdjiwTfqKxxAVi+tQtKn+pkzpB/rlxAl/ZmA7EIk +KVQ==
X-Gm-Message-State: AG10YOTn/26LrBQLRI2nYKO+fbLi1kZ+qU6R6vdU19HP4p+ndeXkww6kvrJegFtSNflMkw==
X-Received: by 10.66.62.132 with SMTP id y4mr21783420par.49.1454700143715; Fri, 05 Feb 2016 11:22:23 -0800 (PST)
Received: from ?IPv6:2406:e007:4357:1:28cc:dc4c:9703:6781? ([2406:e007:4357:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id ze5sm26269619pac.32.2016.02.05.11.22.19 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 05 Feb 2016 11:22:21 -0800 (PST)
Subject: Re: 6MAN WG Last Call - draft-ietf-6man-multi-homed-host-03.txt
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
References: <2052A806-4D40-4A17-9892-90E39B67C65C@gmail.com> <CAJE_bqekFsfHPkfLTAOHgdL-MpvwNSV=gB8Cv0x+YrD66JUyMg@mail.gmail.com> <56B3D4BF.9000202@gmail.com> <CAJE_bqczUQ1UX=mLBzd=XpoKDjO616NrO4iQYZvK7T7CFVzXOQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56B4F674.5050207@gmail.com>
Date: Sat, 6 Feb 2016 08:22:28 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <CAJE_bqczUQ1UX=mLBzd=XpoKDjO616NrO4iQYZvK7T7CFVzXOQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Ms5BAIvF_coA9zgUXPqNGozDxfA>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 19:22:25 -0000

On 06/02/2016 06:06, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 wrote:
> At Fri, 5 Feb 2016 11:46:23 +1300,
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>=20
>>>   The seeming open points are:
>>>   + whether to move the host-model discussion to an appendix
>>
>> My personal choice is not to move it, but I would certainly do so
>> if that was the WG's preference.
>=20
> Okay.
>=20
>>> - Section 3.1
>>>
>>>    As described in [RFC4191] and [RFC4861], a Router Advertisement ma=
y
>>>    contain zero or more Prefix information Options (PIOs), zero or mo=
re
>>>    Route Information Options (RIOs), or a Default Router List.
>>>
>>>   I'm not sure if I can understand the "or a Default Router List"
>>>   part.  If it means 'Router Advertisement may contain...a Default
>>>   Router List', it doesn't make sense since an RA (or any of its
>>>   options) doesn't contain such a list (Default Router List is
>>>   something that a host maintains based on the content of RA).
>>
>> I think you're correct.
>=20
> Then I guess the sentence will have to be revised, but I can't suggest
> anything specific as I don't understand the original intent.  Does
> this "Default Router List" perhaps actually means the source IPv6
> address of the RA (which will be maintained in the Default Router List
> of the receiving host)?

I think we should simply delete ", or a Default Router List". That list
is created and maintained by the host, as you say.

    Brian

>=20
>>> - Section 3.1: likewise, the use of 'a default router list' in the
>>>   following sentence is confusing, too:
>>>
>>>    [...]  In a multi-
>>>    homed network implementing source/destination routing, the
>>>    interpretation of a default router list or an RIO has to be modifi=
ed
>>>    with the words "if the source address is in one of the prefixes I
>>>    advertise in a PIO".
>>
>> This is correct, isn't it? It applies to what the host has stored in
>> its default router list and to any new RIOs that it receives. It could=

>> be phrased more carefully, I agree.
>=20
> Maybe one source of confusion comes from the fact that this paragraph
> starts talking about the content of an RA.  So one possible way to
> improve the text would be to revise it focusing on hosts' conceptual
> data structures rather than RAs that populate these structures.
>=20
> On re-reading the text again, I've also noticed a few more glitches:
>=20
>    [...] In their
>    original intent, these indicate general information to a host: [...]=

>    "you might create or be configured with an address in this prefix", =
=2E..
>=20
> Technically, "you might create an address in this prefix" is a matter
> of RFC4862, so I think it should be referenced with RFC4191 and
> RFC4861.
>=20
> Also, I'm not sure if "you might be configured with an address in this
> prefix" is part of the "original intent".  While it would be usually
> the case that a global address manually configured or by DHCPv6 is in
> a prefix advertised in a PIO (and normally with L=3D1), I would rather
> consider it operational reality rather than an "original intent" of
> these RFCs.
>=20
> I think I can suggest alternate text to address some or all of these
> points, but to do so I'd like to know the answer to the previous
> point.
>=20
>>> - Section 3.4
>>>
>>>    There is potential for adverse interaction with any off-link Redir=
ect
>>>    (Redirect for a GUA destination that is not on-link) message sent =
by
>>>
>>>   Is there any particular intent about why we specially say "GUA" her=
e
>>>   instead of, e.g., just "a global destination"?  For example, does i=
t
>>>   intend to exclude ULAs?  If so, why?  In case of ULAs, while the
>>>   proposed host behavior may be less critical with ULAs in practice, =
I
>>>   don't see any technical reason why we can't use it for ULAs.
>>
>> To me it's clear that both "GUA" and "global" include ULAs, because UL=
As
>> are defined to have global scope. Do you think there is a formal
>> difference between "GUA" and "global"?  If so, is it documented?
>=20
> It's probably not so clearly documented, but, for example, RFC4193 has
> this text:
>=20
>    It is expected that they would share the same Subnet IDs with
>    provider-based global unicast addresses, if they were being used
>    concurrently [GLOBAL].
>=20
> (Here "they" means local IPv6 addresses) To me this sounds like if you
> explicitly say a "global unicast address" it can implicitly indicates
> the address is not a local addresses.
>=20
> On the other hand, I (personally) don't feel such ambiguity about the
> term "a global IPv6 address" since, as you noted above, ULAs have the
> global scope.
>=20
> Going back to my original comment, I now see there was no specific
> intent in the use of GUA.  Then I suggest revising this
>=20
>    (Redirect for a GUA destination that is not on-link) message sent by=

>=20
> to
>=20
>    (Redirect for a global destination that is not on-link) message sent=
 by
>=20
> to avoid possible confusion.  The latter doesn't explicitly say it's a
> unicast destination, but I believe it's obvious from the context (the
> destination of a redirect cannot be a multicast address).
>=20
> --
> JINMEI, Tatuya
>=20


From nobody Fri Feb  5 11:52:23 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A0641AC430 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 11:52:22 -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 BFzwShxwKTHT for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 11:52:20 -0800 (PST)
Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B24ED1AC42F for <ipv6@ietf.org>; Fri,  5 Feb 2016 11:52:20 -0800 (PST)
Received: by mail-pf0-x236.google.com with SMTP id o185so73749679pfb.1 for <ipv6@ietf.org>; Fri, 05 Feb 2016 11:52:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=91kHfgCXV6xAiHM6so4T9A4E3Mb7dWsCJnAZoyEqCIc=; b=Yi1znDicqtSdlmuvtyf40sF/WLrunZ6lR/2CoRga5qC3Fz+dlJ9sRBW7i8hTrS8caZ iIZLKc+3vLZUP2zbqoVbef1DUUGDUBSTUefuU+vhjaPVrLdP3mACAWH9g10IDJEmiSHM ll4oN1ET6246tZJxpMUmIBu4dPlqQf5FyDPmKdXIsxDiwkiImRNhFV66NBciFfvapZnp BYmgrmtBS27eEvUdmYs+79weTJuWVpX5HOYlwLYQDwzXQhQ7eNyUGYOWOHkURje2kEq2 eXLJe4NdZqiZ0I5xfm+SYaU9VZZ1V5wWUzcYbnxndk4VJg6ng0375DPWNc/PU1E5i51v +V2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=91kHfgCXV6xAiHM6so4T9A4E3Mb7dWsCJnAZoyEqCIc=; b=DWqBDSP1UopqFPI6uhXtyAo27GnaWCKm5r0avx0obdeO1cjh7JFY+GSMEZ0Z+QpAIZ 5vshgmfrwShfTYdmcn3vwX355rHvZGjmUR96krfc2RudKS6JRzGWzpqRPJEwgoSsksBR NlJncXo3+fEUC8BZ4nEecOGZDVfvh+Xr4OtVjwd43/f2M+LyywaJ4LvXR4R9G6JYsmIm xLlueEIkdevDjc/dw6OgIx0LZ8FOOJ8dJdv+Q1VUzl9igYA3D1+iaTnxXLZ2UwU1dTb3 M2xE32E0nzZ2Z8bGkqGvsCcoflraTxF0MITjQEmrYplf/Ql1j6cOcD4XYT5rEtNjKkOu CIhw==
X-Gm-Message-State: AG10YORzYkbXzHWAMMjCapIAZqqxuLiyyKO5Xr/OMVoRrlMe3Cflp9utLn4NqmpvwiEgRA==
X-Received: by 10.98.67.149 with SMTP id l21mr22409240pfi.112.1454701940370; Fri, 05 Feb 2016 11:52:20 -0800 (PST)
Received: from ?IPv6:2406:e007:4357:1:28cc:dc4c:9703:6781? ([2406:e007:4357:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id yh5sm26356239pab.13.2016.02.05.11.52.17 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 05 Feb 2016 11:52:19 -0800 (PST)
Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
To: Bob Hinden <bob.hinden@gmail.com>, "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com> <93A717B5-CDAD-4273-B3A3-8A48C984109D@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56B4FD7A.3090105@gmail.com>
Date: Sat, 6 Feb 2016 08:52:26 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <93A717B5-CDAD-4273-B3A3-8A48C984109D@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/BSK7qFtK0L24yZLGdwD0CyXV0Aw>
Cc: IPv6 List <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 19:52:22 -0000

On 06/02/2016 08:04, Bob Hinden wrote:
> Fred,
>=20
>> On Feb 5, 2016, at 10:13 AM, Templin, Fred L <Fred.L.Templin@boeing.co=
m> wrote:
>>
>> Starting this under a new thread, IMHO if we want to promote RFC1981 t=
o standard
>> we should understand its use cases as well as the use cases for RFC482=
1.
>=20
> Sorry for being argumentative, but this is not a requirement to move RF=
C1981 to Internet Standard.  It=E2=80=99s already at Draft Standard.  See=
 RFC6410.
>=20
> Instead continuing the debate over how RFC4821 should be cited in rfc19=
81bis, I am starting to think that a separate new document could discuss =
the relationship between the two approaches to learning the MTU, and make=
 some recommendations on how they should be used together or separately. =
 Perhaps a BCP or update to Node Requirements.
>=20
> I don=E2=80=99t think this topic needs to be part of advancing RFC1981.=


Yes, that seems right to me.

And in answer to other messages, I think it would be ludicrous to conside=
r
obsoleting RFC 1981. It isn't broken. It is fair to note that in cases wh=
ere
ICMP fails, PMTUD fails too.

   Brian


From nobody Fri Feb  5 12:00:32 2016
Return-Path: <fred@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCE511ACEB4 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 12:00:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.502
X-Spam-Level: 
X-Spam-Status: No, score=-114.502 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3YQBYuSmMrxW for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 12:00:29 -0800 (PST)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88B781ACE8C for <ipv6@ietf.org>; Fri,  5 Feb 2016 12:00:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3668; q=dns/txt; s=iport; t=1454702421; x=1455912021; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=oXsLh0TYyeXVk2ZyI8Z6aOLkT4h7DgV1M0ntEsGt/5c=; b=YazXb2zd9g8HkPgQgXaoNJ/XnPqMM1QpzYdzhTUHKFEaHP6lvPaSTDEu f8ydzWdusEgvaSEi0UJJv+zPG2M8xrqGaTlfBfcayfJCivdbYv6+LjjAE Ry/qFAlJe8v+ODdXCFgE7BrtnsYCk2NfDP06GRdzyRBa94NV1e2gIs9EA M=;
X-Files: signature.asc : 833
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DVAgBJ/rRW/4UNJK1YBoM6gT8GiFWue?= =?us-ascii?q?IITDoFmhg0CgTU4FAEBAQEBAQGBCoRBAQEBAwEjSgUHBQsCAQgYIwcCAiERJQI?= =?us-ascii?q?EDgUOh3gDCgixCIoBDYRDAQEBAQEBAQEBAQEBAQEBAQEBAQEBDQiHf4JKgjeBa?= =?us-ascii?q?4MQK4EPBZZ1AYJ9gWSGe4FzgVuNGIVugQ+HQAEeAUOCMIE0aokAfAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.22,401,1449532800";  d="asc'?scan'208";a="68713035"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 05 Feb 2016 20:00:18 +0000
Received: from XCH-ALN-013.cisco.com (xch-aln-013.cisco.com [173.36.7.23]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id u15K0Ijm023471 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 5 Feb 2016 20:00:19 GMT
Received: from xch-rcd-013.cisco.com (173.37.102.23) by XCH-ALN-013.cisco.com (173.36.7.23) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 5 Feb 2016 14:00:18 -0600
Received: from xch-rcd-013.cisco.com ([173.37.102.23]) by XCH-RCD-013.cisco.com ([173.37.102.23]) with mapi id 15.00.1104.009; Fri, 5 Feb 2016 14:00:18 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
Thread-Topic: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
Thread-Index: AQHRYE/W5JhQnqQeUkq4tinjvD+flA==
Date: Fri, 5 Feb 2016 20:00:18 +0000
Message-ID: <DD26D90F-0B66-4C53-B306-971E8539F1E8@cisco.com>
References: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com> <93A717B5-CDAD-4273-B3A3-8A48C984109D@gmail.com>
In-Reply-To: <93A717B5-CDAD-4273-B3A3-8A48C984109D@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3112)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.248.62]
Content-Type: multipart/signed; boundary="Apple-Mail=_EC85B599-F29E-4CF2-912B-05F2DF70B509"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/WS4W3MaUqvYmYchhchdJBzJI0pU>
Cc: IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 20:00:30 -0000

--Apple-Mail=_EC85B599-F29E-4CF2-912B-05F2DF70B509
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Feb 5, 2016, at 11:04 AM, Bob Hinden <bob.hinden@gmail.com> wrote:
>=20
> Instead continuing the debate over how RFC4821 should be cited in =
rfc1981bis, I am starting to think that a separate new document could =
discuss the relationship between the two approaches to learning the MTU, =
and make some recommendations on how they should be used together or =
separately.  Perhaps a BCP or update to Node Requirements.
>=20
> I don=E2=80=99t think this topic needs to be part of advancing =
RFC1981.

That thought has crossed my mind as well. It is unusual to have a =
specification describing one approach comment on a different =
specification about a different approach.

If we were to write such a specification, what would it need to say?

I think the following would need to be present:

1) pointers to RFCs 1981bis and 4821
2) reports of experience (not just concern) with each
2a) environments in which each works well
2b) demonstrated issues with each
3) recommendations about deployment

2a for RFC 1981bis, would likely say that if ICMP PTB is not being =
blocked and a host is sending TCP segments that are too large, it =
quickly knocks them to a workable size. 2b for RFC 1981bis would likely =
say that if ICMP PTB is being blocked or spoofed, it doesn't behave =
well.

2a for RFC 4821 should likely say that it achieves a reasonable MSS. 2b =
might observe that it is not guaranteed to do so quickly.

As a recommendation, it seems like TCP should follow some kind of rule. =
There is an argument for sending segments in the initial burst of IW =
different sizes (including at least one derived from a 1280 byte MTU, =
one from a 1500 byte MTU, and one from a 9000 byte MTU, each less the =
sizes of any known headers) and either seeding the 4821 algorithm with =
the ack/sack response information, using the number found in a =
responding ICMP PTB, or, in the absence of an ICMP PTB, selecting the =
largest of those sizes that was acked or sacked. I'll bet Matt Mathis or =
one of his compadres would have a better approach.

We would also want to have an implementation report on the =
recommendations (at least one, ideally one used in each of several =
operational environments including virtualized data center, mobile =
wireless, wifi, broadband, and backbone).



--Apple-Mail=_EC85B599-F29E-4CF2-912B-05F2DF70B509
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIVAwUBVrT/UUayAOS/EQ8MAQJBTg//WRx3CqOiy+5+1IGEGWOEYff9/IJ5QXNG
2Z/bhZNdfqWlzcjVk+MfzPeGNsjYHb/OYNIyxubHRkHnoB4Bq0Hhhz12ynO6UsyD
PbX82R5w+uj/aZDfP0evkW2YUNBBmhZFyazCo4wFVKVdTja2e1gBwPSVs+utlUuu
p/Mal4dwQry/JBtVnvwoteMUj9QR5vER68pNN8qK1/3a1PbdbuzMqcCL2H8wQSaG
+yjSZIekO7/MFfrSB7v+3C71XixdEBW3uSSqPqucY3eRBNwvSOKdl0t5F96fb3cf
pAtEhrFdYmGu7gwZVX6aP9bo8R4qbc39VRFa8nsd7rIcSutee74pAZ1gcgqXvRFc
Ws9GipFGoKHo+LID5IG1CJ4O5M2K/xzgtxY5K+M3wrPciRtrgzQO6j1F3amlUT4l
n8kmv8psCnbg2P5GldBXOT+rZahu4KXDccBSok+JeTU2MOXOQlgC+0/ri5ZJAGUe
YrQTpB9Xw4Ewon0SUa+Fy30QTRM8ZGymV/7B9S/Al4vwodfCnwHU2T9lcYKXwdCc
rd9HylQFW5hHMVPvgFQSyW/F0yXfomUbhDMm5jcvtRueMYaQUtHn/LLzsI6gTPhv
K4uEM30DxyYfzLttIR428rRBqpHZzSn5vsjCrSuU7j/vs6ND1793GFIae+AhX4OT
bKGH7o7ceS4=
=HID/
-----END PGP SIGNATURE-----

--Apple-Mail=_EC85B599-F29E-4CF2-912B-05F2DF70B509--


From nobody Fri Feb  5 12:01:48 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF07C1ACDFA for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 12:01:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 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, J_CHICKENPOX_12=0.6, 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 N-ry6f0Hv7tw for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 12:01:46 -0800 (PST)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DBE01ACDA0 for <ipv6@ietf.org>; Fri,  5 Feb 2016 12:01:27 -0800 (PST)
Received: by mail-pa0-x22a.google.com with SMTP id yy13so39039459pab.3 for <ipv6@ietf.org>; Fri, 05 Feb 2016 12:01:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=sdYZ9feGG7Nx+onU74ImU/btf0ZG7IOevKZCbuCqSP0=; b=DPc/kH4e9k4l5JmEqnYrlJHkhYNNl4b/4IbZhQFFZbcLPvz8Xy+72BD3SYB+D+1kaT R+Ao+M+OwFrriyXfcalRDa7TygtyceSz0DAGjL+SowpVtloH9fNChorMNBUMc9ptLYaI S15VIMpqzFn+CYkIGgd5h2OBznXe3IeOfIYwa596GWUQAykf2B4Y/DD3iFK7OlPIB9Pm 7rb+yO7QeFdyVPaeqRDGjhz0OG/xwtG5kfaXr4rtR/+bFuvjhWjqkswB8Za53AYiBRNn CXgrnshBqQjnoprTogiblfvLeiRZDHTMZLRdS23dmEUCSGVZ5pYB52wU1WSHkjAyCcAy /0KA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=sdYZ9feGG7Nx+onU74ImU/btf0ZG7IOevKZCbuCqSP0=; b=k7ZAeTHVTc+DwudCKowWZwCpP3J+QBfvD4t4Ud78/Et3cV0M+K9AoscbpdXvV1HiHR T0hs3fcFoh8C5f+GBOIJm4J99OeSoUbZFfMPMZhrMqaq2wLOoDL3PvN3Y6z12Bq+V2jm uRwLttHmYbvq3wDXn6gHP+34G8mfDryliipiT8PaaXIFy5+RLN9bP2oIO+VSHTBvxKt0 DCBIp2o6OYN9Hv3uRkpZ6qaAxAfaXeMmyeaAheO87ztssf+Ib1AWOBno9K1dnoQslQNa JtcvqEfdSPE+c24701n50pabpvAS4o3qEzx4tXHX8xvGkJ+m2KyHNFpCMFV/tlyA4LqS NInw==
X-Gm-Message-State: AG10YORFmrh0MwcHa9jvRHTaJf/Y6Up+NvfAoFkPRhViKQtIrHWNTbGmMyu3ATgtcsdN4A==
X-Received: by 10.66.122.8 with SMTP id lo8mr22799711pab.35.1454702486832; Fri, 05 Feb 2016 12:01:26 -0800 (PST)
Received: from ?IPv6:2406:e007:4357:1:28cc:dc4c:9703:6781? ([2406:e007:4357:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id u21sm26395319pfi.15.2016.02.05.12.01.23 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 05 Feb 2016 12:01:25 -0800 (PST)
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: Fernando Gont <fgont@si6networks.com>, otroan@employees.org
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56B4FF9D.10203@gmail.com>
Date: Sat, 6 Feb 2016 09:01:33 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B4E7FB.5010700@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Mj-A9q6yvTiFmSm_lhsiXMgza8Q>
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 20:01:47 -0000

On 06/02/2016 07:20, Fernando Gont wrote:
> On 02/05/2016 03:07 PM, otroan@employees.org wrote:
>> Fernando,
>>
>> [...]
>>
>>>>
>>>> What is the risk of using the same IID for link-local and global addresses?
>>>> Typically if you can snoop the link-local address then you're onlink and leak information about all addresses and their correlations anyway.
>>>
>>> We discussed this one a hundred times now (including for RFC7217). The
>>> risk is that at times such addressess can leak, without the need of the
>>> attacker being pesent on the local link.
>>>
>>> e.g., your MTA is on the local-link, and you end up connecting to it
>>> with a LL, which then appears in the email headers. (and there are a
>>> bunch of other possible reasons for that to happen).
>>>
>>> Be proactive. MAC addresses in the IID are wrong. Putting them there is
>>> just waiting for trouble.
>>
>> I didn't say the LL was based on a MAC.
>> my question was if there was any issue with re-using the IID from the link-local in the GUA. assume the link-local is generated f.ex with 7217.
> 
> Oops, my apologies. My answer would be "It unnecessarily enables
> correlation of the activities that you carry between the two addresses".
> 
> i.e., by simply inspecting the IID I could easily tell that the
> activities carried out with one address were performed by the same node
> that employed the other address.
> 
> My take here is, again: be proactive. If there's no requirement (and
> there isn't) for the two IIDs to be the same, then make them different,
> and fail on the safe side.

But Ole's point was that any observer who sees a LL packet is on-link and
can therefore see the MAC address anyway; an observer who can see MAC addresses
can just laugh at RFC 7217 or RFC 4941.

   Brian


From nobody Fri Feb  5 12:18:14 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD47D1ACE4B for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 12:18:12 -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] 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 ypQc6-hWigqW for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 12:18:10 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3717D1ACDC5 for <ipv6@ietf.org>; Fri,  5 Feb 2016 12:18:10 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 4CEEF206A2B; Fri,  5 Feb 2016 21:18:04 +0100 (CET)
Subject: Re: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "Fred Baker (fred)" <fred@cisco.com>
References: <2134F8430051B64F815C691A62D983183395EF42@XCH-BLV-105.nw.nos.boeing.com> <56B4E39A.5040608@si6networks.com> <2134F8430051B64F815C691A62D983183395F017@XCH-BLV-105.nw.nos.boeing.com> <56B4EA46.3080102@si6networks.com> <2134F8430051B64F815C691A62D983183395F0CE@XCH-BLV-105.nw.nos.boeing.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B50285.9010204@si6networks.com>
Date: Fri, 5 Feb 2016 17:13:57 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <2134F8430051B64F815C691A62D983183395F0CE@XCH-BLV-105.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Ef23rav53--_xaAaxu7BLeK-5-I>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 20:18:12 -0000

On 02/05/2016 03:42 PM, Templin, Fred L wrote:
> Hi Fernando,
> 
>> -----Original Message-----
>> From: Fernando Gont [mailto:fgont@si6networks.com]
>> Sent: Friday, February 05, 2016 10:31 AM
>> To: Templin, Fred L; Fred Baker (fred)
>> Cc: Bob Hinden; 6man WG
>> Subject: Re: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
>>
>> On 02/05/2016 03:25 PM, Templin, Fred L wrote:
>>> Hi Fernando,
>>>
>>>> -----Original Message-----
>>>> From: Fernando Gont [mailto:fgont@si6networks.com]
>>>> Sent: Friday, February 05, 2016 10:02 AM
>>>> To: Templin, Fred L; Fred Baker (fred)
>>>> Cc: 6man WG; Bob Hinden
>>>> Subject: Re: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
>>>>
>>>> On 02/05/2016 02:46 PM, Templin, Fred L wrote:
>>>>> Hi Fred,
>>>>>
>>>>>> As soon as I say "there is no such attack", one will materialize, so I won't assert that.  However, I am not aware of attacks in
>> which
>>>>>> someone creates ICMP PTBs and sends them to someone else in order to reduce their windows unnecessarily.
>>>>>
>>>>> RFC4821 Section 11 (Security Considerations) recognizes the potential for spoofed
>>>>> (i.e., inaccurate) ICMP PTB messages and suggests a mitigation (ignore all ICMP PTBs).
>>>>> For paths over which any node in the network can inject an inaccurate ICMP PTB
>>>>> message, an attack vector exists.
>>>>
>>>> In theory, you can do some basic validation for ICMP messages. However,
>>>> in v6, as a result of possible EHs, you may not find any meaningful data
>>>> in the ICMP payload to apply validity checks on.
>>>>
>>>> Anyway, you can implement the countermeasure we implemented in
>>>> <https://tools.ietf.org/html/rfc5927#section-7.2> -- I implemented it
>>>> for OpenBSD, and it still runs it... and IIRC it was ported to at least
>>>> NetBSD later.
>>>
>>> Thanks for the reference. It seems to account for the case of paths that may
>>> deliver inaccurate ICMP PTBs, but does not account for the case of paths that
>>> fail to deliver accurate ICMP PTBs. Do we know of paths always deliver
>>> accurate ICMP PTBs but can also deliver inaccurate ICMP PTBs?
>>
>> What do you mean by "accurate"?
> 
> By "accurate" I mean:
> 
> - the router that sends the ICMP PTB is telling the truth that there is a restricting link
> - the MTU value that the router writes in the PTB is in fact the true MTU of the
>    restricting link

Well, most of these protocols run on "good faith", right? -- If I cannot
trust the router to tell the truth, why should I trust it to e.g.
forward my packets?

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





From nobody Fri Feb  5 12:18:26 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 422551ACE7C for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 12:18:20 -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] 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 OPW6MIwBhFzH for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 12:18:16 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AC8E1ACE7B for <ipv6@ietf.org>; Fri,  5 Feb 2016 12:18:16 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id B8CB3206AF1; Fri,  5 Feb 2016 21:18:12 +0100 (CET)
Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "otroan@employees.org" <otroan@employees.org>
References: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com> <56B4E91C.6090905@si6networks.com> <2134F8430051B64F815C691A62D983183395F14A@XCH-BLV-105.nw.nos.boeing.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <56B502FB.4050302@si6networks.com>
Date: Fri, 5 Feb 2016 17:15:55 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <2134F8430051B64F815C691A62D983183395F14A@XCH-BLV-105.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/LVGz4o63358gYDiT5lp9E1outl4>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 20:18:20 -0000

On 02/05/2016 04:00 PM, Templin, Fred L wrote:
> Hi Fernando,
> 
>> -----Original Message-----
>> From: Fernando Gont [mailto:fgont@si6networks.com]
>> Sent: Friday, February 05, 2016 10:26 AM
>> To: Templin, Fred L; otroan@employees.org
>> Cc: Bob Hinden; 6man WG; Fred Baker (fred)
>> Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
>>
>> On 02/05/2016 03:13 PM, Templin, Fred L wrote:
>>> Starting this under a new thread, IMHO if we want to promote RFC1981 to standard
>>> we should understand its use cases as well as the use cases for RFC4821.
>>>
>>> First, it is reasonable to expect that paths that begin and end within the same
>>> well-managed administrative domain can be counted on to deliver the necessary
>>> ICMPs. An example is my employer's corporate network. In that case, traditional
>>> PMTUD per RFC1981(bis) can be applied alone w/o having to apply RFC4821.
>>>
>>> On the other hand, paths that lead to Internet destinations cannot be counted
>>> on to deliver the necessary ICMPs. In that case, RFC4821 provides a mitigation.
>>>
>>> But, if we do not believe that there are paths for which traditional PMTUD
>>> can still be used safely, then we should be working to deprecate RFC1981
>>> instead of making it a standard.
>>
>> Well, the thing here that you can do RFC1981-only, RFC4821-only, or
>> RFC1981/RFC4821 (should I say "dual stack"? :-) ).
>>
>> With that in mind, one could as well have both RFC1981 and RFC4821 as
>> standards, I guess...
>>
>> But yes, generally speaking, RFC1981-only is certaianly unreliable.
> 
> Except for within well-managed administrative domains where RFC1981-only
> is sufficient. They do exist; I am typing this message from within one right now.

I'd expect 6man to produce protocols that work everywhere, rather than
just on some subset scearios...

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





From nobody Fri Feb  5 12:18:50 2016
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D48C11ACE7B for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 12:18:48 -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] 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 IyC5dng2WtiX for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 12:18:47 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29AE91ACE4D for <ipv6@ietf.org>; Fri,  5 Feb 2016 12:18:47 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 3DC2F206A2B; Fri,  5 Feb 2016 21:18:41 +0100 (CET)
Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
To: Michael Richardson <mcr+ietf@sandelman.ca>, "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com> <7592.1454699773@obiwan.sandelman.ca>
From: Fernando Gont <fernando@gont.com.ar>
Message-ID: <56B50394.2010504@gont.com.ar>
Date: Fri, 5 Feb 2016 17:18:28 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <7592.1454699773@obiwan.sandelman.ca>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/_Ojf1vFHPLmgZ7Bb-LyoJB3-0d0>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 20:18:49 -0000

On 02/05/2016 04:16 PM, Michael Richardson wrote:
> 
> Templin, Fred L <Fred.L.Templin@boeing.com> wrote:
>     > On the other hand, paths that lead to Internet destinations cannot be
>     > counted on to deliver the necessary ICMPs. In that case, RFC4821
>     > provides a mitigation.
> 
>     > But, if we do not believe that there are paths for which traditional
>     > PMTUD can still be used safely, then we should be working to deprecate
>     > RFC1981 instead of making it a standard.
> 
> I think that the mitigation is far more reliable than 1981.
> So, I'd rather deprecate RFC1981.
> 
> {I noticed that 4821 is not on by default in most Linux distros/kernels,
> and I actually want to know if there is some reason for it}

Yes: convergence time.

-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From nobody Fri Feb  5 12:26:02 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7B421ACE91 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 12:26:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 2LYJHuLJG1xO for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 12:25:59 -0800 (PST)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (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 DE9221ACE4C for <ipv6@ietf.org>; Fri,  5 Feb 2016 12:25:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u15KPwag058674; Fri, 5 Feb 2016 13:25:58 -0700
Received: from XCH-PHX-313.sw.nos.boeing.com (xch-phx-313.sw.nos.boeing.com [130.247.25.175]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u15KPrNr058594 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Fri, 5 Feb 2016 13:25:53 -0700
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-PHX-313.sw.nos.boeing.com ([169.254.13.135]) with mapi id 14.03.0235.001;  Fri, 5 Feb 2016 12:25:52 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>, "Fred Baker (fred)" <fred@cisco.com>
Subject: RE: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
Thread-Topic: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
Thread-Index: AdFgO8UgUUOFg9xdTwqIJb3fPhAIDQARpl8AABAVV8D//4dJAIAAg16g//+ZiYCAAIRKUA==
Date: Fri, 5 Feb 2016 20:25:52 +0000
Message-ID: <2134F8430051B64F815C691A62D983183395F2DD@XCH-BLV-105.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D983183395EF42@XCH-BLV-105.nw.nos.boeing.com> <56B4E39A.5040608@si6networks.com> <2134F8430051B64F815C691A62D983183395F017@XCH-BLV-105.nw.nos.boeing.com> <56B4EA46.3080102@si6networks.com> <2134F8430051B64F815C691A62D983183395F0CE@XCH-BLV-105.nw.nos.boeing.com> <56B50285.9010204@si6networks.com>
In-Reply-To: <56B50285.9010204@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/l4Cy7MzAn04bxYdDOW2mHmfeeEI>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 20:26:01 -0000

Hi Fernando,

> -----Original Message-----
> From: Fernando Gont [mailto:fgont@si6networks.com]
> Sent: Friday, February 05, 2016 12:14 PM
> To: Templin, Fred L; Fred Baker (fred)
> Cc: 6man WG; Bob Hinden
> Subject: Re: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on d=
raft-hinden-6man-rfc1981bis-01)
>=20
> On 02/05/2016 03:42 PM, Templin, Fred L wrote:
> > Hi Fernando,
> >
> >> -----Original Message-----
> >> From: Fernando Gont [mailto:fgont@si6networks.com]
> >> Sent: Friday, February 05, 2016 10:31 AM
> >> To: Templin, Fred L; Fred Baker (fred)
> >> Cc: Bob Hinden; 6man WG
> >> Subject: Re: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call o=
n draft-hinden-6man-rfc1981bis-01)
> >>
> >> On 02/05/2016 03:25 PM, Templin, Fred L wrote:
> >>> Hi Fernando,
> >>>
> >>>> -----Original Message-----
> >>>> From: Fernando Gont [mailto:fgont@si6networks.com]
> >>>> Sent: Friday, February 05, 2016 10:02 AM
> >>>> To: Templin, Fred L; Fred Baker (fred)
> >>>> Cc: 6man WG; Bob Hinden
> >>>> Subject: Re: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call=
 on draft-hinden-6man-rfc1981bis-01)
> >>>>
> >>>> On 02/05/2016 02:46 PM, Templin, Fred L wrote:
> >>>>> Hi Fred,
> >>>>>
> >>>>>> As soon as I say "there is no such attack", one will materialize, =
so I won't assert that.  However, I am not aware of attacks in
> >> which
> >>>>>> someone creates ICMP PTBs and sends them to someone else in order =
to reduce their windows unnecessarily.
> >>>>>
> >>>>> RFC4821 Section 11 (Security Considerations) recognizes the potenti=
al for spoofed
> >>>>> (i.e., inaccurate) ICMP PTB messages and suggests a mitigation (ign=
ore all ICMP PTBs).
> >>>>> For paths over which any node in the network can inject an inaccura=
te ICMP PTB
> >>>>> message, an attack vector exists.
> >>>>
> >>>> In theory, you can do some basic validation for ICMP messages. Howev=
er,
> >>>> in v6, as a result of possible EHs, you may not find any meaningful =
data
> >>>> in the ICMP payload to apply validity checks on.
> >>>>
> >>>> Anyway, you can implement the countermeasure we implemented in
> >>>> <https://tools.ietf.org/html/rfc5927#section-7.2> -- I implemented i=
t
> >>>> for OpenBSD, and it still runs it... and IIRC it was ported to at le=
ast
> >>>> NetBSD later.
> >>>
> >>> Thanks for the reference. It seems to account for the case of paths t=
hat may
> >>> deliver inaccurate ICMP PTBs, but does not account for the case of pa=
ths that
> >>> fail to deliver accurate ICMP PTBs. Do we know of paths always delive=
r
> >>> accurate ICMP PTBs but can also deliver inaccurate ICMP PTBs?
> >>
> >> What do you mean by "accurate"?
> >
> > By "accurate" I mean:
> >
> > - the router that sends the ICMP PTB is telling the truth that there is=
 a restricting link
> > - the MTU value that the router writes in the PTB is in fact the true M=
TU of the
> >    restricting link
>=20
> Well, most of these protocols run on "good faith", right? -- If I cannot
> trust the router to tell the truth, why should I trust it to e.g.
> forward my packets?

A router's trustworthiness for forwarding packets and for telling the truth
in any ICMP PTB message it sends are mutually exclusive - the first questio=
n
is one of availability and the second is one of integrity.

Plus, it is not necessarily just the on-path routers - any off-path "router=
"
could also inject spurious PTBs.

Thanks - Fred
fred.l.templin@boeing.com


From nobody Fri Feb  5 12:27:26 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05B451ACEA7 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 12:27:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level: 
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_12=0.6, 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 IQIuOUpEh35N for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 12:27:24 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFC1C1ACEA4 for <ipv6@ietf.org>; Fri,  5 Feb 2016 12:27:23 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 64691206A2B; Fri,  5 Feb 2016 21:27:18 +0100 (CET)
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, otroan@employees.org
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com> <56B4FF9D.10203@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B50567.6030607@si6networks.com>
Date: Fri, 5 Feb 2016 17:26:15 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B4FF9D.10203@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ICOhTlGRz_skYac7GYH6ARq8qyE>
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 20:27:25 -0000

On 02/05/2016 05:01 PM, Brian E Carpenter wrote:
> On 06/02/2016 07:20, Fernando Gont wrote:
>> On 02/05/2016 03:07 PM, otroan@employees.org wrote:
>>> Fernando,
>>>
>>> [...]
>>>
>>>>>
>>>>> What is the risk of using the same IID for link-local and global addresses?
>>>>> Typically if you can snoop the link-local address then you're onlink and leak information about all addresses and their correlations anyway.
>>>>
>>>> We discussed this one a hundred times now (including for RFC7217). The
>>>> risk is that at times such addressess can leak, without the need of the
>>>> attacker being pesent on the local link.
>>>>
>>>> e.g., your MTA is on the local-link, and you end up connecting to it
>>>> with a LL, which then appears in the email headers. (and there are a
>>>> bunch of other possible reasons for that to happen).
>>>>
>>>> Be proactive. MAC addresses in the IID are wrong. Putting them there is
>>>> just waiting for trouble.
>>>
>>> I didn't say the LL was based on a MAC.
>>> my question was if there was any issue with re-using the IID from the link-local in the GUA. assume the link-local is generated f.ex with 7217.
>>
>> Oops, my apologies. My answer would be "It unnecessarily enables
>> correlation of the activities that you carry between the two addresses".
>>
>> i.e., by simply inspecting the IID I could easily tell that the
>> activities carried out with one address were performed by the same node
>> that employed the other address.
>>
>> My take here is, again: be proactive. If there's no requirement (and
>> there isn't) for the two IIDs to be the same, then make them different,
>> and fail on the safe side.
> 
> But Ole's point was that any observer who sees a LL packet is on-link 

That assumption is not correct. You may see a LL because it leaked out
somehow (e.g., you connected to your local MTA using LL, and then the
address got stamped in the email headers).


> and
> can therefore see the MAC address anyway; an observer who can see MAC addresses
> can just laugh at RFC 7217 or RFC 4941.

An observer that sees a MAC address can laugh at 7217 or 4941 for the
purpose of host tracking if the attacer is always on-link. At which
point, you could also argue that the attacker is also able to sniff
traffic...  At which point, mitigating the problem in a comprehensive
manner becomes rather complex. (I'm not saying "impossible", nor am I
saying that you don't want to do that).


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





From nobody Fri Feb  5 12:40:52 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECB881ACEE3 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 12:40:49 -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] 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 ShORWUa86IvP for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 12:40:47 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D0DF1ACEF1 for <ipv6@ietf.org>; Fri,  5 Feb 2016 12:40:47 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id DA289206AF6; Fri,  5 Feb 2016 21:40:41 +0100 (CET)
Subject: Re: ICMP PTB spoofing attacks
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "Fred Baker (fred)" <fred@cisco.com>
References: <2134F8430051B64F815C691A62D983183395EF42@XCH-BLV-105.nw.nos.boeing.com> <56B4E39A.5040608@si6networks.com> <2134F8430051B64F815C691A62D983183395F017@XCH-BLV-105.nw.nos.boeing.com> <56B4EA46.3080102@si6networks.com> <2134F8430051B64F815C691A62D983183395F0CE@XCH-BLV-105.nw.nos.boeing.com> <56B50285.9010204@si6networks.com> <2134F8430051B64F815C691A62D983183395F2DD@XCH-BLV-105.nw.nos.boeing.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B50889.8080201@si6networks.com>
Date: Fri, 5 Feb 2016 17:39:37 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <2134F8430051B64F815C691A62D983183395F2DD@XCH-BLV-105.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/FR5MgGVKSCfh6tikOUgiO8vN9A4>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 20:40:50 -0000

On 02/05/2016 05:25 PM, Templin, Fred L wrote:
>>>
>>> By "accurate" I mean:
>>>
>>> - the router that sends the ICMP PTB is telling the truth that there is a restricting link
>>> - the MTU value that the router writes in the PTB is in fact the true MTU of the
>>>    restricting link
>>
>> Well, most of these protocols run on "good faith", right? -- If I cannot
>> trust the router to tell the truth, why should I trust it to e.g.
>> forward my packets?
> 
> A router's trustworthiness for forwarding packets and for telling the truth
> in any ICMP PTB message it sends are mutually exclusive - the first question
> is one of availability and the second is one of integrity.

I think that, at the end of the day, its about trust. Can I trust the
device, or not?

I my goal as an attacker is to DoS your communications, I don't care
whether I achieve that by simply throwing your packets away, or by
sending you some packet that will cause yourself to shutdown and not talk.

I should say, however, that in the IPv6 case, the worst case scenario is
a 1280-byte MTU link...


> Plus, it is not necessarily just the on-path routers - any off-path "router"
> could also inject spurious PTBs.

For off-path attackers, you validate ICMP PTBs. If you don't, well...
prepare for trouble.  And, yes, if EHs are in use, you may not be able
to verify them.

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





From nobody Fri Feb  5 14:17:45 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F383E1B2E11 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 14:17:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 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, J_CHICKENPOX_12=0.6, 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 NGepqjHHG9fb for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 14:17:42 -0800 (PST)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B658F1B2E13 for <ipv6@ietf.org>; Fri,  5 Feb 2016 14:17:42 -0800 (PST)
Received: by mail-pa0-x22e.google.com with SMTP id cy9so40753777pac.0 for <ipv6@ietf.org>; Fri, 05 Feb 2016 14:17:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=YJh55x61DONfVLyoZXgoWrpDWaEY32KpxTjvOABWjj8=; b=T1WYd6Khz7gQ7dpP/BdPTYbd4P38FZbKNHMlrt/77EzNaA1JWmE4v0AqtkDdxpiYmv 2k7ocHYyLmgvJgxHmFjPUjIA5g7Eo+eNlR0nH+/ld3AvSXnIDJNDzszI8lOoeTAl62b5 dN3Yu48WEvUvjG2JiMY9elFNzO+qSNLNByIi6hy4HZsEF+/js/xKiwfkYl6ZaiJ4WhQW 4JhVC5MI4M/JjVg4LPfvqmF3xe6WRC9Bn5UniFVo00F5UzIbXveUzwO2N5Wyo2d5swig NZ4uT33V3MxCPGJK75JS3NRREYEeRj/N0mBRbn8bxmEnfqPA+b2xpWWcPykf5UhfTgY3 BTqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=YJh55x61DONfVLyoZXgoWrpDWaEY32KpxTjvOABWjj8=; b=KBr2nFKzpq9C+gIlC2s8Uw8ARV+2cV93mYUB3TmchT+jeTs//xoDpvebQAi/HQ9dI8 r6f+UElxHZYHsJMHaQ31OQz7t7faActPXg+gofurbwCzXSBZYgvsEbTc0iDevg8lxlbs XxkPrldw1hqK/siiyqNCvtH6KPeQRDgeN9MFlCowcdV7ZFYVjsXfZ7atMacmLdyUea3d 7jKcFTnmtSBPVL4V0S0n6H25LDp/DYeBURV5OMuvYi9hT72oWkLLxvmftR2A17pzLCZ3 AUiN05qGy5ijqZuqY5KMETUH9sgrLNBHymdBlRszQCK8c8LGl0eCpoFTE88G/miFCEWA e9Ow==
X-Gm-Message-State: AG10YOQDiKb+Na+CYZ8Uw2qeKPZLAvgBE0Ye5jhelSJPdZWcSNNv86F+clQKazX6tEopmA==
X-Received: by 10.66.218.225 with SMTP id pj1mr22805064pac.40.1454710662366; Fri, 05 Feb 2016 14:17:42 -0800 (PST)
Received: from ?IPv6:2406:e007:4357:1:28cc:dc4c:9703:6781? ([2406:e007:4357:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id fa3sm26590006pab.45.2016.02.05.14.17.38 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 05 Feb 2016 14:17:40 -0800 (PST)
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: Fernando Gont <fgont@si6networks.com>, otroan@employees.org
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com> <56B4FF9D.10203@gmail.com> <56B50567.6030607@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56B51F8D.6010309@gmail.com>
Date: Sat, 6 Feb 2016 11:17:49 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B50567.6030607@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/4yfK7oGrikAK3mJgzpQnL1bwAqQ>
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 22:17:44 -0000

On 06/02/2016 09:26, Fernando Gont wrote:
> On 02/05/2016 05:01 PM, Brian E Carpenter wrote:
>> On 06/02/2016 07:20, Fernando Gont wrote:
>>> On 02/05/2016 03:07 PM, otroan@employees.org wrote:
>>>> Fernando,
>>>>
>>>> [...]
>>>>
>>>>>>
>>>>>> What is the risk of using the same IID for link-local and global addresses?
>>>>>> Typically if you can snoop the link-local address then you're onlink and leak information about all addresses and their correlations anyway.
>>>>>
>>>>> We discussed this one a hundred times now (including for RFC7217). The
>>>>> risk is that at times such addressess can leak, without the need of the
>>>>> attacker being pesent on the local link.
>>>>>
>>>>> e.g., your MTA is on the local-link, and you end up connecting to it
>>>>> with a LL, which then appears in the email headers. (and there are a
>>>>> bunch of other possible reasons for that to happen).
>>>>>
>>>>> Be proactive. MAC addresses in the IID are wrong. Putting them there is
>>>>> just waiting for trouble.
>>>>
>>>> I didn't say the LL was based on a MAC.
>>>> my question was if there was any issue with re-using the IID from the link-local in the GUA. assume the link-local is generated f.ex with 7217.
>>>
>>> Oops, my apologies. My answer would be "It unnecessarily enables
>>> correlation of the activities that you carry between the two addresses".
>>>
>>> i.e., by simply inspecting the IID I could easily tell that the
>>> activities carried out with one address were performed by the same node
>>> that employed the other address.
>>>
>>> My take here is, again: be proactive. If there's no requirement (and
>>> there isn't) for the two IIDs to be the same, then make them different,
>>> and fail on the safe side.
>>
>> But Ole's point was that any observer who sees a LL packet is on-link 
> 
> That assumption is not correct. You may see a LL because it leaked out
> somehow (e.g., you connected to your local MTA using LL, and then the
> address got stamped in the email headers).

I've certainly seen RFC1918 addresses that way, but I don't recall
seeing IPv6 LL. However, you're correct, it could happen. So I'm certainly
not opposed to recommending a different IID for LL. But we'd better be
sure that there aren't any unintended side-effects, since this would change
20 years of IPv6 practice.

>> and
>> can therefore see the MAC address anyway; an observer who can see MAC addresses
>> can just laugh at RFC 7217 or RFC 4941.
> 
> An observer that sees a MAC address can laugh at 7217 or 4941 for the
> purpose of host tracking if the attacer is always on-link. At which
> point, you could also argue that the attacker is also able to sniff
> traffic...  At which point, mitigating the problem in a comprehensive
> manner becomes rather complex. (I'm not saying "impossible", nor am I
> saying that you don't want to do that).

It definitely takes you out of scope for this draft ;-)

    Brian


From nobody Fri Feb  5 15:01:15 2016
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23CD31B2EA8 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 15:01:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level: 
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, 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 ODaD49VoSBrM for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 15:01:12 -0800 (PST)
Received: from mail-vk0-x22f.google.com (mail-vk0-x22f.google.com [IPv6:2607:f8b0:400c:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A11BA1B2EA7 for <ipv6@ietf.org>; Fri,  5 Feb 2016 15:01:12 -0800 (PST)
Received: by mail-vk0-x22f.google.com with SMTP id c3so19443895vkb.3 for <ipv6@ietf.org>; Fri, 05 Feb 2016 15:01:12 -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=WcBLecvS7jIpORobVIg8/fBvPKIUkrIV+HPYRGWc4zo=; b=yQxXXsTuxtfZJqB3pX7NAVdU6trJ+VMDBCu6SoA0zThNHql++0tWejl7MOr3U7YHqr MbO8AiYlSiWlSuH+mri8fYh9NsHwDejxIZUCckej4FJ7rpdGq3GxVTZygM3H+evU+us1 xbJubZCcfD2O+qr4zSnK9n1VTdTG8WNLigeHhYqlb03Dz/SSd7CAOh30wrI2/w7VMFBF L+XD3dUlCUzERRmfRBSnnRmgMn833jsSWk+gLeo5tBxxhuMTevh9jngUFT+tWp4uGTYy PdRV4ImyPUgaM6G+oRSvRlWWHJPuTzkllwpZuTscqnQA34wrhqBvMNvtiCwjsup7HBlj N2cg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=WcBLecvS7jIpORobVIg8/fBvPKIUkrIV+HPYRGWc4zo=; b=dsBsQ1i3WA+cE3FiPUGahehNTXukG3o2LukO98DL97wi4zF415nx/F9P4qFbNkLCAl xEgE5dRODuPCYBTrT3d1HTpaaXn0/0q5kpilNNRSLMfdRmvG6raSMy+f++jLBz7oFwQF 9m+dbTKd/AuwvmJWrDREaSwc2qyPYkRfXtFo1HqjTZgK5LS/u80Ulw3DFrLLucXJIenF yPcUFbQZxiQZ3OaqqIRqtkM3CyLyJZO/hSbfFnyTDFaxQclfz5VPW8MChpG6cjX9XTOa 7T0YZWXrENqa8J+W5sk/Isz/VSGjbMEcTBRW928OwP2ERHdVle9kA5gw0JBtJl3/zvrt lYOw==
X-Gm-Message-State: AG10YOTH3OZoLx0+GWSbRX1RbJDdri86pvxMBNuqVF4X0w1xLXyn9avmoCsurdup+xDH24xQvzXSWplKoOstCg==
X-Received: by 10.31.188.142 with SMTP id m136mr11580619vkf.89.1454713271800;  Fri, 05 Feb 2016 15:01:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.92.67 with HTTP; Fri, 5 Feb 2016 15:00:42 -0800 (PST)
In-Reply-To: <56B51F8D.6010309@gmail.com>
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com> <56B4FF9D.10203@gmail.com> <56B50567.6030607@si6networks.com> <56B51F8D.6010309@gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Sat, 6 Feb 2016 10:00:42 +1100
Message-ID: <CAO42Z2yNTB7jGCmK_x1iKhEWKrv=j6Pf9z6J22pNiJkJ6hPW4A@mail.gmail.com>
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/p0_6y9844mYd8dXMMqpJYfCKNHc>
Cc: Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 23:01:14 -0000

On 6 February 2016 at 09:17, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
> On 06/02/2016 09:26, Fernando Gont wrote:
>> On 02/05/2016 05:01 PM, Brian E Carpenter wrote:
>>> On 06/02/2016 07:20, Fernando Gont wrote:
>>>> On 02/05/2016 03:07 PM, otroan@employees.org wrote:
>>>>> Fernando,
>>>>>
>>>>> [...]
>>>>>
>>>>>>>

<snip>

>>>> My take here is, again: be proactive. If there's no requirement (and
>>>> there isn't) for the two IIDs to be the same, then make them different,
>>>> and fail on the safe side.
>>>
>>> But Ole's point was that any observer who sees a LL packet is on-link
>>
>> That assumption is not correct. You may see a LL because it leaked out
>> somehow (e.g., you connected to your local MTA using LL, and then the
>> address got stamped in the email headers).
>
> I've certainly seen RFC1918 addresses that way, but I don't recall
> seeing IPv6 LL. However, you're correct, it could happen. So I'm certainly
> not opposed to recommending a different IID for LL. But we'd better be
> sure that there aren't any unintended side-effects, since this would change
> 20 years of IPv6 practice.
>

My general concern in this area is that attacker access to many links
has become easier, because many of the links are now wireless rather
than wired.

Public wifi networks "protected" by captive portals are now switching
off all of the Wifi security, including WEP, so they're Privacy isn't
even Wired Equivalent, making it easy to attach and capture much of
the traffic without anybody noticing.

Bluetooth 'links' are in general also another example of links that
are easy to collect device details from, using tools such as this one,

https://play.google.com/store/apps/details?id=com.bluemotionlabs.bluescan

that not only record bluetooth device MAC addresses, but also GPS
co-ordinates, and by default uploads them to the earthping.com
website. (Run it while you visit a cafe or shopping centre, it is
somewhat surprising how many bluetooth devices are out there and
announcing themselves - plenty of fitness trackers and phones, what is
surprising is that my local cafe's Smart TV is bluetooth enabled for
some reason or another.)

So I think it is worth starting to rely less on what was the inherent
security of a link, and to treat them as equivalent to "multi-link" or
global threats. That's why I think LLs having different IIDs to any of
the other prefixes on the link is a good idea, and also, ideally, LL
IIDs should be different on different links (to stop LL IIDs being
used to build a similar database to the earthping.com one across, for
example, visits to Internet cafe/hotel/conference networks.)

Regards,
Mark.


From nobody Fri Feb  5 15:03:10 2016
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AC071B2EA8 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 15:03:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 eKDTwu35IZcF for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 15:03:08 -0800 (PST)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CB821B2E72 for <ipv6@ietf.org>; Fri,  5 Feb 2016 15:03:08 -0800 (PST)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 3635B88167; Fri,  5 Feb 2016 15:03:08 -0800 (PST)
Received: from clemson.local (unknown [76.21.129.88]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id C7189328081A; Fri,  5 Feb 2016 15:03:07 -0800 (PST)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
To: otroan@employees.org
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <2134F8430051B64F815C691A62D983183395D25D@XCH-BLV-105.nw.nos.boeing.com> <F01DCA0F-BCBF-4CD3-BF2B-412EE2FDC19C@employees.org> <56B49D89.5050202@innovationslab.net> <39408594-E513-46DA-820A-AB0D5CB85C9E@employees.org>
From: Brian Haberman <brian@innovationslab.net>
Message-ID: <56B52A25.5050706@innovationslab.net>
Date: Fri, 5 Feb 2016 18:03:01 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <39408594-E513-46DA-820A-AB0D5CB85C9E@employees.org>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Tn7xXSNX9S7UhiLFlnvCuuOxRswox1nis"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/7_IZ2Gryj463tGBcWgF6zz_8M2w>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 23:03:09 -0000

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

Hi Ole,

On 2/5/16 1:11 PM, otroan@employees.org wrote:
> Brian,
>=20
>>>> One question on the authorship - I can say with some certainty that
>>>> Jack McCann and Jeff Mogul are no longer with Digital Equipment
>>>> Corporation. Would they  be actively involved in this work if it is
>>>> accepted as a working group item?
>>>
>>> I don't expect them to be. For the documents we're advancing to
>>> Internet Standard, and therefore only do very minor tweaks to, I
>>> think it makes most sense to keep the original authors. Unless they
>>> object.
>>
>> Um, no. The original authors stay on the draft because they are the on=
es
>> responsible for most of the text within the document. Accurate
>> representation of authorship is critical for many reasons (e.g., IPR).=

>=20
> my view is that it is the working group that is responsible for the doc=
ument (and at a larger level the IETF).
> and that we have the authors listed on the first page as a way to recog=
nise them as the main contributors.

The WG is responsible for the document, but things like our IPR rules
are indexed by the document authors.

>=20
> perhaps it is time to remove author names from our documents then.
> (as something the IETF should look at, not for these sets of documents =
obviously).
>=20

That has been raised several times since I have been on the IESG. The
push back on that proposal naturally deals with IPR issues, publication
credit, and RFC Editor interactions.

Regards,
Brian


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2

iQEcBAEBCAAGBQJWtSoqAAoJEBOZRqCi7goqouUH/jGKEbJPOjAi/aDUZPXLMFo4
Ox1xl8tgkH1sjmbCopkvT/193lreGb+eZreJxpfxm/vlWxBJH/oRcz3U36jZ0lyk
bF39q28tBNH7SE9tMYlGQ6OXx+pV4wN0GJ+rsMXJjnrz4Bf9p5/VFzsxygpG0KPF
rA06Tq4WgJugHeI+9wBBWBXjjonmjzdEVub3ILIho+npeIqDZxJG4ahjwp0md2XO
Z9SEvV2TNX2jr3tYrms2TZGphF7vMa+Dj3zKc5lvtXSF/9AQfWt3RbBiZ6oSomBA
qf4EhBw0CEvmG/mPu14RO+gI42b5C1tRBo5uHfEhh++yLVW14deDladpTGCo2MI=
=PSVS
-----END PGP SIGNATURE-----

--Tn7xXSNX9S7UhiLFlnvCuuOxRswox1nis--


From nobody Fri Feb  5 15:06:27 2016
Return-Path: <marka@isc.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C3341B2EBC for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 15:06:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-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 rzrPW0b6ydTB for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 15:06:24 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7321F1B2EBA for <ipv6@ietf.org>; Fri,  5 Feb 2016 15:06:24 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx.ams1.isc.org (Postfix) with ESMTPS id A1C011FCAE1; Fri,  5 Feb 2016 23:06:20 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id DCA6D160035; Fri,  5 Feb 2016 23:06:53 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id C9C0216009D; Fri,  5 Feb 2016 23:06:53 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 7SBE4OliIG0y; Fri,  5 Feb 2016 23:06:53 +0000 (UTC)
Received: from rock.dv.isc.org (c110-21-49-25.carlnfd1.nsw.optusnet.com.au [110.21.49.25]) by zmx1.isc.org (Postfix) with ESMTPSA id 81A85160035; Fri,  5 Feb 2016 23:06:53 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id CA7A1419BA10; Sat,  6 Feb 2016 10:06:16 +1100 (EST)
To: Fernando Gont <fgont@si6networks.com>
From: Mark Andrews <marka@isc.org>
References: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com> <56B4E91C.6090905@si6networks.com> <2134F8430051B64F815C691A62D983183395F14A@XCH-BLV-105.nw.nos.boeing.com> <56B502FB.4050302@si6networks.com>
Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
In-reply-to: Your message of "Fri, 05 Feb 2016 17:15:55 -0300." <56B502FB.4050302@si6networks.com>
Date: Sat, 06 Feb 2016 10:06:16 +1100
Message-Id: <20160205230616.CA7A1419BA10@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/MYxhqR3-PCG9RwyL8ABhZQcUj1c>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 23:06:26 -0000

In message <56B502FB.4050302@si6networks.com>, Fernando Gont writes:
> On 02/05/2016 04:00 PM, Templin, Fred L wrote:
> > Hi Fernando,
> > 
> >> -----Original Message-----
> >> From: Fernando Gont [mailto:fgont@si6networks.com]
> >> Sent: Friday, February 05, 2016 10:26 AM
> >> To: Templin, Fred L; otroan@employees.org
> >> Cc: Bob Hinden; 6man WG; Fred Baker (fred)
> >> Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call
>  on draft-hinden-6man-rfc1981bis-01)
> >>
> >> On 02/05/2016 03:13 PM, Templin, Fred L wrote:
> >>> Starting this under a new thread, IMHO if we want to promote RFC1981 to s
> tandard
> >>> we should understand its use cases as well as the use cases for RFC4821.
> >>>
> >>> First, it is reasonable to expect that paths that begin and end within th
> e same
> >>> well-managed administrative domain can be counted on to deliver the neces
> sary
> >>> ICMPs. An example is my employer's corporate network. In that case, tradi
> tional
> >>> PMTUD per RFC1981(bis) can be applied alone w/o having to apply RFC4821.
> >>>
> >>> On the other hand, paths that lead to Internet destinations cannot be cou
> nted
> >>> on to deliver the necessary ICMPs. In that case, RFC4821 provides a mitig
> ation.
> >>>
> >>> But, if we do not believe that there are paths for which traditional PMTU
> D
> >>> can still be used safely, then we should be working to deprecate RFC1981
> >>> instead of making it a standard.
> >>
> >> Well, the thing here that you can do RFC1981-only, RFC4821-only, or
> >> RFC1981/RFC4821 (should I say "dual stack"? :-) ).
> >>
> >> With that in mind, one could as well have both RFC1981 and RFC4821 as
> >> standards, I guess...
> >>
> >> But yes, generally speaking, RFC1981-only is certaianly unreliable.
> > 
> > Except for within well-managed administrative domains where RFC1981-only
> > is sufficient. They do exist; I am typing this message from within one righ
> t now.
> 
> I'd expect 6man to produce protocols that work everywhere, rather than
> just on some subset scearios...

RFC 1981 works for TCP unless you *deliberately* break it by dropping
PTB as TCP retries.

RFC 1981 does NOT work in general for UDP.  DNS/UDP is a perfect
example as it is the responding server that get the PTB and the DNS
client is trying multiple servers.  Often by the time the server
is tried again especially when a server is anycast the MTU knowledge
has been lost.

> -- 
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
> 
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Fri Feb  5 15:27:25 2016
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B8791B2F54 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 15:27:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level: 
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, 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 51Wy3utQTOLx for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 15:27:22 -0800 (PST)
Received: from mail-vk0-x236.google.com (mail-vk0-x236.google.com [IPv6:2607:f8b0:400c:c05::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA1151B2F50 for <ipv6@ietf.org>; Fri,  5 Feb 2016 15:27:21 -0800 (PST)
Received: by mail-vk0-x236.google.com with SMTP id e185so66157385vkb.1 for <ipv6@ietf.org>; Fri, 05 Feb 2016 15:27:21 -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=uVm4aSRG87XK6dh2+67zQFiFY/hGiEEZGZ07vVt+jcs=; b=eLf5N+kPcS8eulcXlV0rGzto2jkRHzzbzlv/1Jd5Qri/WzthW1TjlV9c3vGJWbvNjW YUD4IiqTFBxOwOGEvFkxRMUaJXElkLepllufxbc6zzwxylvUbny1/5oT/fuMOUQ+tL9b j8f+VJlkQmCie3bS3omCla18bxdMNDb1wuKJ2W+139D8gCz0M4XQO1NbGkpjovC9HhJz mBqggoz5gAhrg6R4u5HL9hQIMto0lUBt23zzL/opE66NNC1VveTfS3C6pfTjNc46ilPN etCfSTqmI/GW8kv5dUUpS72DcmZOfKk14BWlwvIg2/BPI4hwE8vwe3q2oCT5oxgkeWYA uSNg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=uVm4aSRG87XK6dh2+67zQFiFY/hGiEEZGZ07vVt+jcs=; b=HVZLEK1hzxvtbL8EWK+4TiSdIes4/RmwdsgD8i8DSKsoDYSRPFu2Vt0P7wj9GnZOBy rllxGh+V8UovuHxG8vDll+4k1S3fxJMsKBIjJbbJcxMXnNq8GzKgSHebTWvrWeKheSeh itwSYhhosACJguIwyOdMhuqbh3EcZflXBmNRlKkBk5+QWBp0+0rWYBUpeWVDskkZab18 vrR1vwCF5hZybQoQp7nkax3k7XDgO6pjdym48wTNFjIxQN+MhjzJcD6A5ObohU8Wuq3/ UCZ2ExpqMKjtJwgc/uUYj+vfuwiQEjuPRIAQRZjyYwv7E4nMAH8t2ERPZ5zkztBYsMCK mA5Q==
X-Gm-Message-State: AG10YOT8nfigBm19WaAaSCEQ/Wj+p0rvkycOMhXkL+yHNcQ/DRg8UbmjMWp67TzEgcvTod0rVOMtf3JYmvhOxA==
X-Received: by 10.31.156.129 with SMTP id f123mr11443611vke.40.1454714840705;  Fri, 05 Feb 2016 15:27:20 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.92.67 with HTTP; Fri, 5 Feb 2016 15:26:51 -0800 (PST)
In-Reply-To: <20160205230616.CA7A1419BA10@rock.dv.isc.org>
References: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com> <56B4E91C.6090905@si6networks.com> <2134F8430051B64F815C691A62D983183395F14A@XCH-BLV-105.nw.nos.boeing.com> <56B502FB.4050302@si6networks.com> <20160205230616.CA7A1419BA10@rock.dv.isc.org>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Sat, 6 Feb 2016 10:26:51 +1100
Message-ID: <CAO42Z2xt+ykaoxHcL=tf5zmpBUA6pUz2hDMF3=s+hCvFrq+ojQ@mail.gmail.com>
Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
To: Mark Andrews <marka@isc.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/suJQNjmYAeK6nF1Bt5Q9zm0uETg>
Cc: Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 23:27:23 -0000

On 6 February 2016 at 10:06, Mark Andrews <marka@isc.org> wrote:
>
> In message <56B502FB.4050302@si6networks.com>, Fernando Gont writes:
>> On 02/05/2016 04:00 PM, Templin, Fred L wrote:
>> > Hi Fernando,
>> >
>> >> -----Original Message-----
>> >> From: Fernando Gont [mailto:fgont@si6networks.com]
>> >> Sent: Friday, February 05, 2016 10:26 AM
>> >> To: Templin, Fred L; otroan@employees.org
>> >> Cc: Bob Hinden; 6man WG; Fred Baker (fred)
>> >> Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call
>>  on draft-hinden-6man-rfc1981bis-01)
>> >>
>> >> On 02/05/2016 03:13 PM, Templin, Fred L wrote:
>> >>> Starting this under a new thread, IMHO if we want to promote RFC1981 to s
>> tandard
>> >>> we should understand its use cases as well as the use cases for RFC4821.
>> >>>
>> >>> First, it is reasonable to expect that paths that begin and end within th
>> e same
>> >>> well-managed administrative domain can be counted on to deliver the neces
>> sary
>> >>> ICMPs. An example is my employer's corporate network. In that case, tradi
>> tional
>> >>> PMTUD per RFC1981(bis) can be applied alone w/o having to apply RFC4821.
>> >>>
>> >>> On the other hand, paths that lead to Internet destinations cannot be cou
>> nted
>> >>> on to deliver the necessary ICMPs. In that case, RFC4821 provides a mitig
>> ation.
>> >>>
>> >>> But, if we do not believe that there are paths for which traditional PMTU
>> D
>> >>> can still be used safely, then we should be working to deprecate RFC1981
>> >>> instead of making it a standard.
>> >>
>> >> Well, the thing here that you can do RFC1981-only, RFC4821-only, or
>> >> RFC1981/RFC4821 (should I say "dual stack"? :-) ).
>> >>
>> >> With that in mind, one could as well have both RFC1981 and RFC4821 as
>> >> standards, I guess...
>> >>
>> >> But yes, generally speaking, RFC1981-only is certaianly unreliable.
>> >
>> > Except for within well-managed administrative domains where RFC1981-only
>> > is sufficient. They do exist; I am typing this message from within one righ
>> t now.
>>
>> I'd expect 6man to produce protocols that work everywhere, rather than
>> just on some subset scearios...
>
> RFC 1981 works for TCP unless you *deliberately* break it by dropping
> PTB as TCP retries.
>
> RFC 1981 does NOT work in general for UDP.  DNS/UDP is a perfect
> example as it is the responding server that get the PTB and the DNS
> client is trying multiple servers.  Often by the time the server
> is tried again especially when a server is anycast the MTU knowledge
> has been lost.
>

I think the main reason that fragments are dropped by some networks is
that they don't have any upper layer protocol header and port fields
in the payload.

One idea discussed a while ago (on this or the v6ops list) was to
shift fragmentation into the UDP layer, which would mean that every
UDP fragment would have the upper layer protocol header and port
numbers that some people want to look at.

At the time I thought UDP source port 0 could be used to indicate
there are UDP options in the packet, however I found that it actually
means no source port (e.g., protocols like DHCP and SNMP don't use
source ports because both client and server destination ports are well
known.)

I came across this draft by Joe last week, and I was thinking that
that might facilitate UDP layer fragmentation.

"Transport Options for UDP"
https://tools.ietf.org/html/draft-touch-tsvwg-udp-options-02

Fred has also started writing up a draft to shift fragmentation into
the GRE layer:

"GRE Tunnel Fragmentation"
https://tools.ietf.org/html/draft-templin-intarea-grefrag-02


Regards,
Mark.




>> --
>> Fernando Gont
>> SI6 Networks
>> e-mail: fgont@si6networks.com
>> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>>
>>
>>
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
> --
> Mark Andrews, ISC
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Fri Feb  5 16:20:35 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B4C61B30EB for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 16:20:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cRS5nLFrvfX8 for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 16:20:32 -0800 (PST)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B94D31B30D7 for <ipv6@ietf.org>; Fri,  5 Feb 2016 16:20:32 -0800 (PST)
Received: by mail-pa0-x232.google.com with SMTP id yy13so41911162pab.3 for <ipv6@ietf.org>; Fri, 05 Feb 2016 16:20:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=to:from:subject:organization:message-id:date:user-agent :mime-version:content-type:content-transfer-encoding; bh=TuAYPRViOZ2hNuSzn/TamZGToztt27GY0sNlkEXjjdA=; b=GxQNnzha6Q7s0jLPV8Pt0i/MAXtF3e7r7aTWVLdLWKWEcUWqPCbE65By1XU/tcY4bS g/0ulwJf4JFVQGhT0Khz5klWNCxjExHzrwQgi6ZKWPibn02hpFbgbH7V02DoxpPoCDld pefl0Cl+cUCAf2jJf8R0nGC69DausoYBuxr5EnQlZ5HvrAGz7XDst2Q5gP27NTMTUVlU qnMtF0LzpNbMIIsxPaBz8Wi1BjauR0cEWF6H3PK4/c+dVMMlMJBThhKkMLJxBWO0XCoq CHg5gdUNhaWLGAnPVwceI1fWOeV721HJhdKE3YQ72A3xBPgc2/ZFr08L8TKgRnoXhQgt JMsg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:to:from:subject:organization:message-id:date :user-agent:mime-version:content-type:content-transfer-encoding; bh=TuAYPRViOZ2hNuSzn/TamZGToztt27GY0sNlkEXjjdA=; b=XSAnSWIL9EUq2cun0EyvZrV05G1GZVE8P8zGwkmkbNeU3nBhKJSj2KjPeOdtl6zlds bfYoHSwAJlczY4pQxXInW93nB/olvl+273DPlw3zHLmaLncJtgZpTHDJP5Ick7jRy0rv T9e7b9IG1T07CjaF1uNjXgKVDDTVKaDLqqkgiNQ7P8re5XBuQ5ZkmZl0oI85tPjFwKtX uH0xhQ7lyHVMxiyNJxLbhYJrfUgT9FsTcjJ0GqYhbz6y+4KV5IcKRMeAUoye+arvK9Ry fXo2wfso5Cqj0qD/fR8HIHmj42DhPiOO9HWxSYOW5zGzxs1Z7S5/4lHewUYM1cWkVuqb yz2w==
X-Gm-Message-State: AG10YORvAL69c73FOuxBkMdaegBv3xXz0nw5/q/z5sLOMLjYYVx7+kUFY8BKRMYoUiET0g==
X-Received: by 10.66.235.162 with SMTP id un2mr23900709pac.17.1454718032432; Fri, 05 Feb 2016 16:20:32 -0800 (PST)
Received: from ?IPv6:2406:e007:4357:1:28cc:dc4c:9703:6781? ([2406:e007:4357:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id i13sm26874924pfi.95.2016.02.05.16.20.29 for <ipv6@ietf.org> (version=TLSv1/SSLv3 cipher=OTHER); Fri, 05 Feb 2016 16:20:31 -0800 (PST)
To: 6man <ipv6@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-dhc-anonymity-profile-06.txt> (Anonymity profile for DHCP clients) to Proposed Standard
Organization: University of Auckland
Message-ID: <56B53C58.9020802@gmail.com>
Date: Sat, 6 Feb 2016 13:20:40 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/J_SnGxd2JunlpOeL4JprV03UA7s>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Feb 2016 00:20:34 -0000

Hi,

https://tools.ietf.org/html/draft-ietf-dhc-anonymity-profile is in IETF Last Call,
and I drew the short straw to review it for Gen-ART.

I believe IPv6ers need to look at this draft. Among other things, it says:

> 4.5.2.  Prefix delegation
>
>   The interaction between prefix delegation and anonymity require
>   further study.  For now, the simple solution is to avoid using prefix
>   delegation when striving for anonymity.  When using the anonymity
>   profiles, clients SHOULD NOT use IA_PD, the prefix delegation form of
>   address assignment.

Please, any discussion should be in response to the Last Call, not here:

> Please send substantive comments to the
> ietf@ietf.org mailing lists by 2016-02-15. 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.

Regards
   Brian


From nobody Fri Feb  5 16:35:51 2016
Return-Path: <marka@isc.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AB141B30FA for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 16:35:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 sDBJORKbbJHX for <ipv6@ietfa.amsl.com>; Fri,  5 Feb 2016 16:35:47 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B4921B313E for <ipv6@ietf.org>; Fri,  5 Feb 2016 16:35:45 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx.pao1.isc.org (Postfix) with ESMTPS id EFB0C34930F; Sat,  6 Feb 2016 00:35:42 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 8B2BA160035; Sat,  6 Feb 2016 00:36:17 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 7A3CC16009D; Sat,  6 Feb 2016 00:36:17 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ganI6g6Tmq2z; Sat,  6 Feb 2016 00:36:17 +0000 (UTC)
Received: from rock.dv.isc.org (c110-21-49-25.carlnfd1.nsw.optusnet.com.au [110.21.49.25]) by zmx1.isc.org (Postfix) with ESMTPSA id 2F9B8160035; Sat,  6 Feb 2016 00:36:17 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 6D767419CED2; Sat,  6 Feb 2016 11:35:40 +1100 (EST)
To: Fernando Gont <fgont@si6networks.com>
From: Mark Andrews <marka@isc.org>
References: <2134F8430051B64F815C691A62D983183395EF42@XCH-BLV-105.nw.nos.boeing.com> <56B4E39A.5040608@si6networks.com> <2134F8430051B64F815C691A62D983183395F017@XCH-BLV-105.nw.nos.boeing.com> <56B4EA46.3080102@si6networks.com> <2134F8430051B64F815C691A62D983183395F0CE@XCH-BLV-105.nw.nos.boeing.com> <56B50285.9010204@si6networks.com> <2134F8430051B64F815C691A62D983183395F2DD@XCH-BLV-105.nw.nos.boeing.com> <56B50889.8080201@si6networks.com>
Subject: Re: ICMP PTB spoofing attacks
In-reply-to: Your message of "Fri, 05 Feb 2016 17:39:37 -0300." <56B50889.8080201@si6networks.com>
Date: Sat, 06 Feb 2016 11:35:40 +1100
Message-Id: <20160206003540.6D767419CED2@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/EZyLFK4DD8sLhM0KISuVy8oTKis>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Feb 2016 00:35:49 -0000

In message <56B50889.8080201@si6networks.com>, Fernando Gont writes:
> On 02/05/2016 05:25 PM, Templin, Fred L wrote:
> >>>
> >>> By "accurate" I mean:
> >>>
> >>> - the router that sends the ICMP PTB is telling the truth that there is a restricting link
> >>> - the MTU value that the router writes in the PTB is in fact the true MTU of the
> >>>    restricting link
> >>
> >> Well, most of these protocols run on "good faith", right? -- If I cannot
> >> trust the router to tell the truth, why should I trust it to e.g.
> >> forward my packets?
> > 
> > A router's trustworthiness for forwarding packets and for telling the truth
> > in any ICMP PTB message it sends are mutually exclusive - the first question
> > is one of availability and the second is one of integrity.
> 
> I think that, at the end of the day, its about trust. Can I trust the
> device, or not?
> 
> I my goal as an attacker is to DoS your communications, I don't care
> whether I achieve that by simply throwing your packets away, or by
> sending you some packet that will cause yourself to shutdown and not talk.
> 
> I should say, however, that in the IPv6 case, the worst case scenario is
> a 1280-byte MTU link...

Which is what we force the nameservers we ship to use (for both TCP
and UDP) as PMTUD takes too long for DNS even when it works.

> > Plus, it is not necessarily just the on-path routers - any off-path "router"
> > could also inject spurious PTBs.
> 
> For off-path attackers, you validate ICMP PTBs. If you don't, well...
> prepare for trouble.  And, yes, if EHs are in use, you may not be able
> to verify them.

Only if all the original headers + PTB header > 1280 which should
be a vanishing small pecentage of times.

> -- 
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
> 
> 
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Sat Feb  6 04:48:38 2016
Return-Path: <tore@fud.no>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB4801B2DBB for <ipv6@ietfa.amsl.com>; Sat,  6 Feb 2016 04:48:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.399
X-Spam-Level: 
X-Spam-Status: No, score=0.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_TOOL=2.3, RP_MATCHES_RCVD=-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 8iHy09oh2FnL for <ipv6@ietfa.amsl.com>; Sat,  6 Feb 2016 04:48:35 -0800 (PST)
Received: from greed.fud.no (greed.fud.no [IPv6:2a02:c0:1001:100::145]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C0211B2DB8 for <ipv6@ietf.org>; Sat,  6 Feb 2016 04:48:35 -0800 (PST)
Received: from [2a02:fe0:c421:2034::c68] (port=40560 helo=envy) by greed.fud.no with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from <tore@fud.no>) id 1aS2Hv-0006vc-II; Sat, 06 Feb 2016 13:48:31 +0100
Date: Sat, 6 Feb 2016 13:48:31 +0100
From: Tore Anderson <tore@fud.no>
To: otroan@employees.org
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Message-ID: <20160206134831.0ef1c371@envy>
In-Reply-To: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org>
X-Mailer: Claws Mail 3.13.1 (GTK+ 2.24.29; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/W1usGcpzp4scZXsa54hfLlShgmk>
Cc: bob.hinden@gmail.com, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Feb 2016 12:48:37 -0000

* otroan@employees.org

> This message starts a two week 6MAN call on adopting:
> 
> Name:	draft-hinden-6man-rfc1981bis-01
> Title:	Path MTU Discovery for IP version 6
> Document date:	2015-12-01
> Pages:	16
> URL:         https://datatracker.ietf.org/doc/draft-hinden-6man-rfc1981bis/
> Htmlized:  https://tools.ietf.org/html/draft-hinden-6man-rfc1981bis-01
> Diff:          https://tools.ietf.org/rfcdiff?url2=draft-hinden-6man-rfc1981bis-01.txt
> 
> as a working group item. Substantive comments and statements of support
> for adopting this document should be directed to the mailing
> list. Editorial suggestions can be sent to the authors.

I support adoption.

I see one issue that I would like to remind the WG about:

   A node MUST NOT reduce its estimate of the Path MTU below the IPv6
   minimum link MTU.

-     Note: A node may receive a Packet Too Big message reporting a
-     next-hop MTU that is less than the IPv6 minimum link MTU.  In that
-     case, the node is not required to reduce the size of subsequent
-     packets sent on the path to less than the IPv6 minimun link MTU,
-     but rather must include a Fragment header in those packets
-     [I-D.ietf-6man-rfc2460bis].

The lines prefixed with "-" have been removed in -01. In my opinion,
this leaves the text in an ambiguous state. What is a node conforming
to -01 expected to do, when receiving a PTB reporting a next-hop MTU
lower than 1280? I see two distinct options:

a) Reduce its PMTU estimate to exactly 1280.
b) Ignore the "invalid" PTB (retaining its previous PMTU estimate).

I think it would be preferable to replace the removed paragraph with a
clarification as to which behaviour is the correct and expected one. I
do not know which one that would be, though.

Tore


From nobody Sun Feb  7 08:15:22 2016
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2332E1B3C81 for <ipv6@ietfa.amsl.com>; Sun,  7 Feb 2016 08:15:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.502
X-Spam-Level: 
X-Spam-Status: No, score=-0.502 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-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 EsXZzVUG4-k4 for <ipv6@ietfa.amsl.com>; Sun,  7 Feb 2016 08:15:19 -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 92B7C1B3C7D for <ipv6@ietf.org>; Sun,  7 Feb 2016 08:15:19 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id B49F4200A3; Sun,  7 Feb 2016 11:15:24 -0500 (EST)
Received: from obiwan.sandelman.ca (ip6-localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id F18FE63751; Sun,  7 Feb 2016 11:15:17 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
In-Reply-To: <56B50394.2010504@gont.com.ar>
References: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com> <7592.1454699773@obiwan.sandelman.ca> <56B50394.2010504@gont.com.ar>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sun, 07 Feb 2016 11:15:17 -0500
Message-ID: <14373.1454861717@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/2BQI5bj2gNLeJlrRsN83RWy1RWI>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2016 16:15:21 -0000

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


Fernando Gont <fernando@gont.com.ar> wrote:
    >> Templin, Fred L <Fred.L.Templin@boeing.com> wrote: > On the other
    >> hand, paths that lead to Internet destinations cannot be > counted on
    >> to deliver the necessary ICMPs. In that case, RFC4821 > provides a
    >> mitigation.
    >>
    >> > But, if we do not believe that there are paths for which traditional
    >> > PMTUD can still be used safely, then we should be working to
    >> deprecate > RFC1981 instead of making it a standard.
    >>
    >> I think that the mitigation is far more reliable than 1981.  So, I'd
    >> rather deprecate RFC1981.
    >>
    >> {I noticed that 4821 is not on by default in most Linux
    >> distros/kernels, and I actually want to know if there is some reason
    >> for it}

    > Yes: convergence time.

Yes, I've noticed that it takes a few re-transmissions on the first
connection to a site in the case where the MTU is limited and the ICMPs are
lost, but when the MTU is unblocked, there is no delay.

An implementation that wanted to avoid even the re-transmissions in the
blocked case could limit themselves to 1280 sized packets and send some 1500
byte probes have gotten through.

If 4821 is turned off, then the connection is mysteriously blocked, and
always fail.

So, your answer does not make sense to me.

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




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

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

iQEVAwUBVrdtk4CLcPvd0N1lAQLrmAf+OX2qWcIvUGTv/3wvBTLqAIn3E17PBm4J
fsQKkqmpyIGYZh0+A5rPlRpU9s5+AfaDYsylVSohEuE5/9Rb/XLFxKMkOSh7gUv4
UkXahbvUFDbtxF6pUseHvhA3rLs8H3kLRh5Qtrejw/HCMorHtZHdbK4osfnrgpdH
vASsLmXXqWrwTPmCF7WD9LkqoajsQqtlbvGbi2EUU9DtszONjlrVTC0kZRO2wDdC
irFVQ4VnbD8vgl2OY/wVXB8sABnl8eRDS86aOuwKGQCNfEx7swU9I5r65d1RoMGi
H1QDUQiXcml7vyAQGDjJnGYBUc4tlaA8OAL+2IvMoZW2jV6FbpW/mw==
=hzAB
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Feb  7 08:24:40 2016
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63CBF1B3C93 for <ipv6@ietfa.amsl.com>; Sun,  7 Feb 2016 08:24:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-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 1M83_NBH2lM6 for <ipv6@ietfa.amsl.com>; Sun,  7 Feb 2016 08:24:38 -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 4EACE1B3C91 for <ipv6@ietf.org>; Sun,  7 Feb 2016 08:24:38 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id B65D7200A3; Sun,  7 Feb 2016 11:19:31 -0500 (EST)
Received: from obiwan.sandelman.ca (ip6-localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id EBA8F63751; Sun,  7 Feb 2016 11:19:24 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Mark Andrews <marka@isc.org>
Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
In-Reply-To: <20160205230616.CA7A1419BA10@rock.dv.isc.org>
References: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com> <56B4E91C.6090905@si6networks.com> <2134F8430051B64F815C691A62D983183395F14A@XCH-BLV-105.nw.nos.boeing.com> <56B502FB.4050302@si6networks.com> <20160205230616.CA7A1419BA10@rock.dv.isc.org>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sun, 07 Feb 2016 11:19:24 -0500
Message-ID: <15275.1454861964@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/nve_YPy-QZke7nEuVY_ov7dxDck>
Cc: Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2016 16:24:39 -0000

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


Mark Andrews <marka@isc.org> wrote:
    >> Except for within well-managed administrative domains where
    >> RFC1981-only > is sufficient. They do exist; I am typing this message
    >> from within one righ t now.
    >>
    >> I'd expect 6man to produce protocols that work everywhere, rather than
    >> just on some subset scearios...

    > RFC 1981 works for TCP unless you *deliberately* break it by dropping
    > PTB as TCP retries.

Yes, and we know that many networks do this.

{It appears that the Linux IPv6 XFRM/NetKey IPsec stack also fails to send
 PTBs when operating in one-arm router mode, but I haven't fully convinced
 myself that this is where the failure is yet}

    > RFC 1981 does NOT work in general for UDP.  DNS/UDP is a perfect
    > example as it is the responding server that get the PTB and the DNS
    > client is trying multiple servers.  Often by the time the server is
    > tried again especially when a server is anycast the MTU knowledge has
    > been lost.

I didn't think PLPMTUD worked any better in this situation, or are I wrong here?

i.e: both are broken for UDP, and in the DNS/UDP case, the server never
     retransmits either... so absent using TCP, it will always just fail.

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




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

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

iQEVAwUBVrduiYCLcPvd0N1lAQJ7RQf/bInuCsHmVH6AONDSavt/Ut1/xo0NdnRp
1vtfg2LwHG5cUJGNpHOdnlg0OdhIJS9KVYN6xP0FQqbfTq4E6zRpoBkw4kMFQFWK
cYOe8MaXx4FJFWF6MWcugglhWRkFQeSaQyYcn0Odhmeoc7w2/ehlsTfuFNGCnpH9
2bJS2Og80JWMDy7Q95IL6JrsKE1/VDDLpJJkQTfqPboZ1BG5Vn6IlDUT+lEMsZly
By2CSNBglAqVtU5fUPYCa6yCx92I2g8MYePqkjclN1dAlELhlOUllsrJ8F3kCuFs
4eT9yAOtU4W7tP/Ka3bBdJTRYnS31NXozgdIlPsnhZ7mXdrks1tQcg==
=kitT
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Feb  7 09:01:30 2016
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48A881A0030 for <ipv6@ietfa.amsl.com>; Sun,  7 Feb 2016 09:01:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.622
X-Spam-Level: 
X-Spam-Status: No, score=-0.622 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_12=0.6, RP_MATCHES_RCVD=-0.001, 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 QdhaPF7KbPGG for <ipv6@ietfa.amsl.com>; Sun,  7 Feb 2016 09:01:27 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EBE51A0031 for <ipv6@ietf.org>; Sun,  7 Feb 2016 09:01:26 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u17H1HgF019507; Sun, 7 Feb 2016 17:01:17 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u17H1HgF019507
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1454864477; bh=G92pim0vjLYpgjy3B8QOEG+vHaE=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=oyx/MMSHdV4NYB4Dm8vbBqdDzpfDxLkzB0scBf+j9u0WLMJSR5un1X/x8we1h57Pj TLnDocFtTCPuH4i+xyXigXG2J+z/pwLtByXsMl1VOQYn1+cGc8lvyOqBHJmr3ylzZK SF2b0HU0+404VBlPycAmIBWq+TmFRjdroSgPV3u4=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s16H1H25963025327z ret-id none; Sun, 07 Feb 2016 17:01:17 +0000
Received: from [192.168.0.10] (tchowndsl.claranet.co.uk [212.188.254.49]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u17GxvQL026452 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 7 Feb 2016 16:59:57 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <56B4FF9D.10203@gmail.com>
Date: Sun, 7 Feb 2016 16:59:56 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|5048bb3e4f22902e3e9b18a621e7fd32s16H1H03tjc|ecs.soton.ac.uk|5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk>
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com> <56B4FF9D.10203@gmail.com> <5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3112)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s16H1H259630253200; tid=s16H1H25963025327z; client=relay,ipv6; mail=; rcpt=; nrcpt=5:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u17H1HgF019507
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/X89KxubjHbhj03K8HjizgyzIm1w>
Cc: Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2016 17:01:29 -0000

On 5 Feb 2016, at 20:01, Brian E Carpenter <brian.e.carpenter@gmail.com> =
wrote:
>=20
> On 06/02/2016 07:20, Fernando Gont wrote:
>> On 02/05/2016 03:07 PM, otroan@employees.org wrote:
>>> Fernando,
>>>=20
>>> [...]
>>>=20
>>>>>=20
>>>>> What is the risk of using the same IID for link-local and global =
addresses?
>>>>> Typically if you can snoop the link-local address then you're =
onlink and leak information about all addresses and their correlations =
anyway.
>>>>=20
>>>> We discussed this one a hundred times now (including for RFC7217). =
The
>>>> risk is that at times such addressess can leak, without the need of =
the
>>>> attacker being pesent on the local link.
>>>>=20
>>>> e.g., your MTA is on the local-link, and you end up connecting to =
it
>>>> with a LL, which then appears in the email headers. (and there are =
a
>>>> bunch of other possible reasons for that to happen).
>>>>=20
>>>> Be proactive. MAC addresses in the IID are wrong. Putting them =
there is
>>>> just waiting for trouble.
>>>=20
>>> I didn't say the LL was based on a MAC.
>>> my question was if there was any issue with re-using the IID from =
the link-local in the GUA. assume the link-local is generated f.ex with =
7217.
>>=20
>> Oops, my apologies. My answer would be "It unnecessarily enables
>> correlation of the activities that you carry between the two =
addresses".
>>=20
>> i.e., by simply inspecting the IID I could easily tell that the
>> activities carried out with one address were performed by the same =
node
>> that employed the other address.
>>=20
>> My take here is, again: be proactive. If there's no requirement (and
>> there isn't) for the two IIDs to be the same, then make them =
different,
>> and fail on the safe side.
>=20
> But Ole's point was that any observer who sees a LL packet is on-link =
and
> can therefore see the MAC address anyway; an observer who can see MAC =
addresses
> can just laugh at RFC 7217 or RFC 4941.

Well, except that the device might be varying its MAC address as well.

I thought RFC7217 states that a device is expected to have a different =
IID for=20
each prefix on an interface. (Though whether there=E2=80=99s a NetworkID =
available to
seed a different LL IID per visited network is another question, else =
the device
presumably has the same LL IID as it moves?)

There=E2=80=99s definitely value in avoiding correlation. If there=E2=80=99=
s an equal cost either=20
way, why allow such potential?

Tim


From nobody Sun Feb  7 10:48:05 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C64B1A1A30 for <ipv6@ietfa.amsl.com>; Sun,  7 Feb 2016 10:48:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 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, J_CHICKENPOX_12=0.6, 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 AeY2QqdsaLS4 for <ipv6@ietfa.amsl.com>; Sun,  7 Feb 2016 10:48:02 -0800 (PST)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C35001A1A36 for <ipv6@ietf.org>; Sun,  7 Feb 2016 10:48:02 -0800 (PST)
Received: by mail-pa0-x229.google.com with SMTP id ho8so61869236pac.2 for <ipv6@ietf.org>; Sun, 07 Feb 2016 10:48:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=QJGEFVCwHrly/pMWM9n5sAcPDzg/C2WLE9AR6/cEnN4=; b=fyNpKkJ8Mp6l9U/v0QLPwfwB3rZUaGrMU4YcwSV+0diRXPaQoyYO+FlW4Jq6Q8IbJA qTzxOvvrrI8mqxx7obwXt5pnMX4pdbBKg8edFSWtZRxfUuUjyRohNJ0mng4hwJJDQL0p 7+2BAkPJl8gcBn+pVSBKIxHeNPG9haBk+yy2qIaa4K9Z5J2ADeDFsC1wwZ9AaFwqzarb bIWfpwxEI1G9ja78ATr8lkvGedl+Gig/lBB089mMCd6wwZ/4ZbnQajlAZRgq+ZHLPBU3 WROVFNFlgkDXb/+IZ113E3Jeh23tvzLdirj4es7xtQeqXaOCuBmaWyCwaKgFWQYmana5 vS0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=QJGEFVCwHrly/pMWM9n5sAcPDzg/C2WLE9AR6/cEnN4=; b=bfKTwEZx+HIU8Vpd7XNNdgttVvRwsIPRKZFuqBLSMGUt4DWHyVT9BScNYE+19JGH9H 3LoWtSRC+MCZlrzFLPTBGCIkhKzxJF793+VAKqfwfOnI/UBs20O1xs93TyQWRCMvj19q ErGMMq3J0gL3JgySVmREiJwKZ6Kem+B7lPnbwRIMDsF3lG5/e3Zzh1X2ED0OXLGjJTXv os8WjxUft33ljr/z5eD8mqF5VNfx8d/6k5giFtQbU3vmdt76c6M4ZQZ9555wDuCOl4Y+ +6XUy+p78L0VyVxFrOXj1zAwzpdIJaMWuPxDAUhkFP/ntSO4OQyero3qaa3Q9lweaDyB gBYA==
X-Gm-Message-State: AG10YOQg3R+APWC6qGjLmF858m2sMsbfqk/XiBlMNZOzQS7K0OPTr0gedRS5MxzQDZo3pQ==
X-Received: by 10.66.234.104 with SMTP id ud8mr36774461pac.143.1454870882454;  Sun, 07 Feb 2016 10:48:02 -0800 (PST)
Received: from ?IPv6:2406:e007:5a31:1:28cc:dc4c:9703:6781? ([2406:e007:5a31:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id xv2sm38043759pab.10.2016.02.07.10.47.58 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 07 Feb 2016 10:48:01 -0800 (PST)
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: Tim Chown <tjc@ecs.soton.ac.uk>
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com> <56B4FF9D.10203@gmail.com> <5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <EMEW3|5048bb3e4f22902e3e9b18a621e7fd32s16H1H03tjc|ecs.soton.ac.uk|5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56B7915D.2060300@gmail.com>
Date: Mon, 8 Feb 2016 07:47:57 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <EMEW3|5048bb3e4f22902e3e9b18a621e7fd32s16H1H03tjc|ecs.soton.ac.uk|5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/jLJKtxNbUCgUAD7OUNoByPB2KlU>
Cc: Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2016 18:48:04 -0000

On 08/02/2016 05:59, Tim Chown wrote:
> On 5 Feb 2016, at 20:01, Brian E Carpenter <brian.e.carpenter@gmail.com=
> wrote:
>>
>> On 06/02/2016 07:20, Fernando Gont wrote:
>>> On 02/05/2016 03:07 PM, otroan@employees.org wrote:
>>>> Fernando,
>>>>
>>>> [...]
>>>>
>>>>>>
>>>>>> What is the risk of using the same IID for link-local and global a=
ddresses?
>>>>>> Typically if you can snoop the link-local address then you're onli=
nk and leak information about all addresses and their correlations anyway=
=2E
>>>>>
>>>>> We discussed this one a hundred times now (including for RFC7217). =
The
>>>>> risk is that at times such addressess can leak, without the need of=
 the
>>>>> attacker being pesent on the local link.
>>>>>
>>>>> e.g., your MTA is on the local-link, and you end up connecting to i=
t
>>>>> with a LL, which then appears in the email headers. (and there are =
a
>>>>> bunch of other possible reasons for that to happen).
>>>>>
>>>>> Be proactive. MAC addresses in the IID are wrong. Putting them ther=
e is
>>>>> just waiting for trouble.
>>>>
>>>> I didn't say the LL was based on a MAC.
>>>> my question was if there was any issue with re-using the IID from th=
e link-local in the GUA. assume the link-local is generated f.ex with 721=
7.
>>>
>>> Oops, my apologies. My answer would be "It unnecessarily enables
>>> correlation of the activities that you carry between the two addresse=
s".
>>>
>>> i.e., by simply inspecting the IID I could easily tell that the
>>> activities carried out with one address were performed by the same no=
de
>>> that employed the other address.
>>>
>>> My take here is, again: be proactive. If there's no requirement (and
>>> there isn't) for the two IIDs to be the same, then make them differen=
t,
>>> and fail on the safe side.
>>
>> But Ole's point was that any observer who sees a LL packet is on-link =
and
>> can therefore see the MAC address anyway; an observer who can see MAC =
addresses
>> can just laugh at RFC 7217 or RFC 4941.
>=20
> Well, except that the device might be varying its MAC address as well.
>=20
> I thought RFC7217 states that a device is expected to have a different =
IID for=20
> each prefix on an interface. (Though whether there=E2=80=99s a NetworkI=
D available to
> seed a different LL IID per visited network is another question, else t=
he device
> presumably has the same LL IID as it moves?)
>=20
> There=E2=80=99s definitely value in avoiding correlation. If there=E2=80=
=99s an equal cost either=20
> way, why allow such potential?

Extra code? But my real concern is that there might be unintended side ef=
fects,
because the interface identifier will no longer identify an interface.

    Brian


From nobody Sun Feb  7 11:37:45 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 169461A1B43; Sun,  7 Feb 2016 11:37:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.3
X-Spam-Level: 
X-Spam-Status: No, score=0.3 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, MANGLED_TOOL=2.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NU92vHOY-PoI; Sun,  7 Feb 2016 11:37:42 -0800 (PST)
Received: from mail-pf0-x235.google.com (mail-pf0-x235.google.com [IPv6:2607:f8b0:400e:c00::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A36A1A1B40; Sun,  7 Feb 2016 11:37:42 -0800 (PST)
Received: by mail-pf0-x235.google.com with SMTP id e127so2745414pfe.3; Sun, 07 Feb 2016 11:37:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=h5+PwXeDaD684ZR+UoJwnqHGt08vTLjp1Sb8kkFZWbs=; b=Cva5tHUeVuVhLidYxSZ3ZJ3OHQVFnSyPMYxS4oQHHfKNu5II3CqYWscBGeLHC6PEXr 5XaPMmfUGCRn2Qnbsc+J5d3y4H/phOccn151dZyu6MgrbFvwPy60Z+lFg0iPYfIkYAih cQH/FX3HqLJWqBu6rvz/ZPTbq/GFSPhoEjhecs6yXGCozifJTeuhazNbQF7EORftzAjY BHLc4bMs09BZmM9PvIeO71nSnZW3KdL421+IUgTgXGtiNwBS3FKrEsAaErvi+yPyUkvd c8CT5HvQCdRUQdxZgwr23aQHyNTamzNxIecIaOMmK/m2CjOlXnnsoZ6VWlCGVheghn+a kT2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=h5+PwXeDaD684ZR+UoJwnqHGt08vTLjp1Sb8kkFZWbs=; b=BwG9HWO7ygeH0NDn9IB553REmvf19oo3Q536YHcFF9yuhgZNKVmkavTSX7Unl250XZ kFFHv27rxQBDv9R/esofxw97XwGL5/F1JBiUt2dJ/+xQz1bYS1vv56fpN1GGfB+N8oNC GWLmIyUhX/rhwHQcm/CGW/AhgMsbLZDsqAL2aKXOFnvX0kKBvQZdLt0Lt6mwCdBh+Ejl AcatXyxJcqRn9S+0R6oCJh03O0YHxG7St2z2g1ibHqn/dVEM3LonaXLylAdo4TUROKNi NcKFfIVQUP3YUI4JZwb4NZKKRS+WeQ3uRhKXKEG1Zkb6/7ZchqjS7CgI5ockWVb5ncl4 95tg==
X-Gm-Message-State: AG10YOSaBDpfQs/dCP3E8GvbTRjMBYmcKIX5Edg+m+PxZmev1WsiALjQH1D1UJZRIJiKMg==
X-Received: by 10.98.17.28 with SMTP id z28mr23697956pfi.38.1454873862315; Sun, 07 Feb 2016 11:37:42 -0800 (PST)
Received: from ?IPv6:2406:e007:5a31:1:28cc:dc4c:9703:6781? ([2406:e007:5a31:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id ah10sm38139719pad.23.2016.02.07.11.37.37 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 07 Feb 2016 11:37:40 -0800 (PST)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
To: Tore Anderson <tore@fud.no>, otroan@employees.org
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <20160206134831.0ef1c371@envy>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56B79D01.6050307@gmail.com>
Date: Mon, 8 Feb 2016 08:37:37 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <20160206134831.0ef1c371@envy>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/uCBvtOhrN4MdmpYrJJNMeBDts9Q>
Cc: 6man WG <ipv6@ietf.org>, bob.hinden@gmail.com, draft-bao-v6ops-rfc6145bis@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2016 19:37:44 -0000

On 07/02/2016 01:48, Tore Anderson wrote:
> * otroan@employees.org
> 
>> This message starts a two week 6MAN call on adopting:
>>
>> Name:	draft-hinden-6man-rfc1981bis-01
>> Title:	Path MTU Discovery for IP version 6
>> Document date:	2015-12-01
>> Pages:	16
>> URL:         https://datatracker.ietf.org/doc/draft-hinden-6man-rfc1981bis/
>> Htmlized:  https://tools.ietf.org/html/draft-hinden-6man-rfc1981bis-01
>> Diff:          https://tools.ietf.org/rfcdiff?url2=draft-hinden-6man-rfc1981bis-01.txt
>>
>> as a working group item. Substantive comments and statements of support
>> for adopting this document should be directed to the mailing
>> list. Editorial suggestions can be sent to the authors.
> 
> I support adoption.
> 
> I see one issue that I would like to remind the WG about:
> 
>    A node MUST NOT reduce its estimate of the Path MTU below the IPv6
>    minimum link MTU.
> 
> -     Note: A node may receive a Packet Too Big message reporting a
> -     next-hop MTU that is less than the IPv6 minimum link MTU.  In that
> -     case, the node is not required to reduce the size of subsequent
> -     packets sent on the path to less than the IPv6 minimun link MTU,
> -     but rather must include a Fragment header in those packets
> -     [I-D.ietf-6man-rfc2460bis].
> 
> The lines prefixed with "-" have been removed in -01. 

Isn't this the same change that has been made to 2460bis anyway?

>       01)  Removed paragraph in Section 5 that required including a
>            fragment header to outgoing packets if a ICMP Packet Too Big
>            message reporting a Next-Hop MTU less than 1280.  This is
>            based on the update in draft-ietf-6man-deprecate-atomfrag-
>            generation-03.

It seems to me that RFC 6145 and draft-bao-v6ops-rfc6145bis (SIIT) still
rely on this behaviour, whatever draft-ietf-6man-deprecate-atomfrag-generation
says. Or I am confused.

   Brian

> In my opinion,
> this leaves the text in an ambiguous state. What is a node conforming
> to -01 expected to do, when receiving a PTB reporting a next-hop MTU
> lower than 1280? I see two distinct options:
> 
> a) Reduce its PMTU estimate to exactly 1280.
> b) Ignore the "invalid" PTB (retaining its previous PMTU estimate).
> 
> I think it would be preferable to replace the removed paragraph with a
> clarification as to which behaviour is the correct and expected one. I
> do not know which one that would be, though.
> 
> Tore
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 


From nobody Sun Feb  7 16:48:29 2016
Return-Path: <marka@isc.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C888E1A8707 for <ipv6@ietfa.amsl.com>; Sun,  7 Feb 2016 16:48:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.602
X-Spam-Level: 
X-Spam-Status: No, score=-4.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_HERE=2.3, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 U96-3hItWUMe for <ipv6@ietfa.amsl.com>; Sun,  7 Feb 2016 16:48:26 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 457601A8702 for <ipv6@ietf.org>; Sun,  7 Feb 2016 16:48:26 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx.ams1.isc.org (Postfix) with ESMTPS id 49D761FCAB9; Mon,  8 Feb 2016 00:48:22 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 256591600A0; Mon,  8 Feb 2016 00:48:21 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 155DE1600A1; Mon,  8 Feb 2016 00:48:21 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 58V5ZDLF7z5l; Mon,  8 Feb 2016 00:48:21 +0000 (UTC)
Received: from rock.dv.isc.org (c110-21-49-25.carlnfd1.nsw.optusnet.com.au [110.21.49.25]) by zmx1.isc.org (Postfix) with ESMTPSA id 92E2C1600A0; Mon,  8 Feb 2016 00:48:20 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id A351E41AF670; Mon,  8 Feb 2016 11:48:18 +1100 (EST)
To: Michael Richardson <mcr+ietf@sandelman.ca>
From: Mark Andrews <marka@isc.org>
References: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com> <56B4E91C.6090905@si6networks.com> <2134F8430051B64F815C691A62D983183395F14A@XCH-BLV-105.nw.nos.boeing.com> <56B502FB.4050302@si6networks.com> <20160205230616.CA7A1419BA10@rock.dv.isc.org> <15275.1454861964@obiwan.sandelman.ca>
Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
In-reply-to: Your message of "Sun, 07 Feb 2016 11:19:24 -0500." <15275.1454861964@obiwan.sandelman.ca>
Date: Mon, 08 Feb 2016 11:48:18 +1100
Message-Id: <20160208004818.A351E41AF670@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/zF86I45vee8qN8HNYUTAbiCDFjQ>
Cc: Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 00:48:28 -0000

In message <15275.1454861964@obiwan.sandelman.ca>, Michael Richardson writes:
> 
> Mark Andrews <marka@isc.org> wrote:
>     >> Except for within well-managed administrative domains where
>     >> RFC1981-only > is sufficient. They do exist; I am typing this message
>     >> from within one righ t now.
>     >>
>     >> I'd expect 6man to produce protocols that work everywhere, rather than
>     >> just on some subset scearios...
> 
>     > RFC 1981 works for TCP unless you *deliberately* break it by dropping
>     > PTB as TCP retries.
> 
> Yes, and we know that many networks do this.
> 
> {It appears that the Linux IPv6 XFRM/NetKey IPsec stack also fails to send
>  PTBs when operating in one-arm router mode, but I haven't fully convinced
>  myself that this is where the failure is yet}
> 
>     > RFC 1981 does NOT work in general for UDP.  DNS/UDP is a perfect
>     > example as it is the responding server that get the PTB and the DNS
>     > client is trying multiple servers.  Often by the time the server is
>     > tried again especially when a server is anycast the MTU knowledge has
>     > been lost.
> 
> I didn't think PLPMTUD worked any better in this situation, or are I wrong he
> re?

Conceptually you do PLPMTUD by adjusting the EDNS UDP size advertised
in the query until you get a response.  This isn't strict PMTUD as
it also accounts for firewalls that are blocking fragments, firewalls
that still think DNS is limited to 512 byte UDP payloads.  Unfortunately
you only have about 3 seconds to do this all in as well as talking
to other servers.  The DNS doesn't have a way of signaling "fragment
at this size".

Named tracks successful answers/timeouts with different EDNS udp
sizes as well as the actual response sizes that have got through.

; [edns success/4096 timeout/1432 timeout/1232 timeout/512 timeout]

Too many timeouts with a particlar size and we stop offering a EDNS
UDP buffer of that size and fallback to the next break point.  These
values are set for 4in6/6in4 + a UDP header.  timeouts with a smaller
EDNS buffer size also count against larger sizes.

> i.e: both are broken for UDP, and in the DNS/UDP case, the server never
>      retransmits either... so absent using TCP, it will always just fail.

But the client re-queries leading to a re-transmission.
 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
> 
> 
> 
> 
> --=-=-=
> Content-Type: application/pgp-signature; name="signature.asc"
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> 
> iQEVAwUBVrduiYCLcPvd0N1lAQJ7RQf/bInuCsHmVH6AONDSavt/Ut1/xo0NdnRp
> 1vtfg2LwHG5cUJGNpHOdnlg0OdhIJS9KVYN6xP0FQqbfTq4E6zRpoBkw4kMFQFWK
> cYOe8MaXx4FJFWF6MWcugglhWRkFQeSaQyYcn0Odhmeoc7w2/ehlsTfuFNGCnpH9
> 2bJS2Og80JWMDy7Q95IL6JrsKE1/VDDLpJJkQTfqPboZ1BG5Vn6IlDUT+lEMsZly
> By2CSNBglAqVtU5fUPYCa6yCx92I2g8MYePqkjclN1dAlELhlOUllsrJ8F3kCuFs
> 4eT9yAOtU4W7tP/Ka3bBdJTRYnS31NXozgdIlPsnhZ7mXdrks1tQcg==
> =kitT
> -----END PGP SIGNATURE-----
> --=-=-=--
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Sun Feb  7 22:18:54 2016
Return-Path: <tore@fud.no>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 297E21A92BA; Sun,  7 Feb 2016 22:18:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.799
X-Spam-Level: *
X-Spam-Status: No, score=1.799 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_BACKHAIR_34=1, RP_MATCHES_RCVD=-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 aGqb6Bd9m_2w; Sun,  7 Feb 2016 22:18:51 -0800 (PST)
Received: from greed.fud.no (greed.fud.no [IPv6:2a02:c0:1001:100::145]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B39031A923D; Sun,  7 Feb 2016 22:18:51 -0800 (PST)
Received: from [2a02:c0:2:1:1194:17:0:1029] (port=44448 helo=echo.ms.redpill-linpro.com) by greed.fud.no with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from <tore@fud.no>) id 1aSf9q-0001w3-JH; Mon, 08 Feb 2016 07:18:46 +0100
Date: Mon, 8 Feb 2016 07:18:46 +0100
From: Tore Anderson <tore@fud.no>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Message-ID: <20160208071846.180b4b23@echo.ms.redpill-linpro.com>
In-Reply-To: <56B79D01.6050307@gmail.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <20160206134831.0ef1c371@envy> <56B79D01.6050307@gmail.com>
X-Mailer: Claws Mail 3.13.1 (GTK+ 2.24.29; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/TcnINZcp8RyWKIOKV8RcAMQgbHQ>
Cc: bob.hinden@gmail.com, 6man WG <ipv6@ietf.org>, draft-bao-v6ops-rfc6145bis@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 06:18:53 -0000

Hello Brian,

* Brian E Carpenter <brian.e.carpenter@gmail.com>

> On 07/02/2016 01:48, Tore Anderson wrote:
> > I see one issue that I would like to remind the WG about:
> > 
> >    A node MUST NOT reduce its estimate of the Path MTU below the IPv6
> >    minimum link MTU.
> > 
> > -     Note: A node may receive a Packet Too Big message reporting a
> > -     next-hop MTU that is less than the IPv6 minimum link MTU.  In that
> > -     case, the node is not required to reduce the size of subsequent
> > -     packets sent on the path to less than the IPv6 minimun link MTU,
> > -     but rather must include a Fragment header in those packets
> > -     [I-D.ietf-6man-rfc2460bis].
> > 
> > The lines prefixed with "-" have been removed in -01.   
> 
> Isn't this the same change that has been made to 2460bis anyway?

Similar text was removed from 2460bis, that is true.

That said, 2460bis contains no prohibition against a node reducing its
PMTU below 1280; this restriction only found in 1981(bis) immediately
preceding the deleted paragraph.

2460bis does not really say anything about how PMTUD should be
implemented (it just refers to 1981), so I think it makes sense to
contain this information in 1981bis.

> >       01)  Removed paragraph in Section 5 that required including a
> >            fragment header to outgoing packets if a ICMP Packet Too Big
> >            message reporting a Next-Hop MTU less than 1280.  This is
> >            based on the update in draft-ietf-6man-deprecate-atomfrag-
> >            generation-03.  
> 
> It seems to me that RFC 6145 and draft-bao-v6ops-rfc6145bis (SIIT) still
> rely on this behaviour, whatever
> draft-ietf-6man-deprecate-atomfrag-generation says. Or I am confused.

A translator conforming to 6145bis will never emit translated ICMPv6 PTBs
indicating a PMTU < 1280. From section 4.2:

               The MTU field MUST be adjusted for the difference
               between the IPv4 and IPv6 header sizes, but MUST NOT be
               set to a value smaller than the minimum IPv6 MTU (1280
               bytes).

To the best of my knowledge, an ICMPv6 PTB with MTU<1280 can only
legitimately occur in the wild as a result from translation from an
IPv4 FN by a 6145-not-bis translator implementing the "first approach"
in section 6. (The "second approach" is basically the same as what
6145bis mandates, for what it's worth.)

Actually, this made me realise that my option a) is probably the best
choice, i.e., that an IPv6 node receiving an PTB with MTU<1280 should
interpret it as if it had MTU=1280. Doing so would increase the
likelihood of successful communication in the case where the IPv4->IPv6
translator conforms to 6145-1st-approach while the IPv6->IPv4
translator conforms to 6145bis (or 6145-2nd-approach) one.

Tore


From nobody Mon Feb  8 00:42:00 2016
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD8631ACD9A for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 00:41:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zkGzPvA9zsAB for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 00:41:51 -0800 (PST)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B06D1ACD98 for <ipv6@ietf.org>; Mon,  8 Feb 2016 00:41:51 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u188fm0a030235; Mon, 8 Feb 2016 09:41:48 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 3C294201830; Mon,  8 Feb 2016 09:50:02 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 3099A200EE9; Mon,  8 Feb 2016 09:50:02 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u188fmnd019219; Mon, 8 Feb 2016 09:41:48 +0100
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: Fernando Gont <fgont@si6networks.com>, ipv6@ietf.org
References: <56B48386.2040300@gmail.com> <56B4CCE0.7090207@si6networks.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <56B854CC.70307@gmail.com>
Date: Mon, 8 Feb 2016 09:41:48 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B4CCE0.7090207@si6networks.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/3rdqGyjuIQgTgcPhLaiBUhjCzxs>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 08:41:55 -0000

Le 05/02/2016 17:25, Fernando Gont a écrit :
> Hi, ALex,
>
> On 02/05/2016 08:12 AM, Alexandre Petrescu wrote:
>> Hello 6manners,
>>
>> draft-ietf-6man-default-iids-09 rightfully indicates that the same IID
>> should not be used in the LL and GUA addresses of a same interface.
>> Because there may be a risk of correlation between addresses by a snooper.
>>
>> The draft says:
>>    The negotiated interface identifier is used by the local end of the
>>    PPP link to autoconfigure an IPv6 link-local unicast address for the
>>    PPP interface.  However, it SHOULD NOT be assumed that the same
>>    interface identifier is used in configuring global unicast addresses
>>    for the PPP interface using IPv6 stateless address autoconfiguration
>>    [3].
>>
>> But what does it mean "it SHOULD NOT be assumed"?  Who should not
>> assume?  I think the text should rather say: "a same IID should not be
>> used for several different scoped addresses of a same interface because
>> snoopers may correlated them".
>
> You're right. Actually, I'd remove this sentence altogether:
> "  However, it SHOULD NOT be assumed that the same
>     interface identifier is used in configuring global unicast addresses
>     for the PPP interface using IPv6 stateless address autoconfiguration
>     [3]."
>
> since RFC7217 takes care of this. Thoughts?

I think it is good.  Better would be "the same IID present in LL SHOULD 
NOT be used in configuring GUA (or ULA) for the ppp interface".

'SHOULD NOT be assumed' is unclear.

>> And what is [3]?  I guess the brackets should be escaped somehow
>> otherwise looking at the list of References in this draft there is no [3].
>
> That's a reference in the RFC we're quoting.

Ok, I understand.  So this RFC-to-be is less self-contained - it must be 
read together with the referred RFCs.

Alex

>
> Thanks,
>


From nobody Mon Feb  8 00:46:37 2016
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C05A71ACDA3 for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 00:46:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.383
X-Spam-Level: 
X-Spam-Status: No, score=-4.383 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, J_CHICKENPOX_12=0.6, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Auv5w9nCtgMF for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 00:46:34 -0800 (PST)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE96C1ACDA1 for <ipv6@ietf.org>; Mon,  8 Feb 2016 00:46:33 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u188kTrW025242; Mon, 8 Feb 2016 09:46:29 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id A02D6202E8B; Mon,  8 Feb 2016 09:54:42 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 8FDFE202E78; Mon,  8 Feb 2016 09:54:42 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u188kSZs009229; Mon, 8 Feb 2016 09:46:28 +0100
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Fernando Gont <fgont@si6networks.com>, otroan@employees.org
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com> <56B4FF9D.10203@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <56B855E4.7070500@gmail.com>
Date: Mon, 8 Feb 2016 09:46:28 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B4FF9D.10203@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/JU-hu0wfBb6Tsgs7hUTbyVO49Lc>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 08:46:35 -0000

Le 05/02/2016 21:01, Brian E Carpenter a Ã©crit :
> On 06/02/2016 07:20, Fernando Gont wrote:
>> On 02/05/2016 03:07 PM, otroan@employees.org wrote:
>>> Fernando,
>>>
>>> [...]
>>>
>>>>>
>>>>> What is the risk of using the same IID for link-local and global addresses?
>>>>> Typically if you can snoop the link-local address then you're onlink and leak information about all addresses and their correlations anyway.
>>>>
>>>> We discussed this one a hundred times now (including for RFC7217). The
>>>> risk is that at times such addressess can leak, without the need of the
>>>> attacker being pesent on the local link.
>>>>
>>>> e.g., your MTA is on the local-link, and you end up connecting to it
>>>> with a LL, which then appears in the email headers. (and there are a
>>>> bunch of other possible reasons for that to happen).
>>>>
>>>> Be proactive. MAC addresses in the IID are wrong. Putting them there is
>>>> just waiting for trouble.
>>>
>>> I didn't say the LL was based on a MAC.
>>> my question was if there was any issue with re-using the IID from the link-local in the GUA. assume the link-local is generated f.ex with 7217.
>>
>> Oops, my apologies. My answer would be "It unnecessarily enables
>> correlation of the activities that you carry between the two addresses".
>>
>> i.e., by simply inspecting the IID I could easily tell that the
>> activities carried out with one address were performed by the same node
>> that employed the other address.
>>
>> My take here is, again: be proactive. If there's no requirement (and
>> there isn't) for the two IIDs to be the same, then make them different,
>> and fail on the safe side.
>
> But Ole's point was that any observer who sees a LL packet is on-link and
> can therefore see the MAC address anyway;

Links which share same non-MAC IID for LL and GUA are necessarily ppp 
links (this sharing does not happen on wifi links for example).

On these ppp links there are no MAC addresses and no MAC headers, so the 
observer can't see them.

> an observer who can see MAC addresses
> can just laugh at RFC 7217 or RFC 4941.

There are observers and observers.  We need to protected against 
unlawful observers.  In ppp links the lawful observers (lawful 
interception) have access to the IIDs.  The unlawful observers dont.

The lawful observers dont need to make correlations because they have them.

Alex

>
>     Brian
>


From nobody Mon Feb  8 00:57:52 2016
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB44B1ACDBB for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 00:57:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.898
X-Spam-Level: 
X-Spam-Status: No, score=-0.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, 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 Ct56G6baDehx for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 00:57:49 -0800 (PST)
Received: from mail-vk0-x232.google.com (mail-vk0-x232.google.com [IPv6:2607:f8b0:400c:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3FFF1ACDB8 for <ipv6@ietf.org>; Mon,  8 Feb 2016 00:57:48 -0800 (PST)
Received: by mail-vk0-x232.google.com with SMTP id k196so24293034vka.0 for <ipv6@ietf.org>; Mon, 08 Feb 2016 00:57:48 -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; bh=VSTKM1xa7Phz96ZTt1RRo8On8GPy3TLEb5QT0g4Ucr0=; b=s4s+qIrhH+StAVLsqQ8pAHocfmSsOqP9oEPm3Ae/Wtb+Yft5A9Iyx/hZyUqVuzm2mm Om3pWoFJxJhmmsM88TOiMarnPnaq081k1YA40a5b0Vcqg7/Z4B2xsHSXOc/VANpEP8Eo 6t37zJHRytfy70nmuB1rlE9S+0A2X68W2b3IBcd09x8GcW0/ggndVc167aNkcVz42Iqb 1wHvPcOMysnnHdjEVFBENCKt1Tz9uYiKroa2zGckmW6hKQdVgEhx7lb9y+bKlFkMl6Lr r05miQ//5mo9G7vqNK/vUEuI6qUZlQqauF9cAlsW4J88WJug79gCWeqAGdo1H+Os659Z I3Tw==
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=VSTKM1xa7Phz96ZTt1RRo8On8GPy3TLEb5QT0g4Ucr0=; b=LXdWxllLA+eJJkscYfhQ4Sqy/llvNYapKFJs2JYVX5OJVfp2GgHy61cM6JHxn7X2V5 +VDUULZvVmVt+H4kTT7Kbl3z1TPwLFXaN77o1OSyxuu7nZWyOfMwGBBXYFSUrJwuI6Lx qIYOuBEc7sMX9wbF4AO0oPZuKa6ykXyQN/gE/syLkmc9InTM1rxuIJaX452mNmpKYPBY tCvEG00R5t2UgPvAm84PIeFsKgxTWNW8s0VuEAMlhseyrkjl0Jy/RxGhkgkQDWv0lzB9 k7Lit0NMhxiRGlhueGCki3B3OBC/UdRg267nohfsVh30b8+SFDaCQJIcrjJUcZHklnmv OZoQ==
X-Gm-Message-State: AG10YOQPCWFsbodKVwYGMxoDJ9KW3+G6edTVeljCv3ocNROROx1GL9q57jC8R3DRDlsZC2cmQIDNhOITooq4IA==
MIME-Version: 1.0
X-Received: by 10.31.128.82 with SMTP id b79mr19159423vkd.47.1454921867949; Mon, 08 Feb 2016 00:57:47 -0800 (PST)
Received: by 10.159.34.103 with HTTP; Mon, 8 Feb 2016 00:57:47 -0800 (PST)
Received: by 10.159.34.103 with HTTP; Mon, 8 Feb 2016 00:57:47 -0800 (PST)
In-Reply-To: <56B855E4.7070500@gmail.com>
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com> <56B4FF9D.10203@gmail.com> <56B855E4.7070500@gmail.com>
Date: Mon, 8 Feb 2016 19:57:47 +1100
Message-ID: <CAO42Z2wToBa-Wsk=QuqJw8dVjB1GNmYVm4yE9tT-xTTN3a2MCg@mail.gmail.com>
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
From: Mark Smith <markzzzsmith@gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=001a11429ce41d7ca4052b3e6555
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/mUqv-YyrogygCOfg0qeVd9d5gjY>
Cc: Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 08:57:51 -0000

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

On 8 Feb 2016 7:46 PM, "Alexandre Petrescu" <alexandre.petrescu@gmail.com>
wrote:
>
>
>
> Le 05/02/2016 21:01, Brian E Carpenter a =C3=A9crit :
>>
>> On 06/02/2016 07:20, Fernando Gont wrote:
>>>
>>> On 02/05/2016 03:07 PM, otroan@employees.org wrote:
>>>>
>>>> Fernando,
>>>>
>>>> [...]
>>>>
>>>>>>
>>>>>> What is the risk of using the same IID for link-local and global
addresses?
>>>>>> Typically if you can snoop the link-local address then you're onlink
and leak information about all addresses and their correlations anyway.
>>>>>
>>>>>
>>>>> We discussed this one a hundred times now (including for RFC7217). Th=
e
>>>>> risk is that at times such addressess can leak, without the need of
the
>>>>> attacker being pesent on the local link.
>>>>>
>>>>> e.g., your MTA is on the local-link, and you end up connecting to it
>>>>> with a LL, which then appears in the email headers. (and there are a
>>>>> bunch of other possible reasons for that to happen).
>>>>>
>>>>> Be proactive. MAC addresses in the IID are wrong. Putting them there
is
>>>>> just waiting for trouble.
>>>>
>>>>
>>>> I didn't say the LL was based on a MAC.
>>>> my question was if there was any issue with re-using the IID from the
link-local in the GUA. assume the link-local is generated f.ex with 7217.
>>>
>>>
>>> Oops, my apologies. My answer would be "It unnecessarily enables
>>> correlation of the activities that you carry between the two addresses"=
.
>>>
>>> i.e., by simply inspecting the IID I could easily tell that the
>>> activities carried out with one address were performed by the same node
>>> that employed the other address.
>>>
>>> My take here is, again: be proactive. If there's no requirement (and
>>> there isn't) for the two IIDs to be the same, then make them different,
>>> and fail on the safe side.
>>
>>
>> But Ole's point was that any observer who sees a LL packet is on-link an=
d
>> can therefore see the MAC address anyway;
>
>
> Links which share same non-MAC IID for LL and GUA are necessarily ppp
links (this sharing does not happen on wifi links for example).
>
> On these ppp links there are no MAC addresses and no MAC headers, so the
observer can't see them.
>
>
>> an observer who can see MAC addresses
>> can just laugh at RFC 7217 or RFC 4941.
>
>
> There are observers and observers.  We need to protected against unlawful
observers.  In ppp links the lawful observers (lawful interception) have
access to the IIDs.  The unlawful observers dont.
>

So I don't think there are any technical constraints preventing running PPP
over PPPoE over Wi-Fi or some other wireless link prone to offlink
capturing. (e.g. an ISP might backhaul traffic via a wireless link, and use
PPPoE over it to distinguish users, rather than put a NAS/BRAS/BNG at the
remote site (perhaps a mine site, providing after hours Internet access to
onsite workers.)

IOW, PPP framing doesn't ensure the underlying link is a physical one with
only two ends.

> The lawful observers dont need to make correlations because they have
them.
>
> Alex
>
>
>>
>>     Brian
>>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

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

<p dir=3D"ltr"><br>
On 8 Feb 2016 7:46 PM, &quot;Alexandre Petrescu&quot; &lt;<a href=3D"mailto=
:alexandre.petrescu@gmail.com">alexandre.petrescu@gmail.com</a>&gt; wrote:<=
br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Le 05/02/2016 21:01, Brian E Carpenter a =C3=A9crit :<br>
&gt;&gt;<br>
&gt;&gt; On 06/02/2016 07:20, Fernando Gont wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; On 02/05/2016 03:07 PM, <a href=3D"mailto:otroan@employees.org=
">otroan@employees.org</a> wrote:<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Fernando,<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; [...]<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;&gt; What is the risk of using the same IID for link-lo=
cal and global addresses?<br>
&gt;&gt;&gt;&gt;&gt;&gt; Typically if you can snoop the link-local address =
then you&#39;re onlink and leak information about all addresses and their c=
orrelations anyway.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; We discussed this one a hundred times now (including f=
or RFC7217). The<br>
&gt;&gt;&gt;&gt;&gt; risk is that at times such addressess can leak, withou=
t the need of the<br>
&gt;&gt;&gt;&gt;&gt; attacker being pesent on the local link.<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; e.g., your MTA is on the local-link, and you end up co=
nnecting to it<br>
&gt;&gt;&gt;&gt;&gt; with a LL, which then appears in the email headers. (a=
nd there are a<br>
&gt;&gt;&gt;&gt;&gt; bunch of other possible reasons for that to happen).<b=
r>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; Be proactive. MAC addresses in the IID are wrong. Putt=
ing them there is<br>
&gt;&gt;&gt;&gt;&gt; just waiting for trouble.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; I didn&#39;t say the LL was based on a MAC.<br>
&gt;&gt;&gt;&gt; my question was if there was any issue with re-using the I=
ID from the link-local in the GUA. assume the link-local is generated f.ex =
with 7217.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Oops, my apologies. My answer would be &quot;It unnecessarily =
enables<br>
&gt;&gt;&gt; correlation of the activities that you carry between the two a=
ddresses&quot;.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; i.e., by simply inspecting the IID I could easily tell that th=
e<br>
&gt;&gt;&gt; activities carried out with one address were performed by the =
same node<br>
&gt;&gt;&gt; that employed the other address.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; My take here is, again: be proactive. If there&#39;s no requir=
ement (and<br>
&gt;&gt;&gt; there isn&#39;t) for the two IIDs to be the same, then make th=
em different,<br>
&gt;&gt;&gt; and fail on the safe side.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; But Ole&#39;s point was that any observer who sees a LL packet is =
on-link and<br>
&gt;&gt; can therefore see the MAC address anyway;<br>
&gt;<br>
&gt;<br>
&gt; Links which share same non-MAC IID for LL and GUA are necessarily ppp =
links (this sharing does not happen on wifi links for example).<br>
&gt;<br>
&gt; On these ppp links there are no MAC addresses and no MAC headers, so t=
he observer can&#39;t see them.<br>
&gt;<br>
&gt;<br>
&gt;&gt; an observer who can see MAC addresses<br>
&gt;&gt; can just laugh at RFC 7217 or RFC 4941.<br>
&gt;<br>
&gt;<br>
&gt; There are observers and observers.=C2=A0 We need to protected against =
unlawful observers.=C2=A0 In ppp links the lawful observers (lawful interce=
ption) have access to the IIDs.=C2=A0 The unlawful observers dont.<br>
&gt;</p>
<p dir=3D"ltr">So I don&#39;t think there are any technical constraints pre=
venting running PPP over PPPoE over Wi-Fi or some other wireless link prone=
 to offlink capturing. (e.g. an ISP might backhaul traffic via a wireless l=
ink, and use PPPoE over it to distinguish users, rather than put a NAS/BRAS=
/BNG at the remote site (perhaps a mine site, providing after hours Interne=
t access to onsite workers.)</p>
<p dir=3D"ltr">IOW, PPP framing doesn&#39;t ensure the underlying link is a=
 physical one with only two ends. <br></p>
<p dir=3D"ltr">&gt; The lawful observers dont need to make correlations bec=
ause they have them.<br>
&gt;<br>
&gt; Alex<br>
&gt;<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; =C2=A0 =C2=A0 Brian<br>
&gt;&gt;<br>
&gt;<br>
&gt; --------------------------------------------------------------------<b=
r>
&gt; IETF IPv6 working group mailing list<br>
&gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
&gt; Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listi=
nfo/ipv6">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
&gt; --------------------------------------------------------------------<b=
r>
</p>

--001a11429ce41d7ca4052b3e6555--


From nobody Mon Feb  8 01:56:52 2016
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF5541ACE4D for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 01:56:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.622
X-Spam-Level: 
X-Spam-Status: No, score=-0.622 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_12=0.6, RP_MATCHES_RCVD=-0.001, 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 zFeNdF28QCh4 for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 01:56:49 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B45DE1ACE03 for <ipv6@ietf.org>; Mon,  8 Feb 2016 01:56:48 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u189udCv000982; Mon, 8 Feb 2016 09:56:39 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u189udCv000982
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1454925399; bh=nn0xjxGsKwaZgdBnfdaU7LoPZ6E=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=QM4/KhKCkzCt2rjr7czWP4Gh2SLXGEzFT9Mn0sgbgtWDIu8GPQ7Uah7RvTNbqukgI ZL0eL73DsIOES3Vn012X6yIrsyYQ3wDg/fbahCMpwgP3+cReFQsshiNozl+4E1inxf aXPyPeMoI5/41FzCZLTJWQ7Z0KZLMfCpBs97yxzs=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s179uc3185902681dN ret-id none; Mon, 08 Feb 2016 09:56:39 +0000
Received: from [192.168.0.10] (tchowndsl.claranet.co.uk [212.188.254.49]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u189uVUg018883 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Feb 2016 09:56:31 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <56B7915D.2060300@gmail.com>
Date: Mon, 8 Feb 2016 09:56:31 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|84deaef4b4572380170c25cc18973ac9s179uc03tjc|ecs.soton.ac.uk|FC23908F-3570-4F76-8005-6880E77ECF89@ecs.soton.ac.uk>
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com> <56B4FF9D.10203@gmail.com> <5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <EMEW3|5048bb3e4f22902e3e9b18a621e7fd32s16H1H03tjc|ecs.soton.ac.uk|5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <56B7915D.2060300@gmail.com> <FC23908F-3570-4F76-8005-6880E77ECF89@ecs.soton.ac.uk>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3112)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s179uc318590268100; tid=s179uc3185902681dN; client=relay,ipv6; mail=; rcpt=; nrcpt=5:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u189udCv000982
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/NN_pvL931uAWoN_Ki-AyXgaOU_c>
Cc: Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 09:56:50 -0000

> On 7 Feb 2016, at 18:47, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> On 08/02/2016 05:59, Tim Chown wrote:
>> On 5 Feb 2016, at 20:01, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>>>=20
>>> On 06/02/2016 07:20, Fernando Gont wrote:
>>>> On 02/05/2016 03:07 PM, otroan@employees.org wrote:
>>>>> Fernando,
>>>>>=20
>>>>> [...]
>>>>>=20
>>>>>>>=20
>>>>>>> What is the risk of using the same IID for link-local and global =
addresses?
>>>>>>> Typically if you can snoop the link-local address then you're =
onlink and leak information about all addresses and their correlations =
anyway.
>>>>>>=20
>>>>>> We discussed this one a hundred times now (including for =
RFC7217). The
>>>>>> risk is that at times such addressess can leak, without the need =
of the
>>>>>> attacker being pesent on the local link.
>>>>>>=20
>>>>>> e.g., your MTA is on the local-link, and you end up connecting to =
it
>>>>>> with a LL, which then appears in the email headers. (and there =
are a
>>>>>> bunch of other possible reasons for that to happen).
>>>>>>=20
>>>>>> Be proactive. MAC addresses in the IID are wrong. Putting them =
there is
>>>>>> just waiting for trouble.
>>>>>=20
>>>>> I didn't say the LL was based on a MAC.
>>>>> my question was if there was any issue with re-using the IID from =
the link-local in the GUA. assume the link-local is generated f.ex with =
7217.
>>>>=20
>>>> Oops, my apologies. My answer would be "It unnecessarily enables
>>>> correlation of the activities that you carry between the two =
addresses".
>>>>=20
>>>> i.e., by simply inspecting the IID I could easily tell that the
>>>> activities carried out with one address were performed by the same =
node
>>>> that employed the other address.
>>>>=20
>>>> My take here is, again: be proactive. If there's no requirement =
(and
>>>> there isn't) for the two IIDs to be the same, then make them =
different,
>>>> and fail on the safe side.
>>>=20
>>> But Ole's point was that any observer who sees a LL packet is =
on-link and
>>> can therefore see the MAC address anyway; an observer who can see =
MAC addresses
>>> can just laugh at RFC 7217 or RFC 4941.
>>=20
>> Well, except that the device might be varying its MAC address as =
well.
>>=20
>> I thought RFC7217 states that a device is expected to have a =
different IID for=20
>> each prefix on an interface. (Though whether there=E2=80=99s a =
NetworkID available to
>> seed a different LL IID per visited network is another question, else =
the device
>> presumably has the same LL IID as it moves?)
>>=20
>> There=E2=80=99s definitely value in avoiding correlation. If =
there=E2=80=99s an equal cost either=20
>> way, why allow such potential?
>=20
> Extra code? But my real concern is that there might be unintended side =
effects,
> because the interface identifier will no longer identify an interface.

Fair enough, and there are some notes on this in RFC 4914 with a section=20=

on the possible implications of varying IIDs.=20

But RFC 7217, and draft-ietf-6man-default-iids-09 say different. Perhaps=20=

you should look at capturing these concerns in that draft, so such side =
effects
are noted.

One premise within that draft is:
=E2=80=9Cgiven two addresses, it must be difficult for an outside entity
 to tell whether the addresses have been generated by the same host."
which further reinforces the different IIDs for GUAs (multiple, if the =
device
is multihomed) and LLs.

Tim


From nobody Mon Feb  8 08:05:48 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FA651B2DCF for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 08:05:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 mYeNHGnS4PAk for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 08:05:46 -0800 (PST)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) (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 DA3FE1B2DD2 for <ipv6@ietf.org>; Mon,  8 Feb 2016 08:05:45 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u18G5gGZ007035; Mon, 8 Feb 2016 10:05:42 -0600
Received: from XCH-BLV-304.nw.nos.boeing.com (xch-blv-304.nw.nos.boeing.com [130.247.25.216]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u18G5cYh006993 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 8 Feb 2016 10:05:38 -0600
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-BLV-304.nw.nos.boeing.com ([169.254.4.162]) with mapi id 14.03.0235.001; Mon, 8 Feb 2016 08:05:39 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Mark Smith <markzzzsmith@gmail.com>, Mark Andrews <marka@isc.org>
Subject: RE: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
Thread-Topic: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
Thread-Index: AdFgPnAxn72vBLTpQqid+VAMpL4ryQARzbYAAA+V7eD//1GY7P/7xlMg
Date: Mon, 8 Feb 2016 16:05:38 +0000
Message-ID: <2134F8430051B64F815C691A62D9831833962C14@XCH-BLV-105.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com> <56B4E91C.6090905@si6networks.com> <2134F8430051B64F815C691A62D983183395F14A@XCH-BLV-105.nw.nos.boeing.com> <56B502FB.4050302@si6networks.com> <20160205230616.CA7A1419BA10@rock.dv.isc.org> <CAO42Z2xt+ykaoxHcL=tf5zmpBUA6pUz2hDMF3=s+hCvFrq+ojQ@mail.gmail.com>
In-Reply-To: <CAO42Z2xt+ykaoxHcL=tf5zmpBUA6pUz2hDMF3=s+hCvFrq+ojQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/iK_h_Cm8uOj3eI-5nD22DCOY-iY>
Cc: Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 16:05:47 -0000

Hi Mark,

> Fred has also started writing up a draft to shift fragmentation into
> the GRE layer:
>=20
> "GRE Tunnel Fragmentation"
> https://tools.ietf.org/html/draft-templin-intarea-grefrag-02

Yes, also "Fragmentation Option for Generic UDP Encapsulation":

https://datatracker.ietf.org/doc/draft-herbert-gue-fragmentation/

Both are essentially the same concept - hike the fragmentation header
up to the encapsulation layer instead of the IP layer. The idea originally
came from RFC2764.

Thanks - Fred
fred.l.templin@boeing.com



From nobody Mon Feb  8 08:31:11 2016
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AEB01B2EAB for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 08:31:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 Zz8Mv5xOQeVB for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 08:31:07 -0800 (PST)
Received: from stl-mbsout-01.boeing.com (stl-mbsout-01.boeing.com [130.76.96.169]) (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 BB3C01B2EA0 for <ipv6@ietf.org>; Mon,  8 Feb 2016 08:31:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u18GV44e016994; Mon, 8 Feb 2016 10:31:05 -0600
Received: from XCH-BLV-204.nw.nos.boeing.com (xch-blv-204.nw.nos.boeing.com [10.57.37.58]) by stl-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u18GUwj5016839 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 8 Feb 2016 10:30:58 -0600
Received: from XCH-BLV-105.nw.nos.boeing.com ([169.254.5.221]) by XCH-BLV-204.nw.nos.boeing.com ([169.254.4.253]) with mapi id 14.03.0235.001; Mon, 8 Feb 2016 08:30:59 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Fred Baker (fred)" <fred@cisco.com>, Bob Hinden <bob.hinden@gmail.com>
Subject: RE: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
Thread-Topic: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
Thread-Index: AdFgPnAxn72vBLTpQqid+VAMpL4ryQCTYyqg
Date: Mon, 8 Feb 2016 16:30:58 +0000
Message-ID: <2134F8430051B64F815C691A62D9831833962CAB@XCH-BLV-105.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com> <93A717B5-CDAD-4273-B3A3-8A48C984109D@gmail.com> <DD26D90F-0B66-4C53-B306-971E8539F1E8@cisco.com>
In-Reply-To: <DD26D90F-0B66-4C53-B306-971E8539F1E8@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/W_0LrXfUbtRGSf1hhVakndIXD-Y>
Cc: IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 16:31:09 -0000

SGkgRnJlZCwNCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBGcmVkIEJh
a2VyIChmcmVkKSBbbWFpbHRvOmZyZWRAY2lzY28uY29tXQ0KPiBTZW50OiBGcmlkYXksIEZlYnJ1
YXJ5IDA1LCAyMDE2IDEyOjAwIFBNDQo+IFRvOiBCb2IgSGluZGVuDQo+IENjOiBUZW1wbGluLCBG
cmVkIEw7IE9sZSBUcsO4YW47IElQdjYgTGlzdA0KPiBTdWJqZWN0OiBSZTogVXNlIGNhc2VzIGZv
ciBQTVRVRCBhbmQgUExQTVRVRCAod2FzOiBSRTogNk1BTjogQWRvcHRpb24gY2FsbCBvbiBkcmFm
dC1oaW5kZW4tNm1hbi1yZmMxOTgxYmlzLTAxKQ0KPiANCj4gDQo+ID4gT24gRmViIDUsIDIwMTYs
IGF0IDExOjA0IEFNLCBCb2IgSGluZGVuIDxib2IuaGluZGVuQGdtYWlsLmNvbT4gd3JvdGU6DQo+
ID4NCj4gPiBJbnN0ZWFkIGNvbnRpbnVpbmcgdGhlIGRlYmF0ZSBvdmVyIGhvdyBSRkM0ODIxIHNo
b3VsZCBiZSBjaXRlZCBpbiByZmMxOTgxYmlzLCBJIGFtIHN0YXJ0aW5nIHRvIHRoaW5rIHRoYXQg
YSBzZXBhcmF0ZSBuZXcgZG9jdW1lbnQNCj4gY291bGQgZGlzY3VzcyB0aGUgcmVsYXRpb25zaGlw
IGJldHdlZW4gdGhlIHR3byBhcHByb2FjaGVzIHRvIGxlYXJuaW5nIHRoZSBNVFUsIGFuZCBtYWtl
IHNvbWUgcmVjb21tZW5kYXRpb25zIG9uIGhvdyB0aGV5DQo+IHNob3VsZCBiZSB1c2VkIHRvZ2V0
aGVyIG9yIHNlcGFyYXRlbHkuICBQZXJoYXBzIGEgQkNQIG9yIHVwZGF0ZSB0byBOb2RlIFJlcXVp
cmVtZW50cy4NCj4gPg0KPiA+IEkgZG9u4oCZdCB0aGluayB0aGlzIHRvcGljIG5lZWRzIHRvIGJl
IHBhcnQgb2YgYWR2YW5jaW5nIFJGQzE5ODEuDQo+IA0KPiBUaGF0IHRob3VnaHQgaGFzIGNyb3Nz
ZWQgbXkgbWluZCBhcyB3ZWxsLiBJdCBpcyB1bnVzdWFsIHRvIGhhdmUgYSBzcGVjaWZpY2F0aW9u
IGRlc2NyaWJpbmcgb25lIGFwcHJvYWNoIGNvbW1lbnQgb24gYSBkaWZmZXJlbnQNCj4gc3BlY2lm
aWNhdGlvbiBhYm91dCBhIGRpZmZlcmVudCBhcHByb2FjaC4NCj4NCj4gSWYgd2Ugd2VyZSB0byB3
cml0ZSBzdWNoIGEgc3BlY2lmaWNhdGlvbiwgd2hhdCB3b3VsZCBpdCBuZWVkIHRvIHNheT8NCj4g
DQo+IEkgdGhpbmsgdGhlIGZvbGxvd2luZyB3b3VsZCBuZWVkIHRvIGJlIHByZXNlbnQ6DQo+IA0K
PiAxKSBwb2ludGVycyB0byBSRkNzIDE5ODFiaXMgYW5kIDQ4MjENCj4gMikgcmVwb3J0cyBvZiBl
eHBlcmllbmNlIChub3QganVzdCBjb25jZXJuKSB3aXRoIGVhY2gNCj4gMmEpIGVudmlyb25tZW50
cyBpbiB3aGljaCBlYWNoIHdvcmtzIHdlbGwNCj4gMmIpIGRlbW9uc3RyYXRlZCBpc3N1ZXMgd2l0
aCBlYWNoDQo+IDMpIHJlY29tbWVuZGF0aW9ucyBhYm91dCBkZXBsb3ltZW50DQo+IA0KPiAyYSBm
b3IgUkZDIDE5ODFiaXMsIHdvdWxkIGxpa2VseSBzYXkgdGhhdCBpZiBJQ01QIFBUQiBpcyBub3Qg
YmVpbmcgYmxvY2tlZCBhbmQgYSBob3N0IGlzIHNlbmRpbmcgVENQIHNlZ21lbnRzIHRoYXQgYXJl
IHRvbyBsYXJnZSwgaXQNCj4gcXVpY2tseSBrbm9ja3MgdGhlbSB0byBhIHdvcmthYmxlIHNpemUu
IDJiIGZvciBSRkMgMTk4MWJpcyB3b3VsZCBsaWtlbHkgc2F5IHRoYXQgaWYgSUNNUCBQVEIgaXMg
YmVpbmcgYmxvY2tlZCBvciBzcG9vZmVkLCBpdCBkb2Vzbid0DQo+IGJlaGF2ZSB3ZWxsLg0KPiAN
Cj4gMmEgZm9yIFJGQyA0ODIxIHNob3VsZCBsaWtlbHkgc2F5IHRoYXQgaXQgYWNoaWV2ZXMgYSBy
ZWFzb25hYmxlIE1TUy4gMmIgbWlnaHQgb2JzZXJ2ZSB0aGF0IGl0IGlzIG5vdCBndWFyYW50ZWVk
IHRvIGRvIHNvIHF1aWNrbHkuDQoNCkFub3RoZXIgcG9pbnQgdGhhdCBuZWVkcyB0byBiZSBjb25z
aWRlcmVkIGlzIGludGVyYWN0aW9ucyB3aXRoIG11bHRpcGF0aC4gV2l0aA0KUkZDMTk4MShiaXMp
LCB0aGUgcGF0aCBNVFUgd2lsbCBldmVudHVhbGx5IGNvbnZlcmdlIHRvIHRoZSBtaW5pbXVtIE1U
VSBvZg0KYWxsIHBhdGhzIHRoYXQgY29udHJpYnV0ZSB0byB0aGUgbXVsdGlwYXRoLiBCdXQsIHdp
dGggUkZDNDgyMSwgZWFjaCBwYXRoIGluIHRoZQ0KbXVsdGlwYXRoIHdvdWxkIG5lZWQgdG8gYmUg
dGVzdGVkIGluZGVwZW5kZW50bHksIGkuZS4sIHBlci1mbG93IGFuZCBub3QganVzdA0KcGVyLWRl
c3RpbmF0aW9uIHBhdGggTVRVIHByb2JpbmcuDQoNCkltcGxlbWVudGF0aW9ucyBtaWdodCBhcHBy
b2FjaCB0aGlzIGJ5IHN0YXJ0aW5nIHRoZSBSRkM0ODIxIHBhdGggTVRVDQpwcm9iaW5nIHByb2Nl
c3MgZnJvbSBzY3JhdGNoIGZvciBldmVyeSBuZXcgVENQIGNvbm5lY3Rpb24gYW5kIG5vdCBjYWNo
ZQ0KdGhlIE1UVSBkaXNjb3ZlcmVkIGJ5IHByZXZpb3VzIGNvbm5lY3Rpb25zLiBJdCB3b3VsZCB3
b3JrLCBidXQgY291bGQNCnJlc3VsdCBpbiBsb3RzIG9mIHByb2JpbmcuDQoNClRoYW5rcyAtIEZy
ZWQNCmZyZWQubC50ZW1wbGluQGJvZWluZy5jb20NCg0KPiBBcyBhIHJlY29tbWVuZGF0aW9uLCBp
dCBzZWVtcyBsaWtlIFRDUCBzaG91bGQgZm9sbG93IHNvbWUga2luZCBvZiBydWxlLiBUaGVyZSBp
cyBhbiBhcmd1bWVudCBmb3Igc2VuZGluZyBzZWdtZW50cyBpbiB0aGUgaW5pdGlhbCBidXJzdA0K
PiBvZiBJVyBkaWZmZXJlbnQgc2l6ZXMgKGluY2x1ZGluZyBhdCBsZWFzdCBvbmUgZGVyaXZlZCBm
cm9tIGEgMTI4MCBieXRlIE1UVSwgb25lIGZyb20gYSAxNTAwIGJ5dGUgTVRVLCBhbmQgb25lIGZy
b20gYSA5MDAwIGJ5dGUgTVRVLA0KPiBlYWNoIGxlc3MgdGhlIHNpemVzIG9mIGFueSBrbm93biBo
ZWFkZXJzKSBhbmQgZWl0aGVyIHNlZWRpbmcgdGhlIDQ4MjEgYWxnb3JpdGhtIHdpdGggdGhlIGFj
ay9zYWNrIHJlc3BvbnNlIGluZm9ybWF0aW9uLCB1c2luZyB0aGUNCj4gbnVtYmVyIGZvdW5kIGlu
IGEgcmVzcG9uZGluZyBJQ01QIFBUQiwgb3IsIGluIHRoZSBhYnNlbmNlIG9mIGFuIElDTVAgUFRC
LCBzZWxlY3RpbmcgdGhlIGxhcmdlc3Qgb2YgdGhvc2Ugc2l6ZXMgdGhhdCB3YXMgYWNrZWQgb3IN
Cj4gc2Fja2VkLiBJJ2xsIGJldCBNYXR0IE1hdGhpcyBvciBvbmUgb2YgaGlzIGNvbXBhZHJlcyB3
b3VsZCBoYXZlIGEgYmV0dGVyIGFwcHJvYWNoLg0KPiANCj4gV2Ugd291bGQgYWxzbyB3YW50IHRv
IGhhdmUgYW4gaW1wbGVtZW50YXRpb24gcmVwb3J0IG9uIHRoZSByZWNvbW1lbmRhdGlvbnMgKGF0
IGxlYXN0IG9uZSwgaWRlYWxseSBvbmUgdXNlZCBpbiBlYWNoIG9mIHNldmVyYWwNCj4gb3BlcmF0
aW9uYWwgZW52aXJvbm1lbnRzIGluY2x1ZGluZyB2aXJ0dWFsaXplZCBkYXRhIGNlbnRlciwgbW9i
aWxlIHdpcmVsZXNzLCB3aWZpLCBicm9hZGJhbmQsIGFuZCBiYWNrYm9uZSkuDQo+IA0KDQo=


From nobody Mon Feb  8 10:21:13 2016
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 015FA1B30DA for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 10:21:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.398
X-Spam-Level: 
X-Spam-Status: No, score=0.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_HERE=2.3, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-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 7zz4WYtAbdQq for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 10:21:10 -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 779E91B30DB for <ipv6@ietf.org>; Mon,  8 Feb 2016 10:21:10 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 6F3B42009E; Mon,  8 Feb 2016 13:21:19 -0500 (EST)
Received: from obiwan.sandelman.ca (ip6-localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D7A1163751; Mon,  8 Feb 2016 13:21:08 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Mark Andrews <marka@isc.org>
Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
In-Reply-To: <20160208004818.A351E41AF670@rock.dv.isc.org>
References: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com> <56B4E91C.6090905@si6networks.com> <2134F8430051B64F815C691A62D983183395F14A@XCH-BLV-105.nw.nos.boeing.com> <56B502FB.4050302@si6networks.com> <20160205230616.CA7A1419BA10@rock.dv.isc.org> <15275.1454861964@obiwan.sandelman.ca> <20160208004818.A351E41AF670@rock.dv.isc.org>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Mon, 08 Feb 2016 13:21:08 -0500
Message-ID: <32587.1454955668@obiwan.sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Ekk4iRTCSVq1xzFKAObnWahIN1k>
Cc: Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 18:21:12 -0000

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


Mark Andrews <marka@isc.org> wrote:
    >> I didn't think PLPMTUD worked any better in this situation, or are I
    >> wrong he re?

    > Conceptually you do PLPMTUD by adjusting the EDNS UDP size advertised
    > in the query until you get a response.  This isn't strict PMTUD as it
    > also accounts for firewalls that are blocking fragments, firewalls that
    > still think DNS is limited to 512 byte UDP payloads.  Unfortunately you
    > only have about 3 seconds to do this all in as well as talking to other
    > servers.  The DNS doesn't have a way of signaling "fragment at this
    > size".

I'd forgotten about doing it this way.
I now recall you explaining it many times before :-)

It would seem that ICMP based PMTUD is useless for DNS too, and that we
should do away with 1981?

    > Named tracks successful answers/timeouts with different EDNS udp sizes
    > as well as the actual response sizes that have got through.

    > ; [edns success/4096 timeout/1432 timeout/1232 timeout/512 timeout]

    > Too many timeouts with a particlar size and we stop offering a EDNS UDP
    > buffer of that size and fallback to the next break point.  These values
    > are set for 4in6/6in4 + a UDP header.  timeouts with a smaller EDNS
    > buffer size also count against larger sizes.

    >> i.e: both are broken for UDP, and in the DNS/UDP case, the server
    >> never retransmits either... so absent using TCP, it will always just
    >> fail.

    > But the client re-queries leading to a re-transmission.

    >> --
    >> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
    >> -= IPv6 IoT consulting =-
    >>
    >>
    >>
    >>
    >> --=-=-= Content-Type: application/pgp-signature; name="signature.asc"
    >>
    >> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux)
    >>
    >> iQEVAwUBVrduiYCLcPvd0N1lAQJ7RQf/bInuCsHmVH6AONDSavt/Ut1/xo0NdnRp
    >> 1vtfg2LwHG5cUJGNpHOdnlg0OdhIJS9KVYN6xP0FQqbfTq4E6zRpoBkw4kMFQFWK
    >> cYOe8MaXx4FJFWF6MWcugglhWRkFQeSaQyYcn0Odhmeoc7w2/ehlsTfuFNGCnpH9
    >> 2bJS2Og80JWMDy7Q95IL6JrsKE1/VDDLpJJkQTfqPboZ1BG5Vn6IlDUT+lEMsZly
    >> By2CSNBglAqVtU5fUPYCa6yCx92I2g8MYePqkjclN1dAlELhlOUllsrJ8F3kCuFs
    >> 4eT9yAOtU4W7tP/Ka3bBdJTRYnS31NXozgdIlPsnhZ7mXdrks1tQcg== =kitT
    >> -----END PGP SIGNATURE----- --=-=-=--
    > --
    > Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia
    > PHONE: +61 2 9871 4742 INTERNET: marka@isc.org

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




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

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

iQEVAwUBVrjckYCLcPvd0N1lAQI/1wf/f42aJtsGxKjkEwNFSedh2jJCEs7H9hhW
onkwzKj+d+D9zhWwJyiqrZ2C/jLaxz+N6KowvCO8/+xNrbo0yDca5RLfcqWyEMkz
hb3zwQiDoBdoTFiZ/R+leTWclTx2h9lMzqyCB4cL69PNgmQBFy5NxwSdGE79AUiP
uQJhbfxxjkKXNkddgAj3z6q8UFuikZQSeYfrAUyoqF+6L/ZlqDIvHLZnw8w1YA5p
2krSML8S5XdA0YBcOuH3CAXvLG9tYQiLkRso3UG4OPqD9JgydSUJM/4ef+7cIOOq
LSl9YKXN2r2E9rcCCye0RL5LPyYo+deL1ZieYOAqaUuKgxW9e7Ozaw==
=Nax3
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Feb  8 10:52:48 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E2D71B317D; Mon,  8 Feb 2016 10:52: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 msHRbniylbEJ; Mon,  8 Feb 2016 10:52:45 -0800 (PST)
Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C696A1B3185; Mon,  8 Feb 2016 10:52:45 -0800 (PST)
Received: by mail-pf0-x22c.google.com with SMTP id q63so10063181pfb.0; Mon, 08 Feb 2016 10:52:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=fRnLb7TWEpJvlRphWh0z3lqgNdOev2GEl+KenKlF3PY=; b=NeBleKGd030h3r4vtjKbEn/ULx331y6hHM+HOF3xlyxG7sg184ZLLu3b5gkKS5qJAS IgNGrjtZj/HDymx0eZEnwc5x6c62g69ZQC1Nub2BP/X51peZmqGsjXxakdjpOSQ97IIQ ahxQM1ZSwuTdGn1ZT+9kzyOppi3sUGky6jhGBhC7AMbnTGH/FQ2Yv2VkCejDRrs9v1cj ZaM0wHYWyzNz+5P89xjBhir1A4ibpXG4oc1U8gkSxPvzWYoNKbDtkalO7rou/OXqqVRc GUTdgH/eh+dqraXfiyG4VLpUHqNeshGnOHoix8SLfVWwHv21YbvAi4nPsUjKhsVyYqTD 1Vtg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=fRnLb7TWEpJvlRphWh0z3lqgNdOev2GEl+KenKlF3PY=; b=Ez0Vvi0dKHg1BBA3aDeS2YL8Ji7JBap8PQRIG4lFRKdaCGJrT2XlSNWBBVkiJhm3B6 qujsTrphpHoLMdK3wWl3mBlKc3LzxaTMmqlTRhSqgwflq5/5Pn8TpolkTbDuUYMsHqa2 iCBh8NJoKgrFXW1UHRWum48mmPcfihhOdkl0BaSnoCzmoythvRSAbNwjebYJJ1AXEL39 3QbjpmAoUdHUWCNoms/+3arVfLyzda6p8XobjvA1qlf44vA2bcGkEgh2uQYCEGvPVz3I dSrCEj7rDKCYHtX2UA7cn1LnHakNSXWT1OMGPAJa6QPoD5PFytM3Xah6EVnwTaVFwk/9 kvmQ==
X-Gm-Message-State: AG10YORGLoaNhfMTH3STuiQiE3WhCVSP5RUq/g6wyjzsA28FtZeDMznksOSqWyJ0t40fwQ==
X-Received: by 10.98.1.203 with SMTP id 194mr45055492pfb.10.1454957565436; Mon, 08 Feb 2016 10:52:45 -0800 (PST)
Received: from ?IPv6:2406:e007:67f3:1:28cc:dc4c:9703:6781? ([2406:e007:67f3:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id q8sm1604762pfa.70.2016.02.08.10.52.41 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 08 Feb 2016 10:52:44 -0800 (PST)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
To: Tore Anderson <tore@fud.no>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <20160206134831.0ef1c371@envy> <56B79D01.6050307@gmail.com> <20160208071846.180b4b23@echo.ms.redpill-linpro.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56B8E3FA.5060109@gmail.com>
Date: Tue, 9 Feb 2016 07:52:42 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <20160208071846.180b4b23@echo.ms.redpill-linpro.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/q8y3n6uVJQOKXxYvmJ4eKmNhioo>
Cc: bob.hinden@gmail.com, 6man WG <ipv6@ietf.org>, draft-bao-v6ops-rfc6145bis@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 18:52:47 -0000

OK, got it, except for a backwards compatibility issue with some 6145-not-bis boxes.
But we can't expect translation to be perfect anyway.

Thanks
   Brian

On 08/02/2016 19:18, Tore Anderson wrote:
> Hello Brian,
> 
> * Brian E Carpenter <brian.e.carpenter@gmail.com>
> 
>> On 07/02/2016 01:48, Tore Anderson wrote:
>>> I see one issue that I would like to remind the WG about:
>>>
>>>    A node MUST NOT reduce its estimate of the Path MTU below the IPv6
>>>    minimum link MTU.
>>>
>>> -     Note: A node may receive a Packet Too Big message reporting a
>>> -     next-hop MTU that is less than the IPv6 minimum link MTU.  In that
>>> -     case, the node is not required to reduce the size of subsequent
>>> -     packets sent on the path to less than the IPv6 minimun link MTU,
>>> -     but rather must include a Fragment header in those packets
>>> -     [I-D.ietf-6man-rfc2460bis].
>>>
>>> The lines prefixed with "-" have been removed in -01.   
>>
>> Isn't this the same change that has been made to 2460bis anyway?
> 
> Similar text was removed from 2460bis, that is true.
> 
> That said, 2460bis contains no prohibition against a node reducing its
> PMTU below 1280; this restriction only found in 1981(bis) immediately
> preceding the deleted paragraph.
> 
> 2460bis does not really say anything about how PMTUD should be
> implemented (it just refers to 1981), so I think it makes sense to
> contain this information in 1981bis.
> 
>>>       01)  Removed paragraph in Section 5 that required including a
>>>            fragment header to outgoing packets if a ICMP Packet Too Big
>>>            message reporting a Next-Hop MTU less than 1280.  This is
>>>            based on the update in draft-ietf-6man-deprecate-atomfrag-
>>>            generation-03.  
>>
>> It seems to me that RFC 6145 and draft-bao-v6ops-rfc6145bis (SIIT) still
>> rely on this behaviour, whatever
>> draft-ietf-6man-deprecate-atomfrag-generation says. Or I am confused.
> 
> A translator conforming to 6145bis will never emit translated ICMPv6 PTBs
> indicating a PMTU < 1280. From section 4.2:
> 
>                The MTU field MUST be adjusted for the difference
>                between the IPv4 and IPv6 header sizes, but MUST NOT be
>                set to a value smaller than the minimum IPv6 MTU (1280
>                bytes).
> 
> To the best of my knowledge, an ICMPv6 PTB with MTU<1280 can only
> legitimately occur in the wild as a result from translation from an
> IPv4 FN by a 6145-not-bis translator implementing the "first approach"
> in section 6. (The "second approach" is basically the same as what
> 6145bis mandates, for what it's worth.)
> 
> Actually, this made me realise that my option a) is probably the best
> choice, i.e., that an IPv6 node receiving an PTB with MTU<1280 should
> interpret it as if it had MTU=1280. Doing so would increase the
> likelihood of successful communication in the case where the IPv4->IPv6
> translator conforms to 6145-1st-approach while the IPv6->IPv4
> translator conforms to 6145bis (or 6145-2nd-approach) one.
> 
> Tore
> 


From nobody Mon Feb  8 15:33:18 2016
Return-Path: <marka@isc.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83B781B3D5A for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 15:33:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.398
X-Spam-Level: 
X-Spam-Status: No, score=0.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_HERE=2.3, RP_MATCHES_RCVD=-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 oLC497GtfiRJ for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 15:33:15 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03FA01B2CFC for <ipv6@ietf.org>; Mon,  8 Feb 2016 15:33:15 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx.ams1.isc.org (Postfix) with ESMTPS id B21A91FCAE1; Mon,  8 Feb 2016 23:33:11 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 9B157160041; Mon,  8 Feb 2016 23:33:10 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 887C21600A2; Mon,  8 Feb 2016 23:33:10 +0000 (UTC)
Received: from zmx1.isc.org ([127.0.0.1]) by localhost (zmx1.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Nbp7kwgMr1Hq; Mon,  8 Feb 2016 23:33:10 +0000 (UTC)
Received: from rock.dv.isc.org (c110-21-49-25.carlnfd1.nsw.optusnet.com.au [110.21.49.25]) by zmx1.isc.org (Postfix) with ESMTPSA id 1AF34160041; Mon,  8 Feb 2016 23:33:10 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id D0EF941B734E; Tue,  9 Feb 2016 10:33:07 +1100 (EST)
To: Michael Richardson <mcr+ietf@sandelman.ca>
From: Mark Andrews <marka@isc.org>
References: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com> <56B4E91C.6090905@si6networks.com> <2134F8430051B64F815C691A62D983183395F14A@XCH-BLV-105.nw.nos.boeing.com> <56B502FB.4050302@si6networks.com> <20160205230616.CA7A1419BA10@rock.dv.isc.org> <15275.1454861964@obiwan.sandelman.ca> <20160208004818.A351E41AF670@rock.dv.isc.org> <32587.1454955668@obiwan.sandelman.ca>
Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
In-reply-to: Your message of "Mon, 08 Feb 2016 13:21:08 -0500." <32587.1454955668@obiwan.sandelman.ca>
Date: Tue, 09 Feb 2016 10:33:07 +1100
Message-Id: <20160208233307.D0EF941B734E@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/wq13-szoRHiC4NSNbHh4ITwxwZw>
Cc: Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>, "Fred Baker \(fred\)" <fred@cisco.com>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 23:33:16 -0000

In message <32587.1454955668@obiwan.sandelman.ca>, Michael Richardson writes:
> --=-=-=
> Content-Type: text/plain
> 
> 
> Mark Andrews <marka@isc.org> wrote:
>     >> I didn't think PLPMTUD worked any better in this situation, or are I
>     >> wrong he re?
> 
>     > Conceptually you do PLPMTUD by adjusting the EDNS UDP size advertised
>     > in the query until you get a response.  This isn't strict PMTUD as it
>     > also accounts for firewalls that are blocking fragments, firewalls that
>     > still think DNS is limited to 512 byte UDP payloads.  Unfortunately you
>     > only have about 3 seconds to do this all in as well as talking to other
>     > servers.  The DNS doesn't have a way of signaling "fragment at this
>     > size".
> 
> I'd forgotten about doing it this way.
> I now recall you explaining it many times before :-)
> 
> It would seem that ICMP based PMTUD is useless for DNS too, and that we
> should do away with 1981?

There is a difference between trying to avoid something and doing
away with something.  Named turns off PMTUD for the sockets it opens
because even with TCP there isn't the recovery time available to
deal with lost PTBs.

That said RFC 1981 works well when the PTB get through for TCP and
if most of the DNS/UDP traffic was fragmented it would work reasonable
well there too however DNS/UDP packets are variable sizes and you
have 1 in N packets being fragmented and the MTU knowledge times
out.  N is dropping and more sites sign their zones.

Firewall developers really don't know how to handle DNS.  They do
lots of really stupid things like dropping EDNS != 0 packets for
no sane reason, dropping EDNS requests with a EDNS option or EDNS
flag set.  EDNS specified safe default behaviours for all these
event but firewall developers seem to think they know better.

Ahhhh this EDNS flag bit is set, the world may end, lets drop the
packet and break the protocol instead of reading the protocol spec
and seeing that the default is for the server to ignore the bit.

Similarly dropping ICMP PTB and fragments.  The world will not end
if you let through a "bad" ICMP PTB or a IP fragment.

Mark

>     > Named tracks successful answers/timeouts with different EDNS udp sizes
>     > as well as the actual response sizes that have got through.
> 
>     > ; [edns success/4096 timeout/1432 timeout/1232 timeout/512 timeout]
> 
>     > Too many timeouts with a particlar size and we stop offering a EDNS UDP
>     > buffer of that size and fallback to the next break point.  These values
>     > are set for 4in6/6in4 + a UDP header.  timeouts with a smaller EDNS
>     > buffer size also count against larger sizes.
> 
>     >> i.e: both are broken for UDP, and in the DNS/UDP case, the server
>     >> never retransmits either... so absent using TCP, it will always just
>     >> fail.
> 
>     > But the client re-queries leading to a re-transmission.
> 
>     >> --
>     >> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>     >> -= IPv6 IoT consulting =-
>     >>
>     >>
>     >>
>     >>
>     >> --=-=-= Content-Type: application/pgp-signature; name="signature.asc"
>     >>
>     >> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux)
>     >>
>     >> iQEVAwUBVrduiYCLcPvd0N1lAQJ7RQf/bInuCsHmVH6AONDSavt/Ut1/xo0NdnRp
>     >> 1vtfg2LwHG5cUJGNpHOdnlg0OdhIJS9KVYN6xP0FQqbfTq4E6zRpoBkw4kMFQFWK
>     >> cYOe8MaXx4FJFWF6MWcugglhWRkFQeSaQyYcn0Odhmeoc7w2/ehlsTfuFNGCnpH9
>     >> 2bJS2Og80JWMDy7Q95IL6JrsKE1/VDDLpJJkQTfqPboZ1BG5Vn6IlDUT+lEMsZly
>     >> By2CSNBglAqVtU5fUPYCa6yCx92I2g8MYePqkjclN1dAlELhlOUllsrJ8F3kCuFs
>     >> 4eT9yAOtU4W7tP/Ka3bBdJTRYnS31NXozgdIlPsnhZ7mXdrks1tQcg== =kitT
>     >> -----END PGP SIGNATURE----- --=-=-=--
>     > --
>     > Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia
>     > PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
> 
> 
> 
> 
> --=-=-=
> Content-Type: application/pgp-signature; name="signature.asc"
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> 
> iQEVAwUBVrjckYCLcPvd0N1lAQI/1wf/f42aJtsGxKjkEwNFSedh2jJCEs7H9hhW
> onkwzKj+d+D9zhWwJyiqrZ2C/jLaxz+N6KowvCO8/+xNrbo0yDca5RLfcqWyEMkz
> hb3zwQiDoBdoTFiZ/R+leTWclTx2h9lMzqyCB4cL69PNgmQBFy5NxwSdGE79AUiP
> uQJhbfxxjkKXNkddgAj3z6q8UFuikZQSeYfrAUyoqF+6L/ZlqDIvHLZnw8w1YA5p
> 2krSML8S5XdA0YBcOuH3CAXvLG9tYQiLkRso3UG4OPqD9JgydSUJM/4ef+7cIOOq
> LSl9YKXN2r2E9rcCCye0RL5LPyYo+deL1ZieYOAqaUuKgxW9e7Ozaw==
> =Nax3
> -----END PGP SIGNATURE-----
> --=-=-=--
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Mon Feb  8 15:51:51 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5B181B3D9F for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 15:51:49 -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] 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 9xzLJNthgBhp for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 15:51:47 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 253371B3D9D for <ipv6@ietf.org>; Mon,  8 Feb 2016 15:51:45 -0800 (PST)
Received: from [192.168.1.66] (unknown [186.56.164.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 515A7206AA8; Tue,  9 Feb 2016 00:51:38 +0100 (CET)
Subject: Re: ICMP PTB spoofing attacks (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "Fred Baker (fred)" <fred@cisco.com>
References: <2134F8430051B64F815C691A62D983183395EF42@XCH-BLV-105.nw.nos.boeing.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <56B90D2B.4000204@si6networks.com>
Date: Mon, 8 Feb 2016 18:48:27 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <2134F8430051B64F815C691A62D983183395EF42@XCH-BLV-105.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/gS0lV60bIaiKzjVtkltTcNbF-Lk>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 23:51:49 -0000

On 02/05/2016 02:46 PM, Templin, Fred L wrote:
> 
>> As far as I know, RFC 4821 is a response to the latter issue.
> 
> RFC4821 is a response to both issues: 1) Loss of accurate ICMP PTBs, and
> 2) Receipt of inaccurate ICMP PTBs.

FWIW, RFC4821 is rather orthogonal to ICMP-based attacks, since, in
principle, it can be implemented along RFC1918 or in replacement of it.

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





From nobody Mon Feb  8 15:52:12 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 356851B3DAC for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 15:52:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.399
X-Spam-Level: 
X-Spam-Status: No, score=0.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_TOOL=2.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QjKzgXjOKBpz for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 15:52:10 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DFD21B3DB6 for <ipv6@ietf.org>; Mon,  8 Feb 2016 15:51:52 -0800 (PST)
Received: from [192.168.1.66] (unknown [186.56.164.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id D6456206B3F; Tue,  9 Feb 2016 00:51:48 +0100 (CET)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
To: Tore Anderson <tore@fud.no>, otroan@employees.org
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <20160206134831.0ef1c371@envy>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <56B9157F.3030302@si6networks.com>
Date: Mon, 8 Feb 2016 19:23:59 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <20160206134831.0ef1c371@envy>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/n6eepSaViGMpqXkKJWphldK0tJM>
Cc: 6man WG <ipv6@ietf.org>, bob.hinden@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 23:52:11 -0000

On 02/06/2016 09:48 AM, Tore Anderson wrote:
> * otroan@employees.org
> 
>> This message starts a two week 6MAN call on adopting:
>>
>> Name:	draft-hinden-6man-rfc1981bis-01
>> Title:	Path MTU Discovery for IP version 6
>> Document date:	2015-12-01
>> Pages:	16
>> URL:         https://datatracker.ietf.org/doc/draft-hinden-6man-rfc1981bis/
>> Htmlized:  https://tools.ietf.org/html/draft-hinden-6man-rfc1981bis-01
>> Diff:          https://tools.ietf.org/rfcdiff?url2=draft-hinden-6man-rfc1981bis-01.txt
>>
>> as a working group item. Substantive comments and statements of support
>> for adopting this document should be directed to the mailing
>> list. Editorial suggestions can be sent to the authors.
> 
> I support adoption.
> 
> I see one issue that I would like to remind the WG about:
> 
>    A node MUST NOT reduce its estimate of the Path MTU below the IPv6
>    minimum link MTU.
> 
> -     Note: A node may receive a Packet Too Big message reporting a
> -     next-hop MTU that is less than the IPv6 minimum link MTU.  In that
> -     case, the node is not required to reduce the size of subsequent
> -     packets sent on the path to less than the IPv6 minimun link MTU,
> -     but rather must include a Fragment header in those packets
> -     [I-D.ietf-6man-rfc2460bis].
> 
> The lines prefixed with "-" have been removed in -01. In my opinion,
> this leaves the text in an ambiguous state. What is a node conforming
> to -01 expected to do, when receiving a PTB reporting a next-hop MTU
> lower than 1280? I see two distinct options:
> 
> a) Reduce its PMTU estimate to exactly 1280.
> b) Ignore the "invalid" PTB (retaining its previous PMTU estimate).
> 
> I think it would be preferable to replace the removed paragraph with a
> clarification as to which behaviour is the correct and expected one. I
> do not know which one that would be, though.

I'd be in favor of going with the suggested option "a" above.

Thanks!

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





From nobody Mon Feb  8 15:52:35 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B5BC1B3DB8 for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 15:52:34 -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] 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 AGv088TDJSrK for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 15:52:30 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AC0F1B3D9F for <ipv6@ietf.org>; Mon,  8 Feb 2016 15:51:59 -0800 (PST)
Received: from [192.168.1.66] (unknown [186.56.164.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 9E058206AA8; Tue,  9 Feb 2016 00:51:55 +0100 (CET)
Subject: Re: Use cases for PMTUD and PLPMTUD (was: RE: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01)
To: Michael Richardson <mcr+ietf@sandelman.ca>, Fernando Gont <fernando@gont.com.ar>
References: <2134F8430051B64F815C691A62D983183395EFC6@XCH-BLV-105.nw.nos.boeing.com> <7592.1454699773@obiwan.sandelman.ca> <56B50394.2010504@gont.com.ar> <14373.1454861717@obiwan.sandelman.ca>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B916EF.5080200@si6networks.com>
Date: Mon, 8 Feb 2016 19:30:07 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <14373.1454861717@obiwan.sandelman.ca>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/WFqu3W9ZwsQsxS5H3P93Ig-pU7o>
Cc: 6man WG <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "Fred Baker \(fred\)" <fred@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Feb 2016 23:52:34 -0000

On 02/07/2016 01:15 PM, Michael Richardson wrote:
> 
> Fernando Gont <fernando@gont.com.ar> wrote:
>     >> Templin, Fred L <Fred.L.Templin@boeing.com> wrote: > On the other
>     >> hand, paths that lead to Internet destinations cannot be > counted on
>     >> to deliver the necessary ICMPs. In that case, RFC4821 > provides a
>     >> mitigation.
>     >>
>     >> > But, if we do not believe that there are paths for which traditional
>     >> > PMTUD can still be used safely, then we should be working to
>     >> deprecate > RFC1981 instead of making it a standard.
>     >>
>     >> I think that the mitigation is far more reliable than 1981.  So, I'd
>     >> rather deprecate RFC1981.
>     >>
>     >> {I noticed that 4821 is not on by default in most Linux
>     >> distros/kernels, and I actually want to know if there is some reason
>     >> for it}
> 
>     > Yes: convergence time.
> 
> Yes, I've noticed that it takes a few re-transmissions on the first
> connection to a site in the case where the MTU is limited and the ICMPs are
> lost, but when the MTU is unblocked, there is no delay.

If you employ RFC4821 as icmp-less PMTUD, it doesn't matter whether the
ICMPs get blocked or not. If you implement RFC4821 for blackhole
detection, then I agree with you.




> An implementation that wanted to avoid even the re-transmissions in the
> blocked case could limit themselves to 1280 sized packets and send some 1500
> byte probes have gotten through.
> 
> If 4821 is turned off, then the connection is mysteriously blocked, and
> always fail.
> 
> So, your answer does not make sense to me.

"My" answer is actually what I recall from discussing this with Linux
kernel developers 10 years ago -- I guess that they were referring to
"RFC4821 as icmp-less PMTUD".

That said, if the toggle in Linux is to use RFC4821 as icmp-less PMTUD,
then my (relayed) response would apply. OTOH, if the toggle is simply to
employ RFC4821 for blackhole detection then I'd agree with you.

FWIW, I'd expect RFC4821 fo blackhole detection to be "on by default",
and, if anything, to be able to turn on RFC4821 as icmp-less PMTUD (but
this one *not* "on by default", for the reasons already stated).

Thanks!

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





From nobody Mon Feb  8 19:07:48 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06D0B1A009B for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 19:07:47 -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] 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 W29PehoS7xDW for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 19:07:44 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B79221A008F for <ipv6@ietf.org>; Mon,  8 Feb 2016 19:07:44 -0800 (PST)
Received: from [192.168.1.66] (unknown [186.56.164.217]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 26DB5206B3D; Tue,  9 Feb 2016 04:07:39 +0100 (CET)
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Tim Chown <tjc@ecs.soton.ac.uk>
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com> <56B4FF9D.10203@gmail.com> <5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <EMEW3|5048bb3e4f22902e3e9b18a621e7fd32s16H1H03tjc|ecs.soton.ac.uk|5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <56B7915D.2060300@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B93CA0.7080000@si6networks.com>
Date: Mon, 8 Feb 2016 22:10:56 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B7915D.2060300@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/6cQEPfV7uZ-S0jUHMTcn3LWoIwk>
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 03:07:47 -0000

On 02/07/2016 03:47 PM, Brian E Carpenter wrote:
[....]
>>>
>>> But Ole's point was that any observer who sees a LL packet is on-link and
>>> can therefore see the MAC address anyway; an observer who can see MAC addresses
>>> can just laugh at RFC 7217 or RFC 4941.
>>
>> Well, except that the device might be varying its MAC address as well.
>>
>> I thought RFC7217 states that a device is expected to have a different IID for 
>> each prefix on an interface. (Though whether thereâ€™s a NetworkID available to
>> seed a different LL IID per visited network is another question, else the device
>> presumably has the same LL IID as it moves?)
>>
>> Thereâ€™s definitely value in avoiding correlation. If thereâ€™s an equal cost either 
>> way, why allow such potential?
> 
> Extra code? But my real concern is that there might be unintended side effects,
> because the interface identifier will no longer identify an interface.

Well, the IID only really identifies an interface for a given prefix.
For instance, DAD is done only for such given prefix.

And there is no requirement whatsoever that the IID for one prefix is
the same as that used for the same interface for a different autoconf
prefix.

Thanks!

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





From nobody Mon Feb  8 22:09:17 2016
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 401881A1AB9 for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 22:09:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jb-coWoNJpxL for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 22:09:14 -0800 (PST)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB6F91A1AB6 for <ipv6@ietf.org>; Mon,  8 Feb 2016 22:09:13 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u1969AjV007641; Tue, 9 Feb 2016 07:09:10 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5E920201354; Tue,  9 Feb 2016 07:17:25 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 4DF7A2012DF; Tue,  9 Feb 2016 07:17:25 +0100 (CET)
Received: from [132.166.84.22] ([132.166.84.22]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u196999A027252; Tue, 9 Feb 2016 07:09:09 +0100
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: Fernando Gont <fgont@si6networks.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Tim Chown <tjc@ecs.soton.ac.uk>
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com> <56B4FF9D.10203@gmail.com> <5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <EMEW3|5048bb3e4f22902e3e9b18a621e7fd32s16H1H03tjc|ecs.soton.ac.uk|5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <56B7915D.2060300@gmail.com> <56B93CA0.7080000@si6networks.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <56B98285.9030306@gmail.com>
Date: Tue, 9 Feb 2016 07:09:09 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B93CA0.7080000@si6networks.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Y-bF2HcsBUvbfKZmlbmgZiejoNQ>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 06:09:16 -0000

Le 09/02/2016 02:10, Fernando Gont a Ã©crit :
> On 02/07/2016 03:47 PM, Brian E Carpenter wrote:
> [....]
>>>>
>>>> But Ole's point was that any observer who sees a LL packet is on-link and
>>>> can therefore see the MAC address anyway; an observer who can see MAC addresses
>>>> can just laugh at RFC 7217 or RFC 4941.
>>>
>>> Well, except that the device might be varying its MAC address as well.
>>>
>>> I thought RFC7217 states that a device is expected to have a different IID for
>>> each prefix on an interface. (Though whether thereâ€™s a NetworkID available to
>>> seed a different LL IID per visited network is another question, else the device
>>> presumably has the same LL IID as it moves?)
>>>
>>> Thereâ€™s definitely value in avoiding correlation. If thereâ€™s an equal cost either
>>> way, why allow such potential?
>>
>> Extra code? But my real concern is that there might be unintended side effects,
>> because the interface identifier will no longer identify an interface.
>
> Well, the IID only really identifies an interface for a given prefix.
> For instance, DAD is done only for such given prefix.

I agree.  It's an interface identifier but only within a prefix.

The IID alone (w/o prefix) is not used anywhere AFAIK.  In dhhcpv6.conf, 
in neigh cache, etc it's the MAC address being used.

Alex

>
> And there is no requirement whatsoever that the IID for one prefix is
> the same as that used for the same interface for a different autoconf
> prefix.
>
> Thanks!
>
> Cheers,
>


From nobody Mon Feb  8 22:33:26 2016
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F397E1A1B56 for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 22:33:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level: 
X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, 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 U4oTTUqVMIzk for <ipv6@ietfa.amsl.com>; Mon,  8 Feb 2016 22:33:22 -0800 (PST)
Received: from mail-vk0-x231.google.com (mail-vk0-x231.google.com [IPv6:2607:f8b0:400c:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96AB31A1B51 for <ipv6@ietf.org>; Mon,  8 Feb 2016 22:33:22 -0800 (PST)
Received: by mail-vk0-x231.google.com with SMTP id k196so44311956vka.0 for <ipv6@ietf.org>; Mon, 08 Feb 2016 22:33:22 -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; bh=HdKtrZa87qHWCoTMpRP5xEcgOWzX7hWDpZ15E/I0y2E=; b=yDc6akm+Fkg46aJcllu4z4NdcxvRUfE7BhOl4/FygjYsiuti5sM24bSp1ffmZI4M7Y zbYcGG9MilCbT2WfIlmdqyetw7sg19IePlxHoW1Rc6xchVIftgrezaIOk8GvmlwQE7qR KKCHoXQS2JRaOfQbJuDE43vs3NE5yqA4NZbWpa6o0ibmgNi67yJqXgb67GsZKzHg/S3j G/Ho35P1BQsSffCu7PzUagHZSS1gy93HwEmSZFB4yVvZ8oSgQI+agP53hLopCYva42Kj 6+ra2S9pmQdj9T1s7xKs0PrOXLzSeAeI1LtIik/ufs+VTr8tZH8IY+QZR4SAWRbqMWxN Tv+Q==
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=HdKtrZa87qHWCoTMpRP5xEcgOWzX7hWDpZ15E/I0y2E=; b=TRKGEX9JQW1szPGvvBv1mFVDK67PwSCNT2E8LcEIDnlW3Jg/3bs4tYuF6EfM5wlawq 58ZMtnmTJat1I82a1kk/s78JO3OHOrwA/HFSjlydgZxcMCASouPlqotv6YLDUemtJMH4 S0gIzgtRMTzHB5HOP32aZ2Zc3nuKwUG+PVkyUTF2ZRlEB9iZ5Xu8TXKbIksBQy4YgCpS Ox5dbbxTSPqbrf+StCswF0x8pHFCy5da9bBrUbuBEFdM7JYh5JzlocIWWXyz325xGsd4 gDRoatlvtSjiJ/BqnTECLAR379Frpxk4AoV7TxPSz/BbawlXwVxO/nbUNj9awuUhWvW+ XgsQ==
X-Gm-Message-State: AG10YORRoj9m4SMISlT0MU3P86DaBgN5XavEeCCIB9ABW+NW1bTgwkVgJu+sGN1BczjKQm4hz7IprUPOfb+Quw==
MIME-Version: 1.0
X-Received: by 10.31.107.1 with SMTP id g1mr24479374vkc.15.1454999601763; Mon, 08 Feb 2016 22:33:21 -0800 (PST)
Received: by 10.159.34.103 with HTTP; Mon, 8 Feb 2016 22:33:21 -0800 (PST)
Received: by 10.159.34.103 with HTTP; Mon, 8 Feb 2016 22:33:21 -0800 (PST)
In-Reply-To: <56B98285.9030306@gmail.com>
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com> <56B4FF9D.10203@gmail.com> <5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <EMEW3|5048bb3e4f22902e3e9b18a621e7fd32s16H1H03tjc|ecs.soton.ac.uk|5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <56B7915D.2060300@gmail.com> <56B93CA0.7080000@si6networks.com> <56B98285.9030306@gmail.com>
Date: Tue, 9 Feb 2016 17:33:21 +1100
Message-ID: <CAO42Z2xz=PGbcTYLozCy651Tm2iX9GMiP1RMT1Yt6zof4feO_g@mail.gmail.com>
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
From: Mark Smith <markzzzsmith@gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=001a114790a8695cf2052b507e7f
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/m599rKouK-gXkxkMDZYDEIswYwk>
Cc: Fernando Gont <fgont@si6networks.com>, Tim Chown <tjc@ecs.soton.ac.uk>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 06:33:25 -0000

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

On 9 Feb 2016 17:09, "Alexandre Petrescu" <alexandre.petrescu@gmail.com>
wrote:
>
>
>
> Le 09/02/2016 02:10, Fernando Gont a =C3=A9crit :
>>
>> On 02/07/2016 03:47 PM, Brian E Carpenter wrote:
>> [....]
>>>>>
>>>>>
>>>>> But Ole's point was that any observer who sees a LL packet is on-link
and
>>>>> can therefore see the MAC address anyway; an observer who can see MAC
addresses
>>>>> can just laugh at RFC 7217 or RFC 4941.
>>>>
>>>>
>>>> Well, except that the device might be varying its MAC address as well.
>>>>
>>>> I thought RFC7217 states that a device is expected to have a different
IID for
>>>> each prefix on an interface. (Though whether there=E2=80=99s a Network=
ID
available to
>>>> seed a different LL IID per visited network is another question, else
the device
>>>> presumably has the same LL IID as it moves?)
>>>>
>>>> There=E2=80=99s definitely value in avoiding correlation. If there=E2=
=80=99s an equal
cost either
>>>> way, why allow such potential?
>>>
>>>
>>> Extra code? But my real concern is that there might be unintended side
effects,
>>> because the interface identifier will no longer identify an interface.
>>
>>
>> Well, the IID only really identifies an interface for a given prefix.
>> For instance, DAD is done only for such given prefix.
>
>
> I agree.  It's an interface identifier but only within a prefix.
>

And RFC4291 even specifically says that a node may use the same IIDs on
different interfaces, and that they can be different for different prefixes
on the same link, which I think  shows their significance is limited to
within a prefix.

https://tools.ietf.org/html/rfc4291#section-2.5.1

> The IID alone (w/o prefix) is not used anywhere AFAIK.  In dhhcpv6.conf,
in neigh cache, etc it's the MAC address being used.
>
> Alex
>
>
>>
>> And there is no requirement whatsoever that the IID for one prefix is
>> the same as that used for the same interface for a different autoconf
>> prefix.
>>
>> Thanks!
>>
>> Cheers,
>>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

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

<p dir=3D"ltr"><br>
On 9 Feb 2016 17:09, &quot;Alexandre Petrescu&quot; &lt;<a href=3D"mailto:a=
lexandre.petrescu@gmail.com">alexandre.petrescu@gmail.com</a>&gt; wrote:<br=
>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Le 09/02/2016 02:10, Fernando Gont a =C3=A9crit :<br>
&gt;&gt;<br>
&gt;&gt; On 02/07/2016 03:47 PM, Brian E Carpenter wrote:<br>
&gt;&gt; [....]<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; But Ole&#39;s point was that any observer who sees a L=
L packet is on-link and<br>
&gt;&gt;&gt;&gt;&gt; can therefore see the MAC address anyway; an observer =
who can see MAC addresses<br>
&gt;&gt;&gt;&gt;&gt; can just laugh at RFC 7217 or RFC 4941.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Well, except that the device might be varying its MAC addr=
ess as well.<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; I thought RFC7217 states that a device is expected to have=
 a different IID for<br>
&gt;&gt;&gt;&gt; each prefix on an interface. (Though whether there=E2=80=
=99s a NetworkID available to<br>
&gt;&gt;&gt;&gt; seed a different LL IID per visited network is another que=
stion, else the device<br>
&gt;&gt;&gt;&gt; presumably has the same LL IID as it moves?)<br>
&gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; There=E2=80=99s definitely value in avoiding correlation. =
If there=E2=80=99s an equal cost either<br>
&gt;&gt;&gt;&gt; way, why allow such potential?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Extra code? But my real concern is that there might be uninten=
ded side effects,<br>
&gt;&gt;&gt; because the interface identifier will no longer identify an in=
terface.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Well, the IID only really identifies an interface for a given pref=
ix.<br>
&gt;&gt; For instance, DAD is done only for such given prefix.<br>
&gt;<br>
&gt;<br>
&gt; I agree.=C2=A0 It&#39;s an interface identifier but only within a pref=
ix.<br>
&gt;</p>
<p dir=3D"ltr">And RFC4291 even specifically says that a node may use the s=
ame IIDs on different interfaces, and that they can be different for differ=
ent prefixes on the same link, which I think=C2=A0 shows their significance=
 is limited to within a prefix.</p>
<p dir=3D"ltr"><a href=3D"https://tools.ietf.org/html/rfc4291#section-2.5.1=
">https://tools.ietf.org/html/rfc4291#section-2.5.1</a></p>
<p dir=3D"ltr">&gt; The IID alone (w/o prefix) is not used anywhere AFAIK.=
=C2=A0 In dhhcpv6.conf, in neigh cache, etc it&#39;s the MAC address being =
used.<br>
&gt;<br>
&gt; Alex<br>
&gt;<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; And there is no requirement whatsoever that the IID for one prefix=
 is<br>
&gt;&gt; the same as that used for the same interface for a different autoc=
onf<br>
&gt;&gt; prefix.<br>
&gt;&gt;<br>
&gt;&gt; Thanks!<br>
&gt;&gt;<br>
&gt;&gt; Cheers,<br>
&gt;&gt;<br>
&gt;<br>
&gt; --------------------------------------------------------------------<b=
r>
&gt; IETF IPv6 working group mailing list<br>
&gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
&gt; Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listi=
nfo/ipv6">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
&gt; --------------------------------------------------------------------<b=
r>
</p>

--001a114790a8695cf2052b507e7f--


From nobody Tue Feb  9 01:54:25 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B9F31A87C1 for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 01:54:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-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 lPA5dDU6Yxx3 for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 01:54:22 -0800 (PST)
Received: from cowbell.employees.org (cowbell.employees.org [IPv6:2001:1868:a000:17::142]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 657321A87A4 for <ipv6@ietf.org>; Tue,  9 Feb 2016 01:54:22 -0800 (PST)
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id EE084D7883; Tue,  9 Feb 2016 01:54:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :content-type:subject:date:message-id:cc:to:mime-version; s= selector1; bh=fQcuoVsry44Sr9n8ItDnrWe5raI=; b=oIP/Znl9WkQKVfF4t4 P9hta+W7eFPWnNrw6XZQh7vvpPv9T0ELgMvI+jqwhTLcDX8dDIPsmR9bY4kAW/Jp H5qJh7bmWHC7Q7ybDj2CnGsF4u0U1ul2eQGz8ANd9zz1QhSZynFFXejpXHYjvW72 IrArLm2SUewJpYvaFw4BwZH8M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :content-type:subject:date:message-id:cc:to:mime-version; q=dns; s=selector1; b=Dr/QI3wwIoIMnra0+cua4j2+u10ufyBLU34cus6GH/ZPsJ+p sjUD0rVjLulRC5bz0izdWvCLh6SetZaSMrjQMxAWIbQQReGd8huLYNegZxXy9qU3 HkHHUVAHUOCuH0af5rFePjm/1ma3e31V6PmIic/6EijDL+cI3J6OSn+85fw=
Received: from h.hanazo.no (unknown [173.38.220.49]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id ACFB1D7884; Tue,  9 Feb 2016 01:54:19 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 608B4109E572; Tue,  9 Feb 2016 10:54:17 +0100 (CET)
From: otroan@employees.org
X-Pgp-Agent: GPGMail 2.6b2
Content-Type: multipart/signed; boundary="Apple-Mail=_ACB17949-D090-40E4-8173-656E55819931"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: 6MAN Working group last call: draft-ietf-6man-rdnss-rfc6106bis
Date: Tue, 9 Feb 2016 10:54:16 +0100
Message-Id: <6AC58C26-01B6-4C16-851F-0C1228CDD2AF@employees.org>
To: 6man WG <ipv6@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Z4Op0HsFDjw_XOZ4DVskJyElPY8>
Cc: bob.hinden@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 09:54:24 -0000

--Apple-Mail=_ACB17949-D090-40E4-8173-656E55819931
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

This message starts a two week 6MAN Working Group Last Call on =
advancing:

     Title    : IPv6 Router Advertisement Options for DNS Configuration
     Authors  : J. Jeong, S. Park, L. Beloeil, S. Madanapalli
     Filename : draft-ietf-6man-rdnss-rfc6106bis-06
     Pages    : 17
     Date     : 2015-10-09

    https://tools.ietf.org/html/draft-ietf-6man-rdnss-rfc6106bis-06

as a Proposed Standard.  Substantive comments and statements of support =
for publishing this document should be directed to the mailing list.  =
Editorial suggestions can be sent to the authors.  This last call will =
end on 23 February 2016.

We would like this document to follow the experimental document shepherd =
procedure. We will need a volunteer document shepherd, before we can =
advance this document.

Best regards,
Ole & Bob


--Apple-Mail=_ACB17949-D090-40E4-8173-656E55819931
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIcBAEBCgAGBQJWubdJAAoJEL7aWKiYQt92ua0P/jf20E0yZnoEdtlUuq46YFVA
6dt1Cnu8MI+UHYzaA4i7ZU6qZOhOYNeajYCBt+60imyDAwp2NcPKYtInOIMlhFWj
zmntLUpgCd9AsE9se/ZS6Tj8UwVskOFI0DTp1mLHr96GXoHDRQnTV0FpQXFok+mX
WBTe3xxXLre/TfcvOh5m2yepQluf9WaNwE27TxOcDu6eztT5TIcnWilSQxMHt8QC
f7BUz3d6uTMT4Y3uEPZGQgCMSM/A+mR3KHBf6T4HDF78lKQnvEvPnT5p0GGZgDqO
RqP/f1hhssCSZJq3SajTBCdeu+F3XiIHkJ/HqM+/qKUXlKITGrsDWlOM5yMuAg6n
FZfCw4KnKKfSoiLeGFfkgV5/BVF+jrCA99EVcq9zWvfNRDir+uSXrcx0RaLHbEr8
gdkaYjM59+IviunS1AAMQp+hsYG/kaHl2LllpZmHT2mljETCm4DvPF8OeI0Crfsp
WEhN4iCiN5Wxo+yxyB2KDJdozsR/83pWR/8miQ41wgZ8VhDkQwGwf9ZCC3eFbJPi
haHWl8GC0tqYhQzfIRowsX4yVMvh9rmWDF4SBCLgS3dtcaAyd1B733zMeAIe+wJd
X+DvxNJz8vgavWuh5ondPQk/KdtZitykpwpAmxhGnzGpu/bPJdkerbKlXflcprKa
Q0Ho1e4uRg3jgTUYCUaI
=cHFK
-----END PGP SIGNATURE-----

--Apple-Mail=_ACB17949-D090-40E4-8173-656E55819931--


From nobody Tue Feb  9 02:30:04 2016
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B5071A8859 for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 02:30:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.221
X-Spam-Level: 
X-Spam-Status: No, score=-1.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, 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 qoYOHx1FRrrJ for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 02:30:00 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 48AC51A885C for <ipv6@ietf.org>; Tue,  9 Feb 2016 02:30:00 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u19ATv8V030102; Tue, 9 Feb 2016 10:29:57 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u19ATv8V030102
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1455013797; bh=M8ZcWMKL+Z+QBgnQD3wTeTPvzWE=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=QIvddl/T+2yqncl7x8nwAOqzZBv01T2mjjTsjE3y2fcX2KlzUQkzkpYrE74xjGOr3 b9RY0NcT1UQm1yQJ1Q/mp2MEz2g2sDNJy/hpRmGZHEmw6oF+MHKfwnBOlgLfIrXfjr PAsJU5cIPjx3pSqDmsy3oPRPn4BSeOHgQqq8JLBs=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s18AYv1463904409Aw ret-id none; Tue, 09 Feb 2016 10:29:57 +0000
Received: from [10.1.11.170] (firewall-lho-ext.management.janet.ac.uk [194.82.140.195]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u19ATnUS001725 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Feb 2016 10:29:49 GMT
Content-Type: multipart/alternative; boundary="Apple-Mail=_A0E59D42-7E55-4071-9919-CAAE27BF6B4C"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <CAO42Z2xz=PGbcTYLozCy651Tm2iX9GMiP1RMT1Yt6zof4feO_g@mail.gmail.com>
Date: Tue, 9 Feb 2016 10:29:47 +0000
Message-ID: <EMEW3|6807d354e539c8c40962851c0cfae6a7s18AYv03tjc|ecs.soton.ac.uk|C90A0366-751A-4E11-9F62-64E074A5DFD7@ecs.soton.ac.uk>
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com> <56B4FF9D.10203@gmail.com> <5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <EMEW3|5048bb3e4f22902e3e9b18a621e7fd32s16H1H03tjc|ecs.soton.ac.uk|5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <56B7915D.2060300@gmail.com> <56B93CA0.7080000@si6networks.com> <56B98285.9030306@gmail.com> <CAO42Z2xz=PGbcTYLozCy651Tm2iX9GMiP1RMT1Yt6zof4feO_g@mail.gmail.com> <C90A0366-751A-4E11-9F62-64E074A5DFD7@ecs.soton.ac.uk>
To: Mark Smith <markzzzsmith@gmail.com>
X-Mailer: Apple Mail (2.3112)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s18AYv146390440900; tid=s18AYv1463904409Aw; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=4:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u19ATv8V030102
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Mv8ItYnH05301ULfBJ2z9D7jOtk>
Cc: Fernando Gont <fgont@si6networks.com>, Alexandre Petrescu <alexandre.petrescu@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 10:30:03 -0000

--Apple-Mail=_A0E59D42-7E55-4071-9919-CAAE27BF6B4C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On 9 Feb 2016, at 06:33, Mark Smith <markzzzsmith@gmail.com> wrote:
> On 9 Feb 2016 17:09, "Alexandre Petrescu" =
<alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>> =
wrote:
> >
> >
> >
> > Le 09/02/2016 02:10, Fernando Gont a =C3=A9crit :
> >>
> >> On 02/07/2016 03:47 PM, Brian E Carpenter wrote:
> >> [....]
> >>>>>
> >>>>>
> >>>>> But Ole's point was that any observer who sees a LL packet is =
on-link and
> >>>>> can therefore see the MAC address anyway; an observer who can =
see MAC addresses
> >>>>> can just laugh at RFC 7217 or RFC 4941.
> >>>>
> >>>>
> >>>> Well, except that the device might be varying its MAC address as =
well.
> >>>>
> >>>> I thought RFC7217 states that a device is expected to have a =
different IID for
> >>>> each prefix on an interface. (Though whether there=E2=80=99s a =
NetworkID available to
> >>>> seed a different LL IID per visited network is another question, =
else the device
> >>>> presumably has the same LL IID as it moves?)
> >>>>
> >>>> There=E2=80=99s definitely value in avoiding correlation. If =
there=E2=80=99s an equal cost either
> >>>> way, why allow such potential?
> >>>
> >>>
> >>> Extra code? But my real concern is that there might be unintended =
side effects,
> >>> because the interface identifier will no longer identify an =
interface.
> >>
> >>
> >> Well, the IID only really identifies an interface for a given =
prefix.
> >> For instance, DAD is done only for such given prefix.
> >
> >
> > I agree.  It's an interface identifier but only within a prefix.
> >
>=20
> And RFC4291 even specifically says that a node may use the same IIDs =
on different interfaces, and that they can be different for different =
prefixes on the same link, which I think  shows their significance is =
limited to within a prefix.
>=20
> https://tools.ietf.org/html/rfc4291#section-2.5.1 =
<https://tools.ietf.org/html/rfc4291#section-2.5.1>Indeed. So long as =
they are unique within that subnet prefix, as stated.

The interesting question with LL IIDs is whether they should change per =
visited network. My understanding of RFC 7217 is that the LL IID will =
remain the same unless the visited network presents a Network ID to be =
used in the generation of the IID, and even then if the ID is the SSID =
then it may well be the same SSID name on many visited networks.  Or =
might the MAC address be used for Net_Iface allowing the LL IID to =
change when the MAC address is changed (given there=E2=80=99s recent =
movement towards dynamic/temporary MAC addresses).

I don=E2=80=99t think it=E2=80=99s good to assume that using the same =
IID for GUAs and LLs is OK. I do support documenting potential side =
effects in the currently active IIDs draft.

Tim
> > The IID alone (w/o prefix) is not used anywhere AFAIK.  In =
dhhcpv6.conf, in neigh cache, etc it's the MAC address being used.
> >
> > Alex
> >
> >
> >>
> >> And there is no requirement whatsoever that the IID for one prefix =
is
> >> the same as that used for the same interface for a different =
autoconf
> >> prefix.
> >>
> >> Thanks!
> >>
> >> Cheers,
> >>
> >
> > --------------------------------------------------------------------
> > IETF IPv6 working group mailing list
> > ipv6@ietf.org <mailto:ipv6@ietf.org>
> > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 =
<https://www.ietf.org/mailman/listinfo/ipv6>
> > --------------------------------------------------------------------
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_A0E59D42-7E55-4071-9919-CAAE27BF6B4C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
9 Feb 2016, at 06:33, Mark Smith &lt;<a =
href=3D"mailto:markzzzsmith@gmail.com" =
class=3D"">markzzzsmith@gmail.com</a>&gt; =
wrote:</div></blockquote><blockquote type=3D"cite" class=3D""><div =
class=3D""><p dir=3D"ltr" class=3D"">
On 9 Feb 2016 17:09, "Alexandre Petrescu" &lt;<a =
href=3D"mailto:alexandre.petrescu@gmail.com" =
class=3D"">alexandre.petrescu@gmail.com</a>&gt; wrote:<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt; Le 09/02/2016 02:10, Fernando Gont a =C3=A9crit :<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; On 02/07/2016 03:47 PM, Brian E Carpenter wrote:<br class=3D"">
&gt;&gt; [....]<br class=3D"">
&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;&gt; But Ole's point was that any observer who sees a LL =
packet is on-link and<br class=3D"">
&gt;&gt;&gt;&gt;&gt; can therefore see the MAC address anyway; an =
observer who can see MAC addresses<br class=3D"">
&gt;&gt;&gt;&gt;&gt; can just laugh at RFC 7217 or RFC 4941.<br =
class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; Well, except that the device might be varying its MAC =
address as well.<br class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; I thought RFC7217 states that a device is expected to =
have a different IID for<br class=3D"">
&gt;&gt;&gt;&gt; each prefix on an interface. (Though whether there=E2=80=99=
s a NetworkID available to<br class=3D"">
&gt;&gt;&gt;&gt; seed a different LL IID per visited network is another =
question, else the device<br class=3D"">
&gt;&gt;&gt;&gt; presumably has the same LL IID as it moves?)<br =
class=3D"">
&gt;&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;&gt; There=E2=80=99s definitely value in avoiding =
correlation. If there=E2=80=99s an equal cost either<br class=3D"">
&gt;&gt;&gt;&gt; way, why allow such potential?<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt;<br class=3D"">
&gt;&gt;&gt; Extra code? But my real concern is that there might be =
unintended side effects,<br class=3D"">
&gt;&gt;&gt; because the interface identifier will no longer identify an =
interface.<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; Well, the IID only really identifies an interface for a given =
prefix.<br class=3D"">
&gt;&gt; For instance, DAD is done only for such given prefix.<br =
class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt; I agree.&nbsp; It's an interface identifier but only within a =
prefix.<br class=3D"">
&gt;</p><p dir=3D"ltr" class=3D"">And RFC4291 even specifically says =
that a node may use the same IIDs on different interfaces, and that they =
can be different for different prefixes on the same link, which I =
think&nbsp; shows their significance is limited to within a =
prefix.</p><p dir=3D"ltr" class=3D""><a =
href=3D"https://tools.ietf.org/html/rfc4291#section-2.5.1" =
class=3D"">https://tools.ietf.org/html/rfc4291#section-2.5.1</a></p></div>=
</blockquote>Indeed. So long as they are unique within that subnet =
prefix, as stated.</div><div><br class=3D""></div><div>The interesting =
question with LL IIDs is whether they should change per visited network. =
My understanding of RFC 7217 is that the LL IID will remain the same =
unless the visited network presents a Network ID to be used in the =
generation of the IID, and even then if the ID is the SSID then it may =
well be the same SSID name on many visited networks. &nbsp;Or might the =
MAC address be used for Net_Iface allowing the LL IID to change when the =
MAC address is changed (given there=E2=80=99s recent movement towards =
dynamic/temporary MAC addresses).</div><div><br class=3D""></div><div>I =
don=E2=80=99t think it=E2=80=99s good to assume that using the same IID =
for GUAs and LLs is OK. I do support documenting potential side effects =
in the currently active IIDs draft.</div><div><br =
class=3D""></div><div>Tim<br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D""><p dir=3D"ltr" class=3D"">&gt; The IID alone =
(w/o prefix) is not used anywhere AFAIK.&nbsp; In dhhcpv6.conf, in neigh =
cache, etc it's the MAC address being used.<br class=3D"">
&gt;<br class=3D"">
&gt; Alex<br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; And there is no requirement whatsoever that the IID for one =
prefix is<br class=3D"">
&gt;&gt; the same as that used for the same interface for a different =
autoconf<br class=3D"">
&gt;&gt; prefix.<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; Thanks!<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;&gt; Cheers,<br class=3D"">
&gt;&gt;<br class=3D"">
&gt;<br class=3D"">
&gt; =
--------------------------------------------------------------------<br =
class=3D"">
&gt; IETF IPv6 working group mailing list<br class=3D"">
&gt; <a href=3D"mailto:ipv6@ietf.org" class=3D"">ipv6@ietf.org</a><br =
class=3D"">
&gt; Administrative Requests: <a =
href=3D"https://www.ietf.org/mailman/listinfo/ipv6" =
class=3D"">https://www.ietf.org/mailman/listinfo/ipv6</a><br class=3D"">
&gt; =
--------------------------------------------------------------------<br =
class=3D"">
</p>
--------------------------------------------------------------------<br =
class=3D"">IETF IPv6 working group mailing list<br class=3D""><a =
href=3D"mailto:ipv6@ietf.org" class=3D"">ipv6@ietf.org</a><br =
class=3D"">Administrative Requests: =
https://www.ietf.org/mailman/listinfo/ipv6<br =
class=3D"">---------------------------------------------------------------=
-----<br class=3D""></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_A0E59D42-7E55-4071-9919-CAAE27BF6B4C--


From nobody Tue Feb  9 03:17:03 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11A381A891F for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 03:17:02 -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] 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 FWg2SSiDK9r4 for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 03:17:00 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11C261A891E for <ipv6@ietf.org>; Tue,  9 Feb 2016 03:16:59 -0800 (PST)
Received: from [192.168.1.66] (unknown [186.56.188.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id BE776206AA8; Tue,  9 Feb 2016 12:16:53 +0100 (CET)
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: Tim Chown <tjc@ecs.soton.ac.uk>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com> <56B4FF9D.10203@gmail.com> <5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <EMEW3|5048bb3e4f22902e3e9b18a621e7fd32s16H1H03tjc|ecs.soton.ac.uk|5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B9C7EC.9030904@si6networks.com>
Date: Tue, 9 Feb 2016 08:05:16 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <EMEW3|5048bb3e4f22902e3e9b18a621e7fd32s16H1H03tjc|ecs.soton.ac.uk|5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/DnHajBz25-CySr8Ob_qcb-eXwxw>
Cc: 6man WG <ipv6@ietf.org>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 11:17:02 -0000

On 02/07/2016 01:59 PM, Tim Chown wrote:
[....]
> 
> Well, except that the device might be varying its MAC address as well.
> 
> I thought RFC7217 states that a device is expected to have a different IID for 
> each prefix on an interface.

Yes.


> (Though whether thereâ€™s a NetworkID available to
> seed a different LL IID per visited network is another question, else the device
> presumably has the same LL IID as it moves?)

The NetworkID parameter was made optional mostly because e.g. in wired
internet such identifier might not be easily available (at least as
easily as e.g. the SSID of the net). But yes, I would expect the LL
addresses to have a different IID per network.

> Thereâ€™s definitely value in avoiding correlation. If thereâ€™s an equal cost either 
> way, why allow such potential?

That's my take as well.

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





From nobody Tue Feb  9 03:17:11 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F9AD1A892B for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 03:17:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level: 
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_12=0.6, 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 kEEEAcdVZdGS for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 03:17:06 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11F3C1A8928 for <ipv6@ietf.org>; Tue,  9 Feb 2016 03:17:06 -0800 (PST)
Received: from [192.168.1.66] (unknown [186.56.188.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id F2183206B4D; Tue,  9 Feb 2016 12:17:01 +0100 (CET)
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Tim Chown <tjc@ecs.soton.ac.uk>
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com> <56B4FF9D.10203@gmail.com> <5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <EMEW3|5048bb3e4f22902e3e9b18a621e7fd32s16H1H03tjc|ecs.soton.ac.uk|5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <56B7915D.2060300@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <56B9C841.9020908@si6networks.com>
Date: Tue, 9 Feb 2016 08:06:41 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B7915D.2060300@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/upoKd-tS4w96EwTv7zk3WuqiVQo>
Cc: 6man WG <ipv6@ietf.org>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 11:17:07 -0000

On 02/07/2016 03:47 PM, Brian E Carpenter wrote:
> On 08/02/2016 05:59, Tim Chown wrote:
>> On 5 Feb 2016, at 20:01, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>>
>>> On 06/02/2016 07:20, Fernando Gont wrote:
>>>> On 02/05/2016 03:07 PM, otroan@employees.org wrote:
>>>>> Fernando,
>>>>>
>>>>> [...]
>>>>>
>>>>>>>
>>>>>>> What is the risk of using the same IID for link-local and global addresses?
>>>>>>> Typically if you can snoop the link-local address then you're onlink and leak information about all addresses and their correlations anyway.
>>>>>>
>>>>>> We discussed this one a hundred times now (including for RFC7217). The
>>>>>> risk is that at times such addressess can leak, without the need of the
>>>>>> attacker being pesent on the local link.
>>>>>>
>>>>>> e.g., your MTA is on the local-link, and you end up connecting to it
>>>>>> with a LL, which then appears in the email headers. (and there are a
>>>>>> bunch of other possible reasons for that to happen).
>>>>>>
>>>>>> Be proactive. MAC addresses in the IID are wrong. Putting them there is
>>>>>> just waiting for trouble.
>>>>>
>>>>> I didn't say the LL was based on a MAC.
>>>>> my question was if there was any issue with re-using the IID from the link-local in the GUA. assume the link-local is generated f.ex with 7217.
>>>>
>>>> Oops, my apologies. My answer would be "It unnecessarily enables
>>>> correlation of the activities that you carry between the two addresses".
>>>>
>>>> i.e., by simply inspecting the IID I could easily tell that the
>>>> activities carried out with one address were performed by the same node
>>>> that employed the other address.
>>>>
>>>> My take here is, again: be proactive. If there's no requirement (and
>>>> there isn't) for the two IIDs to be the same, then make them different,
>>>> and fail on the safe side.
>>>
>>> But Ole's point was that any observer who sees a LL packet is on-link and
>>> can therefore see the MAC address anyway; an observer who can see MAC addresses
>>> can just laugh at RFC 7217 or RFC 4941.
>>
>> Well, except that the device might be varying its MAC address as well.
>>
>> I thought RFC7217 states that a device is expected to have a different IID for 
>> each prefix on an interface. (Though whether thereâ€™s a NetworkID available to
>> seed a different LL IID per visited network is another question, else the device
>> presumably has the same LL IID as it moves?)
>>
>> Thereâ€™s definitely value in avoiding correlation. If thereâ€™s an equal cost either 
>> way, why allow such potential?
> 
> Extra code? But my real concern is that there might be unintended side effects,
> because the interface identifier will no longer identify an interface.

Not really. RFC7217 automagically achieves that.


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





From nobody Tue Feb  9 03:17:25 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C52221A8930 for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 03:17:13 -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] 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 RNeG50NhUkDn for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 03:17:12 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53CA81A8928 for <ipv6@ietf.org>; Tue,  9 Feb 2016 03:17:12 -0800 (PST)
Received: from [192.168.1.66] (unknown [186.56.188.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 11DEB206B50; Tue,  9 Feb 2016 12:17:08 +0100 (CET)
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, ipv6@ietf.org
References: <56B48386.2040300@gmail.com> <56B4CCE0.7090207@si6networks.com> <56B854CC.70307@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B9CA2C.5070904@si6networks.com>
Date: Tue, 9 Feb 2016 08:14:52 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B854CC.70307@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/bxu0ExFyzi8ryMZRJ5huIiVD26Y>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 11:17:14 -0000

On 02/08/2016 05:41 AM, Alexandre Petrescu wrote:
[....]
>>> draft-ietf-6man-default-iids-09 rightfully indicates that the same IID
>>> should not be used in the LL and GUA addresses of a same interface.
>>> Because there may be a risk of correlation between addresses by a
>>> snooper.
>>>
>>> The draft says:
>>>    The negotiated interface identifier is used by the local end of the
>>>    PPP link to autoconfigure an IPv6 link-local unicast address for the
>>>    PPP interface.  However, it SHOULD NOT be assumed that the same
>>>    interface identifier is used in configuring global unicast addresses
>>>    for the PPP interface using IPv6 stateless address autoconfiguration
>>>    [3].
>>>
>>> But what does it mean "it SHOULD NOT be assumed"?  Who should not
>>> assume?  I think the text should rather say: "a same IID should not be
>>> used for several different scoped addresses of a same interface because
>>> snoopers may correlated them".
>>
>> You're right. Actually, I'd remove this sentence altogether:
>> "  However, it SHOULD NOT be assumed that the same
>>     interface identifier is used in configuring global unicast addresses
>>     for the PPP interface using IPv6 stateless address autoconfiguration
>>     [3]."
>>
>> since RFC7217 takes care of this. Thoughts?
> 
> I think it is good.  Better would be "the same IID present in LL SHOULD
> NOT be used in configuring GUA (or ULA) for the ppp interface".
>
> 'SHOULD NOT be assumed' is unclear.

But this would mean that the IPv6-over-PPP document would have extra
requirements for ID generation, and that wouldn't be a good thing.
Removing the offending the solves the problem, because RFC7217 simply
will not use the same IID for GUAs and LLs.



>>> And what is [3]?  I guess the brackets should be escaped somehow
>>> otherwise looking at the list of References in this draft there is no
>>> [3].
>>
>> That's a reference in the RFC we're quoting.
> 
> Ok, I understand.  So this RFC-to-be is less self-contained - it must be
> read together with the referred RFCs.

Not really. The section about "changes to RFCs" is, IMO, mostly a list
of patches that must be applied to RFCs when/if they are revised.

The self-contained part of the document essentially is "whenever you
need to generate IIDs, use RFC7217".

Thanks!

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





From nobody Tue Feb  9 03:39:50 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 609E81A8940 for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 03:39:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level: 
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_12=0.6, 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 1kevrFmqXf7Z for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 03:39:43 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E43D71A8944 for <ipv6@ietf.org>; Tue,  9 Feb 2016 03:39:42 -0800 (PST)
Received: from [192.168.1.66] (unknown [186.56.188.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 75285206B57; Tue,  9 Feb 2016 12:39:37 +0100 (CET)
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: Tim Chown <tjc@ecs.soton.ac.uk>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com> <56B4FF9D.10203@gmail.com> <5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <EMEW3|5048bb3e4f22902e3e9b18a621e7fd32s16H1H03tjc|ecs.soton.ac.uk|5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <56B7915D.2060300@gmail.com> <FC23908F-3570-4F76-8005-6880E77ECF89@ecs.soton.ac.uk> <EMEW3|84deaef4b4572380170c25cc18973ac9s179uc03tjc|ecs.soton.ac.uk|FC23908F-3570-4F76-8005-6880E77ECF89@ecs.soton.ac.uk>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B9CEDA.704@si6networks.com>
Date: Tue, 9 Feb 2016 08:34:50 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <EMEW3|84deaef4b4572380170c25cc18973ac9s179uc03tjc|ecs.soton.ac.uk|FC23908F-3570-4F76-8005-6880E77ECF89@ecs.soton.ac.uk>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/NglZuRoLWt76dElas7KDnand-Rs>
Cc: 6man WG <ipv6@ietf.org>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 11:39:47 -0000

On 02/08/2016 06:56 AM, Tim Chown wrote:
>> On 7 Feb 2016, at 18:47, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>
>> On 08/02/2016 05:59, Tim Chown wrote:
>>> On 5 Feb 2016, at 20:01, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>>>
>>>> On 06/02/2016 07:20, Fernando Gont wrote:
>>>>> On 02/05/2016 03:07 PM, otroan@employees.org wrote:
>>>>>> Fernando,
>>>>>>
>>>>>> [...]
>>>>>>
>>>>>>>>
>>>>>>>> What is the risk of using the same IID for link-local and global addresses?
>>>>>>>> Typically if you can snoop the link-local address then you're onlink and leak information about all addresses and their correlations anyway.
>>>>>>>
>>>>>>> We discussed this one a hundred times now (including for RFC7217). The
>>>>>>> risk is that at times such addressess can leak, without the need of the
>>>>>>> attacker being pesent on the local link.
>>>>>>>
>>>>>>> e.g., your MTA is on the local-link, and you end up connecting to it
>>>>>>> with a LL, which then appears in the email headers. (and there are a
>>>>>>> bunch of other possible reasons for that to happen).
>>>>>>>
>>>>>>> Be proactive. MAC addresses in the IID are wrong. Putting them there is
>>>>>>> just waiting for trouble.
>>>>>>
>>>>>> I didn't say the LL was based on a MAC.
>>>>>> my question was if there was any issue with re-using the IID from the link-local in the GUA. assume the link-local is generated f.ex with 7217.
>>>>>
>>>>> Oops, my apologies. My answer would be "It unnecessarily enables
>>>>> correlation of the activities that you carry between the two addresses".
>>>>>
>>>>> i.e., by simply inspecting the IID I could easily tell that the
>>>>> activities carried out with one address were performed by the same node
>>>>> that employed the other address.
>>>>>
>>>>> My take here is, again: be proactive. If there's no requirement (and
>>>>> there isn't) for the two IIDs to be the same, then make them different,
>>>>> and fail on the safe side.
>>>>
>>>> But Ole's point was that any observer who sees a LL packet is on-link and
>>>> can therefore see the MAC address anyway; an observer who can see MAC addresses
>>>> can just laugh at RFC 7217 or RFC 4941.
>>>
>>> Well, except that the device might be varying its MAC address as well.
>>>
>>> I thought RFC7217 states that a device is expected to have a different IID for 
>>> each prefix on an interface. (Though whether thereâ€™s a NetworkID available to
>>> seed a different LL IID per visited network is another question, else the device
>>> presumably has the same LL IID as it moves?)
>>>
>>> Thereâ€™s definitely value in avoiding correlation. If thereâ€™s an equal cost either 
>>> way, why allow such potential?
>>
>> Extra code? But my real concern is that there might be unintended side effects,
>> because the interface identifier will no longer identify an interface.
> 
> Fair enough, and there are some notes on this in RFC 4914 with a section 
> on the possible implications of varying IIDs. 

FWIW, the concerns in RFC4941 are rather about the temporary nature of
the IIDs rather than as a result of different IIDs in e.g. LLS vs GUAs...


> 
> But RFC 7217, and draft-ietf-6man-default-iids-09 say different. Perhaps 
> you should look at capturing these concerns in that draft, so such side effects
> are noted.
> 
> One premise within that draft is:
> â€œgiven two addresses, it must be difficult for an outside entity
>  to tell whether the addresses have been generated by the same host."
> which further reinforces the different IIDs for GUAs (multiple, if the device
> is multihomed) and LLs.

Exactly.

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





From nobody Tue Feb  9 03:40:02 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A201D1A8968 for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 03:39:55 -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] 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 Fk1Y5g8Osu3X for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 03:39:51 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C3201A8953 for <ipv6@ietf.org>; Tue,  9 Feb 2016 03:39:50 -0800 (PST)
Received: from [192.168.1.66] (unknown [186.56.188.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 897B1206B5B; Tue,  9 Feb 2016 12:39:46 +0100 (CET)
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: Erik Kline <ek@google.com>, Tim Chown <tjc@ecs.soton.ac.uk>
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com> <56B4FF9D.10203@gmail.com> <5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <EMEW3|5048bb3e4f22902e3e9b18a621e7fd32s16H1H03tjc|ecs.soton.ac.uk|5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <FC23908F-3570-4F76-8005-6880E77ECF89@ecs.soton.ac.uk> <56B7915D.2060300@gmail.com> <EMEW3|84deaef4b4572380170c25cc18973ac9s179uc03tjc|ecs.soton.ac.uk|FC23908F-3570-4F76-8005-6880E77ECF89@ecs.soton.ac.uk> <CAAedzxqbyb-SQFEvbhJjrmUAXQzfCFkTBoKXQ6W2CUUaRaCYOA@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56B9CFE1.1040701@si6networks.com>
Date: Tue, 9 Feb 2016 08:39:13 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <CAAedzxqbyb-SQFEvbhJjrmUAXQzfCFkTBoKXQ6W2CUUaRaCYOA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/CxKsk1GP-FesWb8a6kig3OBSyUE>
Cc: Alexandre Petrescu <alexandre.petrescu@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 11:39:55 -0000

Hi, Erik,

On 02/08/2016 07:17 AM, Erik Kline wrote:
> One drawback of increasing the number of IIDs in use on the link is it
> increases the number of solicited node multicast groups to which the
> device must subscribe.  On shared /64 links this is probably
> unavoidable.

Yes. However, this hen compared to the "10 temp addresses per prefix at
a time" is a piece of cake (i.e., one group for LL and one grop for GUA).



> (Obviously, trying to get all your "random" IIDs into the same or a
> few /104s would be rather lame.  :-)
> 
> I'm not sure I see any real problem with having the same LL and GUA
> IID, even if they do leak.
> 
>     [1] if they're randomized at network attach (and I'm not on the
> link too long) then who cares
> 
>     [2] if they're "stable" 7217-style then they're "permanently
> leaked" by design and who cares

It's not necessarily a problem.

However, it would actually take special code to make the two IIDs the
same (FC7217, by default, would result in different IIDs for each). And,
being proactive, you fail on the safe side, even if there's no evident
drawback

Thanks!

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





From nobody Tue Feb  9 04:24:27 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1610D1A8A05 for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 04:24:23 -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] 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 dIJZEKvaS1WC for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 04:24:18 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F7131A89FA for <ipv6@ietf.org>; Tue,  9 Feb 2016 04:24:18 -0800 (PST)
Received: from [192.168.1.66] (unknown [186.56.188.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id ECB9C206B5C; Tue,  9 Feb 2016 13:24:14 +0100 (CET)
Subject: Re: 6MAN Working group last call: draft-ietf-6man-rdnss-rfc6106bis
To: otroan@employees.org, 6man WG <ipv6@ietf.org>
References: <6AC58C26-01B6-4C16-851F-0C1228CDD2AF@employees.org>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <56B9DA5D.2080906@si6networks.com>
Date: Tue, 9 Feb 2016 09:23:57 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <6AC58C26-01B6-4C16-851F-0C1228CDD2AF@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/i5TUCzEi4JXCgNkiT6Pj-7Tg9ls>
Cc: bob.hinden@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 12:24:23 -0000

On 02/09/2016 06:54 AM, otroan@employees.org wrote:
> This message starts a two week 6MAN Working Group Last Call on advancing:
> 
>      Title    : IPv6 Router Advertisement Options for DNS Configuration
>      Authors  : J. Jeong, S. Park, L. Beloeil, S. Madanapalli
>      Filename : draft-ietf-6man-rdnss-rfc6106bis-06
>      Pages    : 17
>      Date     : 2015-10-09
> 
>     https://tools.ietf.org/html/draft-ietf-6man-rdnss-rfc6106bis-06
> 
> as a Proposed Standard.  Substantive comments and statements of support for publishing this document should be directed to the mailing list.  Editorial suggestions can be sent to the authors.  This last call will end on 23 February 2016.
> 
> We would like this document to follow the experimental document shepherd procedure. We will need a volunteer document shepherd, before we can advance this document.

I can volunteer for that if it helps.

Thanks!

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





From nobody Tue Feb  9 05:12:28 2016
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D872A1A8AC1 for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 05:12:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.3
X-Spam-Level: 
X-Spam-Status: No, score=0.3 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, MANGLED_TOOL=2.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WuyPrh0vktb8 for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 05:12:26 -0800 (PST)
Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78C861A8AC3 for <ipv6@ietf.org>; Tue,  9 Feb 2016 05:12:26 -0800 (PST)
Received: by mail-qk0-x230.google.com with SMTP id o6so70137573qkc.2 for <ipv6@ietf.org>; Tue, 09 Feb 2016 05:12:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=aprI35gtyYcRO/aFygHNV1fFwkqQ3NM6f0kwBF6ImaQ=; b=XOwUYpLxAOfoSq1xqJueI5GwBK7OGtxrhLTfYRJYUK6m0JYE4aRSS7VwE0TnEEhbyq QfAnXBENK5vn9G2mVKBfZ+URJqeVVkDtPMSmDfE2yHKshNaoyrAAUI3mMbASaj+7qCNR g1JvP6NlpyNv6SMAhhUF78glNb6+4DxcMkbJvRf9Lw7iD1zWsvGMbFACYFlYhbChHlJF buJ5nLXtyLrQrbS6xm8JhGrXqCCV458jagB+oaDlu8Ky/BqbGhm29EX4qJhlMB7kLjYa bUkLjSX3uO8W8ql251/k0+kxz1egV0eFmi89t/tIKPUUjanw/oaDjIRtZEC784RIAtgh YM2g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=aprI35gtyYcRO/aFygHNV1fFwkqQ3NM6f0kwBF6ImaQ=; b=NY7TMERhNl52mupqFmqtkHew+S4BpZ+HOUJqnEQJoGjCPNbt1MgOQTWKlDEDc/wHNC sgdtMWDMemLepey0t+AKy6BguUhCvAyjcD443nyDDJqjKuokCql4mCJYCYi3lULdeB2H 2/QwTaZDbOh6XyIKnhaT5JruOAJqJFrK0NvYPBu333MXI7BBZOlCZoz6YQSCwYvBDbev Fj09TsrIePSE+Cn2O3XvC+i7PLNGwcbkLN+TAKYKp2Fxh60k+GJilAsgVJkD4ViDPzWb gm35eztfcyrFjF0iVsPZn6drhZ8e7zW20AViJrxFliaYdI8noVMPnXMShBZN0oMuD/TH zY/w==
X-Gm-Message-State: AG10YOSk7xeUlKGMT13euKMyBLw0LhIG/fpBEEgZEAUVYO18V7Doa/RC+AYTTe9Yl/O6cQ==
X-Received: by 10.55.25.150 with SMTP id 22mr10741511qkz.15.1455023545605; Tue, 09 Feb 2016 05:12:25 -0800 (PST)
Received: from [172.24.248.18] (dyn32-131.checkpoint.com. [194.29.32.131]) by smtp.gmail.com with ESMTPSA id 50sm3170561qgh.15.2016.02.09.05.12.23 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 09 Feb 2016 05:12:24 -0800 (PST)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_ABAFE858-9E7C-46F5-80F2-495C5FD8FBBA"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <20160206134831.0ef1c371@envy>
Date: Tue, 9 Feb 2016 15:12:21 +0200
Message-Id: <B6FF8CB1-1A3D-42A7-9715-03937C6A223A@gmail.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <20160206134831.0ef1c371@envy>
To: Tore Anderson <tore@fud.no>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ffYzNW6cLuit1x5TL6ooWV-SdGM>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 13:12:28 -0000

--Apple-Mail=_ABAFE858-9E7C-46F5-80F2-495C5FD8FBBA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Tore,

> On Feb 6, 2016, at 2:48 PM, Tore Anderson <tore@fud.no> wrote:
>=20
> * otroan@employees.org
>=20
>> This message starts a two week 6MAN call on adopting:
>>=20
>> Name:	draft-hinden-6man-rfc1981bis-01
>> Title:	Path MTU Discovery for IP version 6
>> Document date:	2015-12-01
>> Pages:	16
>> URL:         =
https://datatracker.ietf.org/doc/draft-hinden-6man-rfc1981bis/
>> Htmlized:  =
https://tools.ietf.org/html/draft-hinden-6man-rfc1981bis-01
>> Diff:          =
https://tools.ietf.org/rfcdiff?url2=3Ddraft-hinden-6man-rfc1981bis-01.txt
>>=20
>> as a working group item. Substantive comments and statements of =
support
>> for adopting this document should be directed to the mailing
>> list. Editorial suggestions can be sent to the authors.
>=20
> I support adoption.
>=20
> I see one issue that I would like to remind the WG about:
>=20
>   A node MUST NOT reduce its estimate of the Path MTU below the IPv6
>   minimum link MTU.
>=20
> -     Note: A node may receive a Packet Too Big message reporting a
> -     next-hop MTU that is less than the IPv6 minimum link MTU.  In =
that
> -     case, the node is not required to reduce the size of subsequent
> -     packets sent on the path to less than the IPv6 minimun link MTU,
> -     but rather must include a Fragment header in those packets
> -     [I-D.ietf-6man-rfc2460bis].
>=20
> The lines prefixed with "-" have been removed in -01. In my opinion,
> this leaves the text in an ambiguous state. What is a node conforming
> to -01 expected to do, when receiving a PTB reporting a next-hop MTU
> lower than 1280? I see two distinct options:
>=20
> a) Reduce its PMTU estimate to exactly 1280.
> b) Ignore the "invalid" PTB (retaining its previous PMTU estimate).
>=20
> I think it would be preferable to replace the removed paragraph with a
> clarification as to which behaviour is the correct and expected one. I
> do not know which one that would be, though.


My take is that by removing this text from rfc2460bis we are turning a =
ICMP PTB with MTU < 1280 into an error condition.  All IPv6 links are =
required to be 1280 or larger, so there isn=E2=80=99t any legitimate =
reason to reduce the MTU to less than 1280.   Based on this, I think =
rfc1981bis can say they should be ignored.

Also, my understanding is that rfc6145bis no longer generates ICMP PTB =
with MTU < 1280.  This makes rfc2460bis, rfc1981bis, and rfc6145bis all =
consistent.

Bob













--Apple-Mail=_ABAFE858-9E7C-46F5-80F2-495C5FD8FBBA
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJWueW1AAoJEK7rdBF357uouggIALhj/5AD5g/Z+xe5qYPIQVoL
F7CHQPcwxH2ZuL9w4BQpnNyI8Iy28iNUxYiNIc7odtUfMb1ZcsILNpTWCLfXMVX2
LvpOgUNFmPiQuFsp9j+MiH/y2qUUYY2L2+eRS7PbFiT1aEV1hsFtADJ5Cqeh7IE3
t0Kube+I1GRDyhedrQtmd9oPc2twYnAAhfM2jSYr1u2vLUbNsTfUbthDcKSh0zMr
J95GEv9J93P46ECcgs7+uzaWUmavwEAymHZBwhnfjTieHt4/eGkct0d7HRbWO2uy
ETMvwm/iPaTk2tVDtod00XANxtANawy7l3Epj6fDgTKzgPQnCeCyTohzVRd0Bms=
=ePif
-----END PGP SIGNATURE-----

--Apple-Mail=_ABAFE858-9E7C-46F5-80F2-495C5FD8FBBA--


From nobody Tue Feb  9 05:38:44 2016
Return-Path: <tore@fud.no>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A0801A9006 for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 05:38:35 -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, RP_MATCHES_RCVD=-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 vRRXiZeMdE6w for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 05:38:32 -0800 (PST)
Received: from greed.fud.no (greed.fud.no [IPv6:2a02:c0:1001:100::145]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C390E1A9030 for <ipv6@ietf.org>; Tue,  9 Feb 2016 05:38:29 -0800 (PST)
Received: from [2a02:c0:2:1:1194:17:0:1029] (port=37152 helo=echo.ms.redpill-linpro.com) by greed.fud.no with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from <tore@fud.no>) id 1aT8Uq-0008SD-5D; Tue, 09 Feb 2016 14:38:24 +0100
Date: Tue, 9 Feb 2016 14:38:23 +0100
From: Tore Anderson <tore@fud.no>
To: Bob Hinden <bob.hinden@gmail.com>
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Message-ID: <20160209143823.14d3fd59@echo.ms.redpill-linpro.com>
In-Reply-To: <B6FF8CB1-1A3D-42A7-9715-03937C6A223A@gmail.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <20160206134831.0ef1c371@envy> <B6FF8CB1-1A3D-42A7-9715-03937C6A223A@gmail.com>
X-Mailer: Claws Mail 3.13.1 (GTK+ 2.24.29; x86_64-redhat-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Y8MLMK950qC0F2VvjecgbQpjaWw>
Cc: IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 13:38:35 -0000

Hi Bob,

> My take is that by removing this text from rfc2460bis we are turning
> a ICMP PTB with MTU < 1280 into an error condition.  All IPv6 links
> are required to be 1280 or larger, so there isn=E2=80=99t any legitimate
> reason to reduce the MTU to less than 1280.

The exception would be packets coming through a 6145-not-bis
translator, as I explained in my reply to Brian. But I doubt that many
of these will be seen in the wild anyway, so I think it is OK to just
ignore that temporary corner case and focus on the desired end state
(with three consistent bis documents).

> Based on this, I think rfc1981bis can say they should be ignored.

I'd be fine with that (as long as it is clearly and unequivocally
stated).

> Also, my understanding is that rfc6145bis no longer generates ICMP
> PTB with MTU < 1280.  This makes rfc2460bis, rfc1981bis, and
> rfc6145bis all consistent.

I concur.

Tore


From nobody Tue Feb  9 06:49:58 2016
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 040B01A90B0 for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 06:49: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 HE3yZTSlum1W for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 06:49:55 -0800 (PST)
Received: from mail-qg0-x22c.google.com (mail-qg0-x22c.google.com [IPv6:2607:f8b0:400d:c04::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8CF611A90AA for <ipv6@ietf.org>; Tue,  9 Feb 2016 06:49:55 -0800 (PST)
Received: by mail-qg0-x22c.google.com with SMTP id y89so67927463qge.2 for <ipv6@ietf.org>; Tue, 09 Feb 2016 06:49:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :message-id:references:to; bh=TMedHKAhZg5qfo9wbpujb11ZHC244TqgAk1uQl9y3Kk=; b=IqwD2fuq8AA3N6GXAN6Di/AoDCugdkqqYw6+3W/KKcu5hqPaix2bERiVSZyj40aRIo PBs2n5LSuYJNDxIUoNWYo0RwQ/IAOfF//s6YP9dDOHnytPam0yHdeCGWXuD+1EcHBDzD J/an9a2yPzGF+Ye5neKm2tsIH+6HVdLRIKRtwy009MqTuecbpA2T3gD5XFYNW4eNnPq2 Jrlfo8B3aAA3yIafJfvVvwUO038Ez+IABxB8Z4NcLzNS/iXVK6vGkAQS6rZfvCGhaypw E4BfMOx3Fpl1qxMukda7AOfY/mZANZ9tDNDXI3HG461wj+Zx9GWcEaUKertWv6bpVKkL SuiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=TMedHKAhZg5qfo9wbpujb11ZHC244TqgAk1uQl9y3Kk=; b=RJeLMGZ8EsR2o4U//SsGOHFsF2f8EYTUX++p1nkEaP4cPtLebX1/CbG0vAVPaMRBDY FcLs+zXgwjzm5nArcDbBNdsZnlXeAJ5SFyh8uQmMw//8YtEe1lxYKmhpHXRdhvb/1l2k V69I6rLcnczcR0TWXtdLoKbd6L/dV1TMuTbfzoMetamSgo+8AF6sG9OJmxYDROZjMivA wN2nukpn4JMc5sWrYRR+Bhw7GLDwBpBLRJ1Z0VrwHd9PBY+z7LtInEIeWqAuZiOa0EFa KWqupbxyk4a/Yc4FPJjTtAFaT6nbwvsluprWAMOwaDtQgcGwk/ITzWqpYZPZjU8fWNNN m6jA==
X-Gm-Message-State: AG10YOS22zPsEtlbrOJJ/Xxsr/sBYlPVti1ANE75hQ769Us7K5GdmeDfP/VArs4qxtTFaQ==
X-Received: by 10.140.235.137 with SMTP id g131mr44902571qhc.43.1455029394664;  Tue, 09 Feb 2016 06:49:54 -0800 (PST)
Received: from [172.24.248.18] (dyn32-131.checkpoint.com. [194.29.32.131]) by smtp.gmail.com with ESMTPSA id j67sm15860909qgj.35.2016.02.09.06.49.51 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 09 Feb 2016 06:49:52 -0800 (PST)
Subject: Re: 6MAN: Adoption call on draft-hinden-6man-rfc1981bis-01
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: multipart/signed; boundary="Apple-Mail=_14A2C267-9FB7-4A6E-A733-D8B832A72C13"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5.2
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <20160209143823.14d3fd59@echo.ms.redpill-linpro.com>
Date: Tue, 9 Feb 2016 16:49:48 +0200
Message-Id: <FA6C7CDA-11C8-496B-AD3A-85AF6F007654@gmail.com>
References: <9C0F366C-4887-4A63-8422-1C370F9CBD3E@employees.org> <20160206134831.0ef1c371@envy> <B6FF8CB1-1A3D-42A7-9715-03937C6A223A@gmail.com> <20160209143823.14d3fd59@echo.ms.redpill-linpro.com>
To: Tore Anderson <tore@fud.no>
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/PnMD8i8kGhjSLdK8zNuvpxIoaAk>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 14:49:57 -0000

--Apple-Mail=_14A2C267-9FB7-4A6E-A733-D8B832A72C13
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Tore,

> On Feb 9, 2016, at 3:38 PM, Tore Anderson <tore@fud.no> wrote:
>=20
> Hi Bob,
>=20
>> My take is that by removing this text from rfc2460bis we are turning
>> a ICMP PTB with MTU < 1280 into an error condition.  All IPv6 links
>> are required to be 1280 or larger, so there isn=E2=80=99t any =
legitimate
>> reason to reduce the MTU to less than 1280.
>=20
> The exception would be packets coming through a 6145-not-bis
> translator, as I explained in my reply to Brian. But I doubt that many
> of these will be seen in the wild anyway, so I think it is OK to just
> ignore that temporary corner case and focus on the desired end state
> (with three consistent bis documents).

Also, a translator that relies on ICMP PTB messages arriving all of the =
time, is going to have other problems.

>=20
>> Based on this, I think rfc1981bis can say they should be ignored.
>=20
> I'd be fine with that (as long as it is clearly and unequivocally
> stated).
>=20
>> Also, my understanding is that rfc6145bis no longer generates ICMP
>> PTB with MTU < 1280.  This makes rfc2460bis, rfc1981bis, and
>> rfc6145bis all consistent.
>=20
> I concur.

I will work on some text in the next version of the draft.

Thanks,
Bob


>=20
> Tore


--Apple-Mail=_14A2C267-9FB7-4A6E-A733-D8B832A72C13
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJWufyNAAoJEK7rdBF357uosr4H/1MMmsTWDD553Ca1NhOheSAU
gdlfmdkMezy+xaJiNC9R1dBsVgadToLd2AoB2hAE7F+h7QYZ6tM/H/8gAVvPDtGP
GV9/GhzNLx8DwC7+K0m8aAb1rmrRLt8c6tXS0Sjh9GLZU23a3bYLBVjI0bDFbthX
5Pv7wT3TUkpb8tOV+P7vGmHKdhK12XE1ZVMxhdf9gv40kac6L7Y4Ykqrof53o3Bb
V+Kd0fEiWHxhNc4DpQi+FE6LEEAI7ISq+dcohxl6yzbbxMKC2l3TZwqAWEEtFT3W
1XUVwwuOq++x95nxPyHfmmnWXL6mNpPnKoqNaa+n/pWdQPSNyA+gG3eWbTuULOM=
=URA/
-----END PGP SIGNATURE-----

--Apple-Mail=_14A2C267-9FB7-4A6E-A733-D8B832A72C13--


From nobody Tue Feb  9 10:53:39 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9B241ACE51 for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 10:53:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 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, J_CHICKENPOX_12=0.6, 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 CXbhVRA2howi for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 10:53:36 -0800 (PST)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CF311ACE4C for <ipv6@ietf.org>; Tue,  9 Feb 2016 10:53:36 -0800 (PST)
Received: by mail-pa0-x22d.google.com with SMTP id ho8so95434841pac.2 for <ipv6@ietf.org>; Tue, 09 Feb 2016 10:53:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=v839ZQ3Y6iZTx7/siQkXpeFcb7EbjU+2yhyuoH9OP+A=; b=cOijuYYP1j+Eaqmc7tjj5WnVV4nN9VNRnEVGRcXLutOT7X2YpQKsyFV8sPqGsFbKAT ruGDgbB9TTVjLp6mo+1Kn3WLDZIncaRIrxNE6zRNlzRnuNls9R+K9SrzD8wIlTXNP9JB cAo3/Kjh5da63QNEg2GuwO2gVFuXePjXHO7quaY/EsdVMUJPlq6bN+MmjHtw0B4ADloC nYMg6qzS+neanJukBL5LWRJByylVihFd9ROt/nRZmWl0oyS/FlmIdxrFVUdfjAIvDHVu 2OuvRDDuQXOcyOpl6DMLEiRr3caNRBW0+nBP3zXeXGTnftClJtip5uw+qhaLYVcccK11 JuYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=v839ZQ3Y6iZTx7/siQkXpeFcb7EbjU+2yhyuoH9OP+A=; b=Vi4MyfOldb6L38nJetisGzarh42FYggAy8HT6OX3uwK7nM2sgERTVYcchKhiDbPGsE 8l40DQmof4hg7K5p+ONt8YsA/LpPuJsZxqNhLDyDfUe3ajL/NO02mKSGGnARHOVJMd0t Y/zwKo0SbAH98vc4gvRHxzil8efXxCZzb18KbwTv5PYiR0a8hTjopURF62qOQtQTu7Cc 7dW5cbe9UWOaoGm76AitRCcLurkYktNnzAKvCV3RKYqgdW9aw4W9eBTnqZrcNTt6WpiV b147lqWH0fpKCSItN92c3/4xx579UUcGJdxl2nxapekqIdoBWjlS7bjSWFWy1i6qWcxr YIgw==
X-Gm-Message-State: AG10YORe6TELQPX+vu28U3akjbm0xbpGxcv1kG02bhBkGQ6Cqzx5zny0dwmxYuKxC2SvZg==
X-Received: by 10.66.235.36 with SMTP id uj4mr53478655pac.85.1455044015842; Tue, 09 Feb 2016 10:53:35 -0800 (PST)
Received: from ?IPv6:2406:e007:59fb:1:28cc:dc4c:9703:6781? ([2406:e007:59fb:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id a21sm52303388pfj.40.2016.02.09.10.53.31 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 09 Feb 2016 10:53:34 -0800 (PST)
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
To: Fernando Gont <fgont@si6networks.com>, Tim Chown <tjc@ecs.soton.ac.uk>
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com> <56B4FF9D.10203@gmail.com> <5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <EMEW3|5048bb3e4f22902e3e9b18a621e7fd32s16H1H03tjc|ecs.soton.ac.uk|5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <56B7915D.2060300@gmail.com> <56B9C841.9020908@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56BA35B0.3040701@gmail.com>
Date: Wed, 10 Feb 2016 07:53:36 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B9C841.9020908@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/_zRpcS8dIGt-8S5P0ycW8Anj2_s>
Cc: 6man WG <ipv6@ietf.org>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 18:53:37 -0000

On 10/02/2016 00:06, Fernando Gont wrote:
> On 02/07/2016 03:47 PM, Brian E Carpenter wrote:
>> On 08/02/2016 05:59, Tim Chown wrote:
>>> On 5 Feb 2016, at 20:01, Brian E Carpenter <brian.e.carpenter@gmail.c=
om> wrote:
>>>>
>>>> On 06/02/2016 07:20, Fernando Gont wrote:
>>>>> On 02/05/2016 03:07 PM, otroan@employees.org wrote:
>>>>>> Fernando,
>>>>>>
>>>>>> [...]
>>>>>>
>>>>>>>>
>>>>>>>> What is the risk of using the same IID for link-local and global=
 addresses?
>>>>>>>> Typically if you can snoop the link-local address then you're on=
link and leak information about all addresses and their correlations anyw=
ay.
>>>>>>>
>>>>>>> We discussed this one a hundred times now (including for RFC7217)=
=2E The
>>>>>>> risk is that at times such addressess can leak, without the need =
of the
>>>>>>> attacker being pesent on the local link.
>>>>>>>
>>>>>>> e.g., your MTA is on the local-link, and you end up connecting to=
 it
>>>>>>> with a LL, which then appears in the email headers. (and there ar=
e a
>>>>>>> bunch of other possible reasons for that to happen).
>>>>>>>
>>>>>>> Be proactive. MAC addresses in the IID are wrong. Putting them th=
ere is
>>>>>>> just waiting for trouble.
>>>>>>
>>>>>> I didn't say the LL was based on a MAC.
>>>>>> my question was if there was any issue with re-using the IID from =
the link-local in the GUA. assume the link-local is generated f.ex with 7=
217.
>>>>>
>>>>> Oops, my apologies. My answer would be "It unnecessarily enables
>>>>> correlation of the activities that you carry between the two addres=
ses".
>>>>>
>>>>> i.e., by simply inspecting the IID I could easily tell that the
>>>>> activities carried out with one address were performed by the same =
node
>>>>> that employed the other address.
>>>>>
>>>>> My take here is, again: be proactive. If there's no requirement (an=
d
>>>>> there isn't) for the two IIDs to be the same, then make them differ=
ent,
>>>>> and fail on the safe side.
>>>>
>>>> But Ole's point was that any observer who sees a LL packet is on-lin=
k and
>>>> can therefore see the MAC address anyway; an observer who can see MA=
C addresses
>>>> can just laugh at RFC 7217 or RFC 4941.
>>>
>>> Well, except that the device might be varying its MAC address as well=
=2E
>>>
>>> I thought RFC7217 states that a device is expected to have a differen=
t IID for=20
>>> each prefix on an interface. (Though whether there=E2=80=99s a Networ=
kID available to
>>> seed a different LL IID per visited network is another question, else=
 the device
>>> presumably has the same LL IID as it moves?)
>>>
>>> There=E2=80=99s definitely value in avoiding correlation. If there=E2=
=80=99s an equal cost either=20
>>> way, why allow such potential?
>>
>> Extra code? But my real concern is that there might be unintended side=
 effects,
>> because the interface identifier will no longer identify an interface.=

>=20
> Not really. RFC7217 automagically achieves that.

Let me be even clearer about my concern; then I will shut up:

I fully agree that from a privacy point of view, it is better to use
a different IID for link-local and for each GUA prefix (including each
ULA prefix). I'm not aware of anywhere in the IETF standards that this
will lead to a problem. However, I am concerned that in some IPv6 network=
s,
especially networks running with only one GUA prefix (which is most of
them) there are operational practices and/or locally written scripts
that *assume* the same IID is used for all prefixes on a given interface.=

After all, that has been the case for all IPv6 stacks for many years.

    Brian


From nobody Tue Feb  9 11:14:04 2016
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1B3D1ACE8C for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 11:14:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JBxBwoIZxgED for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 11:14:00 -0800 (PST)
Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E3CE1ACE7F for <ipv6@ietf.org>; Tue,  9 Feb 2016 11:14:00 -0800 (PST)
Received: by mail-ig0-x22e.google.com with SMTP id y8so59752762igp.0 for <ipv6@ietf.org>; Tue, 09 Feb 2016 11:14:00 -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=WuFoKsBUjzrH9lniM8wZxIH5d5cuUTBdeupg0Ouphbg=; b=GO50A38VESjGQLtmV7xZlaUdz7F1PqnQqNGyXe2kgwYkpl1lIJgzAvPu3LUPAjVZ7m tqyKSmZX/lz+1hPYhpevmWXkeBtZMPKgvlOcRPWcqarrkODI9jLZSTUZtsMOz+kD9434 IHizYe2OVm+LF/jLzqe8EG/sUS1Jyr3FEzcbnjvhuqc82vD6qiL2sAC5gTnMrLni31Dw xvLdRRgnxSNFrtPXd48UBc2Y5Lf4Md5Rvcj5t0D8COFObbXBYXn7AvYhrBHIH1+XYPkY mNfNWBz4QMVCimdUk2tWENzRdtxJhq1JhPFTZ4SRYqIDtXQ3YrKzZEM97J7e0Pn3Xq5G 2Kqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=WuFoKsBUjzrH9lniM8wZxIH5d5cuUTBdeupg0Ouphbg=; b=NVJDCV0Z96PHgO+cwXyS8IH4YSzsuPSgrvtQ0L4iVarM7joh9NYicGVne6hp6bRyzw 82i5zrzCS05OZB5tYMlHn4RJGwIXxFJGOLoQ92QpoewxpQ95sVIlH2pXUCTMiSlGmsbr BtJNX4lk+5O9dY/jje7NzjJx6g2K6fyvJX7GotyWvMOAt8Xbp7K2+yupZ/HVVdQ67HHq bBh30pA8mIMBaUsrQcMdgXH+Ja6TWUq67GsfRKJzLT2mz5qJjsZfoAu9wwe28GLQbh+X rLZKcw1/t0fmcNO9TUhzwwNnznXiid/ynRAgvvfZCaLvBXAg4AVOnHz7nUBi9eDVECBF CAWw==
X-Gm-Message-State: AG10YOS9gIroubBNzkoRzHOQpP928h+NqMruYMmbFKoWNNUg15Hqpf+Hx/OVJk/fE5Tngid/GpG6pa1BbOT8Lw==
MIME-Version: 1.0
X-Received: by 10.50.64.243 with SMTP id r19mr5530084igs.41.1455045240005; Tue, 09 Feb 2016 11:14:00 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.169.35 with HTTP; Tue, 9 Feb 2016 11:13:59 -0800 (PST)
In-Reply-To: <56B4F674.5050207@gmail.com>
References: <2052A806-4D40-4A17-9892-90E39B67C65C@gmail.com> <CAJE_bqekFsfHPkfLTAOHgdL-MpvwNSV=gB8Cv0x+YrD66JUyMg@mail.gmail.com> <56B3D4BF.9000202@gmail.com> <CAJE_bqczUQ1UX=mLBzd=XpoKDjO616NrO4iQYZvK7T7CFVzXOQ@mail.gmail.com> <56B4F674.5050207@gmail.com>
Date: Tue, 9 Feb 2016 11:13:59 -0800
X-Google-Sender-Auth: Y7SQyjJ77U2oUTiGBgv2cAS1GsE
Message-ID: <CAJE_bqe5fXZKJpekmDCtVxGBVn3Jv9VtDtoUGWhu+HNV6M1X=g@mail.gmail.com>
Subject: Re: 6MAN WG Last Call - draft-ietf-6man-multi-homed-host-03.txt
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/nxFzhEry2jwFMMl-_I6YuMUVFg8>
Cc: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 19:14:02 -0000

At Sat, 6 Feb 2016 08:22:28 +1300,
Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

> >>>   I'm not sure if I can understand the "or a Default Router List"
> >>>   part.  If it means 'Router Advertisement may contain...a Default
> >>>   Router List', it doesn't make sense since an RA (or any of its
> >>>   options) doesn't contain such a list (Default Router List is
> >>>   something that a host maintains based on the content of RA).
> >>
> >> I think you're correct.
> >
> > Then I guess the sentence will have to be revised, but I can't suggest
> > anything specific as I don't understand the original intent.  Does
> > this "Default Router List" perhaps actually means the source IPv6
> > address of the RA (which will be maintained in the Default Router List
> > of the receiving host)?
>
> I think we should simply delete ", or a Default Router List". That list
> is created and maintained by the host, as you say.

Okay, then my personal suggestion for the entire paragraph would be:

   As described in [RFC4191] and [RFC4861], a Router Advertisement may
   contain zero or more Prefix information Options (PIOs), or zero or more
   Route Information Options (RIOs).  In their
   original intent, these indicate general information to a host: "this
   is your default router", "you might create an address in this
   prefix", or "this router would be a good place to
   send traffic directed to a given destination prefix".  In a multi-
   homed network implementing source/destination routing, the
   interpretation of default router or an RIO has to be modified
   with the words "if the source address is in one of the prefixes I
   advertise in a PIO".  Additionally, the PIO must be reinterpreted to
   also imply that the advertising router would be a reasonable first
   hop for any packet using a source address in any advertised prefix.

--
JINMEI, Tatuya


From nobody Tue Feb  9 11:17:53 2016
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7821D1ACE89 for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 11:17:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.622
X-Spam-Level: 
X-Spam-Status: No, score=-0.622 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_12=0.6, RP_MATCHES_RCVD=-0.001, 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 YkHvJOJK8q7N for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 11:17:50 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46E161ACE7F for <ipv6@ietf.org>; Tue,  9 Feb 2016 11:17:50 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u19JHlOL015761; Tue, 9 Feb 2016 19:17:47 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u19JHlOL015761
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1455045467; bh=JP2pse5MSV8irw1tmDoiLmp9ZAg=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=HiyJ4/mW9TvqhkCTkB0WzDnqge+etSnBz4rMxVrTVfEGQscqtsIcbX2/szeRLPKFz vT6U7gahU4XwtMBQd/frOYqBcieONYTvUvwfrmXjDs8EJ+gz+MDcaOnqPTpLqjQw7u FQcTJhd3YeBggjIL71cjHy7g3KQMf0ReoibiH2yE=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s18JHl1463910259UU ret-id none; Tue, 09 Feb 2016 19:17:47 +0000
Received: from [192.168.0.10] (tchowndsl.claranet.co.uk [212.188.254.49]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u19JGRMm024014 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Feb 2016 19:16:27 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <56BA35B0.3040701@gmail.com>
Date: Tue, 9 Feb 2016 19:16:27 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|36396e79e5fba14ce0e242fd915dbd56s18JHl03tjc|ecs.soton.ac.uk|42ACE220-DB6F-4825-BED0-F7A526A1F1EF@ecs.soton.ac.uk>
References: <56B48386.2040300@gmail.com> <FFCCFC5D-CE7C-41A3-BCC3-A7BCAC9BC63C@employees.org> <56B4CD9F.9090606@si6networks.com> <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com> <56B4FF9D.10203@gmail.com> <5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <EMEW3|5048bb3e4f22902e3e9b18a621e7fd32s16H1H03tjc|ecs.soton.ac.uk|5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <56B7915D.2060300@gmail.com> <56B9C841.9020908@si6networks.com> <56BA35B0.3040701@gmail.com> <42ACE220-DB6F-4825-BED0-F7A526A1F1EF@ecs.soton.ac.uk>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3112)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s18JHl146391025900; tid=s18JHl1463910259UU; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=4:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u19JHlOL015761
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/6S4BuZ0KFoGAwWe_Fr18zFfZenk>
Cc: Fernando Gont <fgont@si6networks.com>, Alexandre Petrescu <alexandre.petrescu@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2016 19:17:52 -0000

> On 9 Feb 2016, at 18:53, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> On 10/02/2016 00:06, Fernando Gont wrote:
>> On 02/07/2016 03:47 PM, Brian E Carpenter wrote:
>>> On 08/02/2016 05:59, Tim Chown wrote:
>>>> On 5 Feb 2016, at 20:01, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>>>>>=20
>>>>> On 06/02/2016 07:20, Fernando Gont wrote:
>>>>>> On 02/05/2016 03:07 PM, otroan@employees.org wrote:
>>>>>>> Fernando,
>>>>>>>=20
>>>>>>> [...]
>>>>>>>=20
>>>>>>>>>=20
>>>>>>>>> What is the risk of using the same IID for link-local and =
global addresses?
>>>>>>>>> Typically if you can snoop the link-local address then you're =
onlink and leak information about all addresses and their correlations =
anyway.
>>>>>>>>=20
>>>>>>>> We discussed this one a hundred times now (including for =
RFC7217). The
>>>>>>>> risk is that at times such addressess can leak, without the =
need of the
>>>>>>>> attacker being pesent on the local link.
>>>>>>>>=20
>>>>>>>> e.g., your MTA is on the local-link, and you end up connecting =
to it
>>>>>>>> with a LL, which then appears in the email headers. (and there =
are a
>>>>>>>> bunch of other possible reasons for that to happen).
>>>>>>>>=20
>>>>>>>> Be proactive. MAC addresses in the IID are wrong. Putting them =
there is
>>>>>>>> just waiting for trouble.
>>>>>>>=20
>>>>>>> I didn't say the LL was based on a MAC.
>>>>>>> my question was if there was any issue with re-using the IID =
from the link-local in the GUA. assume the link-local is generated f.ex =
with 7217.
>>>>>>=20
>>>>>> Oops, my apologies. My answer would be "It unnecessarily enables
>>>>>> correlation of the activities that you carry between the two =
addresses".
>>>>>>=20
>>>>>> i.e., by simply inspecting the IID I could easily tell that the
>>>>>> activities carried out with one address were performed by the =
same node
>>>>>> that employed the other address.
>>>>>>=20
>>>>>> My take here is, again: be proactive. If there's no requirement =
(and
>>>>>> there isn't) for the two IIDs to be the same, then make them =
different,
>>>>>> and fail on the safe side.
>>>>>=20
>>>>> But Ole's point was that any observer who sees a LL packet is =
on-link and
>>>>> can therefore see the MAC address anyway; an observer who can see =
MAC addresses
>>>>> can just laugh at RFC 7217 or RFC 4941.
>>>>=20
>>>> Well, except that the device might be varying its MAC address as =
well.
>>>>=20
>>>> I thought RFC7217 states that a device is expected to have a =
different IID for=20
>>>> each prefix on an interface. (Though whether there=E2=80=99s a =
NetworkID available to
>>>> seed a different LL IID per visited network is another question, =
else the device
>>>> presumably has the same LL IID as it moves?)
>>>>=20
>>>> There=E2=80=99s definitely value in avoiding correlation. If =
there=E2=80=99s an equal cost either=20
>>>> way, why allow such potential?
>>>=20
>>> Extra code? But my real concern is that there might be unintended =
side effects,
>>> because the interface identifier will no longer identify an =
interface.
>>=20
>> Not really. RFC7217 automagically achieves that.
>=20
> Let me be even clearer about my concern; then I will shut up:
>=20
> I fully agree that from a privacy point of view, it is better to use
> a different IID for link-local and for each GUA prefix (including each
> ULA prefix). I'm not aware of anywhere in the IETF standards that this
> will lead to a problem. However, I am concerned that in some IPv6 =
networks,
> especially networks running with only one GUA prefix (which is most of
> them) there are operational practices and/or locally written scripts
> that *assume* the same IID is used for all prefixes on a given =
interface.
> After all, that has been the case for all IPv6 stacks for many years.

But those scripts will already fail if correlating privacy addresses =
with others.

It would be interesting to ask on a v6 operators list whether anyone =
really does
make that assumption in scripts, whether their own or in open source =
packages.
If there are any, they=E2=80=99ll probably disable 7217 anyway to have =
MAC-based=20
addresses to correlate IPs and MACs (however good an idea that is).

Tim=


From nobody Tue Feb  9 16:41:17 2016
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 801771B3318 for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 16:41:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.199
X-Spam-Level: 
X-Spam-Status: No, score=-1.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id t6rCjc06exoc for <ipv6@ietfa.amsl.com>; Tue,  9 Feb 2016 16:41:14 -0800 (PST)
Received: from mail-vk0-x22b.google.com (mail-vk0-x22b.google.com [IPv6:2607:f8b0:400c:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A920F1B32B8 for <ipv6@ietf.org>; Tue,  9 Feb 2016 16:41:14 -0800 (PST)
Received: by mail-vk0-x22b.google.com with SMTP id e185so2923924vkb.1 for <ipv6@ietf.org>; Tue, 09 Feb 2016 16:41:14 -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:content-transfer-encoding; bh=SBgikmdUsylEMGaQDLx8q56styZzjxnxpoutwfPxfLA=; b=vBLuUfklFQ2Wvuh+AyT+ceYg82eXAd95NV7XIe+s18592Smx/rEjzo23p8yj4ZXMd6 mq8bvSRnJDzpv6j5nYmgtG1d7jh1AmymM+bhNo1ZT1CMMVEGU7ZQPBj4uwyaj0S6kIPx tw5sPxQU8YGh1Ak7RI/9lLTdgtMpv/3s4Lcb4mvw9k2em9JHHvl0gc+6B4PdDOWOVe9s pIpiT/j2Ko749eW8EEFXQZpbQYF/Mezlq55V5T0ej3K966XJTXYL5YxycCy9z9x1g9A2 CBlpXcNTq8kjy3gXNtwuRIZhKDfnc8GXjMtedndTKFNfLqZrSCF+YotVWpNJxaIfFEfq mXIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=SBgikmdUsylEMGaQDLx8q56styZzjxnxpoutwfPxfLA=; b=m4SGWgGfJTUS7WZndD3OlBCVjsdn0M3flYXAHpugwEW9V3p+sJWG788pWDjm9GxU/5 l3tkmAy2vV9fynZy9SnginZRDVdAKT/bWSW2+Gp7ltVlfBZPAXSt/wvnDc9vME/ilRHK KCOggBRbyPm+vtv5aG2ZhZDutveFtxD05bS1idgYqgFmxfZjHk++CCb/i8IKVv6vD96+ PmLLRONSyXEMXJGqDHYCyTspfhm6ZxJBWlHhwv7ClGwJJxJGZ86pl6y3o7/AObZMEAuy Z84LaKSBI6t8QyMuF11NpjxgVlDTdZCujdK1XzIawtvHOJEjWCqvNgn9aUgjwdvN3U4O IHGw==
X-Gm-Message-State: AG10YOShxv385Vrdt5L9KRItnPMnlWpHQaYW/bQxGW833cpYGg50d6/tdw93uy+cEKRxOzFXvExCItEvfvZKHQ==
X-Received: by 10.31.167.195 with SMTP id q186mr27403088vke.113.1455064873797;  Tue, 09 Feb 2016 16:41:13 -0800 (PST)
MIME-Version: 1.0
Received: by 10.159.34.103 with HTTP; Tue, 9 Feb 2016 16:40:44 -0800 (PST)
In-Reply-To: <CAJE_bqe5fXZKJpekmDCtVxGBVn3Jv9VtDtoUGWhu+HNV6M1X=g@mail.gmail.com>
References: <2052A806-4D40-4A17-9892-90E39B67C65C@gmail.com> <CAJE_bqekFsfHPkfLTAOHgdL-MpvwNSV=gB8Cv0x+YrD66JUyMg@mail.gmail.com> <56B3D4BF.9000202@gmail.com> <CAJE_bqczUQ1UX=mLBzd=XpoKDjO616NrO4iQYZvK7T7CFVzXOQ@mail.gmail.com> <56B4F674.5050207@gmail.com> <CAJE_bqe5fXZKJpekmDCtVxGBVn3Jv9VtDtoUGWhu+HNV6M1X=g@mail.gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Wed, 10 Feb 2016 11:40:44 +1100
Message-ID: <CAO42Z2wWKjQM98jis=LF45gcavtjmRDMH7eqOZm35UPjewrJrA@mail.gmail.com>
Subject: Re: 6MAN WG Last Call - draft-ietf-6man-multi-homed-host-03.txt
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/q1uR6iN3csZfEpre0QBluVNk9tk>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2016 00:41:16 -0000

On 10 February 2016 at 06:13, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 <jinmei@=
wide.ad.jp> wrote:
> At Sat, 6 Feb 2016 08:22:28 +1300,
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>
>> >>>   I'm not sure if I can understand the "or a Default Router List"
>> >>>   part.  If it means 'Router Advertisement may contain...a Default
>> >>>   Router List', it doesn't make sense since an RA (or any of its
>> >>>   options) doesn't contain such a list (Default Router List is
>> >>>   something that a host maintains based on the content of RA).
>> >>
>> >> I think you're correct.
>> >
>> > Then I guess the sentence will have to be revised, but I can't suggest
>> > anything specific as I don't understand the original intent.  Does
>> > this "Default Router List" perhaps actually means the source IPv6
>> > address of the RA (which will be maintained in the Default Router List
>> > of the receiving host)?
>>
>> I think we should simply delete ", or a Default Router List". That list
>> is created and maintained by the host, as you say.
>
> Okay, then my personal suggestion for the entire paragraph would be:
>
>    As described in [RFC4191] and [RFC4861], a Router Advertisement may
>    contain zero or more Prefix information Options (PIOs), or zero or mor=
e
>    Route Information Options (RIOs).  In their
>    original intent, these indicate general information to a host: "this
>    is your default router",

Actually, only the router lifetime field indicates that the RA is
coming from a default router or not.

>"you might create an address in this
>    prefix", or "this router would be a good place to
>    send traffic directed to a given destination prefix".  In a multi-
>    homed network implementing source/destination routing, the
>    interpretation of default router or an RIO has to be modified
>    with the words "if the source address is in one of the prefixes I
>    advertise in a PIO".  Additionally, the PIO must be reinterpreted to
>    also imply that the advertising router would be a reasonable first
>    hop for any packet using a source address in any advertised prefix.
>



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


From nobody Wed Feb 10 02:04:32 2016
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D174D1A1A32 for <ipv6@ietfa.amsl.com>; Wed, 10 Feb 2016 02:04:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-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 bVIbLFlfahj2 for <ipv6@ietfa.amsl.com>; Wed, 10 Feb 2016 02:04:28 -0800 (PST)
Received: from cowbell.employees.org (cowbell.employees.org [IPv6:2001:1868:a000:17::142]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD8A01A1A31 for <ipv6@ietf.org>; Wed, 10 Feb 2016 02:04:28 -0800 (PST)
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 70C5AD7884; Wed, 10 Feb 2016 02:04:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=NXQKWOBN4t6aGklzFfl2k4epb5U=; b= RFc3Eh9AOWBwH3rCjus1UXqw5ruMNhWJv7romXXe6EPLDkUKIKAU2Pgb3s27qd6i a7r6ZSRneJU2zIpnKTmgOsM/Aw9eTd/VAoA3eDeU/QoEmCxxZ2Pke0TJVFIpZa2S 0CjeystmQoy7Q0zz2+jPykX//t0b85eFfHCiShfMhB4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=RLAeytWTRh2HiJv9qNpUQv6Fqq 0T8mgLpr/7u0kQYG3CGTk2CQtxpMwJeskOf5lENZD9FqmaiZC4msK4XVBZcXiL5E rPO/+7fNey2wJD0LAjmJQptKNwxLrdPw86PhoJKUtFZMR2q7b6RK3yWTUHHebiEc RszASsQ4uL0YBb/0s=
Received: from h.hanazo.no (cm-84.215.10.233.getinternet.no [84.215.10.233]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 37276D7883; Wed, 10 Feb 2016 02:04:28 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 2D43910B28DB; Wed, 10 Feb 2016 11:04:26 +0100 (CET)
Subject: Re: 6MAN Working group last call: draft-ietf-6man-rdnss-rfc6106bis
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Content-Type: multipart/signed; boundary="Apple-Mail=_E08DF7DF-58CF-4009-BB27-5A330DC80834"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.6b2
From: otroan@employees.org
In-Reply-To: <56B9DA5D.2080906@si6networks.com>
Date: Wed, 10 Feb 2016 11:04:25 +0100
Message-Id: <DB87BBB6-7047-4B82-993D-331B85120EE0@employees.org>
References: <6AC58C26-01B6-4C16-851F-0C1228CDD2AF@employees.org> <56B9DA5D.2080906@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/5ZpDFHL6300jMfCE_mlYB8dmft8>
Cc: bob.hinden@gmail.com, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2016 10:04:31 -0000

--Apple-Mail=_E08DF7DF-58CF-4009-BB27-5A330DC80834
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

>> This message starts a two week 6MAN Working Group Last Call on =
advancing:
>>=20
>>     Title    : IPv6 Router Advertisement Options for DNS =
Configuration
>>     Authors  : J. Jeong, S. Park, L. Beloeil, S. Madanapalli
>>     Filename : draft-ietf-6man-rdnss-rfc6106bis-06
>>     Pages    : 17
>>     Date     : 2015-10-09
>>=20
>>    https://tools.ietf.org/html/draft-ietf-6man-rdnss-rfc6106bis-06
>>=20
>> as a Proposed Standard.  Substantive comments and statements of =
support for publishing this document should be directed to the mailing =
list.  Editorial suggestions can be sent to the authors.  This last call =
will end on 23 February 2016.
>>=20
>> We would like this document to follow the experimental document =
shepherd procedure. We will need a volunteer document shepherd, before =
we can advance this document.
>=20
> I can volunteer for that if it helps.

Thank you!

Shepherding educational material is here:

http://ietf.org/edu/tutorials/document-editing-sheparding.pdf
https://tools.ietf.org/html/rfc4858
https://www.ietf.org/iesg/statement/document-shepherds.html

I have updated the state in the datatracker to reflect the document =
shepherd:
https://datatracker.ietf.org/doc/draft-ietf-6man-rdnss-rfc6106bis/

Best regards,
Ole


--Apple-Mail=_E08DF7DF-58CF-4009-BB27-5A330DC80834
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQIcBAEBCgAGBQJWuwspAAoJEL7aWKiYQt92/6wQAM0AyppOUlLm+DH3Kzg/1IbQ
ipFmYckw4oucQd1QoO5OPGFFGTbDWokpv0q+Ko2vmA6yxYHiXPEBRqXJV1iBHbSp
GXNApYHXL6nYKfCdmChPJyG/Qe0EeeyJOzh0Mk85MMsGZWSihGO5luBMgLwqo8ac
VZ6b2DwxR6KyXH+V65P03hCmgujUL7ctFVrWgM55aMiXb4jG6v92XlVKuShGZEjw
xvyjBXhaCXkLwK3h8GDuOjtL7AqvDjreSowKc0lGjJBYlCmriLNWepqu4ld0I4yr
7NnIZHhn9SNuGslZE2PQ4Noki+oUB44Fp9WbNxCPE7It8X0u4ZMQ0O/dIM0LecvX
+SIutixSvs71jciFyfMSnAQ3ckvYt1SQaIS6OQ3jb+p+Lu6Z8UfZ9qzPGFIU2g8j
tBOR8q9dwGbvrN8fkZIIpgc+1Ud4hTQEwTd5H8fn7ChmxkjInObSWiJ4Mq74KNCR
OjQ2dcI7xZtPVYmT6wVk1fsq/k11LY4310U4lR1xOypS2cZviq6uAUJSZSHQgsyF
+O80g4MNBGDZjXmj6V6rksZGYlnXkSgeW/8oRNIWwgn2CyeNJFHoB8xt4CHg4kHC
DGwV5++/he5PkwGrgXXCt+NYSImEyLyGm5ZaBKEI+3ZZDO6o1k5v21BzeeZZNFyF
zXrMYL82VFtvNcjqGuLT
=mQlY
-----END PGP SIGNATURE-----

--Apple-Mail=_E08DF7DF-58CF-4009-BB27-5A330DC80834--


From nobody Wed Feb 10 09:49:54 2016
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB3EA1B2DA9 for <ipv6@ietfa.amsl.com>; Wed, 10 Feb 2016 09:49:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7dlgG0Z_39iw for <ipv6@ietfa.amsl.com>; Wed, 10 Feb 2016 09:49:51 -0800 (PST)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 811961B2DA4 for <ipv6@ietf.org>; Wed, 10 Feb 2016 09:49:50 -0800 (PST)
Received: by mail-io0-x233.google.com with SMTP id g203so3841019iof.2 for <ipv6@ietf.org>; Wed, 10 Feb 2016 09:49:50 -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=UoEKJHKeN6m+NKTHgh5yPdXyAjemURRFgNeMYnCji0Q=; b=Lu2gVMjDoDWQeAGemoDaD4so9NNhSJk+9A+YsyWRtQC3S0E5OLtzQXdcNSTNVcoF/a q+BbKLu6xkKa7OIZOpTLOQkGzQJZFJxXbQ49j7pJqffHHIX53olSrO79lSq3L9FIKx/O vSPGeOH4hZkHM7eSkAqSTBv93EilFRKjdZ+wVOweyW7NtKk+8d7qzIWOi+5mn2zheETX kV/ZLI8xzwKN6rgU3hPg1kCy7U9yG48IakRoCC/v/sKShwE5CjnY2beLAdLA0nR2hxsA 3KFjfm0D0VNfex1zkqzt3+mVN/EMacgWxGJTIPnB+XbTNfSpYTppajYz1dLLUIXDnOcZ w2Hw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=UoEKJHKeN6m+NKTHgh5yPdXyAjemURRFgNeMYnCji0Q=; b=WGWAtFH/b6sH7J7ZgzcvH5QewOEzsqLiauZtkMIVdM8CoISkp78RZZV40UusZox2zj EQxMyxNtZehPw3P1n5kPEm2OaW7fthS1yG2UocZdFKqAF2Kavznl38afZMS9qh4ou1F1 dJeGj8H2Je/UdBhXFpuB4KiLOvWAfKT/apIRVo7z00Bcf+6E+NrBbl4itzyS4VV4Zi96 YcC0PEgJkOWdwBrrXp+Pexoe0Mgxk+iDtCUql0FOrJF9+bC2Vgys2xmXQbgt8RNKtH1E IBU/HG72azQy57czLdtu7F6y3tpuY9JhprVm4WgFrJfj3XqIWQJv/5mOWupQBpXjKX4a 8e7Q==
X-Gm-Message-State: AG10YORp4gLC8JlODaAQWxdmn0166aZpWBhjTUSDaXLwr/wwU19exR/8FUbd1lnOS4x8Lzb3Bw04QBYXCnvpvg==
MIME-Version: 1.0
X-Received: by 10.107.198.197 with SMTP id w188mr37651166iof.178.1455126589878;  Wed, 10 Feb 2016 09:49:49 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.169.35 with HTTP; Wed, 10 Feb 2016 09:49:49 -0800 (PST)
In-Reply-To: <CAO42Z2wWKjQM98jis=LF45gcavtjmRDMH7eqOZm35UPjewrJrA@mail.gmail.com>
References: <2052A806-4D40-4A17-9892-90E39B67C65C@gmail.com> <CAJE_bqekFsfHPkfLTAOHgdL-MpvwNSV=gB8Cv0x+YrD66JUyMg@mail.gmail.com> <56B3D4BF.9000202@gmail.com> <CAJE_bqczUQ1UX=mLBzd=XpoKDjO616NrO4iQYZvK7T7CFVzXOQ@mail.gmail.com> <56B4F674.5050207@gmail.com> <CAJE_bqe5fXZKJpekmDCtVxGBVn3Jv9VtDtoUGWhu+HNV6M1X=g@mail.gmail.com> <CAO42Z2wWKjQM98jis=LF45gcavtjmRDMH7eqOZm35UPjewrJrA@mail.gmail.com>
Date: Wed, 10 Feb 2016 09:49:49 -0800
X-Google-Sender-Auth: TV9j01IOic3Xayc1dO9SQTefEFo
Message-ID: <CAJE_bqcUXoOQwEYkOSzqb5NYfL6npPBaXibTojPpiORGYBH0hQ@mail.gmail.com>
Subject: Re: 6MAN WG Last Call - draft-ietf-6man-multi-homed-host-03.txt
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/_25DvQvVvjYYMxsv7CD4XTpnlF0>
Cc: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2016 17:49:53 -0000

At Wed, 10 Feb 2016 11:40:44 +1100,
Mark Smith <markzzzsmith@gmail.com> wrote:

> > Okay, then my personal suggestion for the entire paragraph would be:
> >
> >    As described in [RFC4191] and [RFC4861], a Router Advertisement may
> >    contain zero or more Prefix information Options (PIOs), or zero or more
> >    Route Information Options (RIOs).  In their
> >    original intent, these indicate general information to a host: "this
> >    is your default router",
>
> Actually, only the router lifetime field indicates that the RA is
> coming from a default router or not.

Right, and "this" in "this is your default router" is actually (or
more accurately) the source IPv6 address of the Router Advertisement,
rather than something "contained" in it (as an option).  So the above
suggested text could still sound a bit awkward, but to me it seemed
just good enough and trying to make it super accurate wouldn't be
worth the resulting verbosity.  If you want to make it perfect,
though, I'm not opposed to it - feel free to suggest your own text.

--
JINMEI, Tatuya


From nobody Wed Feb 10 11:30:16 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 693AD1B2EDB for <ipv6@ietfa.amsl.com>; Wed, 10 Feb 2016 11:30:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 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, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4QeOPTFda9T7 for <ipv6@ietfa.amsl.com>; Wed, 10 Feb 2016 11:30:10 -0800 (PST)
Received: from mail-pa0-x22c.google.com (mail-pa0-x22c.google.com [IPv6:2607:f8b0:400e:c03::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 761E41B2F01 for <ipv6@ietf.org>; Wed, 10 Feb 2016 11:30:10 -0800 (PST)
Received: by mail-pa0-x22c.google.com with SMTP id ho8so16435575pac.2 for <ipv6@ietf.org>; Wed, 10 Feb 2016 11:30:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=OL6iaX9A5fKUr8ogtI/mUGKt8/m2lPnckrWPB3+chIA=; b=DVeYy/h5tl5d0fPiGHoSZsC2oOf4Xguo8TTvH/RxlTwEkCn2pY/KblKpLQaVmkSnbm toQ/bkn5k/t5dqfUQI4PqNgWNz6WFdNlfUoz0U2gEGgN7wxhSyGsxGCmpMrFYvOSNvl3 vkAjAiWs2T8lbXPXaJV6WBI53C6ICYd2Ol67ZzrA20Y/XyHma/tFxzHiOxAyjYBXok0O MWF0mt/E7fNrCAc31eCcVl7jIE8u8GnXJfH3ZdzafxV8sWMvRouJ41j6xKetCiKhk0Tx f+9WAeVH/J6iiKKxmFaRO6BzAydVwAV0fCQrQ3IgG62CDVmQokusQAIh/0/S0Zk98b2v y2fQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=OL6iaX9A5fKUr8ogtI/mUGKt8/m2lPnckrWPB3+chIA=; b=bjdsnpIRssgrrN3f24pjra0VFOvGJAG5ctAaBrsy4nmG2ppJXzqtwVre/XpR+3SAW5 tjrWyKjRu3QIaBnUNs8X9iVnN9ndyZF1DzDbCce13Cw3+mxCN/YlObRDyu3WtHuyhb+C OXLmtcvZEgVjvxUV81h2sh3bprnCWIQ0WyfLfyFR8zo0jXs8LPgkv/27DkARar2vE4ee 3fwAAgsnRUnvkWfYFC1QPfbo47j4sX8XHo5SG5HnpK3WqX/hPWEEZJO+C2DOthH75ZxL TVZO/doTrC9K7SGH4u51C4eyzlZBoo2x0G/TOEqb6feDkK0uY+2R4CCg8saMLAsO8RcP KzFA==
X-Gm-Message-State: AG10YOSrqCFvtdCSNErB7WMHI42IXiFIKAKeGpi/DK/NqxD1UwhNu1ZTDOzvli4Ej/EmHw==
X-Received: by 10.66.102.106 with SMTP id fn10mr61883824pab.60.1455132610158;  Wed, 10 Feb 2016 11:30:10 -0800 (PST)
Received: from ?IPv6:2406:e007:60f8:1:28cc:dc4c:9703:6781? ([2406:e007:60f8:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id i23sm6970372pfj.68.2016.02.10.11.30.05 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 10 Feb 2016 11:30:08 -0800 (PST)
Subject: Re: 6MAN WG Last Call - draft-ietf-6man-multi-homed-host-03.txt
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Mark Smith <markzzzsmith@gmail.com>
References: <2052A806-4D40-4A17-9892-90E39B67C65C@gmail.com> <CAJE_bqekFsfHPkfLTAOHgdL-MpvwNSV=gB8Cv0x+YrD66JUyMg@mail.gmail.com> <56B3D4BF.9000202@gmail.com> <CAJE_bqczUQ1UX=mLBzd=XpoKDjO616NrO4iQYZvK7T7CFVzXOQ@mail.gmail.com> <56B4F674.5050207@gmail.com> <CAJE_bqe5fXZKJpekmDCtVxGBVn3Jv9VtDtoUGWhu+HNV6M1X=g@mail.gmail.com> <CAO42Z2wWKjQM98jis=LF45gcavtjmRDMH7eqOZm35UPjewrJrA@mail.gmail.com> <CAJE_bqcUXoOQwEYkOSzqb5NYfL6npPBaXibTojPpiORGYBH0hQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56BB8FC3.3060308@gmail.com>
Date: Thu, 11 Feb 2016 08:30:11 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <CAJE_bqcUXoOQwEYkOSzqb5NYfL6npPBaXibTojPpiORGYBH0hQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/CfjtLVmlZz1-dgqF9PfYzUi34sI>
Cc: IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2016 19:30:11 -0000

On 11/02/2016 06:49, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 wrote:
> At Wed, 10 Feb 2016 11:40:44 +1100,
> Mark Smith <markzzzsmith@gmail.com> wrote:
>=20
>>> Okay, then my personal suggestion for the entire paragraph would be:
>>>
>>>    As described in [RFC4191] and [RFC4861], a Router Advertisement ma=
y
>>>    contain zero or more Prefix information Options (PIOs), or zero or=
 more
>>>    Route Information Options (RIOs).  In their
>>>    original intent, these indicate general information to a host: "th=
is
>>>    is your default router",
>>
>> Actually, only the router lifetime field indicates that the RA is
>> coming from a default router or not.
>=20
> Right, and "this" in "this is your default router" is actually (or
> more accurately) the source IPv6 address of the Router Advertisement,
> rather than something "contained" in it (as an option).  So the above
> suggested text could still sound a bit awkward, but to me it seemed
> just good enough and trying to make it super accurate wouldn't be
> worth the resulting verbosity.  If you want to make it perfect,
> though, I'm not opposed to it - feel free to suggest your own text.

It is tricky to make this text perfect, because the phrase "default route=
r"
is a little bit strange. Logically, there can only be one default at a gi=
ven
instant, but we have the concept of a list of "defaults", which really
means a list of valid routers in the absence of a specific route for
the destination address. Or maybe "a default router" is a router that
claims to be able to route to any destination, but "the default router"
is the router the host is currently using in the absence of a specific
route.

This confusion seems to go back to RFC 1122, where these boxes are called=

"default gateways".

    Bfian


From nobody Wed Feb 10 11:47:35 2016
Return-Path: <dwcarder@wisc.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26E0D1B2F13 for <ipv6@ietfa.amsl.com>; Wed, 10 Feb 2016 11:47:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.602
X-Spam-Level: 
X-Spam-Status: No, score=-3.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-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 rEPnH80DIgBw for <ipv6@ietfa.amsl.com>; Wed, 10 Feb 2016 11:47:31 -0800 (PST)
Received: from smtpauth4.wiscmail.wisc.edu (wmauth4.doit.wisc.edu [144.92.197.145]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49FD41B2F19 for <ipv6@ietf.org>; Wed, 10 Feb 2016 11:47:30 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-disposition: inline
Content-type: text/plain; charset=utf-8
Received: from avs-daemon.smtpauth4.wiscmail.wisc.edu by smtpauth4.wiscmail.wisc.edu (Oracle Communications Messaging Server 7.0.5.33.0 64bit (built Aug 27 2014)) id <0O2C00L00K4JCA00@smtpauth4.wiscmail.wisc.edu> for ipv6@ietf.org; Wed, 10 Feb 2016 13:47:29 -0600 (CST)
X-Spam-PmxInfo: Server=avs-4, Version=6.2.1.2493963, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.2.10.194217, SenderIP=0.0.0.0
Received: from DOIT-2NW1MRFY-X.doit.wisc.edu (brie.doit.wisc.edu [144.92.67.198]) by smtpauth4.wiscmail.wisc.edu (Oracle Communications Messaging Server 7.0.5.33.0 64bit (built Aug 27 2014)) with ESMTPSA id <0O2C00N0FKB30I20@smtpauth4.wiscmail.wisc.edu>; Wed, 10 Feb 2016 13:47:29 -0600 (CST)
Date: Wed, 10 Feb 2016 13:47:27 -0600
From: "Dale W. Carder" <dwcarder@wisc.edu>
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: IID in LL and GUA - draft-ietf-6man-default-iids-09
Message-id: <20160210194727.GG387@DOIT-2NW1MRFY-X.doit.wisc.edu>
References: <C6E767B9-A1DB-4A3A-A4EB-0A6CC38502CD@employees.org> <56B4E7FB.5010700@si6networks.com> <56B4FF9D.10203@gmail.com> <5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <EMEW3|5048bb3e4f22902e3e9b18a621e7fd32s16H1H03tjc|ecs.soton.ac.uk|5A33676B-BE3A-4A12-96E1-A4837C06741B@ecs.soton.ac.uk> <56B7915D.2060300@gmail.com> <56B9C841.9020908@si6networks.com> <56BA35B0.3040701@gmail.com> <42ACE220-DB6F-4825-BED0-F7A526A1F1EF@ecs.soton.ac.uk> <EMEW3|36396e79e5fba14ce0e242fd915dbd56s18JHl03tjc|ecs.soton.ac.uk|42ACE220-DB6F-4825-BED0-F7A526A1F1EF@ecs.soton.ac.uk>
In-reply-to: <EMEW3|36396e79e5fba14ce0e242fd915dbd56s18JHl03tjc|ecs.soton.ac.uk|42ACE220-DB6F-4825-BED0-F7A526A1F1EF@ecs.soton.ac.uk>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/j8MKyDjIJIWHF7YFfihz0dZKEOA>
Cc: Fernando Gont <fgont@si6networks.com>, Alexandre Petrescu <alexandre.petrescu@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2016 19:47:34 -0000

Thus spake Tim Chown (tjc@ecs.soton.ac.uk) on Tue, Feb 09, 2016 at 07:16:27PM +0000:
> > On 9 Feb 2016, at 18:53, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> > 
> > On 10/02/2016 00:06, Fernando Gont wrote:
> >> On 02/07/2016 03:47 PM, Brian E Carpenter wrote:
> >>> On 08/02/2016 05:59, Tim Chown wrote:
> >>>> On 5 Feb 2016, at 20:01, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> >>>>> 
> >>>>> On 06/02/2016 07:20, Fernando Gont wrote:
> >>>>>> On 02/05/2016 03:07 PM, otroan@employees.org wrote:
> >>>>>>> Fernando,
> >>>>>>> 
> >>>>>>> [...]
> >>>>>>> 
> >>>>>>>>> 
> >>>>>>>>> What is the risk of using the same IID for link-local and global addresses?
> >>>>>>>>> Typically if you can snoop the link-local address then you're onlink and leak information about all addresses and their correlations anyway.
> >>>>>>>> 
> >>>>>>>> We discussed this one a hundred times now (including for RFC7217). The
> >>>>>>>> risk is that at times such addressess can leak, without the need of the
> >>>>>>>> attacker being pesent on the local link.
> >>>>>>>> 
> >>>>>>>> e.g., your MTA is on the local-link, and you end up connecting to it
> >>>>>>>> with a LL, which then appears in the email headers. (and there are a
> >>>>>>>> bunch of other possible reasons for that to happen).
> >>>>>>>> 
> >>>>>>>> Be proactive. MAC addresses in the IID are wrong. Putting them there is
> >>>>>>>> just waiting for trouble.
> >>>>>>> 
> >>>>>>> I didn't say the LL was based on a MAC.
> >>>>>>> my question was if there was any issue with re-using the IID from the link-local in the GUA. assume the link-local is generated f.ex with 7217.
> >>>>>> 
> >>>>>> Oops, my apologies. My answer would be "It unnecessarily enables
> >>>>>> correlation of the activities that you carry between the two addresses".
> >>>>>> 
> >>>>>> i.e., by simply inspecting the IID I could easily tell that the
> >>>>>> activities carried out with one address were performed by the same node
> >>>>>> that employed the other address.
> >>>>>> 
> >>>>>> My take here is, again: be proactive. If there's no requirement (and
> >>>>>> there isn't) for the two IIDs to be the same, then make them different,
> >>>>>> and fail on the safe side.
> >>>>> 
> >>>>> But Ole's point was that any observer who sees a LL packet is on-link and
> >>>>> can therefore see the MAC address anyway; an observer who can see MAC addresses
> >>>>> can just laugh at RFC 7217 or RFC 4941.
> >>>> 
> >>>> Well, except that the device might be varying its MAC address as well.
> >>>> 
> >>>> I thought RFC7217 states that a device is expected to have a different IID for 
> >>>> each prefix on an interface. (Though whether thereâ€™s a NetworkID available to
> >>>> seed a different LL IID per visited network is another question, else the device
> >>>> presumably has the same LL IID as it moves?)
> >>>> 
> >>>> Thereâ€™s definitely value in avoiding correlation. If thereâ€™s an equal cost either 
> >>>> way, why allow such potential?
> >>> 
> >>> Extra code? But my real concern is that there might be unintended side effects,
> >>> because the interface identifier will no longer identify an interface.
> >> 
> >> Not really. RFC7217 automagically achieves that.
> > 
> > Let me be even clearer about my concern; then I will shut up:
> > 
> > I fully agree that from a privacy point of view, it is better to use
> > a different IID for link-local and for each GUA prefix (including each
> > ULA prefix). I'm not aware of anywhere in the IETF standards that this
> > will lead to a problem. However, I am concerned that in some IPv6 networks,
> > especially networks running with only one GUA prefix (which is most of
> > them) there are operational practices and/or locally written scripts
> > that *assume* the same IID is used for all prefixes on a given interface.
> > After all, that has been the case for all IPv6 stacks for many years.
> 
> But those scripts will already fail if correlating privacy addresses with others.

I was going to echo this as well, but you beat me to it.

Dale


From nobody Wed Feb 10 13:08:55 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70B661B2FF3 for <ipv6@ietfa.amsl.com>; Wed, 10 Feb 2016 13:08:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.309
X-Spam-Level: 
X-Spam-Status: No, score=-0.309 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, 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 fOElaQSQGWpc for <ipv6@ietfa.amsl.com>; Wed, 10 Feb 2016 13:08:52 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BF121B2FEE for <6man@ietf.org>; Wed, 10 Feb 2016 13:08:52 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id EF42E206B80; Wed, 10 Feb 2016 22:08:48 +0100 (CET)
To: "6man@ietf.org" <6man@ietf.org>
From: Fernando Gont <fgont@si6networks.com>
Subject: Question about the Flow Label in Node Req (RFC6434)
X-Enigmail-Draft-Status: N1110
Message-ID: <56BB6B80.5020105@si6networks.com>
Date: Wed, 10 Feb 2016 13:55:28 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/6daXFQTL2BqyMEIWlnKNuZc1_A8>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2016 21:08:54 -0000

Folks,

Section 5.1 of the aforementioned RFC says:

   All nodes SHOULD support the setting and use of the IPv6 Flow Label
   field as defined in the IPv6 Flow Label specification [RFC6437].
   Forwarding nodes such as routers and load distributors MUST NOT
   depend only on Flow Label values being uniformly distributed.  It is
   RECOMMENDED that source hosts support the flow label by setting the
   Flow Label field for all packets of a given flow to the same value
   chosen from an approximation to a discrete uniform distribution.

What does "MUST NOT depend only on Flow Label values being uniformly
distributed" really mean? Does it mean that if we're using the FL as
input to a hash function fr ECMP, we should also include the src and dst
addresses, or does it mean that we should also include e.g. upper
protocol type and port numbers as input of such hash function?

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





From nobody Wed Feb 10 16:25:24 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2C321A8716 for <ipv6@ietfa.amsl.com>; Wed, 10 Feb 2016 16:25: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 O2CF1MeTDIkS for <ipv6@ietfa.amsl.com>; Wed, 10 Feb 2016 16:25:16 -0800 (PST)
Received: from mail-pf0-x235.google.com (mail-pf0-x235.google.com [IPv6:2607:f8b0:400e:c00::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 420891A8718 for <6man@ietf.org>; Wed, 10 Feb 2016 16:25:16 -0800 (PST)
Received: by mail-pf0-x235.google.com with SMTP id e127so20250228pfe.3 for <6man@ietf.org>; Wed, 10 Feb 2016 16:25:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=SREXQM6/SQAvcSfUUXxKzXPMst2jIDrTy3CwGaVaaWk=; b=FS+xfdxrufMXM80UTHlvJcVMc5Mkkdk6VGMgQQOzRmHDqqxEvDKB/LadSyvkOsUMLy 77edDqrd1kWSXHQtkGtelxarCUNUFQVVOyG3VDFBqEqb8RaQNnAOlnowxNZnxtGu0ye8 UpqZg1Da+5gpXB0EJClI/ZHHBM4jwdnkXi7Vuj8GZ7oEtUJftCKUIjp8qiwOJkSOXYM5 44R8Bhdo3Ezp2VB85sXmiR6bsMB4X4ueNVsCUrsD9cPLT10cG9QZMpwV5ujDoYx1PDiw CHoewn2KI6wbfMGaeSAj7tKlLx87w/fibg+kp3ahAr/B4lsbFAOR598adoQ+eGarnT0w zjJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=SREXQM6/SQAvcSfUUXxKzXPMst2jIDrTy3CwGaVaaWk=; b=BtbBehwzmPK1fy9EEzj7tAQcwIyxRsXfNXGc6Y49D3yeCrRztWzzde40votIcLFeS3 saKnVBgOkcHiXt7KOxAAy8JVcE3xt4LAohKhGGCtJ9BaSyegOm9ZgjUl+xizK6C38gS9 +c/+k6EaRzaM2l8NxtxxzfsXdSpWtcFUNViTAJoLYo5qTJZA974Sv+E2UT0hHyVYTght YXTlpOZ700jyPnJH2elhJOt5nXptpjFD4t6fGwvgkLgpsJzEKQ59atPXwUGPJxcgbUvT 54A0lFrbyOX5uYtwiKZtnOT96I3AlsqHnIKNqbiDbSx7qD/6R8tSlQrP6UFUbqt7s56z krcw==
X-Gm-Message-State: AG10YOQ10JU8rx5IOGZ7ka6iNruVb1DAE7qN7WqVXre8Y5l/HOaxLcNZfsEsUmBcOJgqFQ==
X-Received: by 10.98.74.93 with SMTP id x90mr42589554pfa.80.1455150315886; Wed, 10 Feb 2016 16:25:15 -0800 (PST)
Received: from ?IPv6:2406:e007:60f8:1:28cc:dc4c:9703:6781? ([2406:e007:60f8:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 87sm1320990pfq.93.2016.02.10.16.25.12 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 10 Feb 2016 16:25:14 -0800 (PST)
Subject: Re: Question about the Flow Label in Node Req (RFC6434)
To: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@ietf.org>
References: <56BB6B80.5020105@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56BBD4F0.4080205@gmail.com>
Date: Thu, 11 Feb 2016 13:25:20 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56BB6B80.5020105@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/bO34KiaqgXbKmy79Ia2jObclRhk>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2016 00:25:23 -0000

Hi Fernando,
On 11/02/2016 05:55, Fernando Gont wrote:
> Folks,
> 
> Section 5.1 of the aforementioned RFC says:
> 
>    All nodes SHOULD support the setting and use of the IPv6 Flow Label
>    field as defined in the IPv6 Flow Label specification [RFC6437].
>    Forwarding nodes such as routers and load distributors MUST NOT
>    depend only on Flow Label values being uniformly distributed.  It is
>    RECOMMENDED that source hosts support the flow label by setting the
>    Flow Label field for all packets of a given flow to the same value
>    chosen from an approximation to a discrete uniform distribution.
> 
> What does "MUST NOT depend only on Flow Label values being uniformly
> distributed" really mean? 

That's a direct quotation from RFC 6437, included here because
it's important. In RFC 6437 there is more explanation:

   o  Forwarding nodes such as routers and load distributors MUST NOT
      depend only on Flow Label values being uniformly distributed.  In
      any usage such as a hash key for load distribution, the Flow Label
      bits MUST be combined at least with bits from other sources within
      the packet, so as to produce a constant hash value for each flow
      and a suitable distribution of hash values across flows.
      Typically, the other fields used will be some or all components of
      the usual 5-tuple.  In this way, load distribution will still
      occur even if the Flow Label values are poorly distributed.

It's a precaution against a flow label having a value with very
little entropy (such as zero, or a small integer).

> Does it mean that if we're using the FL as
> input to a hash function fr ECMP, we should also include the src and dst
> addresses, or does it mean that we should also include e.g. upper
> protocol type and port numbers as input of such hash function?

That was intentionally underspecified, because (as some of the discussion
here has shown) the exact description of the hash tends to be proprietary
and not something the operators want to see in the newspaper, because
it might help somebody to tailor an attack.

Hope that helps,

    Brian


From nobody Thu Feb 11 08:54:51 2016
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD8181B34AC for <ipv6@ietfa.amsl.com>; Thu, 11 Feb 2016 08:54:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oCT6YU9Sc_Jn for <ipv6@ietfa.amsl.com>; Thu, 11 Feb 2016 08:54:48 -0800 (PST)
Received: from mail-ig0-x22c.google.com (mail-ig0-x22c.google.com [IPv6:2607:f8b0:4001:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FBC11B3465 for <ipv6@ietf.org>; Thu, 11 Feb 2016 08:54:48 -0800 (PST)
Received: by mail-ig0-x22c.google.com with SMTP id 5so40813967igt.0 for <ipv6@ietf.org>; Thu, 11 Feb 2016 08:54:48 -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=rWFVbyGRk+OLLNZGExs/38L17d489p+A9Add2+cQ6HU=; b=F9EJ3IEGGDM2kSUg9b0KKl0A0HrRX76qvir3q7mIhhbfItShIPSEUFiCCWZdeF7DJa gcDPIdxE39LdQO1HHHOAgXbb1X1EkCCtL+C3vUeZLyiwB8Ggmw0/1rMYaTvHuu5nWeWy XXU6rMtW/My4Y3knlPJbm0dnRgxFrSmwQFxkQco04WBZwKv7PkIFDBGhRSgeEslImjiK q/rlTqsgVYnhtqjywAQwerT3VzxBJ7ZUGIONTvDKxz2ymwlrjG5J0RWqmT8pMO+gLP1W goT7288xA3rMIoibMxC38cGk57EysRKkbLvq4ZTiqjj3TiEkhekUrzPFmw2ybri3VqPG C2Jw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=rWFVbyGRk+OLLNZGExs/38L17d489p+A9Add2+cQ6HU=; b=Ix9A8o+ErDtKJ1cX5ySDzXSxShy1p1qhRYD6NkqzfMdTFmtjxNlU1vMT7+DwTUk6WW ye/WxLVE1GJ793VFtB7T5pjXbHIp6SfiVgcDCej92zRivyukFhtMkmcBGDKNHmbCvuFH Q2VUubU7mE3FG1I7dLGRXDVEvF1r3zVsIXq0f7n2x5ElTt65gHJC+XiiSdqNdyyNaz8a mSLwGZAlznyJsAQZYPvbw+4EKxfyY7XwH0pS2LC2ezCaT1Ivj/URA3dUzj22AgB8jyKT g22ixU6e3GdH347gok3chNMvkN7ctWE7Cg90wWBJBj7eZP4ulthmDIIj1EbFz2DLnzsr 51/w==
X-Gm-Message-State: AG10YORBFbv+QbvHR/NZrN6Q/6zLGrFr6XsMSjgvpJS0tPVDTj4t2RTsSWUQVRyaPospoj6llR9JfRGRS7fQvQ==
MIME-Version: 1.0
X-Received: by 10.50.111.111 with SMTP id ih15mr17992076igb.78.1455209688018;  Thu, 11 Feb 2016 08:54:48 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.169.35 with HTTP; Thu, 11 Feb 2016 08:54:47 -0800 (PST)
In-Reply-To: <56BB8FC3.3060308@gmail.com>
References: <2052A806-4D40-4A17-9892-90E39B67C65C@gmail.com> <CAJE_bqekFsfHPkfLTAOHgdL-MpvwNSV=gB8Cv0x+YrD66JUyMg@mail.gmail.com> <56B3D4BF.9000202@gmail.com> <CAJE_bqczUQ1UX=mLBzd=XpoKDjO616NrO4iQYZvK7T7CFVzXOQ@mail.gmail.com> <56B4F674.5050207@gmail.com> <CAJE_bqe5fXZKJpekmDCtVxGBVn3Jv9VtDtoUGWhu+HNV6M1X=g@mail.gmail.com> <CAO42Z2wWKjQM98jis=LF45gcavtjmRDMH7eqOZm35UPjewrJrA@mail.gmail.com> <CAJE_bqcUXoOQwEYkOSzqb5NYfL6npPBaXibTojPpiORGYBH0hQ@mail.gmail.com> <56BB8FC3.3060308@gmail.com>
Date: Thu, 11 Feb 2016 08:54:47 -0800
X-Google-Sender-Auth: iIkRhbgV87jf8bFgWckaQvFwXZ0
Message-ID: <CAJE_bqezpP4pUGoAMBPbGQUn+67aBhO3NFTv40b7--hm93R2EQ@mail.gmail.com>
Subject: Re: 6MAN WG Last Call - draft-ietf-6man-multi-homed-host-03.txt
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/O77nDDg1mdT73qoiThVEhrtdMT0>
Cc: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2016 16:54:50 -0000

At Thu, 11 Feb 2016 08:30:11 +1300,
Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

> >>> Okay, then my personal suggestion for the entire paragraph would be:
> >>>
> >>>    As described in [RFC4191] and [RFC4861], a Router Advertisement may
> >>>    contain zero or more Prefix information Options (PIOs), or zero or more
> >>>    Route Information Options (RIOs).  In their
> >>>    original intent, these indicate general information to a host: "this
> >>>    is your default router",
> >>
> >> Actually, only the router lifetime field indicates that the RA is
> >> coming from a default router or not.
> >
> > Right, and "this" in "this is your default router" is actually (or
> > more accurately) the source IPv6 address of the Router Advertisement,
> > rather than something "contained" in it (as an option).  So the above
> > suggested text could still sound a bit awkward, but to me it seemed
> > just good enough and trying to make it super accurate wouldn't be
> > worth the resulting verbosity.  If you want to make it perfect,
> > though, I'm not opposed to it - feel free to suggest your own text.
>
> It is tricky to make this text perfect, because the phrase "default router"
> is a little bit strange. Logically, there can only be one default at a given
> instant, but we have the concept of a list of "defaults", which really
> means a list of valid routers in the absence of a specific route for
> the destination address. Or maybe "a default router" is a router that
> claims to be able to route to any destination, but "the default router"
> is the router the host is currently using in the absence of a specific
> route.

To be clear, I don't think my suggestion is about making text of
"default router" perfect.  I just tried to correct the obvious error
of referring to the default router list as content of RA, and adjust
the rest of the paragraph accordingly.

--
JINMEI, Tatuya


From nobody Thu Feb 11 11:06:14 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 687691B3948 for <ipv6@ietfa.amsl.com>; Thu, 11 Feb 2016 11:06:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 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, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5L9iGCcI1TKe for <ipv6@ietfa.amsl.com>; Thu, 11 Feb 2016 11:06:12 -0800 (PST)
Received: from mail-pf0-x233.google.com (mail-pf0-x233.google.com [IPv6:2607:f8b0:400e:c00::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 555371B3941 for <ipv6@ietf.org>; Thu, 11 Feb 2016 11:06:12 -0800 (PST)
Received: by mail-pf0-x233.google.com with SMTP id q63so33819098pfb.0 for <ipv6@ietf.org>; Thu, 11 Feb 2016 11:06:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=FS05ogJlV1IFjawe8BRrcolxa0SEvUN8iW9I90vwDSo=; b=d2tOR9YKIobVpZ/bfVKbo4U5P2MgSWI48ofOuL2UDW49/rYREkW26dddtYCIg3XCqC oiIdJSewgNvD8fvZ0pkeCSV4L50AUHmsjl0YNAJRaYovgyQXKz6EQtlWhvnlw27sB+vs qS8ESWZVXzUVSNE77PsVKxH+tLEpG3fX/S/3MY0sOsPN4+jru7rkgtlypkMyZAFvo9VC X/m692+BvzsJB1WqAh2xoCrWEJBFdltzfRUmYUwIxfoxzBHrDL1wbxttGWaeUCgje6Ub I85Fx7yAAaffBijkf5Ih4TBE12gGj3m5xVtdlKCVlLGR8SYQjHL2kadAixCkPPgX7uA5 G0UA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=FS05ogJlV1IFjawe8BRrcolxa0SEvUN8iW9I90vwDSo=; b=lAjm0PikSXIrLzzlkmMkWOZidXxQBxRbg0dYaD4cQlhCLCC2h4Fg49/lNt/9iE/hrt 3elGkTTGzqWbfBu+0NGI6g1L9tKO9lKDmmmURbDjzxOH1scpk0GWPLdEOH40WiAcEzzQ tpDPvGbzHR2xuQqXE6DUw/FVcm/p3v/z6om8LIsqfh0u09O56lXExznwWBckN/ff5w04 w54kzH03qE8MrjQvhD0D5oyY84bRK68tmgDvpi77lu6LSzAbLzLqz/5t+26QapJ6k06q /4m26VrXWjFxoXWYkr6PvzViPLrm4PHG/OOPIZIEPpEP192RshOtgPtnM2y/pE2PqAIW W+qQ==
X-Gm-Message-State: AG10YORSB87BiF8xjeKx0smmEljtt4wwecVsU5GVXhrL6ucQrbBSIraxNPZZ6fLrJ9+DMg==
X-Received: by 10.98.14.79 with SMTP id w76mr45787704pfi.1.1455217571974; Thu, 11 Feb 2016 11:06:11 -0800 (PST)
Received: from ?IPv6:2406:e007:5496:1:28cc:dc4c:9703:6781? ([2406:e007:5496:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id fc8sm14024735pab.21.2016.02.11.11.06.08 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 11 Feb 2016 11:06:10 -0800 (PST)
Subject: Re: 6MAN WG Last Call - draft-ietf-6man-multi-homed-host-03.txt
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
References: <2052A806-4D40-4A17-9892-90E39B67C65C@gmail.com> <CAJE_bqekFsfHPkfLTAOHgdL-MpvwNSV=gB8Cv0x+YrD66JUyMg@mail.gmail.com> <56B3D4BF.9000202@gmail.com> <CAJE_bqczUQ1UX=mLBzd=XpoKDjO616NrO4iQYZvK7T7CFVzXOQ@mail.gmail.com> <56B4F674.5050207@gmail.com> <CAJE_bqe5fXZKJpekmDCtVxGBVn3Jv9VtDtoUGWhu+HNV6M1X=g@mail.gmail.com> <CAO42Z2wWKjQM98jis=LF45gcavtjmRDMH7eqOZm35UPjewrJrA@mail.gmail.com> <CAJE_bqcUXoOQwEYkOSzqb5NYfL6npPBaXibTojPpiORGYBH0hQ@mail.gmail.com> <56BB8FC3.3060308@gmail.com> <CAJE_bqezpP4pUGoAMBPbGQUn+67aBhO3NFTv40b7--hm93R2EQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56BCDBA9.8050506@gmail.com>
Date: Fri, 12 Feb 2016 08:06:17 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <CAJE_bqezpP4pUGoAMBPbGQUn+67aBhO3NFTv40b7--hm93R2EQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/EStutuXbcLqZnJlAzwqRgSCPp08>
Cc: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Feb 2016 19:06:13 -0000

On 12/02/2016 05:54, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 wrote:
> At Thu, 11 Feb 2016 08:30:11 +1300,
> Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>=20
>>>>> Okay, then my personal suggestion for the entire paragraph would be=
:
>>>>>
>>>>>    As described in [RFC4191] and [RFC4861], a Router Advertisement =
may
>>>>>    contain zero or more Prefix information Options (PIOs), or zero =
or more
>>>>>    Route Information Options (RIOs).  In their
>>>>>    original intent, these indicate general information to a host: "=
this
>>>>>    is your default router",
>>>>
>>>> Actually, only the router lifetime field indicates that the RA is
>>>> coming from a default router or not.
>>>
>>> Right, and "this" in "this is your default router" is actually (or
>>> more accurately) the source IPv6 address of the Router Advertisement,=

>>> rather than something "contained" in it (as an option).  So the above=

>>> suggested text could still sound a bit awkward, but to me it seemed
>>> just good enough and trying to make it super accurate wouldn't be
>>> worth the resulting verbosity.  If you want to make it perfect,
>>> though, I'm not opposed to it - feel free to suggest your own text.
>>
>> It is tricky to make this text perfect, because the phrase "default ro=
uter"
>> is a little bit strange. Logically, there can only be one default at a=
 given
>> instant, but we have the concept of a list of "defaults", which really=

>> means a list of valid routers in the absence of a specific route for
>> the destination address. Or maybe "a default router" is a router that
>> claims to be able to route to any destination, but "the default router=
"
>> is the router the host is currently using in the absence of a specific=

>> route.
>=20
> To be clear, I don't think my suggestion is about making text of
> "default router" perfect.  I just tried to correct the obvious error
> of referring to the default router list as content of RA, and adjust
> the rest of the paragraph accordingly.

Yes, I understand and agree. We will correct the text. But one thought
leads to another, and I was quite surprised to discover that we seem to
have no document that defines "default router" except for the slightly
confusing "default gateway" discussion in RFC 1122.

   Brian


From nobody Tue Feb 16 04:11:01 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94B571B35B2 for <ipv6@ietfa.amsl.com>; Tue, 16 Feb 2016 04:10:59 -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] 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 i0yOd8CP-IBC for <ipv6@ietfa.amsl.com>; Tue, 16 Feb 2016 04:10:55 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 699421B34CA for <6man@ietf.org>; Tue, 16 Feb 2016 04:10:49 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 084C485268; Tue, 16 Feb 2016 13:10:45 +0100 (CET)
Subject: Re: Question about the Flow Label in Node Req (RFC6434)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "6man@ietf.org" <6man@ietf.org>
References: <56BB6B80.5020105@si6networks.com> <56BBD4F0.4080205@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56C304D9.5010003@si6networks.com>
Date: Tue, 16 Feb 2016 08:15:37 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56BBD4F0.4080205@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/k3H0SZjx3ccH5_F78KLrpiUp_mE>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Feb 2016 12:10:59 -0000

On 02/10/2016 09:25 PM, Brian E Carpenter wrote:
> Hi Fernando,
> On 11/02/2016 05:55, Fernando Gont wrote:
>> Folks,
>>
>> Section 5.1 of the aforementioned RFC says:
>>
>>    All nodes SHOULD support the setting and use of the IPv6 Flow Label
>>    field as defined in the IPv6 Flow Label specification [RFC6437].
>>    Forwarding nodes such as routers and load distributors MUST NOT
>>    depend only on Flow Label values being uniformly distributed.  It is
>>    RECOMMENDED that source hosts support the flow label by setting the
>>    Flow Label field for all packets of a given flow to the same value
>>    chosen from an approximation to a discrete uniform distribution.
>>
>> What does "MUST NOT depend only on Flow Label values being uniformly
>> distributed" really mean? 
> 
> That's a direct quotation from RFC 6437,

Ooops, my bad, I should have checked (but assumed it wasn't a quote from
RFC6437).


> included here because
> it's important. In RFC 6437 there is more explanation:
> 
>    o  Forwarding nodes such as routers and load distributors MUST NOT
>       depend only on Flow Label values being uniformly distributed.  In
>       any usage such as a hash key for load distribution, the Flow Label
>       bits MUST be combined at least with bits from other sources within
>       the packet, so as to produce a constant hash value for each flow
>       and a suitable distribution of hash values across flows.
>       Typically, the other fields used will be some or all components of
>       the usual 5-tuple.  In this way, load distribution will still
>       occur even if the Flow Label values are poorly distributed.
> 
> It's a precaution against a flow label having a value with very
> little entropy (such as zero, or a small integer).

mm.. then... should the requirement on the FL setting/geneation be
stronger (if needed?) -- i.e., we'd really want that if the FL is set,
the middlebox/router doesn't really *need* to get the upper-layer ports,
etc.




>> Does it mean that if we're using the FL as
>> input to a hash function fr ECMP, we should also include the src and dst
>> addresses, or does it mean that we should also include e.g. upper
>> protocol type and port numbers as input of such hash function?
> 
> That was intentionally underspecified, because (as some of the discussion
> here has shown) the exact description of the hash tends to be proprietary
> and not something the operators want to see in the newspaper, because
> it might help somebody to tailor an attack.

I guess some suggested possible algorithms might help. -- otherwise I'd
expect yet another member for:
<https://tools.ietf.org/html/draft-gont-predictable-protocol-ids>

Thanks!

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





From nobody Tue Feb 16 11:33:36 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB5101B322E for <ipv6@ietfa.amsl.com>; Tue, 16 Feb 2016 11:33:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I07rhAdFXPXH for <ipv6@ietfa.amsl.com>; Tue, 16 Feb 2016 11:33:33 -0800 (PST)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB5581B31B5 for <6man@ietf.org>; Tue, 16 Feb 2016 11:33:32 -0800 (PST)
Received: by mail-pf0-x234.google.com with SMTP id c10so112482019pfc.2 for <6man@ietf.org>; Tue, 16 Feb 2016 11:33:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=eQUV83HizGG2fF83vhjJWlJKM+v12iBG+cZNJcQuZ9g=; b=Oef8PEZ3ARPOzbGeEN7jJXoDtGI+bS86mZUIRw8O4MKWcpFB/KEEtHM+CyX4005Yzk GdRT7zHDq1CdXmMB3rCaJ9mENX2xHwtTp4Tog8at5ki4hcSvWQ59vhxvWEY48tpjXrXy WnehZPbgGxBBOViBBBj8gMgUYJ7qhisNYJcpsOUf+RHJxqtWvhPAfBGVKfDwqNpTnNlu ILnR5nRrGfCHadazRTLFXN/y8ASTxBoCnnxGzUKNgSANwZ9qExD81SvZ56ZxWsQk3sk1 ORoxMrq1zn+8gCfyu/8HJxirRXCuxQpSit4j5PO87dxUpYbr1bsL04BHtGTT9ILrAmZ4 6eww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=eQUV83HizGG2fF83vhjJWlJKM+v12iBG+cZNJcQuZ9g=; b=GGYe6iwYfj/Wacnl3pM8cy0cqbiYGQUCrcmj9D5Fd8fEdg4vAINUfkyJ00ES6tdOWW iSpy+ZHDARMkj6uZJqrC+jMztgv84I/bxKNTMvbitv54bTy6TJS7oqdiQ9Ny3cNxcxIe 1wgD36vfO8Io03hRIQ3nOqaMb0IDgNwTZAF7xCDBarDxYFaoWsKsVevKwrg+KYccNM+E 9/X8HdENYAgsMLu3GeHLOA0r+ypn7Q7ZhPGQaMjlfwrvPQP/opVf6TOO69HVgzu1bp6T T+T1jK8Z/3jiNpzWCe0/l9M52oCQLEhOeIcb61fsRqLBDWC5NDxDcsgan07ZMJYTEdUv 0VCw==
X-Gm-Message-State: AG10YOSXHPKxTdLLh4loN0Z1veT+ZRjbdaugxZEn2sLFnaJ1PSbPSLY0YAknSQCDep6ImQ==
X-Received: by 10.98.19.205 with SMTP id 74mr33608559pft.31.1455651212692; Tue, 16 Feb 2016 11:33:32 -0800 (PST)
Received: from ?IPv6:2406:e007:666a:1:28cc:dc4c:9703:6781? ([2406:e007:666a:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id d81sm24835885pfj.77.2016.02.16.11.33.30 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 16 Feb 2016 11:33:31 -0800 (PST)
Subject: Re: Question about the Flow Label in Node Req (RFC6434)
To: Fernando Gont <fgont@si6networks.com>, "6man@ietf.org" <6man@ietf.org>
References: <56BB6B80.5020105@si6networks.com> <56BBD4F0.4080205@gmail.com> <56C304D9.5010003@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56C3798E.1030806@gmail.com>
Date: Wed, 17 Feb 2016 08:33:34 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56C304D9.5010003@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/MiQ4BQEYFh7T9Oq9X4yBSGwqtho>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Feb 2016 19:33:35 -0000

On 17/02/2016 00:15, Fernando Gont wrote:
> On 02/10/2016 09:25 PM, Brian E Carpenter wrote:
>> Hi Fernando,
>> On 11/02/2016 05:55, Fernando Gont wrote:
>>> Folks,
>>>
>>> Section 5.1 of the aforementioned RFC says:
>>>
>>>    All nodes SHOULD support the setting and use of the IPv6 Flow Label
>>>    field as defined in the IPv6 Flow Label specification [RFC6437].
>>>    Forwarding nodes such as routers and load distributors MUST NOT
>>>    depend only on Flow Label values being uniformly distributed.  It is
>>>    RECOMMENDED that source hosts support the flow label by setting the
>>>    Flow Label field for all packets of a given flow to the same value
>>>    chosen from an approximation to a discrete uniform distribution.
>>>
>>> What does "MUST NOT depend only on Flow Label values being uniformly
>>> distributed" really mean? 
>>
>> That's a direct quotation from RFC 6437,
> 
> Ooops, my bad, I should have checked (but assumed it wasn't a quote from
> RFC6437).
> 
> 
>> included here because
>> it's important. In RFC 6437 there is more explanation:
>>
>>    o  Forwarding nodes such as routers and load distributors MUST NOT
>>       depend only on Flow Label values being uniformly distributed.  In
>>       any usage such as a hash key for load distribution, the Flow Label
>>       bits MUST be combined at least with bits from other sources within
>>       the packet, so as to produce a constant hash value for each flow
>>       and a suitable distribution of hash values across flows.
>>       Typically, the other fields used will be some or all components of
>>       the usual 5-tuple.  In this way, load distribution will still
>>       occur even if the Flow Label values are poorly distributed.
>>
>> It's a precaution against a flow label having a value with very
>> little entropy (such as zero, or a small integer).
> 
> mm.. then... should the requirement on the FL setting/geneation be
> stronger (if needed?) -- i.e., we'd really want that if the FL is set,
> the middlebox/router doesn't really *need* to get the upper-layer ports,
> etc.

You won't find me disagreeing with that.

   Brian

>>> Does it mean that if we're using the FL as
>>> input to a hash function fr ECMP, we should also include the src and dst
>>> addresses, or does it mean that we should also include e.g. upper
>>> protocol type and port numbers as input of such hash function?
>>
>> That was intentionally underspecified, because (as some of the discussion
>> here has shown) the exact description of the hash tends to be proprietary
>> and not something the operators want to see in the newspaper, because
>> it might help somebody to tailor an attack.
> 
> I guess some suggested possible algorithms might help. -- otherwise I'd
> expect yet another member for:
> <https://tools.ietf.org/html/draft-gont-predictable-protocol-ids>
> 
> Thanks!
> 
> Cheers,
> 


From nobody Tue Feb 16 11:43:24 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63B921B2E2E for <ipv6@ietfa.amsl.com>; Tue, 16 Feb 2016 11:43:12 -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] 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 Zv69UaXGSzBE for <ipv6@ietfa.amsl.com>; Tue, 16 Feb 2016 11:43:10 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F3231B2C2B for <6man@ietf.org>; Tue, 16 Feb 2016 11:43:06 -0800 (PST)
Received: from [192.168.2.101] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 68BD385295; Tue, 16 Feb 2016 20:43:03 +0100 (CET)
Subject: Re: Question about the Flow Label in Node Req (RFC6434)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "6man@ietf.org" <6man@ietf.org>
References: <56BB6B80.5020105@si6networks.com> <56BBD4F0.4080205@gmail.com> <56C304D9.5010003@si6networks.com> <56C3798E.1030806@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56C37BB3.1060203@si6networks.com>
Date: Tue, 16 Feb 2016 16:42:43 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56C3798E.1030806@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/rpJiHqYGZshxW2mnEW7-DmtksyY>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Feb 2016 19:43:12 -0000

On 02/16/2016 04:33 PM, Brian E Carpenter wrote:
> On 17/02/2016 00:15, Fernando Gont wrote:
>> On 02/10/2016 09:25 PM, Brian E Carpenter wrote:
>>> Hi Fernando,
>>> On 11/02/2016 05:55, Fernando Gont wrote:
>>>> Folks,
>>>>
>>>> Section 5.1 of the aforementioned RFC says:
>>>>
>>>>    All nodes SHOULD support the setting and use of the IPv6 Flow Label
>>>>    field as defined in the IPv6 Flow Label specification [RFC6437].
>>>>    Forwarding nodes such as routers and load distributors MUST NOT
>>>>    depend only on Flow Label values being uniformly distributed.  It is
>>>>    RECOMMENDED that source hosts support the flow label by setting the
>>>>    Flow Label field for all packets of a given flow to the same value
>>>>    chosen from an approximation to a discrete uniform distribution.
>>>>
>>>> What does "MUST NOT depend only on Flow Label values being uniformly
>>>> distributed" really mean? 
>>>
>>> That's a direct quotation from RFC 6437,
>>
>> Ooops, my bad, I should have checked (but assumed it wasn't a quote from
>> RFC6437).
>>
>>
>>> included here because
>>> it's important. In RFC 6437 there is more explanation:
>>>
>>>    o  Forwarding nodes such as routers and load distributors MUST NOT
>>>       depend only on Flow Label values being uniformly distributed.  In
>>>       any usage such as a hash key for load distribution, the Flow Label
>>>       bits MUST be combined at least with bits from other sources within
>>>       the packet, so as to produce a constant hash value for each flow
>>>       and a suitable distribution of hash values across flows.
>>>       Typically, the other fields used will be some or all components of
>>>       the usual 5-tuple.  In this way, load distribution will still
>>>       occur even if the Flow Label values are poorly distributed.
>>>
>>> It's a precaution against a flow label having a value with very
>>> little entropy (such as zero, or a small integer).
>>
>> mm.. then... should the requirement on the FL setting/geneation be
>> stronger (if needed?) -- i.e., we'd really want that if the FL is set,
>> the middlebox/router doesn't really *need* to get the upper-layer ports,
>> etc.
> 
> You won't find me disagreeing with that.

I mean, the requirement should not only be strong "to set", but also in
the quality of the FL. Such that if it is set, we can rely on it.

Otherwise, a poor FL is not much better than no FL at all...

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





From nobody Wed Feb 17 03:03:35 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 857961B38A3; Wed, 17 Feb 2016 03:03:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-ietf-6man-default-iids-10.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.14.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160217110334.12586.6254.idtracker@ietfa.amsl.com>
Date: Wed, 17 Feb 2016 03:03:34 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/x5MSsR_RJnAo3TdlfZhHJQH1KNE>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Feb 2016 11:03:34 -0000

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

        Title           : Recommendation on Stable IPv6 Interface Identifiers
        Authors         : Fernando Gont
                          Alissa Cooper
                          Dave Thaler
                          Will Liu
	Filename        : draft-ietf-6man-default-iids-10.txt
	Pages           : 22
	Date            : 2016-02-17

Abstract:
   This document changes the default Interface Identifier generation
   scheme for SLAAC to that specified in RFC7217, and recommends against
   embedding link-layer addresses in IPv6 Interface Identifiers.  It
   formally updates RFC2464, RFC2467, RFC2470, RFC2491, RFC2492,
   RFC2497, RFC2590, RFC3146, RFC3572, RFC4291, RFC4338, RFC4391,
   RFC5072, and RFC5121, by removing the text in these RFCs that
   required the IPv6 Interface Identifiers to be derived from the
   underlying link-layer address, and replacing the aforementioned text
   with a pointer to this document.  Additionally, this document updates
   RFC3315 by specifying additional requirements on the generation of
   Interface Identifiers used in Dynamic Host Configuration Protocol
   version 6 (DHCPv6).  It also provides advice to system administrators
   who employ manual configuration.


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

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

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


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

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


From nobody Wed Feb 17 03:09:57 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F33191B38E2 for <ipv6@ietfa.amsl.com>; Wed, 17 Feb 2016 03:09:56 -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] 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 PF_NbPEyiete for <ipv6@ietfa.amsl.com>; Wed, 17 Feb 2016 03:09:54 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DC941B38DF for <ipv6@ietf.org>; Wed, 17 Feb 2016 03:09:54 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id EE54C80DB5; Wed, 17 Feb 2016 12:09:49 +0100 (CET)
Subject: default-iids ready for WGLC? (Re: I-D Action: draft-ietf-6man-default-iids-10.txt)
References: <20160217110334.12586.6254.idtracker@ietfa.amsl.com>
To: "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@tools.ietf.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56C454F3.30003@si6networks.com>
Date: Wed, 17 Feb 2016 08:09:39 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <20160217110334.12586.6254.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/vbkgcc1Gse9CwYk4Co0hbNBv9c0>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Feb 2016 11:09:57 -0000

Folks,

This rev addresses the feedback received on-list, mostly y Alex, Brian,
and Ray.

I personally think that this one should be ready for WGLC.

Thoughts?

Thanks!

Best regards,
Fernando




On 02/17/2016 08:03 AM, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the IPv6 Maintenance of the IETF.
> 
>         Title           : Recommendation on Stable IPv6 Interface Identifiers
>         Authors         : Fernando Gont
>                           Alissa Cooper
>                           Dave Thaler
>                           Will Liu
> 	Filename        : draft-ietf-6man-default-iids-10.txt
> 	Pages           : 22
> 	Date            : 2016-02-17
> 
> Abstract:
>    This document changes the default Interface Identifier generation
>    scheme for SLAAC to that specified in RFC7217, and recommends against
>    embedding link-layer addresses in IPv6 Interface Identifiers.  It
>    formally updates RFC2464, RFC2467, RFC2470, RFC2491, RFC2492,
>    RFC2497, RFC2590, RFC3146, RFC3572, RFC4291, RFC4338, RFC4391,
>    RFC5072, and RFC5121, by removing the text in these RFCs that
>    required the IPv6 Interface Identifiers to be derived from the
>    underlying link-layer address, and replacing the aforementioned text
>    with a pointer to this document.  Additionally, this document updates
>    RFC3315 by specifying additional requirements on the generation of
>    Interface Identifiers used in Dynamic Host Configuration Protocol
>    version 6 (DHCPv6).  It also provides advice to system administrators
>    who employ manual configuration.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-default-iids/
> 
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-6man-default-iids-10
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-default-iids-10
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 


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





From nobody Wed Feb 17 11:11:03 2016
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3149B1A8703 for <ipv6@ietfa.amsl.com>; Wed, 17 Feb 2016 11:11:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YksxmtQhvBuU for <ipv6@ietfa.amsl.com>; Wed, 17 Feb 2016 11:11:00 -0800 (PST)
Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F89D1A3B9D for <ipv6@ietf.org>; Wed, 17 Feb 2016 11:11:00 -0800 (PST)
Received: by mail-pf0-x22f.google.com with SMTP id x65so16261208pfb.1 for <ipv6@ietf.org>; Wed, 17 Feb 2016 11:11:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=Udw0HN61CsWyfswPNDkYlQRZ4IyoDJzlx7rdToCxrsw=; b=stVXD6CFn5mEFaFyoIT1zeHcggvJHE5avAaTtaQy6FVP2rHLRFlY7r7znh9dP/KX92 rj5cEHtaa4pAtCesuUHeh9YI1T3SZyW7stnRCcowTyYqVayThFCptQzgbMXd7PWzvWRs /2YvM/ilXi0HN7o12T6KOUUK3pWpQX/2aBEWGvaKrsYJ2kFaGenjgSEiHrIZbqeWIVWq +izTcV5NWvqERuxDEeKtfXn3AWFJL3tpzx5eDu7ld9rDseoJ9b+KH8gX6IyR7kLSqXmq W6asy5zrj0GjgqdI2EfD+Rcn+26DUtg3qzaL4RviiP3cv3csKXbNFnQDTFPpaPQnSCfO UGPA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=Udw0HN61CsWyfswPNDkYlQRZ4IyoDJzlx7rdToCxrsw=; b=kSq+e3d0/5D9piq8zPZwzTYi2cQ3ca7KjLJtlPN4wNATMuxoB+48HzhIEIVfjMopl/ zOh4tCJ3yy3oWWLKfPEgJoCwrn2liAOSD5Uu8YmH3fGEsRgdXwnBjHZSlpPJaljgW7p+ 8m2VEM5lKqAnHOdYIZyjWhYsnw4YJHnrpPw05Qq/c99CCfoBxyplwgIcjabE6vyn/72f QTdulH+I12jAkgtRdm86vlv+OReLSbpgJXg9QMG/P5FmVhL0SSfq4E1QdVMV2oGcnboQ 7Kpwh028TVa1NGN66C9bfP928tAk/9ZmQz78A7/DDqHH6M/R16WDeaNEaqZwW1mzWOOF KC0Q==
X-Gm-Message-State: AG10YOQj+hKuyfKp1eWyXgN/TN409Mn9wHRs7nEN3UDsP2NYKJUGwziiSCV/W4zYW/0H/w==
X-Received: by 10.98.89.139 with SMTP id k11mr4478891pfj.56.1455736260109; Wed, 17 Feb 2016 11:11:00 -0800 (PST)
Received: from ?IPv6:2406:e007:4de7:1:28cc:dc4c:9703:6781? ([2406:e007:4de7:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id m87sm4471883pfj.38.2016.02.17.11.10.55 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 17 Feb 2016 11:10:58 -0800 (PST)
Subject: Re: default-iids ready for WGLC? (Re: I-D Action: draft-ietf-6man-default-iids-10.txt)
To: Fernando Gont <fgont@si6networks.com>, "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@tools.ietf.org>
References: <20160217110334.12586.6254.idtracker@ietfa.amsl.com> <56C454F3.30003@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <56C4C5C7.4060107@gmail.com>
Date: Thu, 18 Feb 2016 08:11:03 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <56C454F3.30003@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/gqm_mlTg3BDyAi_0ejbdM_cl16Y>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Feb 2016 19:11:02 -0000

Hi Fernando,

On 18/02/2016 00:09, Fernando Gont wrote:
> Folks,
> 
> This rev addresses the feedback received on-list, mostly y Alex, Brian,
> and Ray.
> 
> I personally think that this one should be ready for WGLC.

I agree. As an early WGLC comment, I think that the paragraph starting
"NOTE: [RFC4291]..." and other parts of the text should be adapted to
mention rfc4291bis, but this should be finalised as late as possible, even
during AUTH48 (ideally to report that 4291 is obsolete!).

Regards
   Brian

> 
> Thoughts?
> 
> Thanks!
> 
> Best regards,
> Fernando
> 
> 
> 
> 
> On 02/17/2016 08:03 AM, internet-drafts@ietf.org wrote:
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>> This draft is a work item of the IPv6 Maintenance of the IETF.
>>
>>         Title           : Recommendation on Stable IPv6 Interface Identifiers
>>         Authors         : Fernando Gont
>>                           Alissa Cooper
>>                           Dave Thaler
>>                           Will Liu
>> 	Filename        : draft-ietf-6man-default-iids-10.txt
>> 	Pages           : 22
>> 	Date            : 2016-02-17
>>
>> Abstract:
>>    This document changes the default Interface Identifier generation
>>    scheme for SLAAC to that specified in RFC7217, and recommends against
>>    embedding link-layer addresses in IPv6 Interface Identifiers.  It
>>    formally updates RFC2464, RFC2467, RFC2470, RFC2491, RFC2492,
>>    RFC2497, RFC2590, RFC3146, RFC3572, RFC4291, RFC4338, RFC4391,
>>    RFC5072, and RFC5121, by removing the text in these RFCs that
>>    required the IPv6 Interface Identifiers to be derived from the
>>    underlying link-layer address, and replacing the aforementioned text
>>    with a pointer to this document.  Additionally, this document updates
>>    RFC3315 by specifying additional requirements on the generation of
>>    Interface Identifiers used in Dynamic Host Configuration Protocol
>>    version 6 (DHCPv6).  It also provides advice to system administrators
>>    who employ manual configuration.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-6man-default-iids/
>>
>> There's also a htmlized version available at:
>> https://tools.ietf.org/html/draft-ietf-6man-default-iids-10
>>
>> A diff from the previous version is available at:
>> https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-default-iids-10
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>
> 
> 


From nobody Thu Feb 18 08:48:58 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EE6B1B2B3D; Thu, 18 Feb 2016 08:48:55 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-ietf-6man-multi-homed-host-04.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.14.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160218164855.13745.24857.idtracker@ietfa.amsl.com>
Date: Thu, 18 Feb 2016 08:48:55 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/pRoZq_342hU3aYAM4BID0pBwFN8>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2016 16:48:56 -0000

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

        Title           : Routing packets from hosts in a multi-prefix network
        Authors         : Fred Baker
                          Brian Carpenter
	Filename        : draft-ietf-6man-multi-homed-host-04.txt
	Pages           : 13
	Date            : 2016-02-18

Abstract:
   This document describes expected IPv6 host behavior in a network that
   has more than one prefix, each allocated by an upstream network that
   implements BCP 38 ingress filtering, when the host has multiple
   routers to choose from.  It also applies to other scenarios such as
   the usage of stateful firewalls that effectively act as address-based
   filters.  This host behavior may interact with source address
   selection in a given implementation, but logically follows it.  Given
   that the network or host is, or appears to be, multihomed with
   multiple provider-allocated addresses, that the host has elected to
   use a source address in a given prefix, and that some but not all
   neighboring routers are advertising that prefix in their Router
   Advertisement Prefix Information Options, this document specifies to
   which router a host should present its transmission.  It updates RFC
   4861.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-multi-homed-host/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-6man-multi-homed-host-04

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-multi-homed-host-04


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

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


From nobody Thu Feb 18 11:43:37 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C4FF1B3065; Thu, 18 Feb 2016 11:43:32 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-ietf-6man-ipv6-mibs-obsolete-01.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.14.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160218194332.831.97624.idtracker@ietfa.amsl.com>
Date: Thu, 18 Feb 2016 11:43:32 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ZrYXNS-dJ2yXdjXT3CHspS1A7Sc>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2016 19:43:32 -0000

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

        Title           : Republishing the IPV6-specific MIB modules as obsolete
        Author          : Bill Fenner
	Filename        : draft-ietf-6man-ipv6-mibs-obsolete-01.txt
	Pages           : 64
	Date            : 2016-02-18

Abstract:
   In 2005, the IPv6 MIB update group published updated versions of the
   IP-MIB, UDP-MIB, TCP-MIB and IP-FORWARD-MIB modules, which use the
   InetAddressType/InetAddress construct to handle IPv4 and IPv6 in the
   same table.  This document contains versions of the obsoleted
   IPV6-MIB, IPV6-TC, IPV6-ICMP-MIB, IPV6-TCP-MIB and IPV6-UDP-MIB
   modules, for the purpose of updating MIB module repositories.


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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-6man-ipv6-mibs-obsolete-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-ipv6-mibs-obsolete-01


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

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


From nobody Sat Feb 20 05:58:15 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 826E51AC3C6 for <ipv6@ietfa.amsl.com>; Sat, 20 Feb 2016 05:58:14 -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] 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 rvZqqVj9vHps for <ipv6@ietfa.amsl.com>; Sat, 20 Feb 2016 05:58:12 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0B181A92F2 for <ipv6@ietf.org>; Sat, 20 Feb 2016 05:58:12 -0800 (PST)
Received: from [192.168.2.101] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id C80B480DA8; Sat, 20 Feb 2016 14:58:07 +0100 (CET)
Subject: Re: default-iids ready for WGLC? (Re: I-D Action: draft-ietf-6man-default-iids-10.txt)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "6man-chairs@tools.ietf.org" <6man-chairs@tools.ietf.org>, "draft-ietf-6man-default-iids@tools.ietf.org" <draft-ietf-6man-default-iids@tools.ietf.org>
References: <20160217110334.12586.6254.idtracker@ietfa.amsl.com> <56C454F3.30003@si6networks.com> <56C4C5C7.4060107@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56C870EC.6090709@si6networks.com>
Date: Sat, 20 Feb 2016 10:58:04 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56C4C5C7.4060107@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/-wRAv_XhH3OnMlN_BMvnhfFS_yE>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Feb 2016 13:58:14 -0000

On 02/17/2016 04:11 PM, Brian E Carpenter wrote:
> Hi Fernando,
> 
> On 18/02/2016 00:09, Fernando Gont wrote:
>> Folks,
>>
>> This rev addresses the feedback received on-list, mostly y Alex, Brian,
>> and Ray.
>>
>> I personally think that this one should be ready for WGLC.
> 
> I agree. As an early WGLC comment, I think that the paragraph starting
> "NOTE: [RFC4291]..." and other parts of the text should be adapted to
> mention rfc4291bis, but this should be finalised as late as possible, even
> during AUTH48 (ideally to report that 4291 is obsolete!).

Agreed.

I guess this would be tweaked as:

   NOTE:  [RFC4291] originally defined the "Modified EUI-64 format" for
IIDs.
      Appendix A of [RFC4291] then described how to transform an IEEE
      EUI-64 identifier, or an IEEE 802 48-bit MAC address from which an
      EUI-64 identifier is derived, into an IID in the Modified EUI-64
      format.

      [rfc4291bis] simply documents "Modified EUI-64 format", but
      references this document for IID generation.

?

Thanks!

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





From nobody Mon Feb 22 10:32:56 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F28C1B354E; Mon, 22 Feb 2016 10:32:52 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-ietf-6man-multi-homed-host-05.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.14.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160222183252.21102.35271.idtracker@ietfa.amsl.com>
Date: Mon, 22 Feb 2016 10:32:52 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/tVkgNJAt_0RPFFo5P24YnuxVFds>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2016 18:32:52 -0000

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

        Title           : Routing packets from hosts in a multi-prefix network
        Authors         : Fred Baker
                          Brian Carpenter
	Filename        : draft-ietf-6man-multi-homed-host-05.txt
	Pages           : 13
	Date            : 2016-02-22

Abstract:
   This document describes expected IPv6 host behavior in a network that
   has more than one prefix, each allocated by an upstream network that
   implements BCP 38 ingress filtering, when the host has multiple
   routers to choose from.  It also applies to other scenarios such as
   the usage of stateful firewalls that effectively act as address-based
   filters.  This host behavior may interact with source address
   selection in a given implementation, but logically follows it.  Given
   that the network or host is, or appears to be, multihomed with
   multiple provider-allocated addresses, that the host has elected to
   use a source address in a given prefix, and that some but not all
   neighboring routers are advertising that prefix in their Router
   Advertisement Prefix Information Options, this document specifies to
   which router a host should present its transmission.  It updates RFC
   4861.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-multi-homed-host/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-6man-multi-homed-host-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-multi-homed-host-05


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

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


From nobody Mon Feb 22 10:55:33 2016
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 670391B3738; Mon, 22 Feb 2016 10:55:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Subject: I-D Action: draft-ietf-6man-multi-homed-host-06.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.14.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160222185530.5662.71093.idtracker@ietfa.amsl.com>
Date: Mon, 22 Feb 2016 10:55:30 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/zf5TADT_jo38F4jdZdYEsqdljxE>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Feb 2016 18:55:30 -0000

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

        Title           : Routing packets from hosts in a multi-prefix network
        Authors         : Fred Baker
                          Brian Carpenter
	Filename        : draft-ietf-6man-multi-homed-host-06.txt
	Pages           : 13
	Date            : 2016-02-22

Abstract:
   This document describes expected IPv6 host behavior in a network that
   has more than one prefix, each allocated by an upstream network that
   implements BCP 38 ingress filtering, when the host has multiple
   routers to choose from.  It also applies to other scenarios such as
   the usage of stateful firewalls that effectively act as address-based
   filters.  This host behavior may interact with source address
   selection in a given implementation, but logically follows it.  Given
   that the network or host is, or appears to be, multihomed with
   multiple provider-allocated addresses, that the host has elected to
   use a source address in a given prefix, and that some but not all
   neighboring routers are advertising that prefix in their Router
   Advertisement Prefix Information Options, this document specifies to
   which router a host should present its transmission.  It updates RFC
   4861.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-multi-homed-host/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-6man-multi-homed-host-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-6man-multi-homed-host-06


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

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


From nobody Mon Feb 22 18:59:05 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31FA41B3C5C for <ipv6@ietfa.amsl.com>; Mon, 22 Feb 2016 18:59:03 -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] 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 zK9ZpKPR3vLi for <ipv6@ietfa.amsl.com>; Mon, 22 Feb 2016 18:59:01 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A0CF1B3B27 for <ipv6@ietf.org>; Mon, 22 Feb 2016 18:59:01 -0800 (PST)
Received: from [192.168.3.107] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 3CD4E80DB9; Tue, 23 Feb 2016 03:58:48 +0100 (CET)
Subject: Reviewers needed (Re: 6MAN Working group last call: draft-ietf-6man-rdnss-rfc6106bis)
To: otroan@employees.org, 6man WG <ipv6@ietf.org>
References: <6AC58C26-01B6-4C16-851F-0C1228CDD2AF@employees.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56CBCAD4.9060407@si6networks.com>
Date: Mon, 22 Feb 2016 23:58:28 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <6AC58C26-01B6-4C16-851F-0C1228CDD2AF@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/Jhdv1RcyZSR3W9IVav5VF06cSYA>
Cc: bob.hinden@gmail.com
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Feb 2016 02:59:03 -0000

Folks,

I'm shepherding this document, and so far there have been no comments or
reviews during the (on-going) WGLC.

If possible, please:

1) Send your comments as indicated by the 6man chairs (see below).

2) It would be great if two folks could volunteer for a detailed review.

Thanks!
Fernando




On 02/09/2016 06:54 AM, otroan@employees.org wrote:
> This message starts a two week 6MAN Working Group Last Call on
> advancing:
> 
> Title    : IPv6 Router Advertisement Options for DNS Configuration 
> Authors  : J. Jeong, S. Park, L. Beloeil, S. Madanapalli Filename :
> draft-ietf-6man-rdnss-rfc6106bis-06 Pages    : 17 Date     :
> 2015-10-09
> 
> https://tools.ietf.org/html/draft-ietf-6man-rdnss-rfc6106bis-06
> 
> as a Proposed Standard.  Substantive comments and statements of
> support for publishing this document should be directed to the
> mailing list.  Editorial suggestions can be sent to the authors.
> This last call will end on 23 February 2016.
> 
> We would like this document to follow the experimental document
> shepherd procedure. We will need a volunteer document shepherd,
> before we can advance this document.
> 
> Best regards, Ole & Bob
> 
> 
> 
> -------------------------------------------------------------------- 
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6 
> --------------------------------------------------------------------
> 


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





From nobody Tue Feb 23 17:34:31 2016
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E79E61B415D for <ipv6@ietfa.amsl.com>; Tue, 23 Feb 2016 17:34:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.309
X-Spam-Level: 
X-Spam-Status: No, score=-0.309 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, 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 cEAU_OCo50Ep for <ipv6@ietfa.amsl.com>; Tue, 23 Feb 2016 17:34:28 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [IPv6:2001:67c:27e4::14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDC7C1B40B2 for <6man@ietf.org>; Tue, 23 Feb 2016 17:34:27 -0800 (PST)
Received: from [192.168.2.101] (unknown [181.165.125.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id B5BAE8068B; Wed, 24 Feb 2016 02:34:17 +0100 (CET)
To: "6man@ietf.org" <6man@ietf.org>
From: Fernando Gont <fgont@si6networks.com>
Subject: Review of draft-ietf-6man-rdnss-rfc6106bis-06
X-Enigmail-Draft-Status: N1110
Message-ID: <56CCD714.5070403@si6networks.com>
Date: Tue, 23 Feb 2016 19:03:00 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/sZE3ktm0h_QF9vu3kFzb2KOjJpA>
Cc: draft-ietf-6man-rdnss-rfc6106bis@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2016 01:34:30 -0000

Folks,

Below you'll find a detailed review of this document. (I would be great
if, besides the authors, other folks could comment on the technical
issues raised below)


** Technical **

* Section 1, page 3:
> Most Internet services are
>    identified by using a DNS name.  The two RA options defined in this
>    document provide the DNS information needed for an IPv6 host to reach
>    Internet services.

I'd not use the term "services" here, but rather use "names" in the
first instance, and possible "servers" in the second one.


* Section 1, page 3:
> For instance, locally defined name
>    spaces would not be available to the host if it were to run its own
>    name server software directly connected to the global DNS.

s/name server software/recursive name server/?


* Section 1, page 3:
>  The DNS information can also be provided through DHCP [RFC3315]
> [RFC3736][RFC3646].

s/DHCP/DHCPv6/


* Section 3, page 4:
> 
>    o  Recursive DNS Server (RDNSS): Server that provides a recursive DNS
>       resolution service for translating domain names into IP addresses
>       as defined in [RFC1034] and [RFC1035].

Not sure if you should augment this definition, as e.g. resolving PTR
records is not about "mapping names into IP addresses".


* Section 3, page 5:
> 
>    o  DNS Repository: Two data structures for managing DNS Configuration
>       Information in the IPv6 protocol stack in addition to Neighbor
>       Cache and Destination Cache for Neighbor Discovery [RFC4861].  The
>       first data structure is the DNS Server List for RDNSS addresses
>       and the second is the DNS Search List for DNS search domain names.

Maybe call this structure "Recursive DNS Server List" instead?


* Section 3, page 5:
> 
>    o  DNS Repository: Two data structures for managing DNS Configuration
>       Information in the IPv6 protocol stack in addition to Neighbor
>       Cache and Destination Cache for Neighbor Discovery [RFC4861].  The
>       first data structure is the DNS Server List for RDNSS addresses
>       and the second is the DNS Search List for DNS search domain names.
> 
>    o  Resolver Repository: Configuration repository with RDNSS addresses
>       and a DNS Search List that a DNS resolver on the host uses for DNS
>       name resolution; for example, the Unix resolver file (i.e., /etc/
>       resolv.conf) and Windows registry.


The difference between these two is not clear. Is the only difference
that the later is maintained in persistent storage, or what?


* Section 4, page 5:
> 
>    This document standardizes the ND option called the RDNSS option
>    defined in [RFC5006] that contains the addresses of recursive DNS
>    servers.

This text is confusing. Advice: Do not mention RFC5006 other than in the
intro.


* Section 4, page 5:
>  The
>    RA options for RDNSS and DNSSL can be used on any network that
>    supports the use of ND.

mmm... isn't ND mandatory, anyway?


* Section 5.3.1, page 8:
>    o  The validity of DNS options is checked with the Length field; that
>       is, the value of the Length field in the RDNSS option is greater
>       than or equal to the minimum value (3), and the value of the
>       Length field in the DNSSL option is greater than or equal to the
>       minimum value (2).

The RDNSS option should have an additional validation check:
(Length -1) % 2 == 0

Additionally, you should validate the addresses: e.g., they should be
unicast addresses.



* Section 5.3.1, page 9:
> Unless explicitly specified for
>    the discovery mechanism, the exact number of addresses and domain
>    names to keep is a matter of local policy and implementation choice.

Are you referring to some local configuration option, or something else?


* Section 5.3.1, page 9:
> However, the ability to store at least three RDNSS addresses (or
>    DNSSL domain names) from at least two different sources is
>    RECOMMENDED.

If there are two sources, this would mean e.g., a total of 6 addresses?
Or a total of three?


* Section 5.3.2, page 9:
> Therefore,
>    the network administrator needs to configure DNS options in multiple
>    sources in order to prevent such problems from happening.

As per draft-ietf-v6ops-dhcpv6-slaac-problem, this may not be enough.


* Section 5.3.2, page 9:
> Therefore,
>    the network administrator needs to configure DNS options in multiple
>    sources in order to prevent such problems from happening.

You mean configure *the same* info in all sources, or something else?
(it's not clear)


* Section 5.3.2, page 9:
> 
>    Second, if different DNS information is provided on different network
>    interfaces, this can lead to inconsistent behavior.  The IETF is
>    working on solving this problem for both DNS and other information
>    obtained by multiple interfaces [MIF-PROBLEM][MIF-PRACTICE].

Without checking [MIF-PROBLEM][MIF-PRACTICE], how about mitigating this
issue a bit by maintaining per-interface configuration -- e.g., if you
receive DNS information in each of your interfaces, you keep such info
on a per-interface basis rather than on a global/system-wide basis.


* Section 6, pages 9-10
>    For the
>    synchronization, an implementation where ND works in the kernel
>    should provide a write operation for updating DNS information from
>    the kernel to the Resolver Repository.

Why not just have a lib/syscall that allows you to read it from
userspace, rather than have the kernel write to userspace?


* Section 6.1, page 10:
>    o  DNSSL domain name for DNS Search List: DNS suffix domain names,
>       which are used to perform DNS query searches for short,
>       unqualified domain names in the network advertising the DNSSL
>       option.

What if you receive the RDNSS on one interface, and the DNSSL on
another? -- put another way, not sure what you mean by "in the network
advertising the DNSSL option"


* Section 7.1, page 13:
> Therefore, the vulnerability
>    of ND is not worse and is a subset of the attacks that any node
>    attached to a LAN can do independently of ND.

Not sure what you mean by "...independently of ND".



* Section 7.2, page 14:
Here you're making recommendations with RFC2119. I recommend you don't.

One one hand, SEND is extremely hard to deploy (if at all possible). A
number of popular OSes don't support it, it requires a PKI, etc., etc.

Besides, all these are operational mitigations, and your document is a
Std Track document.

So my recommendation would be: discuss possible mitigations, reference
the appropriate RFCs, but do not make any RFC2119 recommendations about
this.




** Editorial **

* Section 1, page 3:
>    The purpose of this document is to standardize an IPv6 Router
>    Advertisement (RA) option for DNS Recursive Server Addresses used for
>    the DNS name resolution in IPv6 hosts.  This RA option was originally
>    specified in an earlier Experimental specification [RFC5006]. 

You should note that it was later published as Std Track in RFC6106 --
this is not explicitly noted otherwise.


* Section 1, page 3:
>    Neighbor Discovery (ND) for IP version 6 and IPv6 stateless address
>    autoconfiguration 

Please capitalize SLAAC  -- each word, and then add the acronymn.


* Section 1.2, page 4:
> 
>    Two protocols exist to configure the DNS information on a host, the
>    Router Advertisement options described in this document and the
>    DHCPv6 options described in [RFC3646].

s/described/specified/


* Section 3, page 4:
>    This document uses the terminology described in [RFC4861] and
>    [RFC4862].  In addition, four new terms are defined below:

s/described/defined/


* Section 6.1, page 10:
> When Expiration-time becomes less than the current system
>       time, this entry is regarded as expired.

Probably just me being pedantic, but I'd phrase it as "when the current
time becomes larger than..." (it's the current time that changes, rather
than the expiration time).


* Appendix A, page 17:

Please remove this appendix. Such changelog is in 6106, already.


* Appendix B, page 18:
> 
>    o  The lifetimes of RDNSS and DNSSL options are decoupled from Router
>       Lifetime.  An RA router lifetime of zero does not cause the RDNSS
>       and DNSSL options to be considered invalid because these options
>       have their own lifetime values.  Thus, due to the expiry of the RA
>       router lifetime, the lists in the RDNSS and DNSSL options are not
>       guaranteed to be reachable at any point in time.

While you have removed the corresponding text, I think this deserves a
clarification in the body of the document. i.e., clarify that the DNS
info need not be dropped if [..].

Thanks!

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





From nobody Wed Feb 24 11:27:20 2016
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37CD81B3C8C for <ipv6@ietfa.amsl.com>; Wed, 24 Feb 2016 11:27:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xpJQarufbD_7 for <ipv6@ietfa.amsl.com>; Wed, 24 Feb 2016 11:27:16 -0800 (PST)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1939A1ACD49 for <ipv6@ietf.org>; Wed, 24 Feb 2016 11:27:16 -0800 (PST)
Received: by mail-io0-x22d.google.com with SMTP id l127so60640815iof.3 for <ipv6@ietf.org>; Wed, 24 Feb 2016 11:27:16 -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=JsS7HZYpj/kF0z0rdfZnzVwfQLOTHbYnYNkfGvPuUVU=; b=K8I1Ux9ZIwtu3VmY3w5Q0GQM/SdJL2eS8/NvEfn1qsi5HnSKgam87Sd59hYa18sOWC lqiV1NIpvCmD39OzXAmZaIVUd1LB4InqC+H21yDQKeUyGLdWOLCzCcjkjfD1sXr0MqIp QCc95w4Pw6wIGLS355duH9yArKcnf6nqfULQbbfacBCzjK6Czc61pX6brtm9gMf1OtSW Fe3j93lWGRv3zFv6Ci8CyBTa0Y47TzgoqdeQl6FGhyxonFwQtE2r9Ait6y0uZI6xJ9xC ZVGsMiMjAnSBjts5yibjogPGpmRCNIYH/lc7DVykN8/9FDlDu7MbvDQ6RcE6+IP8S26D k6Fg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=JsS7HZYpj/kF0z0rdfZnzVwfQLOTHbYnYNkfGvPuUVU=; b=EpOrAAYl9SuEo1PhrjRf1d5mnTAW+3jmB8B3H4kHmaQPJNAh4QFMVN/jzJI57KemLd orSz3PlbR0o4J1s7wtdcxgFSpNmwVe21bL/54fW6C3IZwbvbTP6tGDr35amqIKr45wYz 8/jq2KMssCGTJ1QSl0+5Lt1NCJN7m6aJfTNeOL/bYFMkYZ7kVJkAuf/ClxESDeLvCV17 frguBIZJX+7AVO/iMDWqLzrzbwXFalDqbRrUGvnsU09jupPtBhPhJdn9hMwTWKyhp/90 whaYUFno52g0ieniQjElMdMU8vez4kXW7RiUpQB7KOkObwP1dYxoirdinAfQP02ZeGGn t/ow==
X-Gm-Message-State: AG10YOTiLuR38evstR7+W62LZlMEMYfOnDJ0cg0r5LbavPFoGMoMvv4pzL6WzG22ef4kkQ/Wh1D9/JtXkDFK1g==
MIME-Version: 1.0
X-Received: by 10.107.198.197 with SMTP id w188mr38094062iof.178.1456342035340;  Wed, 24 Feb 2016 11:27:15 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.169.35 with HTTP; Wed, 24 Feb 2016 11:27:15 -0800 (PST)
In-Reply-To: <6AC58C26-01B6-4C16-851F-0C1228CDD2AF@employees.org>
References: <6AC58C26-01B6-4C16-851F-0C1228CDD2AF@employees.org>
Date: Wed, 24 Feb 2016 11:27:15 -0800
X-Google-Sender-Auth: lXlFTvuajCZu_AM2zCMq6qcU4mI
Message-ID: <CAJE_bqfvE0jGoRi2X=ohpqsXmGx9AVKnjeGH-P8zWp6=3_kbVA@mail.gmail.com>
Subject: Re: 6MAN Working group last call: draft-ietf-6man-rdnss-rfc6106bis
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ONd704zGa8tIx8fGnQZNd6V9Vbg>
Cc: Bob Hinden <bob.hinden@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2016 19:27:18 -0000

At Tue, 9 Feb 2016 10:54:16 +0100,
otroan@employees.org wrote:

> This message starts a two week 6MAN Working Group Last Call on advancing:
>
>      Title    : IPv6 Router Advertisement Options for DNS Configuration
>      Authors  : J. Jeong, S. Park, L. Beloeil, S. Madanapalli
>      Filename : draft-ietf-6man-rdnss-rfc6106bis-06
>      Pages    : 17
>      Date     : 2015-10-09
>
>     https://tools.ietf.org/html/draft-ietf-6man-rdnss-rfc6106bis-06
>
> as a Proposed Standard.  Substantive comments and statements of
> support for publishing this document should be directed to the
> mailing list.  Editorial suggestions can be sent to the authors.
> This last call will end on 23 February 2016.

I've reviewed the 06 version.  I don't have a particular opinion on
whether to publish it, but I have some comments:

- Section 5

   The IPv6 DNS configuration mechanism in this document needs two new
   ND options in Neighbor Discovery: (i) the Recursive DNS Server
   (RDNSS) option and (ii) the DNS Search List (DNSSL) option.

  "new" sounds like awkward since, well, it's not new any more.  I
  don't know the usual practice (if any) in cases like this for "-bis"
  specifications, but I'd suggest just removing "new".

- Section 5.1

     Lifetime      32-bit unsigned integer.  The maximum time, in
                   seconds (relative to the time the packet is sent),
                   over which this RDNSS address MAY be used for name
                   resolution.

  Shouldn't "relative to the time the packet is sent" actually be
  "relative to the time the packet is received"?  In practice these
  two wouldn't be different very much anyway, but, technically, the
  former looks awkward to me since the recipient can't know that time.

- Section 5.1

   Note:  [...]  The link zone indices SHOULD be
      represented in the textual format for scoped addresses as
      described in [RFC4007].

  Perhaps the actual intent is "The link-local addresses SHOULD be
  represented with their link zone indices in the textual format for
  scoped addresses as described in [RFC4007]."?  Also, it's not very
  clear to me why it's a "SHOULD".  Maybe because it's convenient as
  the DNS client (stub resolver) implementation can simply pass the
  textual text (whether it's link-local or not) to a utility function
  like getaddrinfo()?  If so, that's understandable, but I guess it's
  not obvious and should be explained explicitly.  Also, I'm not sure
  if this convenience (if that's the reason for the SHOULD) is worth
  the RFC2119 keyword.  While it'd certainly be convenient, this seems
  to be a pure implementation choice.

- Section 5.2: s/name/names/

     Lifetime      32-bit unsigned integer.  The maximum time, in
                   [...]
                   (0xffffffff) represents infinity.  A value of zero
                   means that the DNSSL domain name MUST no longer be
                   used.

- Section 5.2

     Domain Names of DNS Search List
                   One or more domain names of DNS Search List that MUST
                   be encoded using the technique described in Section
                   3.1 of [RFC1035].

  The word "technique" sounds awkward to me as it's the standard wire
  format of domain names.  I suggest, e.g., just saying "...encoded as
  described in Section 3.1 of [RFC1035]".

- Section 6

   In environments where the DNS information is stored in user space and
   ND runs in the kernel, it is necessary to synchronize the DNS
   information (i.e., RDNSS addresses and DNS search domain names) in
   kernel space and the Resolver Repository in user space.  For the
   synchronization, an implementation where ND works in the kernel
   should provide a write operation for updating DNS information from
   the kernel to the Resolver Repository.  One simple approach is to
   have a daemon (or a program that is called at defined intervals) that
   keeps monitoring the Lifetimes of RDNSS addresses and DNS search
   domain names all the time.  [...]

  This seems to assume that "ND runs in the kernel" means that all
  information in RAs is managed in the kernel.  I don't know if
  there's such an implementation (does Linux work that way?), but it
  doesn't necessarily have to be so, and is actually different from
  the BSD implementation: the FreeBSD's rtsol(d) completely works as a
  user space application, receives RA via an ICMPv6 socket using the
  standard advanced socket API (RFC3542), and manages RDNSS
  implementation independently from the kernel (even if some other
  parts of the RA are managed in the kernel).  So, I'd at least
  suggest clarifying that this kind of approach is only necessary for
  some deviant protocol stack implementation that doesn't even support
  RFC3542.  And, I'd also mention the FreeBSD-style approach as it
  should be more generic and portable.

- Section 6.3: this section largely repeats the text of Section 6.2
  and looks redundant to me.  I'd consider unifying these two sections
  and eliminate unnecessary duplicates.

- Section 6.3: on a related point, this text looks awkward:

      Step (b): For each DNSSL domain name, check the following: [...]
      [...] for certain reasons in network management,
      e.g., the termination of the RDNSS or a renaming situation.  That
      is, the RDNSS can resign from its DNS service because the machine
      running the RDNSS is out of service intentionally or
      unintentionally.  Also, under the renaming situation, the DNSSL

  How can the termination of a particular RDNSS mean that DNSSL names
  are not usable anymore?  There may be a case where one event is
  realted to the other, but I don't see any obvious relationship
  between these two (the RDNSS may simply be replaced with a new,
  different node).  This text rather seems to be a result of a naive
  copy of Section 6.2.

- Section 7.1, second paragraph.  Most of the text in this paragraph
  is irrelevant to this protocol and looks redundant to me.  I'd
  consider just referring to some other document for the general
  issue.

- Section 7.2

   The Secure Neighbor Discovery (SEND) protocol [RFC3971] is used as a
   security mechanism for ND.  It is RECOMMENDED that ND use SEND to
   allow all the ND options including the RDNSS and DNSSL options to be
   automatically included in the signatures.

  I don't think this "RECOMMENDED" is realistic.  As a matter of fact,
  SEND isn't even widely implemented, and, IMO, its deployability
  issues are not easily resolved.  I don't have a specific suggestion
  on how to make the whole text realistic, but I'd at least suggest
  stopping to make such an unrealistic requirement, especially with an
  RFC2119 keyword.

--
JINMEI, Tatuya


From nobody Thu Feb 25 05:52:51 2016
Return-Path: <leo.liubing@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C4B21ACD2A for <ipv6@ietfa.amsl.com>; Thu, 25 Feb 2016 05:52:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.207
X-Spam-Level: 
X-Spam-Status: No, score=-4.207 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.006, 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 agW9Zw0059_A for <ipv6@ietfa.amsl.com>; Thu, 25 Feb 2016 05:52:46 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D66FA1ACCF4 for <ipv6@ietf.org>; Thu, 25 Feb 2016 05:52:45 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CEZ53448; Thu, 25 Feb 2016 13:52:43 +0000 (GMT)
Received: from LHREML702-CAH.china.huawei.com (10.201.5.99) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 25 Feb 2016 13:52:42 +0000
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml702-cah.china.huawei.com (10.201.5.99) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 25 Feb 2016 13:52:42 +0000
Received: from NKGEML514-MBX.china.huawei.com ([fe80::40a8:f0d:c0f3:2ca5]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Thu, 25 Feb 2016 21:52:36 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: 6man WG <ipv6@ietf.org>
Subject: RE: 6MAN Working group last call: draft-ietf-6man-rdnss-rfc6106bis
Thread-Topic: 6MAN Working group last call: draft-ietf-6man-rdnss-rfc6106bis
Thread-Index: AQHRYx/yRdOWBf4QjE+ptXFcAQPGr588xQHw
Date: Thu, 25 Feb 2016 13:52:35 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F45C2D4692E@nkgeml514-mbx.china.huawei.com>
References: <6AC58C26-01B6-4C16-851F-0C1228CDD2AF@employees.org>
In-Reply-To: <6AC58C26-01B6-4C16-851F-0C1228CDD2AF@employees.org>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.117]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090201.56CF072B.017B, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 5003a8c85842b010ebd8d0f58d760383
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/ZVsdbKf2rcvVGH2d2f9aw6cc3K8>
Cc: "draft-ietf-6man-rdnss-rfc6106bis@tools.ietf.org" <draft-ietf-6man-rdnss-rfc6106bis@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Feb 2016 13:52:49 -0000

Hi Dear authors,

I've read the draft. It was my first time to read it, so please pardon me i=
f I iterated some questions that had been addressed before.

1. Since RFC5006 was already obsolete by RFC6106, and this document is goin=
g to obsolete 6106, I guess this draft should not necessary to mention 5006=
 anymore?
When the document says it defines a "new" option (DNSSL), it is still compa=
ring to 5006. But it is not "new" comparing to 6106. So this is a bit confu=
sing for me.
So I'd suggest the whole text be tweaked in the perspective of obsolete RFC=
6106, not just iterate it.

2. Section 1.1, page3
"  Furthermore,
   the host learns this DNS configuration from the same RA message that
   provides configuration information for the link, thereby avoiding
   also running DHCPv6."
Do you mean the host decides not to initial DHCPv6?
I think "avoiding also running DHCPv6" should not be a principle from hosts=
' perspective. That should come from the administrator's deployment plan.

3. Section 5.3.2
" Second, if different DNS information is provided on different network
   interfaces, this can lead to inconsistent behavior.  The IETF is
   working on solving this problem for both DNS and other information
   obtained by multiple interfaces [MIF-PROBLEM][MIF-PRACTICE]. "

Regarding MIF problems, I think it's nice to mention RFC6731 here, which is=
 the solution for DNSS selection.
Btw, the [MIF-PROBLEM][MIF-PRACTICE] are already RFC6418 and RFC6419.

4. Section 7.2
"It is RECOMMENDED that ND use SEND to
   allow all the ND options including the RDNSS and DNSSL options to be
   automatically included in the signatures."
I think recommending SEND is not very specific to this document. We should =
have more considerations whether to use SEND, not only in term of protectin=
g RDNSS/DNSSL options.

5. Section 1.1, page 3
"However, when in many networks some additional information needs to be dis=
tributed, those networks are likely to employ DHCPv6."
This sentence reads a bit odd. I guess you intended to mean like this:
" However, for networks that need to distribute additional information, DHC=
Pv6 is likely to be employed."

Best regards,
Bing

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of
> otroan@employees.org
> Sent: Tuesday, February 09, 2016 5:54 PM
> To: 6man WG
> Cc: bob.hinden@gmail.com
> Subject: 6MAN Working group last call: draft-ietf-6man-rdnss-rfc6106bis
>=20
> This message starts a two week 6MAN Working Group Last Call on
> advancing:
>=20
>      Title    : IPv6 Router Advertisement Options for DNS Configuration
>      Authors  : J. Jeong, S. Park, L. Beloeil, S. Madanapalli
>      Filename : draft-ietf-6man-rdnss-rfc6106bis-06
>      Pages    : 17
>      Date     : 2015-10-09
>=20
>     https://tools.ietf.org/html/draft-ietf-6man-rdnss-rfc6106bis-06
>=20
> as a Proposed Standard.  Substantive comments and statements of support
> for publishing this document should be directed to the mailing list.  Edi=
torial
> suggestions can be sent to the authors.  This last call will end on 23
> February 2016.
>=20
> We would like this document to follow the experimental document shepherd
> procedure. We will need a volunteer document shepherd, before we can
> advance this document.
>=20
> Best regards,
> Ole & Bob


From nobody Thu Feb 25 10:43:50 2016
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B37EC1B30FA for <ipv6@ietfa.amsl.com>; Thu, 25 Feb 2016 10:43:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9vCjvMMO4jNJ for <ipv6@ietfa.amsl.com>; Thu, 25 Feb 2016 10:43:47 -0800 (PST)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDBB41B30F8 for <6man@ietf.org>; Thu, 25 Feb 2016 10:43:46 -0800 (PST)
Received: by mail-io0-x22b.google.com with SMTP id l127so97683075iof.3 for <6man@ietf.org>; Thu, 25 Feb 2016 10:43:46 -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; bh=P8U2PyyYvHgHlFOThJIGNkQ1/SUWKoC2n7QnQUC07TU=; b=ExKYwHXoocVI3VElw3MhvMSukFlwpZDna/1FUoPAcnGaNe+cKJQGyXMjtweCT2NnJS B7GW3dKTNP/ly5xKNC62KjY1yCtxpKO2xuFhBQr+3Ml5DNKoCn5yiw7e0k0cVsWaUBes 68jJqXRkk3zNCh5iCLbugVX9XPkZF/OvwLPK1FRTaxZU4d7kAb+xRXGJasFZyzucc7n6 Xe+Z0VPk0IA75yMhtVmdLjk+X1Vxu1jrACfjJoz2cvXlkYWGH/MlApTtXpC9hbF8GD8Y a+x7rYZvzdP4qyHGIBezNttkreGtEZPIbIXIxvIQYvzmdrtjNOQDLiXIhuHMo5qMJXNY qY8w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=P8U2PyyYvHgHlFOThJIGNkQ1/SUWKoC2n7QnQUC07TU=; b=EwlnCQB70DXVV72NcIpkgfZee0ekpidJbd/R6+1FI0q2jdC0xgCtxkQmGEUxbq9ciC +IR4sETRiPFGcHG2se8FitM0vdpFIitv4HlZ6wNJUkV1xTNjwG5WFbo4IFv8SgE8EgLQ flPIo7gs2OBreCwV/z1zRkf/6CcrVTpm2orXWCSejF0ft9Yb9f1ukf7q/bAr84n9EeI1 vtWYKPKTGc9ohwLVBdTep3tYu+yPQVBDYf7f74hU/xPrX3AWHQds8TuzNDTfTbTpPIpz xb6SBaSt3MdDNkAgnqATO73nfqOMgPx++ctlRitgO819OBzWMjXSwO1eImH/OW2O4LXY /LkA==
X-Gm-Message-State: AG10YOTOBVqIyCbPuUDEI6fzjAttic73RirgmiTG8czx/L2rhZoMzEo7FHAQzXpZYy1NL4p45Ylgvk1IztbESA==
MIME-Version: 1.0
X-Received: by 10.107.198.197 with SMTP id w188mr4171946iof.178.1456425826325;  Thu, 25 Feb 2016 10:43:46 -0800 (PST)
Sender: jinmei.tatuya@gmail.com
Received: by 10.107.169.35 with HTTP; Thu, 25 Feb 2016 10:43:46 -0800 (PST)
In-Reply-To: <56CCD714.5070403@si6networks.com>
References: <56CCD714.5070403@si6networks.com>
Date: Thu, 25 Feb 2016 10:43:46 -0800
X-Google-Sender-Auth: 7kQ3Y1eJeKQGStRRsGIRxr7rceU
Message-ID: <CAJE_bqcz-LkacRTdU_q2BAFK0q1uN5ZK5YOQAJEf7OBm9zU6MA@mail.gmail.com>
Subject: Re: Review of draft-ietf-6man-rdnss-rfc6106bis-06
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/4RFEOFzyqsMhDwVYciG5ZOo3FMQ>
Cc: "6man@ietf.org" <6man@ietf.org>, draft-ietf-6man-rdnss-rfc6106bis@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Feb 2016 18:43:47 -0000

At Tue, 23 Feb 2016 19:03:00 -0300,
Fernando Gont <fgont@si6networks.com> wrote:

> Below you'll find a detailed review of this document. (I would be great
> if, besides the authors, other folks could comment on the technical
> issues raised below)

Do you have any particular points that you think might need explicit
feedback/comments?  From a very quick read I didn't see anything to
discuss.

--
JINMEI, Tatuya


From nobody Thu Feb 25 16:16:08 2016
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCB331B383C for <ipv6@ietfa.amsl.com>; Thu, 25 Feb 2016 16:16: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 E2XUFZu57OjQ for <ipv6@ietfa.amsl.com>; Thu, 25 Feb 2016 16:16:06 -0800 (PST)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C9501B3837 for <ipv6@ietf.org>; Thu, 25 Feb 2016 16:16:06 -0800 (PST)
Received: by mail-io0-x234.google.com with SMTP id z135so107115215iof.0 for <ipv6@ietf.org>; Thu, 25 Feb 2016 16:16:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:subject:date:message-id:cc:to:mime-version; bh=8+4QkpzBHWQGZOqpej+hfXp8LpXTkSkD6ZaBL3V+xSs=; b=OM8/0xXhTLs3i0ysVwBIsLIKHQjh7P+1xB5+2r9ab3duKfuas/Kwn19YhaGsw8umfn Zcm8w0iuz8aIq0SDcN2LOA3iXd5G3ouCGMiZFy3t+CmV2qAiR0qadhmCMBEhFXjolNog ymPrjbqORQJ5UHutsJPrEtXUPECYXeC41oJWpFl/Hw8VvVimoK6yaOnrToQDPXarUxuW qYxWiEUonX5bCkJMRfWiDRfXLfW4zw6V0KyxS4WWhB8NaYCUN/LEXWq1bkcs6xlofEVF aoJe5c5jEBV6hFer/9TQ3GBRxm7xncQYVzKe6z8cmpsQGU0D0zTpkzlQSiaXZzEEofhA p81A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:subject:date:message-id:cc:to:mime-version; bh=8+4QkpzBHWQGZOqpej+hfXp8LpXTkSkD6ZaBL3V+xSs=; b=KN+r6NuCvPmpONGtVqzIv8mxmMdzMGzme6dfETp5KGOQqYuetPRjt/5bRxXpFY038G PaYZdgqYiEoODJLwZtKmF+SkXS0ikj68TXyyKOHePTzHvKzh0D3AwfjAHk5CJxuk5OzE VTDP46Css+KT3b/Towws8si1WtPrwSp+7z4UHBSHZ4cjGS68J2PeQbErlf72s1DAR6By a2YvdS13XBVAYIr4GnMvmAlOzul7yLfz2v3TjOHJzmRHcPC1C1AqSEyPnHZSOllEVohM +ULadBzCT0BxQS4q6Pg7zC0DgHp8KfK3xsprav4wdb6fvYuNInanv11iZ3cfgfNZks5p n1gw==
X-Gm-Message-State: AG10YORzJyTps2XCuenvR+9rA0FuSBmf+eiapJzYgOo38NMXKx12UKrj8wJXbfokbJccjQ==
X-Received: by 10.107.198.76 with SMTP id w73mr6363517iof.105.1456445765658; Thu, 25 Feb 2016 16:16:05 -0800 (PST)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id wj3sm333027igb.6.2016.02.25.16.16.04 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 25 Feb 2016 16:16:04 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
X-Pgp-Agent: GPGMail 2.5.2
Content-Type: multipart/signed; boundary="Apple-Mail=_5E4036B1-24CA-45B6-A152-70799668A9A3"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: 6MAN IETF95 Call for agenda items
Date: Thu, 25 Feb 2016 16:16:03 -0800
Message-Id: <8A19AEE2-6836-43A4-941B-2AE01363BE55@gmail.com>
To: IPv6 List <ipv6@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
X-Mailer: Apple Mail (2.2104)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/2DSOTVB3P1XFqQ8jShljUoohQNI>
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Feb 2016 00:16:07 -0000

--Apple-Mail=_5E4036B1-24CA-45B6-A152-70799668A9A3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

The 6MAN working group will meet in Buenos Aires at IETF95.

If you have a draft you would like to discuss, please send your request =
for agenda time to the 6man chairs.   Please include in the request, the =
title of the presentation, file name of the draft, the speakers name =
(and email), and how much time you would like.

We will prioritise drafts that are working group items and drafts that =
have been actively discussed on the list.

We expect at least half of each talk=E2=80=99s presentation time to be =
used for open discussion,
please plan your presentation accordingly.

New drafts not discussed on the mailing list prior to the meeting,
or drafts that do not appear to have support from the working group are =
unlikely to get time at the meeting.

Please have agenda items to us by 11 March 2016.

Regards,

Bob & Ole


--Apple-Mail=_5E4036B1-24CA-45B6-A152-70799668A9A3
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

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

iQEcBAEBCgAGBQJWz5lDAAoJEK7rdBF357uoUasH/irvwcrh9r3U+y73yDVG1yNo
tAgLhWXqitEYHWaiggUmYFTg44V16c9t2EeBYPkhjKUzHJeoI6rJGZ6U3lYYZyvj
972ZXhdIuJVDrQx5CSTgdfq/IAeK2O469fthlTdPV/UpmVf5kVCoRHP3g/lpJKS2
hCgLoOtyBCtxWkEwubfkwMdr9WamQxSiAjUQX1yVPJVKUxM1EOZ5MJSJ20ZrUJpH
VM0F8mE7IFfp6rPpknb6997uJK4PK2kWlMHefT/NHbXJvYLwyibYIcStt0ES9jnB
D/qNTEcmjX37PrJeg1q/+2n6Anu4t3RKg4BAgbFlwak7ZOjFP/ZtkhY5QdTX64E=
=qGSv
-----END PGP SIGNATURE-----

--Apple-Mail=_5E4036B1-24CA-45B6-A152-70799668A9A3--

